3.0.1.1120: crossfading uses more than 50% process [F4203]

Pastis · Post by **Pastis** » Wed Dec 19, 2007 6:26 pm

Hello guys, i just noticed that this evening while i was writing on msn:

When MM passes by from one song to the next one on the playlist (cross fading system), it leads to make slower my pc, during one or 2 seconds.
When the new song is played, no problem anymore, until the next song's crossfading, where the problem appears again.

I observed the phenomenon with the task manager processus, and i saw it used until 56% process during thoses 2 seconds.

It never happenned with the previous builts of MM.

Did someone else notice that?

Thank you!

sparker · Post by **sparker** » Wed Dec 19, 2007 6:51 pm

dont know about the older versions, but same here

Post by **rusty** » Thu Dec 20, 2007 10:48 am

Pastis,

Can you re-verify that earlier builds (e.g. RC2/RC3) don't experience this problem on your machine. Also, can you see whether disabling hardware acceleration, OR switching to waveout output plugin solves the problem?

Note: I do see a crossfading-related spike, but that's related to filling the buffer.

-Rusty

MM3 monkey · Post by **MM3 monkey** » Thu Dec 20, 2007 11:57 am

Hello, Rusty. Happy Christmas + thanks for MM + I hope you get to put your feet up soon. I've got the same problem. Didn't report it bcos I thought it was my computer's fault. I haven't got crossfading ticked in the play menu btw.

I changed to wave output but the behaviour is still the same. It spikes on change and then stays spiked for a second or two when the new song has started too.

I think this is a very new thing - maybe RC4/5; sorry, I can't be sure. I don't know what hardware acceleration is, so I'll leave that to someone else till I find out!

Good luck.

MM3 monkey · Post by **MM3 monkey** » Thu Dec 20, 2007 3:35 pm

Proper answer (forget previous post):

I get a spike up to c. 60% in CPU usage when MM changes to the next song.

It happens with and without crossfade, with and without hardware acceleration and also with the waveout output plugin. I also tried it with all the boxes at the bottom unchecked too.

You cannot click on anything else for the three seconds or so this process takes - the program 'seizes up' if you do (but usually comes out of that state when you wait).

Post by **rusty** » Thu Dec 20, 2007 4:52 pm

Will be fixed in RC6.

Thx.

-Rusty

Pastis · Post by **Pastis** » Thu Dec 20, 2007 8:37 pm

Thank you MM3 monkey for the testes, and thank you rusty

TwiztidSinz · Post by **TwiztidSinz** » Thu Dec 20, 2007 10:21 pm

might wanna remove that extra E from 'tests' before people get the wrong idea

paulmt · Post by **paulmt** » Thu Dec 20, 2007 10:25 pm

TwiztidSinz wrote:might wanna remove that extra E from 'tests' before people get the wrong idea

I thought the same thing!

MM3 monkey · Post by **MM3 monkey** » Thu Dec 20, 2007 11:49 pm

I'm glad they arrived safe and sound, Pastis.

Pastis · Post by **Pastis** » Fri Dec 21, 2007 6:34 am

might wanna remove that extra E from 'tests' before people get the wrong idea

Indeed loool sorry

But what wrong idea people could have reading "testes"? Because the word "teste" doesn't exist in english. I didn't find it in dictionnaries...

EDIT:
OK i understood

3.0.1.1120: crossfading uses more than 50% process [F4203]

3.0.1.1120: crossfading uses more than 50% process [F4203]

Spike on track change

CPU spike