TCP/IP as a replacement for S/PDIF is IMO not going to happen in
forseeable future. If you want a solution to the jitter problem by
protocol, have a look at asynchronous USB which some claim is gaining
some popularity.
--
bhaagensen
--
Kellen,
Just to expand on DaveWr's point:
TCP/IP has flow control and error correction
S/PDIF has no flow control and embeds a clock signal in the S/PDIF data
stream
With TCP/IP (or USB come to that) the DAC can control the rate of flow
of data from the server, and uses its own local and hopefu
DaveWr;509053 Wrote:
> SPDIF can transmit a very accurate signal. The 0s and 1s are all
> usually quite correct. The problem is that jitter is small changes in
> duration of the 0s and 1s. Since the system uses serial data any clock
> variation from the source ripples through, although increas
SPDIF can transmit a very accurate signal. The 0s and 1s are all
usually quite correct. The problem is that jitter is small changes in
duration of the 0s and 1s. Since the system uses serial data any clock
variation from the source ripples through, although increasingly clever
techniques are us
>From what I have been able to gather a great deal of the clock jitter
problem results from using the S/PDIF connection from transport (say
SB3) to an external DAC when transporting a digital signal. Like example
2 attached below
If what I also read is true clock jitter isn't so much of a problem
