Microphone disfunctionality

[kris.steenhaut@…]

I can make just one recording with \MMOS2\MMPLAYER\WEPM.EXE. After having closed the session, the sound volume drops about 95 % and wepm.exe doesn't work at all anymore.

Only way out is a reboot.

[vladest]

tested it works on my nf4+alc850

I dont see any logs nor what exactly wepm says :(

Regards, Vlad

[kris.steenhaut@…]

Do you mean the problem can't be solved?

[vladest]

I mean that you have to gimme logs

1. uniaud log
2. what reporting wepm to you etc

Otherwize I cant do abything, couse I cant reproduce the problem on my side

[kris.steenhaut@…]

<I mean that you have to gimme logs 1. uniaud log 2. what reporting wepm to you etc Otherwize I cant do abything, couse I cant reproduce the problem on my side>

OK. Do take in account I'm only a simple human being, so

1. What do I have to do in order to produce an Uniaud log (there is no stoud.exe present here)

2. Same question for wpem.exe: how to create a log?

[vladest]

1. copy alsahlp$ uniaud.log
2. just tell me how "non working" looks like

Thanks, Vlad

[kris.steenhaut@…]

blabla.zip created at 24 februari 2006

[kris.steenhaut@…]

OK. Here we go.

<1. copy alsahlp$ uniaud.log 2> before_uniaud.log is from before the recording session, uniaud_after.log

is from after the recording session. The same applies to before_MMPM2.INI and MMPM2_after.INI

<2. just tell me how "non working" looks like> I tried to record "blabla.wav", shouting as hard in the mic as I could. This time I even hadn't visible nor audible record - it's most like that, sometimes I do get visible and audible output. AND, after closing business ALL sound was gone, completely gone. Never had a problem like that or any problem with the Crystal drivers, so I'm completely at a loss. Included in blabla.zip the files I referred too.

[yoda]

Too old report.

Reopen with logs for current version, if it is still a problem.

[gentux2]

Hm, rather than marking "wontfix", would have been preferable to try to contact the reporter since we have his address. The description makes it seem hardware independent, but that seems doubtful. If we can't reproduce it on just any hardware, let's get hardware information and a recent debug log from the reporter and move this to milestone:"ALSA Hardware Compatibility"