rsh
12th September 2006, 22:44
When I run WinAmp, and TRY to close it, sometimes it does NOT close. Instead Microsoft Kernal Wave Audio Mixer and/or Microsoft Kernal Acoustic Echo Canceller end up with yellow exclaimation points in the device manager, and WinAmp shows up in the Windows Task Manager Process List without showing up in the running applications list. This is particularly likely if I start up my browser(s) while WinAmp is running, based on my observations. I am running the latest beta version but before that I was running 5.24 and had the same problems, which is why I am trying out the beta version. I have kmixer.sys version 5.2600.2180 XPSP_SP2 so you can see I am running the latest version of XP Home SP2 in my notebook. It is a ASUS Z70Va model with a realtek sound chip, 4 speakers in the four corners of the machine, 1 gig of ram and two 60 gig hard drives with about 20% free space on one and 50% free on the other. Anyway, I also have other sound software installed, including:
Direct MIDI to MP3 converter
MID Converter
Midi2Wave Recorder
Midi Disassembler
Midi Maestro
MidiNotate Composer
Mp3tag
Music Master Works
Piano.exe
RealPlayer
Sibelius Scorch
vanBasco's Karaoke Player
Wav2MP3 Wizard
WGPlayer
Windows Media Player
AvRack from RealTek
Cyberlink PowerDVD
so there is other music software installed, which I sometimes use WHILE WinAmp is running. In particular I will use MidiNotate Composer to ALTER the Midi file when WinAmp is playing it. With the Composer I am NOT Playing the file... but merging staves or splitting hands, to create a stereo effect, etc. MP3tag, similarly, does not play the music, but allows me to alter the internal file data to the correct values, so that when I cut a CD it contains the song title, composer, year, etc.
Anyway, it often requires me to log off and back on, OR, in some instances, restart Windows, to clear the problem with WinAmp or it requires MANY attempts to end the WinAmp process using the Windows Task Manager. I have observed as many as three WinAmp processes running when I have been un-judicious and have pressed the WinAmp icon too many times, but it is usually simple to get down to only one running this way... it is shutting down that last one that can be close to impossible.
Anyway, other sound can still play, but the wave files and midi files may well NOT play once those blasted yellow exclaimation points show up.
I can find nothing on solving this problem on the site. This is not related to the midi files that play far too long, when compared to what they should play, as posted a week ago.
FWIW
RsH :cry:
Direct MIDI to MP3 converter
MID Converter
Midi2Wave Recorder
Midi Disassembler
Midi Maestro
MidiNotate Composer
Mp3tag
Music Master Works
Piano.exe
RealPlayer
Sibelius Scorch
vanBasco's Karaoke Player
Wav2MP3 Wizard
WGPlayer
Windows Media Player
AvRack from RealTek
Cyberlink PowerDVD
so there is other music software installed, which I sometimes use WHILE WinAmp is running. In particular I will use MidiNotate Composer to ALTER the Midi file when WinAmp is playing it. With the Composer I am NOT Playing the file... but merging staves or splitting hands, to create a stereo effect, etc. MP3tag, similarly, does not play the music, but allows me to alter the internal file data to the correct values, so that when I cut a CD it contains the song title, composer, year, etc.
Anyway, it often requires me to log off and back on, OR, in some instances, restart Windows, to clear the problem with WinAmp or it requires MANY attempts to end the WinAmp process using the Windows Task Manager. I have observed as many as three WinAmp processes running when I have been un-judicious and have pressed the WinAmp icon too many times, but it is usually simple to get down to only one running this way... it is shutting down that last one that can be close to impossible.
Anyway, other sound can still play, but the wave files and midi files may well NOT play once those blasted yellow exclaimation points show up.
I can find nothing on solving this problem on the site. This is not related to the midi files that play far too long, when compared to what they should play, as posted a week ago.
FWIW
RsH :cry: