I have a misbehaving application (game) that, while mic is disabled in its settings (I prefer to use a voice server with friends), every single time a new group is formed - or I cease to be the 'host' (it seems to use a peer-to-peer host negotiation of some sort) - this application grabs hold of the mic and won't release its grip until I restart the voice software (and sometimes even then, it won't let go).

I have looked into winecfg to see if I can disable the mic capture portion, but no option exists.
I have tried my best to use the correct search terms in search engines, and all that brings up is how to get mic capture enabled.

I only have alsa, no pulse, no oss.

Do I need to build wine with some undocumented configuration? Is there an undocumented setting in regedit? Am I out of luck?

could you try installing jackd and let me know how it goes. It be nice if you actually. had info like. Distro, Version, etc etc there is over 300 distro's out there.
Remeber wine is not windows ok it is a layer and it just uses ALSA. Are you using VIVOX for voice.

Err, oops. Slackware 14.0. Was using teamspeak at first, then moved to mumble, same issue crops up with both. Never heard of vivox, nor jackd. Looking up info on both now. I do understand wine is a layer, was just hoping it was some quick fix. I should know better.

vivox - integration? clarification might be needed, I am not developing said application. I'm just an end user attempting to make said app whose "mic disabled" as per its settings, actually be disabled - rather than act like its muted. I apologize if my first post looked that way.

wine uses ALSA ok and jackd can control your input and output devices. just build jackd and qtjackd and give it a try. Wine just does what ALSA lets it.
you could always try to restart ALSA as root /etc/rc.d/rc.alsa restart see if that works.

Well I tried Jack, after a few odd attempts (xruns) I did finally get it running, but I'm either lazy or didn't find the right info to configure what was what. If I were into recording I bet I would have tried harder, but I was after as simple a solution as possible.

I stumbled upon alsa's dummy driver (Matrix:Module-dummy [snd-dummy]), configured a second card to use said drive, pointed the wine prefix to it. I have tested it for the last few days now and have had no issues with the mic (since wine is no longer using the real card).