I think one possible reason that those WAV/AIFF vs. FLAC/ALAC arguments never get resolved is because of inconsistent results between different computers. Everyone's mileage will vary according to how much processing power is available to uncompress those FLAC/ALAC files in real time, and how much processing power is actually available to do so. If the processing is bottlenecked, then errors are possible in the resultant signal timing stream.
If you have a kickass computer with tons of RAM, you probably won't notice any difference as there will be no bottleneck, but if you are trying to do it on a outdated cheap laptop (for example) it's quite possible that the overtaxed computer could introduce timing errors, particularly if your DAC is is relying on the computer to be the master audio clock because it is using adaptive USB audio protocols. Conversely, if your cheap old laptop doesn't have to uncompress the WAV/AIFF file then there would be less of a bottleneck when processing it and the computer will be less prone to timing errors. At least that's the way I understand it.
As far as jitter goes, geniuses like Gordon Rankin (who developed the driver-less asynchronous Streamlength receiver code), understand that if you move the master audio clock to an outbound device you can eliminate timing errors generated by that overtaxed computer, and he did it within existing USB audio protocols. This results in extremely low jitter and eliminates the need for resampling and reclocking.
Streamlength is a unique and elegant solution that is being licensed to more and more higher-end devices these days and his own line of DACs have a great reputation for sound quality. So I will take his word for it when he says, "software changes the character of sound". He does have a product to sell, but he has nothing to gain by saying that. He explains his clocking technology much better than I ever could, since we're posting links:
http://www.usbdacs.com/Concept/Concept.html
If you have a kickass computer with tons of RAM, you probably won't notice any difference as there will be no bottleneck, but if you are trying to do it on a outdated cheap laptop (for example) it's quite possible that the overtaxed computer could introduce timing errors, particularly if your DAC is is relying on the computer to be the master audio clock because it is using adaptive USB audio protocols. Conversely, if your cheap old laptop doesn't have to uncompress the WAV/AIFF file then there would be less of a bottleneck when processing it and the computer will be less prone to timing errors. At least that's the way I understand it.
As far as jitter goes, geniuses like Gordon Rankin (who developed the driver-less asynchronous Streamlength receiver code), understand that if you move the master audio clock to an outbound device you can eliminate timing errors generated by that overtaxed computer, and he did it within existing USB audio protocols. This results in extremely low jitter and eliminates the need for resampling and reclocking.
Streamlength is a unique and elegant solution that is being licensed to more and more higher-end devices these days and his own line of DACs have a great reputation for sound quality. So I will take his word for it when he says, "software changes the character of sound". He does have a product to sell, but he has nothing to gain by saying that. He explains his clocking technology much better than I ever could, since we're posting links:
http://www.usbdacs.com/Concept/Concept.html