rb2013
Author of The 6922 Tube Review
- Joined
- Apr 12, 2013
- Posts
- 5,930
- Likes
- 514
To be a bit more precise…
It really isn't that the timing and signal data are separated, but that the ethernet protocol doesn't use the timing info from the data stream itself, rather it uses it's own clock to 're-time' the data itself and ignores the timing from the incoming data stream altogether.
This is then passed along to the digital audio converter (AES, SPDIF, USB Toslink, etc.) which then feeds the dac.
I chose the word separated in my previous post because it was 'easier' to try and explain and to help provide more contrast to these 2 critical aspects.
This method of handling these 2 portions (timing and the data itself) of the data stream, is in contrast to both SPDIF and USB which rely upon the 'embedded' timing of the data stream itself, which is a major source of additional jitter among other variables and are problematic.
And if the output of this data stream (from the ethernet data path) is passed along using either AES or I2s, then the data and timing info remain separate as they are used by the dac.
These 2 protocols (SPDIF & USB) are the 'consumer' versions of the method of passing the audio data to the dac, where as AES is a 'pro audio' (meaning more robust) and I2s is a variant of HDMI (or is it visa versa?) which has not been formalized into a set structure (pinout and signal definitions) that all who use it agree upon.
I2s is potentially 'better' but really is best for use with short cable runs and is mostly an internal digital signal pathway to the main digital signal bus.
Ok some other things that make AOIP different from USB 2.0 Async - that is error correction - AOIP is packetized as is USB - but with a robust two way error correction protocol. Something USB 1.0, 2.0 and 3.0 have - but was changed in the USB 2.0 Audio - maybe why MS never supported it?
So SPDIF and AES - are very different then USB audio - in so many ways wouldn't use them in the same context.
As for SPDIF and AES - they are base on the same underlying protocol - and have many of the same limitations:
S/PDIF was developed at the same time as the main standard, AES3, used to interconnect professional audio equipment in the professional audio field. This resulted from the desire of the various standards committees to have at least sufficient similarities between the two interfaces to allow the use of the same, or very similar, designs for interfacing ICs.[4] S/PDIF remained almost identical at the protocol level,[a]but changed the physical connectors from XLR to either electrical coaxial cable (with RCA connectors) or optical fibre (TOSLINK; i.e., F05 or EIAJ Optical), both of which cost less than the XLR connection. The RCA connectors are typically colour-coded orange to differentiate from other RCA connector uses such as composite video. The cable was also changed from 110 Ω balanced twisted pair to 75 Ω coaxial cable, using RCA jacks.
AOIP operates using RTP and is Level 3 compliant - that means is requires no special LAN switches to work - at least in theory.
An example, if a Audinate brooklyn card (or similar) were located inside a dac and fed an ethernet signal and it's output fed the dac via I2s, it could be the ideal means to get the digital signal from the source (computer) directly to the dac with minimal signal processing in between.
And assuming the word clock in the dac was 'good enough' (or could be externally supplied) this would be a single solution dac instead of several digital boxes between the source and the dac itself.
JJ
I guess you haven't been following this thread much. It's not an IF but a reality. Need to bone up my friend.