On 11/01/10 00:02, Erik Hofman wrote: > Historically it just muted the sound. I've now updated the code to not > initialize the sound manager until specifically requested (which can be > at runtime, even when --disable-sound is specified). >
Thanks, that seems to allow it to run without sound :-) Now, next question, is there a way that once FG is running, having given it --disable-sound, that I can trigger the sound manager to kick in and re-enable sound. The Sound Configuration dialog doesn't do anything when --disable-sound is given (looks like it should, but it doesn't). Reason is, that I suspect this may be a more reliable way to get pulseaudio working, I noticed yesterday that if I let FG start up using Alsa->Pulse that the sound quality is all broken and unusable but it doesn't hang, then I can use the sound configuration dialog to switch to pulse and it usually works properly for all the aircraft I tried (where starting FG to directly use Pulse at startup, hangs more often than not if not using the C172 (even then, sometimes)). So I'm thinking that this could be a workaround, if a delay can be enacted so that the sound manager isn't brought "online" until FG is otherwise running and ready to go. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
