<p><br>
On Mar 2, 2011 8:16 AM, "Colin Guthrie" <<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>> wrote:<br>
><br>
> 'Twas brillig, and Maarten Bosmans at 02/03/11 09:51 did gyre and gimble:<br>
> > 2011/2/27 Stephen Lee <<a href="mailto:sl33nyc@gmail.com">sl33nyc@gmail.com</a>>:<br>
> >> I git clone'd master yesterday, successfully compiled, and ran PA<br>
> >> on my MacOS X machine. I was pleasantly surprised to see the<br>
> >> Coreaudio modules! I successfully tunnelled audio from one of my<br>
> >> Linux machines to my MacOS X w/o using esound, but I noticed that<br>
> >> iTunes wasn't included as a client when I was playing it and then<br>
> >> checking list-clients from the PA cli.<br>
> ><br>
> > That is of course expected, as iTunes and other mac apps are not<br>
> > pulse clients. So you have several applications playing audio<br>
> > connected to the CoreAudio subsystem and PulseAudio is one of them.<br>
> > This is the same situation as on Linux, where pulse connects to ALSA<br>
> > and applications that don't use libpulse but connect directly to<br>
> > ALSA cannot be manipulated by pulse. There is however a way to make<br>
> > PulseAudio your default ALSA device, so that even apps that only use<br>
> > libasound are connected to pulse, all be it in a bit of a roundabout<br>
> > way.<br>
><br>
> IIRC Daniel Mack (who wrote most of the OSX support in recent years in<br>
> PA) was intending on writing (perhaps "intending" is too strong a word<br>
> tho'!) a virtual CoreAudio device that is "PulseAudio" that would work<br>
> in the same way that the ALSA->Pulse stuff work on Linux. I'm not sure<br>
> if he ever got around to that or not. IIRC he's still rather active on<br>
> the alsa-devel mailing list. It may be worth asking him? Actually I've<br>
> CC'ed him. Perhaps he can reply with more accurate comments.</p>
<p>Jep, I have plans to continue my work on the OS X port, and finish the virtual audio driver I was working on. Currently, this is all just prove of concept, but I'm confident that it will be really useful once it's finished.</p>
<p>At the moment, I am travelling, but once I'm back in some weeks, I will hopefully find some time to catch up with this project. I'll post updates on this list, of course.</p>
<p>> >> Generally, what's the plan for being able to manipulate native<br>
> >> MacOS X clients/streams via PA? It'd be great to replace the<br>
> >> AirTunes (AirPlay) functionality that Apple offers. If this<br>
> >> functionality is still a work in progress, is there a workaround?<br>
> ><br>
> > The workaround would be to use an audio player that output to<br>
> > PulseAudio, like vlc, rhythmbox, banshee, amarok, though I don't<br>
> > have a clue whether these are ported to OSX and are able to use<br>
> > libpulse there.<br>
><br>
> While I don't know, I strongly suspect that VLC on mac is not compiled<br>
> with PA support....</p>
<p>No, that would't make sense either. What we need is generic way to get audio from all CoreAudio applications, without modifing them. I'm working on this, stay tuned :-)</p>
<p>Daniel<br>
</p>