INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: dungkimham on October 02, 2018, 04:19:23 am
-
I am using JRiver 24 trial version to run on Pi3 bridge, playing DSD on Asus laptop: Core i3, 6MB RAM, installing JRiver as music server but lag many, often have to buffering. Please help me how to setup to enjoy DSD native on PI3 (my DAC support DSD512). Is the installation of JRiver master on PI3 different from JriverId? What should I buy for this purpose? Many thanks!
-
In this case, since you're using DLNA you'll want to use DoPE found in MC's Options > Media Network > Add or configure DLNA servers > pick your server on the top part and on the bottom part click on Advanced > Check Bitstream DSD
Here's a screenshot, I highlighted the option in a red box:
(https://i.imgur.com/NZHgq85.png)
Otherwise, if your device(s) don't support native DSD playback via DoPE, MC has to convert DSD to PCM on-the-fly when playing back DSD files, which is one of the most resource intensive tasks MC does. Which honestly a Raspberry Pi won't be able to handle without issues like buffering. This is what it sounds like it happening right now, without the DoPE option checked - MC is converting DSD to PCM on-the-fly, which since the Pi can't really handle too well it's causing buffering issues and whatnot. The only way around that (if you're forced to convert DSD to PCM on a Pi) is to do a pre-conversion of the DSD files to PCM files (e.g. FLAC files) or connect to a DAC via USB that supports native DSD playback and enable DSD bitstreaming (https://wiki.jriver.com/index.php/DSD). The proper way to do the pre-conversion is to make a copy of the DSD files you want to convert (so not to edit the original DSD files), edit their metadata (like add PCM at the end or whatever you want) and then import the copied files into MC and run the Convert Format tool on them.
But yeah, it's a lot to take in but see if the DoPE option works for you.
-
Thank you for your help! I tried several times but the buffering still occurs when playing DSD. My DAC can plays DSD512, I have also set DOPE as instructed.
JRiver directs DSD via DAC, CPU uses 30%, Ram uses 700MB and system is still buffering, regardless of DSD64, 128 or 256. Is there a way to handle it?
-
The "Bitstream DSD" option on your last screen shot is only used for LOCAL playback.
The DLNA server DoPE setting is used for network devices.
You may have a network bandwidth issue. Are both the Pi and DLNA DAC on wired ethernet or wireless?
Also, have you setup thread priorities on the Pi3?
-
The "Bitstream DSD" option on your last screen shot is only used for LOCAL playback.
The DLNA server DoPE setting is used for network devices.
You may have a network bandwidth issue. Are both the Pi and DLNA DAC on wired ethernet or wireless?
Also, have you setup thread priorities on the Pi3?
Thank you very much, I have used wired lines for both Pi3 and DNLA laptop, I also checked the flow priority setting, the result seems to be my pi3 optimized stream.
Although quality improves significantly when playing DSD native, but after about 3 albums, the JRiver buffer must still occur. What more do I need to do?
-
Thank you very much, I have used wired lines for both Pi3 and DNLA laptop, I also checked the flow priority setting, the result seems to be my pi3 optimized stream.
Although quality improves significantly when playing DSD native, but after about 3 albums, the JRiver buffer must still occur. What more do I need to do?
Since it's after 3 albums, I wonder if there is a memory leak?
Can you go to a terminal window as root and do the commands
free
and
lsof | wc -l
before you start playing
the same after it starts buffering and post the results here??
Thanks...