Thanks for the confirmation. To access the higher rates then, I’d either need a native Linux driver for the Teac or use a Win based End point ? Or accept the fact I won’t be be able to play my vast collection of 10 DSD 256 and 512 tracks. At least ROON is able to transcode down.
That would probably apply to any unix based end point then
In addition to DoP limitation (PCM max frequency) and sometimes Linux drivers unavailability i was thinking DSD512 transport required ethernet bandwidth > 6MB/ s was perhaps too much for RPI architecture where USB and ethernet bandwidth are shared.
Anybody able to play native DSD512 on a PI ?
Im curious about how well the RPi3 will perform with DSD256. I have tried it and get pops, clicks, and dropouts. I never figured out why, but thought i would ask to see if anyone else knows about this issue.
DSD64 seems to work just fine, but DSD256 never did. I assumed it had to do with the USB port sucking up too much power when streaming such a large amount of data that the Pi just couldn’t keep up and would crap out.
I had all sorts of issues when I started off with my Teac 503. Using a native dos driver and JRiver all was well, but it wasn’t until I used the Ropieee build within Roon with a Pi that I was able to get over the DOP problem in Roon.
Sean, who wrote Ropieee wrote a native driver for the Teac.
Let me correct that. I did not write a native driver, I only built a custom kernel that supports the Teac wrt native DSD.
Now on the topic itself: DSD (whether it’s native or DoP) requires an extensive bandwidth. Doing that on a Raspberry Pi you can run into issues due to the design of the Pi that has a shared bus for both ethernet and USB.