SBGK wrote: 
> The bits don't magically move from the ouside the Touch, into the Touch
> and then out of the Touch. At it's heart is a little computer that has
> to make millions of decisions a second about what task it is going to do
> next and what resource to allocate to that task. Out of the box the
> Touch is trying to do lots of multimedia type things eg checking the
> screen brightness 500 times a second, with TT3.0 and other optimisations
> the Touch is made to focus more on allocating those resources to the
> movement of bits from input to output buffers. So, in reality it is just
> tuning a computer, the same as non Touch users have to tune their
> servers to get the best sound out. It's not crypto engineering, it's
> just most people don't understand what the Touch is doing.

No no. The problem is what are you tuning and why, even assuming you can
tune it. 
If the dac correctly decodes sample values from S/PDIF which it can
provided jitter is less than several nanoseconds, then the crypto
engineering question is how the S/pDIf transmitting device can affect
the D/a conversion in the DAC. Assuming that the Dac uses its own clock
to time the d/a conversion
And even then assuming you can identify that process it will not
necessarily affect all Dacs the same way or at all.
Some people claim that short buffers may make more frequent but less
intense power surges- however the theory is far from unimpeachable, and
even the subjective reports (Imagining they were to be taken seriously)
are inconsistent. Assuming that transports do affect the Dac, there is
AFAIK no generally accepted way of measuring what would be a better
transport.


------------------------------------------------------------------------
adamdea's Profile: http://forums.slimdevices.com/member.php?userid=37603
View this thread: http://forums.slimdevices.com/showthread.php?t=95031

_______________________________________________
audiophiles mailing list
audiophiles@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/audiophiles

Reply via email to