<br><br><div><span class="gmail_quote">On 6/26/07, <b class="gmail_sendername">Justin Tulloss</b> <<a href="mailto:jmtulloss@gmail.com">jmtulloss@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>I'm just getting into PulseAudio and I'm looking forward to using it for some challenging projects. I do have a few questions however:<br><br>1. Is good floating point performance necessary? I saw that some of your algorithms do rely on floating point, but I didn't get far enough into it to see whether it was necessary for basic PCM routing.
</blockquote><div>No, it isn't neccesarily. I been working with pulseaudio in an embedded enviroment for a while. There are two current floating point weaknesses. These are software volume and resampling. However I had made a patch to use a newer fixed point speex resampler. It got to the list for a little while. I'll resubmit once the speex stuff is done and stable.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2. How do direct plugin sources/sinks work? For example, the gstreamer plugin communicates directly with pulse. Therefore it doesn't show up as a source in the manager. Is there a way to get a handle to that source? For instance, if I had 2 sinks (A and B) and I wanted to say that all alsa sound (from the alsa plugin) should go to sink A where all gstreamer audio should go to sink B, how would I do that? That's a contrived example, but I am looking for that kind of flexibility.
</blockquote><div><br>This is very easy. There is a API to get current sources and sinks. Each source can tell what sink it wants to go to. (ie. gst-launch audiotestsrc | pulsesink device=secondaudiodevice) <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3. Is anybody actively working on a D-Bus control for this? Seems like it would be easy enough.
</blockquote><div>I believe there has already been work to integrate dbus with pulse's mainloop and there seems to be some code that does this. I haven't found it necessary to use because the native protocol works well. (although I use dbus for everything else.)
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">4. How do you define policy for HAL events? I don't see an obvious way of saying "now that this sink is connected, all audio goes to it and the old sink will be turned off"
</blockquote><div>Sorry, This is the only question I don't know....<br><br><br>Keith<br><br></div></div><br>