-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I tried the Portaudio ALSA one, it compiled, on running: muted master. Jack I don't have installed so I can't test that. And as stated before, native ALSA does not compile. If it can't even keep track of what channel is Master and what one is MIC something is very broken...
The information I gave about what sound card in an earlier mail may be helpful for this. I can also upload some screenshots of kmix after and before FGCOM messing it up if you want. Further, on last try with Portaudio ALSA: ./fgcom - a communication radio based on VoIP with IAX/Asterisk (c)2007 by H. Wirtz <[EMAIL PROTECTED]> Version 1.1.0 build 42M Using iaxclient library Version SVN 42M Reading list of airports...done. Initializing IAX client as XXXXXXXX:[EMAIL PROTECTED] Selected frequency: 120.500 Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range ( 2.2 km) Call 0 accepted KSFO San Francisco Intl 120.500 TWR Call 0 answered [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range ( 2.2 km) [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker Radio-Select: NAV1 Selected frequency: 115.800 Hanging up call 0 Airport San Francisco Intl (KSFO ATIS at 115.800 MHz) is in range ( 2.2 km) Airport San Francisco Intl (KSFO ATIS at 115.800 MHz) is in range ( 2.2 km) No free call appearances [LISTEN] mute mic, unmute speaker Radio-Select: COM2 Selected frequency: 118.300 Segmentation fault The seg fault was after a Shift-Space... Oh and as before it muted the wrong stuff. Regards, AnMaster AnMaster wrote: > Holger Wirtz wrote: >> On Fri, Nov 23, 2007 at 11:42:42AM +0100, AnMaster wrote: >> There are quite a few reasons why fgcom shouldn't touch mixer settings: >> 1) Changing/muting master prevents sound from applications like flightgear >> and >> festival (flightgear got built in support for festival that I use) Even if >> there >> is a reason to mute this, it isn't realistic, the engine sound isn't turned >> off >> in a real airplane... > >>> Only the mic is muted - not the speakers. But for intercom you are > Then OSS alternative is broken, it mutes the MASTER setting. And changes > volume > of Master and Mic. It never mutes mic however. The ALSA one doesn't compile > and > the portaudio one says something about "native 8000Hz for card" (something I > got > no idea if I got). >>> right: I want that my partner can listen everythin I say so fgcom should >>> not mute the mic but only the channel towards the radio. >> 2) Why not do it in the software of fgcom. To mute: just stop listening. > >>> Yep - as I wrote yesterday: this must be coded inside iaxclient because the >>> complete audio layer is baught by iaxclient. Anyone who likes to do this? >>> Regards, Holger > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRrgoWmK6ng/aMNkRCgovAJ9CHBidTSmZl7tmdfnRF1diqx3GmwCdEiUs rzDMY9HjMd5W7RJ0Caifjgg= =IdaR -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
