On Sat, Nov 28, 2009 at 12:56 AM, James Sleeman <flightg...@gogo.co.nz> wrote: > Csaba Halász wrote: >> These are two questions as I see it. >> James wants to *use* pulse while most users would be happy to just >> have FG work *around* pulse. >> For this latter case, I believe an alsoftrc with alsa driver and >> dmix/dsnoop devices should be fine. >> > > I could work around pulse, by killing pulse, using flightgear and > restarting pulse. But that seems a particularly unpleasant workaround.
But have you actually tried keeping pulse running and directing openal to alsa dmix? I don't use pulse myself, so I am just guessing that the topology would be something like this: FG -----------> OpenAl ---> ALSA (dmix) ----> hardware app1 ----------------> pulse ----^ app2 --- ALSA (pulse) ---^ -- Csaba/Jester ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
