INTERACT FORUM
More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: dbalvo on May 11, 2014, 03:24:48 pm
-
I'm playing with JRiver and I'm having a problem where it sits there pegging one of my CPU cores all day and night. When I first start it up, it's fine. But once I start playing music it begins to ramp up to 100% on that core and never stops. I don't have any plugins or special stuff installed.
I tried using a profiler to see what it was doing, and all I cold tell was that all the work was in the thread named GetJRPlayerDLL (I have no Symbols to gather more info.) My music files are located on a network drive if that makes any difference. Please Help!
-
Is auto-import analyzing your library or generating thumbnails for a newly created one?
Try running Tools → Import → Run Auto-Import Now and see what the status window in the lower-left says.
If CPU usage is high during playback, what type of files are you playing? DSD will often result in very high CPU usage for example.
-
Definitely sounds like auto audio analysis to me :)
Sounds like you're reasonably conversant with the innards of the system if you've tried a profiler, so you may wish to look in the log.
This is located in your AppData\Roaming\JRiver folder, or can be accessed through 'Help- Logging'
Alternative, post the log and someone will be able to take a quick poke.
-Leezer-
-
Thanks for the replies. The CPU doesn't start pegging until I start playing music - if the issue was an auto import would playing music kick that off? And would that run for over a day?
As for what type of tracks I'm playing back, they are lossless WMA rips. Nothing too heavy. And the pegging continues after I stop playback.
I'll try to capture a log and see what that says / post here.
-
Thanks for the replies. The CPU doesn't start pegging until I start playing music - if the issue was an auto import would playing music kick that off? And would that run for over a day?
It may be coincidental, as I think it runs a minute or two after you launch the program.
Analysis could certainly run for over a day if you have a large library, depending on your CPU and disk speeds.
-
Antivirus software could do that. AV should not be checking media files each time they are opened.
-
Ok, so I think the connection to playback is coincidence. Nothing to see there.
I tried outputting the log but it literally contained nothing (I know what the log should look like from trying while doing other things.) I don't know about the AV thing, but the files are all on a network share anyway which I wouldn't expect AV to be protecting. I've never had a problem like this before with my AV and it isn't showing any cpu usage itself (it's all in the Media Center app)
I'll try the auto import thing to see what's going on there. Would the process of generating thumbnails literally lock up the app for minutes? Because it frequently goes into not-responding mode. I'd somewhat expect that to be happening in a background thread/process.
-
Ok, tried the auto import trick and it seems I'm spending time 'Analyzing audio...'. Not sure what that means exactly, but i'm guessing that's what's chewing up all my time. I'll let it march along and see what happens when it's done.