Originally Posted by
Qwin
I did a bit of digging, so here goes with a non too technical explanation of what makes this thing tick.
The audio is handled by an i2s serial bus (data transfer method), this only handles audio and is not busy handling lots of other traffic. Most systems use i2s but hand the audio over to the USB bus for output. The USB bus also handles traffic from other devices running at the same time, so I think you can see the benefit of using the cleaner path by using only i2s.
i2s usually shunts audio data around from chip to chip on the PCB and USB is more about shunting data from device to device, that would be the simplest way of looking at it.
To take best advantage of the Rpi system you need to use the piggy backed DAC that plugs directly into the i2s bus. If you use an external DAC connected by the USB you are not really benefitting over any other PC based system.
USB can handle up to 24bit 96kHz in one direction.
i2s can handle up to 64bit 192kHz in one direction and 64bit 96kHz bi directional.
So in theory i2s is better placed for handling high quality audio files. I don’t know if it is fully utilized on the Rpi but in theory it is a good way to go for HQ audio.
The second area where benefits are likely being gained, is that the Rpi is a simple piece of computer hardware, with fewer things going on to get in the way of running audio. One of the things that builders of PC based FBA systems do, is strip out all the unnecessary parts of the system, removing things that get in the way or are a drain on resources and not needed for running audio files, removing both hardware and software routines. No need to do that on the Rpi its allready stripped down to the basics.
So those seem to be the advantages, which I can see how they might contribute to quality audio.