11–20 of 25 posts
Very nice! Can you link some resources regarding how to implement AES67? What kind of latencies are you able to achieve?
FWIW, there's a resources page with a number of links that match your inquiry: https://aes67.app/resources Unfortunately the standard itself you have to buy. It's 50 USD for non-AES-members. https://www.aes.org/publications/standards/
Earlier quoted context omitted.
This is LAN audio streaming right? Like the kind of thing you'd use at a venue. Not internet radio.
Yeah if you want real security use AES256 instead ...
Somewhat related trying to find software that can record whatever source I am sending to my speakers, like virtual audio driver. Any ideas ?
Earlier quoted context omitted.
FWIW, there's a resources page with a number of links that match your inquiry: https://aes67.app/resources Unfortunately the standard itself you have to buy. It's 50 USD for non-AES-members. https://www.aes.org/publications/standards/
Yes, that's the reason I was asking :( A number of projects implement it, but I'm not an AES member and didn't feel like spending the 50USD for the official specs. I was hoping someone had made a writeup of the overall protocol.
As most (all?) PC audio devices don't support clock drifting the audio clock to the PTP clock, this application will either resample fractionally or click now and then. So not AES67 in the true sense.
Earlier quoted context omitted.
Yes, that's the reason I was asking :( A number of projects implement it, but I'm not an AES member and didn't feel like spending the 50USD for the official specs. I was hoping someone had made a writeup of the overall protocol.
RTP PCM packets timed to a Precision Time Protocol clock. As most (all?) PC audio devices don't support clock drifting the audio clock to the PTP clock, this application will either resample fractionally or click now and then. So not AES67 in the true sense.