Re: [pulseaudio-discuss] MacOS X Support
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. 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. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? The workaround would be to use an audio player that output to PulseAudio, like vlc, rhythmbox, banshee, amarok, though I don't have a clue whether these are ported to OSX and are able to use libpulse there. While I don't know, I strongly suspect that VLC on mac is not compiled with PA support 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 :-) You'll be my hero if you make a virtual audio driver. Now, if that isn't incentive enough, then I don't know what is! :)___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] MacOS X Support
2011/2/27 Stephen Lee sl33...@gmail.com: I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. That is of course expected, as iTunes and other mac apps are not pulse clients. So you have several applications playing audio connected to the CoreAudio subsystem and PulseAudio is one of them. This is the same situation as on Linux, where pulse connects to ALSA and applications that don't use libpulse but connect directly to ALSA cannot be manipulated by pulse. There is however a way to make PulseAudio your default ALSA device, so that even apps that only use libasound are connected to pulse, all be it in a bit of a roundabout way. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? The workaround would be to use an audio player that output to PulseAudio, like vlc, rhythmbox, banshee, amarok, though I don't have a clue whether these are ported to OSX and are able to use libpulse there. -Stephen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] MacOS X Support
'Twas brillig, and Maarten Bosmans at 02/03/11 09:51 did gyre and gimble: 2011/2/27 Stephen Lee sl33...@gmail.com: I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. That is of course expected, as iTunes and other mac apps are not pulse clients. So you have several applications playing audio connected to the CoreAudio subsystem and PulseAudio is one of them. This is the same situation as on Linux, where pulse connects to ALSA and applications that don't use libpulse but connect directly to ALSA cannot be manipulated by pulse. There is however a way to make PulseAudio your default ALSA device, so that even apps that only use libasound are connected to pulse, all be it in a bit of a roundabout way. IIRC Daniel Mack (who wrote most of the OSX support in recent years in PA) was intending on writing (perhaps intending is too strong a word tho'!) a virtual CoreAudio device that is PulseAudio that would work in the same way that the ALSA-Pulse stuff work on Linux. I'm not sure if he ever got around to that or not. IIRC he's still rather active on the alsa-devel mailing list. It may be worth asking him? Actually I've CC'ed him. Perhaps he can reply with more accurate comments. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? The workaround would be to use an audio player that output to PulseAudio, like vlc, rhythmbox, banshee, amarok, though I don't have a clue whether these are ported to OSX and are able to use libpulse there. While I don't know, I strongly suspect that VLC on mac is not compiled with PA support Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] MacOS X Support
On Mar 2, 2011 8:16 AM, Colin Guthrie gm...@colin.guthr.ie wrote: 'Twas brillig, and Maarten Bosmans at 02/03/11 09:51 did gyre and gimble: 2011/2/27 Stephen Lee sl33...@gmail.com: I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. That is of course expected, as iTunes and other mac apps are not pulse clients. So you have several applications playing audio connected to the CoreAudio subsystem and PulseAudio is one of them. This is the same situation as on Linux, where pulse connects to ALSA and applications that don't use libpulse but connect directly to ALSA cannot be manipulated by pulse. There is however a way to make PulseAudio your default ALSA device, so that even apps that only use libasound are connected to pulse, all be it in a bit of a roundabout way. IIRC Daniel Mack (who wrote most of the OSX support in recent years in PA) was intending on writing (perhaps intending is too strong a word tho'!) a virtual CoreAudio device that is PulseAudio that would work in the same way that the ALSA-Pulse stuff work on Linux. I'm not sure if he ever got around to that or not. IIRC he's still rather active on the alsa-devel mailing list. It may be worth asking him? Actually I've CC'ed him. Perhaps he can reply with more accurate comments. 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. 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. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? The workaround would be to use an audio player that output to PulseAudio, like vlc, rhythmbox, banshee, amarok, though I don't have a clue whether these are ported to OSX and are able to use libpulse there. While I don't know, I strongly suspect that VLC on mac is not compiled with PA support 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 :-) Daniel ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] MacOS X Support
Sorry for following up on my own email, but am I missing something obvious and being completely dumb? :) -- Stephen On Sun, Feb 27, 2011 at 9:34 AM, Stephen Lee sl33...@gmail.com wrote: I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? -Stephen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] MacOS X Support
On Tue, 2011-03-01 at 16:57 -0500, Stephen Lee wrote: Sorry for following up on my own email, but am I missing something obvious and being completely dumb? :) No :) On Sun, Feb 27, 2011 at 9:34 AM, Stephen Lee sl33...@gmail.com wrote: I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? I haven't heard that anyone would be currently working on additional MacOS X features. There are no plans either that I would have heard of. If you're not capable or willing to implement the stuff yourself, you will just have to wait until someone else pops up with patches. -- Tanu ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] MacOS X Support
I git clone'd master yesterday, successfully compiled, and ran PA on my MacOS X machine. I was pleasantly surprised to see the Coreaudio modules! I successfully tunnelled audio from one of my Linux machines to my MacOS X w/o using esound, but I noticed that iTunes wasn't included as a client when I was playing it and then checking list-clients from the PA cli. Generally, what's the plan for being able to manipulate native MacOS X clients/streams via PA? It'd be great to replace the AirTunes (AirPlay) functionality that Apple offers. If this functionality is still a work in progress, is there a workaround? -Stephen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
