INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: mirkotc on January 02, 2019, 10:54:08 am
-
Hi, I've installed JRiver's Media Center 24 (Windows 10 64 bits). It had been worked correctly in my Intel NUC. But after the last updates, it has started to have problems playing SACD ISO files. It starts buffering the files into memory and plays them for 15 to 30 seconds, then stops playing and starts buffering again. The behavior is the same with all the SACD ISO files that I have. Previous versions didn't present this problem.
My NUC is connected to a SONY 5.1 receiver via an HDMI ARC connection through a Samsung LED TV with audio passthrough enabled. I'm using the ASIO4ALL drivers.
The problem doesn't appear when I play the ISO SCAD files with Foobar 2000, also using HDMI and the ASIO4ALL drivers.
I've already uninstalled and reinstalled Media Center 24, rebuilt the library and uninstalled and reinstalled the ASIO4ALL drivers.
Does anybody have a clue about what the cause for this behavior could be?
Intel NUC
8 GB RAM
Files played from local Hybrid HD.
HDMI connection
Sony 5.1 receiver
-
Try using something other than ASIO4All. It's a wrapper for Kernel Streaming.
Antivirus?
-
I'd try turning memory playback off too. It's possible you're trying to load an SACD ISO larger than what is supported by memory playback.
-
I'd try turning memory playback off too. It's possible you're trying to load an SACD ISO larger than what is supported by memory playback.
Tried all memory playback options including no memory playback. Didn't help.
-
Try using something other than ASIO4All. It's a wrapper for Kernel Streaming.
Antivirus?
Using Windows Defender. Tried disabling it. no improvements.
-
What does Audio Path show?
-
Tried everything to no avail. But perusing through the forum I found a recommendation by stricko, I enabled the Sox Resampling option. My Sony receiver can play up to 192 kHz at 24 bits, so I was resampling ISO SACD to either 192 or 176,4 kHz, depending upon the source. Standard resampling produces rebuffering, Sox resampling works like a charm so far. BTW My NUC is a Celeron 4 cores CPU, similar to the one used for the JRiver Id. I run Win 10 Pro and ASIO4All drivers.
Hope it keeps working ok.
-
I would highly recommend avoiding ASIO4All. As Jim said, it's just a wrapper for kernel streaming and not 'true' ASIO. If you have WASAPI available, I'd recommend using that instead.
Kernel streaming is from the Windows 98 to Windows XP days and it's considered legacy (and was replaced by WASAPI), so I wouldn't be surprised if Microsoft completely removed it from Windows at some point in the future (which would render ASIO4All useless).
-
I find that resampling DSDs to 192 KHz uses significantly more CPU that resampling to 176.4 KHz. Unless there is another reason to use 192 Khz I would stick with 176.4 Khz.
-
I find that resampling DSDs to 192 KHz uses significantly more CPU that resampling to 176.4 KHz. Unless there is another reason to use 192 Khz I would stick with 176.4 Khz.
Agree. I always try to re-sample to evenly divisible rates of the source rate.