Max Kellermann wrote: > On 2009/01/13 10:29, Linel Patrice <patnathan...@gmail.com> wrote: >> The "pa_threaded_mainloop" control the mainloop of pulseaudio. So if the >> pulse output is not used, there are no reasons to introduce overhead. > > We didn't need the main loop stuff before your patch. I don't know > the pulse API, please explain why you're using it now. Is it required > for your mixer code? If the user chooses to not use your pulse mixer > code (but uses a pulse output), can we switch off the main loop? > > Max
You did not need the mainloop cause the mainloop was enclosed in the function of the "simple api" of pulse. To control the pulse mixer, you need to have the context( struct for connexion) , the mainloop of pulse , and the stream struct. Strictly , I only need a connexion to the server , the mainloop and the name of the stream. But if the output have it, let's use the same pointer and thus use the stream to drive the mixer. It is clear or not? ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
