Does Streamripper work with windows 7 64bit?
Yes it does mate, just put it on my win7 64bit system, works perfect!
Windows 7 x32 with Winamp 2.9 as well as Winamp 5.63 Lite. CPU USAGE 100% when Winamp WIndow is moved around. WHY HASN'T ANYONE FIXED THIS?!
@ocdamp, how can you be sure it's Streamripper? Does removing the plugin fix the 100% CPU problem?
@jaygoldberg - To answer your question. I am using both Winamp and Foobar. Moving other Plugin Windows around works perfectly fine with both Winamp and Foobar. Since I can only use Streamripper with Winamp *There are ways to use it with Foobar but I dont* With ALL the plugins REMOVED, StreamRipper still causes this issue. Checking Task Manager shows StreamRipper CPU Use going upto 90% for upto 15 seconds on a Single Core Athlon XP Processor and 2 to 5 seconds on a Core 2 Duo processor. After a short time, it settles down back to 0 until StreamRipper is in use. This ONLY Happens with StreamRipper plugin Window. With the Plugins removed, I experience no such problem. This could be a problem with StreamRipper or with Windows itself. Windows comes with its own issues, but so far, this is the only Plugin causing this issue. Also please note that StreamRipper Window will Max out the CPU even when StreamRipper is NOT in use at all and only being moved around the Desktop. This occurs in both x86 and x64 Windows 7 with SP1.
My total Processes 5 minutes after Bootup are 42 Processes, 22% memory use, No tweaking with Windows except Hibernation and System Restore are Off. I do not have any background processes taking up CPU Resources. Everything is clean. No Extra junk. System runs very smooth.
before you compain that a free software isn´t working and that somebody must fix it, why didn´t you start learning programming and try to fix the issue on your own instead of posting some rude stuff? This is why the project is open source…
What are you on about Bastian? Where was I being rude? I am only Reporting that moving the WINDOW Around the Desktop causes the CPU usage to go very high. This happens whether Aero or Basic themes are used in Windows. That's it. If you are here to start an argument, you can go talk to a wall. I am simply reporting the issue.
Log in to post a comment.