INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: Audiodigger on April 02, 2015, 09:06:21 am
-
I have a problem with the new update.
I have interference when i upsample to 384 kHz, sounds like I`m playing an old dusty vinyl record.
Very annoying since I always use this upsample.
-
I have a problem with the new update.
I have interference when i upsample to 384 kHz, sounds like I`m playing an old dusty vinyl record.
Very annoying since I always use this upsample.
Does it work in 20.0.66 (http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter200066.exe), but not 20.0.70 (http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter200070.exe) onwards?
The resampler now uses high precision mode, which results in better audio quality at the cost of requiring more system resources. It's possible that this change means that your system is no longer fast enough to use 384kHz without buffer underruns.
Using a lower sample rate, or increasing the buffer size for your playback device may help.
-
Does it work in 20.0.66 (http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter200066.exe), but not 20.0.70 (http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter200070.exe) onwards?
The resampler now uses high precision mode, which results in better audio quality at the cost of requiring more system resources. It's possible that this change means that your system is no longer fast enough to use 384kHz without buffer underruns.
Using a lower sample rate, or increasing the buffer size for your playback device may help.
It`s a new dedicated computer with no other problems what so ever, and the problems started about two weeks ago, don`t know whitch version of JRiver that was.
Really annoying and hope that you can fix it soon.
-
Still a lot of interference playing 384 kHz
It has taken me a lot of work to come to this conclusion, and it doesn`t matter what buffer time and so on.
-
What device are you playing to? Does it play 384K?
-
Have you tested the two different versions, as I suggested?
It would be useful to know if it still happens in 20.0.66