Yes. JRiver is running in the NAS, The QNAP NAS is also the server. And controlled either directly or via Tremote. Either way it acts the same way. It does seem to have improved some after I made the changes outlined above (increased buffering to the max, enabled read from memory, and maxed out the live playback latency). The problem is much worse when playing back multichannel SACD ISO's during which it typically stops and produces a few snippets of music now and then. Does much better with 24/96 multichannel Flac, where it has an occasional dropout. Anything in stereo is fairly good with only a rare dropout now and then, but it happens. I'm trying to get a gauge now on how much duress the processor and memory are under when it does this. I can monitor the QNAP performance when its playing. I'm beginning to wonder is the JRiver MC incarnation made for QNAP products might be a somewhat unfinished product. Maybe its time to look at running a virtual windows machine on the QNAP and using JRiver for windows or a different player altogether.Where is your JRiver running? Is it on the NAS?
UPDATE: Monitoring the NAS system resources during play show both memory and CPU usage to be less than 10% when playing back 2 channel flac, less than 15% when playing back multichannel flac 24/96, and an increase to over 90% CPU usage but only 12 % memory when trying to play a SACD ISO. The SACD is being output at 1 bit 352.8 kHz . Im wondering if that isn't the problem. Im thinking the Emotiva pre pro cant handle that bitrate anyway. If I set JRiver to reduce the bitrate to 96K for anything greater than 96k the files play, although there are still dropouts. I've noticed other things too. Sometimes after playing 2 channel and then going back to multichannel it somehow sets itself to stereo in playback options. You have to go back in and reset it to number of source channels. Also, when I choose a track to play it momentarily displays the title of a track it played 10 tracks ago. It just seems so buggy.
Last edited: