100% of CPU Cycles on Idle Winamp

xoque · 1st September 2000, 09:34

Hey,

Was just wondering if anyone else has run into this problem. Either I just load winamp and don't do anything or I've been playing songs and I stop them, and so winamp is doing nothing at all, and I go into task manager and it says winamp is using 100% of my cpu cycles (ie taking away from what could be used for seti@home!

. I have two computers, winamp 2.64 on one, 2.65 on the other, and they both do the same thing. I'm running win2000, but a friend in irc is running win2000 with 2.65 and does not have the problem. Any ideas? I tried playing with the player priority.. setting it from normal to idle.. no effect, still 100% cpu cycles. Thanks for any help,

Michael

DJ Egg · 2nd September 2000, 05:06

Mmmm . . . strange 'n curious ?!?!

R.U. using the DirectSound Output instead of WaveOut by any chance ?

What are your sys specs ?
[eg. CPU + Clock Speed; RAM; Soundcard; etc]

Have you installed any extra third party plug-ins ?
Especially DSP/FX or General Purpose ones !

------------------
*******
DJ - Egg
*******
^/^
`v

xoque · 5th September 2000, 10:37

Hey,

My first system is an Athlon 850 MHz w/ 256 meg RAM, sb live gamers.
My second system is a P2-300 w/ 64 meg RAM, and sb live value.

No DSP or general plugins. And yes, its on waveout, not direct sound out.

All visualization options off.

Can't figure it out :/

Thanks,
Michael

peter · 5th September 2000, 21:39

I don't think that it could be caused by output plugins. If winamp is inactive, output plugins do nothing. If AVS window is open, it will certainly eat all available CPU cycles, even if you aren't playing anything. BTW, set process priority to 'idle' if you want something else to use your free CPU cycles instead

DJ Egg · 6th September 2000, 04:09

Do you have the Winamp Agent enabled by any chance ?
Disable it if so & try again !?!?

With those particular sys specs, I can't see any reason for this to be happening !

xoque · 6th September 2000, 11:23

Hey,

Well, thanks for the help guys but still no luck. Even at idle, it sits at 100% CPU and takes it away from SETI. Agent isn't enabled either. Must be something else I have installed.. or something. I think maybe I'll deltree the winamp directory and reinstall and see if that fixes things.

Michael

peter · 6th September 2000, 19:43

Set priority to idle and check if Winamp still has 100% when SETI is active. If priority is idle, any other program with higher priority will take these cycles from Winamp.

DJ Egg · 7th September 2000, 03:07

Don't deltree !
Use the proper uninstall tool in Add/Rem Programs CPL, then re-install.
If there's anything left behind after initial uninstall you can safely delete it.

Tho' I'd have thought that PP's suggestion/s would have worked ?!?!

xoque · 7th September 2000, 09:55

Hey,

No, PP's suggestions did not work. Winamp still stole all 100% of the CPU cycles. However, I did just do a del *.* in the winamp directory to get rid of all the configuration files and then reinstalled it and now it works fine. So what I'm think it was is that a plugin I turned off didn't really turn off and somehow was taking all 100% cycles.. seems weird though. Only explanation I can think of. Well ok I can think of more, just probably the most probably

thanks for the help guys,
Michael

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

1st September 2000, 09:34	#1
xoque Junior Member Join Date: Sep 2000 Location: Tucson, AZ, USA Posts: 4	Hey, Was just wondering if anyone else has run into this problem. Either I just load winamp and don't do anything or I've been playing songs and I stop them, and so winamp is doing nothing at all, and I go into task manager and it says winamp is using 100% of my cpu cycles (ie taking away from what could be used for seti@home! . I have two computers, winamp 2.64 on one, 2.65 on the other, and they both do the same thing. I'm running win2000, but a friend in irc is running win2000 with 2.65 and does not have the problem. Any ideas? I tried playing with the player priority.. setting it from normal to idle.. no effect, still 100% cpu cycles. Thanks for any help, Michael

2nd September 2000, 05:06	#2
DJ Egg Techorator Winamp & Shoutcast Team Join Date: Jun 2000 Posts: 35,894	Mmmm . . . strange 'n curious ?!?! R.U. using the DirectSound Output instead of WaveOut by any chance ? What are your sys specs ? [eg. CPU + Clock Speed; RAM; Soundcard; etc] Have you installed any extra third party plug-ins ? Especially DSP/FX or General Purpose ones ! ------------------ ***** DJ - Egg ***** ^/^ `v

5th September 2000, 10:37	#3
xoque Junior Member Join Date: Sep 2000 Location: Tucson, AZ, USA Posts: 4	Hey, My first system is an Athlon 850 MHz w/ 256 meg RAM, sb live gamers. My second system is a P2-300 w/ 64 meg RAM, and sb live value. No DSP or general plugins. And yes, its on waveout, not direct sound out. All visualization options off. Can't figure it out :/ Thanks, Michael

5th September 2000, 21:39	#4
peter ist death Join Date: May 2000 Posts: 3,704	I don't think that it could be caused by output plugins. If winamp is inactive, output plugins do nothing. If AVS window is open, it will certainly eat all available CPU cycles, even if you aren't playing anything. BTW, set process priority to 'idle' if you want something else to use your free CPU cycles instead

6th September 2000, 04:09	#5
DJ Egg Techorator Winamp & Shoutcast Team Join Date: Jun 2000 Posts: 35,894	Do you have the Winamp Agent enabled by any chance ? Disable it if so & try again !?!? With those particular sys specs, I can't see any reason for this to be happening !

6th September 2000, 11:23	#6
xoque Junior Member Join Date: Sep 2000 Location: Tucson, AZ, USA Posts: 4	Hey, Well, thanks for the help guys but still no luck. Even at idle, it sits at 100% CPU and takes it away from SETI. Agent isn't enabled either. Must be something else I have installed.. or something. I think maybe I'll deltree the winamp directory and reinstall and see if that fixes things. Michael

6th September 2000, 19:43	#7
peter ist death Join Date: May 2000 Posts: 3,704	Set priority to idle and check if Winamp still has 100% when SETI is active. If priority is idle, any other program with higher priority will take these cycles from Winamp.

7th September 2000, 03:07	#8
DJ Egg Techorator Winamp & Shoutcast Team Join Date: Jun 2000 Posts: 35,894	Don't deltree ! Use the proper uninstall tool in Add/Rem Programs CPL, then re-install. If there's anything left behind after initial uninstall you can safely delete it. Tho' I'd have thought that PP's suggestion/s would have worked ?!?!

7th September 2000, 09:55	#9
xoque Junior Member Join Date: Sep 2000 Location: Tucson, AZ, USA Posts: 4	Hey, No, PP's suggestions did not work. Winamp still stole all 100% of the CPU cycles. However, I did just do a del . in the winamp directory to get rid of all the configuration files and then reinstalled it and now it works fine. So what I'm think it was is that a plugin I turned off didn't really turn off and somehow was taking all 100% cycles.. seems weird though. Only explanation I can think of. Well ok I can think of more, just probably the most probably thanks for the help guys, Michael