CPU usage

[NaLe!]

Last night i d/l the latest version of QMP and it occupies my CPU to over 90% (most of the time its actualy 99%) and it "eats" over 25.000K of mem usage nonstop? Is this behaviour normal?

Up until now i kinda stuck on the QCD 4.51 b/c it was the most stable and it did cause me any trouble at all...

Has anyone else experienced this type of trouble?

[Toe]

My guess would be that MusicID is running. Check Preferences -> Settings -> Gracenote -> MusicID File. Look in the status box at the bottom, see if it's cycling through a bunch of tracks.

[NaLe!]

Thanks... i'll check it...

[Todd The Kiwi]

maybe watch folders could do this?
it's ticked by default i think...

[NaLe!]

Nah it looks like the problem was with that ID stuff after i killed it off it now takes about 2.000K (minimized) and 13.000K (focused) mem.
Anyways since i do not use the watch thingie i turned it off after instalation...

Thank you both fot the response... really usefull...

[Toe]

Yeah, I do hope Paul does something to speed up the MusicID process. I get CPU usage bouncing from about 30% to 99% for quite a while after importing.

[Tokelil]

Yeah, I do hope Paul does something to speed up the MusicID process. I get CPU usage bouncing from about 30% to 99% for quite a while after importing.I think it is hard to speed those things up... I would guess that part of the code is highly optimized by now.

[Willow of Oz]

I'm going to assume that System Integration Process Priority refers only to the actual main audio thread / core app, and not to the media IDing (which should be low priority)?

Paul, any comment?

[Paul]

The MusicID'ing takes up a lot of CPU because it needs to decode audio to generate fingerprints which it then looks up.

MusicID runs at the lowest priority, but that doesn't mean it won't use 100% CPU if it needs to. Low priority just means it won't take CPU away from things that are higher priority.

The CPU usage in the process monitor will show the usage for all threads in the application combined.

[Toe]

Ah, I forgot about the fingerprinting part. That makes sense. I kinda suspected it was set to low priority anyway.

I'll have to remember that when I get around to writing the MusicID article for the wiki (unless someone wants to create the page (http://qwiki.toejob.org/musicid) themselves :) )

[Protocol]

Will MusicID overwrite current track tags? :ponder:

I put a lot of work into tagging my tracks, so I don't want something lesser overwriting them.

[Willow of Oz]

Yeah, I figured that was the setup, since it makes sense :beer:

[Tokelil]

Will MusicID overwrite current track tags? :ponder:

I put a lot of work into tagging my tracks, so I don't want something lesser overwriting them.Not unless you explicitly set it to write library content to tags. MusicID just set library information.

[Protocol]

Not unless you explicitly set it to write library content to tags. MusicID just set library information.
OK. Thanks Tokelil. I will have to have a look at the settings.

[EvilDust]

Between 45mb to 77mb here!! I have a strong pc but when QMP build 119 running, all my windows is slow :dead:

[Rex_Mundi_Incarnit]

Between 45mb to 77mb here!! I have a strong pc but when QMP build 119 running, all my windows is slow :dead:

Dude, did you just read all previous posts? :ermm:

Also what makes me wonder how much RAM does your strong pc have? 1GB, 2GB? What fraction is 77MB of that? >_<

[EvilDust]

Yes I readed it. I have 2 g of ram but It's not a reason to take 77mb, if I compare to Windows Media Player 11 or Winamp 5.35, the last build QMP is very slow.

[Rex_Mundi_Incarnit]

Yes I readed it. I have 2 g of ram but It's not a reason to take 77mb, if I compare to Windows Media Player 11 or Winamp 5.35, the last build QMP is very slow.

Why not? Windows Vista takes all the ram that's available. Still have you tried to run qmp with the /safestart command? It will disable all plugins and that way you can diagnose the problem thats causing qmp to run slow.

[Tokelil]

Well memory usage has gone up quite a lot with qmp compared to qcd. QMP b119 uses 40MB when minimized, where qcd used around 4-5MB. So on a 512MB system (which is for from uncommon to say the least) that's almost 10% of all system memory, which is quite a lot IMO. I would properly look else where for a media application if I was running such a system. (Or disable the ML, which I think is properly the cause.)

[Rex_Mundi_Incarnit]

FYI QMP uses 4mb here when minimized and idle (all plugins).

7mb now that im playing something (minimized).

40mb restored and playing something and having a visuals window open.

I think it also depends greatly on what skin you are using. I have made skins that are 1mb+ in size which will leave a memory footprint.

My system:
Core 2 Duo processor 1.66Mhz
Windows Vista
2GB Ram
Nvidia go 7600 256MB

[Tokelil]

Well I'm running the standard skin...

[markdentoffe]

Here it uses 38M of memory when fully opened and playing, with a visual that takes up 1251x814.
CPU usage about 10% (between 03 and 13).
Actually I think the cpu usage has decreased, 'cause it used to consume about 20-30% here if I remember it well.
Of course if I up the grid resolution of honto's phase visual I can get it to use 50-60%, but that's got nothing to do with the QMP core.

I did disable MusicID.

System specs are in my sig.

[NaLe!]

I have to disagree with EvilDust... My personal experience is that QMP/QCD is faster than Winamp especially in the initial loading.
That's one of the reasons i swiched to it, b/c i run on 2000+ AMD with ONLY 256mb. And it doesn't stop "singing" for a ms when i play most of the games that can be runned on this crapper (GTA:SA, CoD2, FarCry etc...).

[Rex_Mundi_Incarnit]

I have to disagree with EvilDust... My personal experience is that QMP/QCD is faster than Winamp especially in the initial loading.
That's one of the reasons i swiched to it, b/c i run on 2000+ AMD with ONLY 256mb. And it doesn't stop "singing" for a ms when i play most of the games that can be runned on this crapper (GTA:SA, CoD2, FarCry etc...).

You play Farcry on a machine with 256MB RAM?? :normal:

[EvilDust]

Nale!, did you try the last development build 119?

[NaLe!]

@Rex_Mundi_Incarnit: Yeah and it runs on 800x600... Freaky huh? esspecialy cuz i have NVidia's crappiest card ever: GeForce4 MX440... and i've got NOD32 in the back... You just need to know how to tweak the damn thingie and what processes to kill.

@EvilDust: I have tested the 118 and i stick to it... ;D

@Everyone: Did anybody notice that sometimes "Play->Play next" doesn't work?

[markdentoffe]

Nope, always worked fine for me so far.

[EvilDust]

In my post, I talked about the build 119 only. The buils 118 crashed many times on my Vista x64

[NaLe!]

for the last two days i've been playing with b119 and it runs fine.. ;D

[NaLe!]

About this "Play->Play next" function... Well it seems that when you press "Back" to reply the same song, it ignores the selected "next" track and chooses rndmly (if shuffle is on)...