Serge_S Posted June 7, 2015 Share Posted June 7, 2015 The industrial approach is IEEE 1588 PTP: I got impression that for regular streaming with Ravenna the network sync is not important. One would only have a single Ravenna-enabled device(D/A). Serge Link to comment
jabbr Posted June 7, 2015 Share Posted June 7, 2015 Oh, I thought the Word Clock would match the sampling frequency to keep up somehow. Hmm a 44.1kHz needs then several iterations to say sync with a 96KHz pulse train, that alone is difficult, can see that. Or you have one super clock that does say 10MHZ, then gear down to whatever sampling frequency is going with the transmission, another tough ask. I gather no one transmits at 10MHz MCLK across Ethernet? Well you could but Ethernet is a packet protocol so "realtime" streaming is an illusion -- an illusion that can be done very well when done correctly -- but nonetheless. With clocks you are better off using a good one on the device that receives the Ethernet (or USB) and converts to I2S etc Custom room treatments for headphone users. Link to comment
Albrecht Posted May 3, 2016 Share Posted May 3, 2016 Just a small comment about the Ravenna being UDP multicast or unicast based. This also means that any packet loss will not be remedied, i.e. there is no re-transmission due to e.g. network congestion as you find with TCP. That is a really good point, and i wonder what the "real world" implication is here with drop outs. But, I don't know how much RTP differs from UDP. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now