More > JRiver Media Center 26 for Linux
Issues USB DAC
bob:
Everything looks good to me.
Try this though.
Change track skipping to gapless.
Seek to Standard
Stop to Immediate
Pause to Immediate
streamerguy:
Still the same.
Only when the next track has a different sample rate, one or two tracks are skipped. And sometimes the error pops up that "something went wrong with playback".
Best,
bob:
--- Quote from: streamerguy on April 23, 2020, 08:46:11 am ---Still the same.
Only when the next track has a different sample rate, one or two tracks are skipped. And sometimes the error pops up that "something went wrong with playback".
Best,
--- End quote ---
From your log, the device is returning an error when trying to set the sample rate, I think that's a device issue.
The only solution I can see is to use DSP studio and set the sample rate for everything to the Max sample rate your source material has. Alternately you could choose one of the PlugHW devices (if there is one) and let the ALSA driver handle it. I don't know that there would be any advantage in that though.
wer:
I think the "device issue" Bob refers to stems from not using the correct device driver, .
The DAC does not misbehave when it is controlled by the Marantz driver.
The problem is Marantz does not offer a driver for that DAC for Linux.
If the drivers you have available to you on Linux can't work correctly with that DAC, you're pretty much stuck. The device might offer only limited Windows-USB compatibility without a driver, which could explain the behavior you saw on the Windows machine.
streamerguy:
Hi Bob and Wer,
There is indeed no Linux driver as far as I know.
But about two years ago I did some testing as well using a RPi3 and an older Rapbian version (can't remember what version).
I am not 100% sure, but I think I haven't seen this issue then, only clicking of the DAC because USB and network share the same bus. I was hoping that this was solved with the RPI4 and indeed I have no clicking anymore, but now the skipping issue. And I can't try an older raspbian version because the RPI4 was not supported yet. Maybe this will be fixed in the future with a new raspbian version or I could try another Linux build.
I also have the idea it's a timing issue. Or do I need to change the values Buffer Time and/or Buffer Time? I played random with these settings and noticed changes but I don't know what values to use for these parameters.
Any idea's.
Thanks again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version