jeffmeh;185037 Wrote: > I recognize the inherent issues with Toslink, but I agree that these > certainly can be worked through and that it is not "horrible." > However, the comparison between Toslink and wireless networking is > inappropriate. > > The former has stringent synchronization requirements that make a > difference in the audio output, where even small disruptions in the > timing can cause the dreaded jitter. > > The latter is asynchronous and can easily recover even when it drops > entire network packets. In the case of wireless streaming to a SB or > Transporter, as long as the next sequential packet arrives in good > order before the buffer runs out, the audio output should be > unaffected. If it does not arrive in time, you get an obvious drop-out > or stutter. > > From an underlying protocol standpoint, they are apples and oranges. Yes that is totally corrrect. Toslink vs. TCP/IP = apples vs. elephants. Personally I have NO issues with Toslink. It works fine. I know we can't wind back the clock but I'm sure this prejudice must date back to a time when digital was poorly understood. These days it's an even call. You have to rememmber that a lot of the CD's we are listening to have (parts of) tracks that at some point went down an optical connnection...
-- Phil Leigh ------------------------------------------------------------------------ Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85 View this thread: http://forums.slimdevices.com/showthread.php?t=33197 _______________________________________________ audiophiles mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/audiophiles
