INTERACT FORUM
More => Old Versions => Media Center 13 (Development Ended) => Topic started by: mlagase on November 02, 2008, 05:52:51 am
-
I've been trying to track down some performance issues on my machine and turned up some logging within MC and found that every time a song it queued for playing, we copy the cover art to the temp directory (C:\Documents and Settings\mike\application data\J River\Media Center 13\Temp )with a name of something similar to MP3 Image - 14636.jpg and also copy over the entire track info html code instead of using what is in the directory already.
0527953: 14636: Database: JRAnalyzerFile::GetImage: Start
0527953: 14636: Database: JRAnalyzerFile::GetImage: Finish (0 ms)
0527953: 14636: Reader: CLocalReader::OpenInternal: Opening: C:\Documents and Settings\mike\Application Data\J River\Media Center 13\Temp\MP3 Image - 14636.jpg
0527953: 14636: Reader: CLocalReader::Close: Closing: C:\Documents and Settings\mike\Application Data\J River\Media Center 13\Temp\MP3 Image - 14636.jpg
0527969: 14636: SDK: CMJPlaylistsAutomation::OnFinalRelease: All objects released
0527969: 14636: SDK: CMJPlaylistsAutomation::~CMJPlaylistsAutomation: Global Count: 0
0527969: 14636: SDK: CMJCurPlaylistAutomation::OnFinalRelease: All objects released
0527969: 14636: SDK: CMJCurPlaylistAutomation::~CMJCurPlaylistAutomation: Global Count: 0
Is this how this is supposed to work by default?
I was also having the high CPU issue with Auto Import turned on as well that other were reporting. I am not sure what option I need to turn off if analyze audio, build thumbnails, or get cover art was the culprit. Since I was not adding anything to my library, we should not have been running at 10-15% CPU or doing anything. I disabled all options except auto-import and it appears it is back to normal after a restart of MC.
-
... we should not have been running at 10-15% CPU or doing anything.
Why is that a problem? When MC first sees your library, it does some work to prepare it for use. Thumbnails, etc. 10 to 15% isn't a problem, in my opinion. Even higher unless something else needs the horsepower.
-
Right, but this is constant CPU usage, not the initial preparation use that you are talking about. I know about the view changing and the CPU it consumes, but sitting there doing nothing watching task manager jump around for a supposedly idle process?
I'll mess with some of the options to see where the CPU is coming in to play here.
-
Are you running any third party products with MC?
-
Nope, this is a new install of MC13 with no added bells/whistles just yet