Re: [pulseaudio-discuss] system-wide daemon

On Wed, Feb 17, 2010 at 12:25:27PM EST, Lennart Poettering wrote: > On Wed, 10.02.10 18:49, Jeremy Nickurak (pulseaudio-disc...@trk.nickurak.ca) > wrote: > > Incidentally, this seems to be the same use case that vision-impaired users > > were dealing with recently: How can system-level processes i

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 18:49, Jeremy Nickurak (pulseaudio-disc...@trk.nickurak.ca) wrote: > A question about the console-kit approach, where the user physically near > the sound hardware is the person that gets to use it... > > A favorite trick of mine is to ssh into a machine, and use the sound > har

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 16, 2010 at 10:17 PM, Lennart Poettering wrote: > On Tue, 16.02.10 20:48, Markus Rechberger (mrechber...@gmail.com) wrote: > >> Lennard, don't spread nonsense around, if you have raw access to a camera >> there >> might be the possibility to update the firmware and damage the device.

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 16.02.10 20:48, Markus Rechberger (mrechber...@gmail.com) wrote: > Lennard, don't spread nonsense around, if you have raw access to a camera > there > might be the possibility to update the firmware and damage the device. > If you would have little experience with hardware you should know

Re: [pulseaudio-discuss] system-wide daemon

On Thu, Feb 11, 2010 at 12:29 AM, Lennart Poettering wrote: > On Wed, 10.02.10 09:59, Markus Rechberger (mrechber...@gmail.com) wrote: > >> this is another wrong assumption, libusb uses raw USB access, if every >> user would have access >> to USB some devices might be damaged. >> Sane would need t

Re: [pulseaudio-discuss] system-wide daemon

Lennart Poettering wrote: > On Wed, 10.02.10 07:14, David Henningsson (launchpad@epost.diwic.se) > wrote: > >> But printers are more of a system-wide resource, and for some use cases, >> so is the soundcard. > > This is nonsense. I am not sure how your ears are constructed, but on > a multi

Re: [pulseaudio-discuss] system-wide daemon

Lennart Poettering wrote: > On Tue, 09.02.10 22:52, David Henningsson (launchpad@epost.diwic.se) > wrote: >> There are just too many people for where the ordinary PA setup (all >> soundcards are of exclusive use to the person logged into the current X >> session) is not acceptable, and worse,

Re: [pulseaudio-discuss] system-wide daemon

I did that originally. The problem is that I'm building Vinux ISOs on Ubuntu using remastersys, and I'd have to modify ubiquity to change the default user groups. The result is that after isntalling Vinux, Orca doesn't come up talking. Now, I may go modify ubiquity, but I'm more familiar now wit

Re: [pulseaudio-discuss] system-wide daemon

2010/2/11 Lennart Poettering : > On Wed, 10.02.10 10:45, Maarten Bosmans (mkbosm...@gmail.com) wrote: > >> The other mode is the system-wide daemon mode. This follows more the >> traditional unix model of a dedicated pulse user running a daemon to >> which other users can connect. The system mode i

Re: [pulseaudio-discuss] system-wide daemon

On Thu, 11.02.10 02:01, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > 'Twas brillig, and Jeremy Nickurak at 11/02/10 01:48 did gyre and gimble: > > A question about the console-kit approach, where the user physically > > near the sound hardware is the person that gets to use it... > > > > A fa

Re: [pulseaudio-discuss] system-wide daemon

On Thu, Feb 11, 2010 at 1:00 AM, Lennart Poettering wrote: > On Mon, 08.02.10 19:11, olin.pulse@shivers.mail0.org > (olin.pulse@shivers.mail0.org) wrote: > >> PA is a system that manages access to a hardware resource, in a network >> distributed context. Such a system must have mechanism

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Jeremy Nickurak at 11/02/10 01:48 did gyre and gimble: > A question about the console-kit approach, where the user physically > near the sound hardware is the person that gets to use it... > > A favorite trick of mine is to ssh into a machine, and use the sound > hardware there

Re: [pulseaudio-discuss] system-wide daemon

A question about the console-kit approach, where the user physically near the sound hardware is the person that gets to use it... A favorite trick of mine is to ssh into a machine, and use the sound hardware there to announce some kind of event. It might be an alarm to wake up a family member, or

Re: [pulseaudio-discuss] system-wide daemon

A question about the console-kit approach, where the user physically near the sound hardware is the person that gets to use it... A favorite trick of mine is to ssh into a machine, and use the sound hardware there to announce some kind of event. It might be an alarm to wake up a family member, or

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 2010-02-10 at 16:52 -0800, Lennart Poettering wrote: > On Wed, 10.02.10 16:45, Andrew McNabb (amcn...@mcnabbs.org) wrote: > > > Detachable ears are called headphones. :) > > > > I'm not arguing that it's practical to do, but an ideal multiseat system > > would be able to give each user tw

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 23:22, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > 'Twas brillig, and Lennart Poettering at 10/02/10 22:36 did gyre and gimble: > > On Tue, 09.02.10 09:43, Markus Rechberger (mrechber...@gmail.com) wrote: > > > >>> Indeed. PA is principally meant to be run per-user. Each use

Re: [pulseaudio-discuss] system-wide daemon

On Thu, 11.02.10 00:44, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > If people want to allow users unconditional access to audio devices, > > regardless whether they are logged in on the console, then they can > > add them to that group. That's fine. ACL certainly are more flexible, > > but jus

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 16:45, Andrew McNabb (amcn...@mcnabbs.org) wrote: > Detachable ears are called headphones. :) > > I'm not arguing that it's practical to do, but an ideal multiseat system > would be able to give each user two dedicated channels, so they can each > plug in their own set of headpho

Re: [pulseaudio-discuss] system-wide daemon

On Thu, 2010-02-11 at 01:46 +0100, Lennart Poettering wrote: > On Tue, 09.02.10 21:57, Michał Sawicz (mic...@sawicz.net) wrote: > > > 4. there's a dialog on the active user's session with 'User tries > > to access your audio equipment with application , allow / deny?' > > For every event

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 11:16, Bill Cox (waywardg...@gmail.com) wrote: > As for concerns about running system-wide... Ubuntu already disallows > user loaded modules, and I'm not hearing a lot of complaints. When it's not Ubuntu that disallows that. It's upstream PA. So, this breaks bt and hotplugging

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 21:57, Michał Sawicz (mic...@sawicz.net) wrote: > 4. there's a dialog on the active user's session with 'User tries > to access your audio equipment with application , allow / deny?' For every event sound? Really? Lennart -- Lennart PoetteringR

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Lennart Poettering at 11/02/10 00:25 did gyre and gimble: > On Tue, 09.02.10 18:51, Colin Guthrie (gm...@colin.guthr.ie) wrote: > >>> By the way normally only the users who are in the audio group are >>> allowed to access audio (not entirely sure how this is handled with >>> osx

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 20:07, Markus Rechberger (mrechber...@gmail.com) wrote: > > Bypassing this layer and accessing things directly is not IMO a good > > design. Everything is possible with the appropriate mechanisms in place > > and no functionality is sacrificed, but you have to be prepared to > > a

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 18:51, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > By the way normally only the users who are in the audio group are > > allowed to access audio (not entirely sure how this is handled with > > osx though), so it's not like a random user is allowed to access the > > audio devic

Re: [pulseaudio-discuss] system-wide daemon

Dnia 2010-02-10, śro o godzinie 16:45 -0700, Andrew McNabb pisze: > I'm not arguing that it's practical to do, but an ideal multiseat > system > would be able to give each user two dedicated channels, so they can > each > plug in their own set of headphones (modern surround sound cards have > tons

Re: [pulseaudio-discuss] system-wide daemon

On Thu, Feb 11, 2010 at 12:16:44AM +0100, Lennart Poettering wrote: > > This is nonsense. I am not sure how your ears are constructed, but on > a multiseat system if you want to share a soundcard between two seats, > where would you put the speakers so that the two users have the same > distance f

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 10:45, Maarten Bosmans (mkbosm...@gmail.com) wrote: > The other mode is the system-wide daemon mode. This follows more the > traditional unix model of a dedicated pulse user running a daemon to > which other users can connect. The system mode is more applicable to > an audio serve

Re: [pulseaudio-discuss] system-wide daemon

On Mon, 08.02.10 19:11, olin.pulse@shivers.mail0.org (olin.pulse@shivers.mail0.org) wrote: > PA is a system that manages access to a hardware resource, in a network > distributed context. Such a system must have mechanism for managing > authentication and privileges -- one that works in a

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 14:51, Bill Cox (waywardg...@gmail.com) wrote: > The power savings on a laptop will be so close to zero, you couldn't > measure the improvement in battery life. 40 interupts per second > (what raw ALSA does) compared to streaming 22KB per seccond to the > sound card is too small

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 11:32, Colin Guthrie (gm...@colin.guthr.ie) wrote: > One is the fact that why should a module be loaded into a system-wide > component for a specific user? e.g. user A pairs his bluetooth headset > which will require that the bluetooth sink becomes available - this > should only b

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 05:50, Bill Cox (waywardg...@gmail.com) wrote: > > Here's what I don't understand. Why doesn't PA run in system-wide > mode, but still do all the same user-permission checks it does now, > and only authorize the current user to access the sound card? Because that is extraordin

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 09:59, Markus Rechberger (mrechber...@gmail.com) wrote: > this is another wrong assumption, libusb uses raw USB access, if every > user would have access > to USB some devices might be damaged. > Sane would need to be serverbased, full raw access to the usb bus > would seriously b

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Lennart Poettering at 10/02/10 22:36 did gyre and gimble: > On Tue, 09.02.10 09:43, Markus Rechberger (mrechber...@gmail.com) wrote: > >>> Indeed. PA is principally meant to be run per-user. Each user logged in >>> will have their own PA process running and each will monitor a s

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 08:54, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Yeah, if we have permission on the device, we use it, otherwise it's > ignored. When users are switched away, CK fires off dbus signals and we > recheck our device access etc. We don't accept any input from alsa when > we do not

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10.02.10 07:14, David Henningsson (launchpad@epost.diwic.se) wrote: > But printers are more of a system-wide resource, and for some use cases, > so is the soundcard. This is nonsense. I am not sure how your ears are constructed, but on a multiseat system if you want to share a soundc

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 17:59, Markus Rechberger (mrechber...@gmail.com) wrote: > > On Tue, Feb 9, 2010 at 5:17 PM, Bill Cox wrote: > > The corking stuff in PA is very cool.  I don't think anyone objects to > > it.  But couldn't we quell all the "PA stinks!" posts by just allowing > > some processes/gr

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 22:52, David Henningsson (launchpad@epost.diwic.se) wrote: > Colin Guthrie wrote: > > 'Twas brillig, and Jeremy Nickurak at 09/02/10 19:24 did gyre and gimble: > > This whole thing has been discussed to death, and I really don't feel > > like being drawn into the whole thing a

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 18:41, Tanu Kaskinen (ta...@iki.fi) wrote: > ti, 2010-02-09 kello 11:17 -0500, Bill Cox kirjoitti: > > The corking stuff in PA is very cool. I don't think anyone objects to > > it. But couldn't we quell all the "PA stinks!" posts by just allowing > > some processes/groups/users

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 12:24, Jeremy Nickurak (jer...@nickurak.ca) wrote: > On Tue, Feb 9, 2010 at 09:41, Tanu Kaskinen wrote: > > > That's easier said than done. Only one process can have direct access to > > the sound card at a time. Each user has his own pulseaudio instance > > running. How do you

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 11:17, Bill Cox (waywardg...@gmail.com) wrote: > The corking stuff in PA is very cool. I don't think anyone objects to > it. But couldn't we quell all the "PA stinks!" posts by just allowing > some processes/groups/users to have constant access to audio? Tsss. This is a pretty

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 09:27, Bill Cox (waywardg...@gmail.com) wrote: > I think this is one area where PulseAudio could be improved, though I > can't quite figure out how! Surely, there must be some way to allow > specific processes or users to have full sound access, while otherwise > sticking to the

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 09:43, Markus Rechberger (mrechber...@gmail.com) wrote: > > Indeed. PA is principally meant to be run per-user. Each user logged in > > will have their own PA process running and each will monitor a system > > service called "ConsoleKit" which tracks which user is active. We adher

Re: [pulseaudio-discuss] system-wide daemon

On Mon, 08.02.10 21:01, olin.pulse@shivers.mail0.org (olin.pulse@shivers.mail0.org) wrote: > > Bill Cox: > > While the "right" way is not system-wide mode, in practice, I find > > system-wide mode to be very stable and usable on Ubuntu systems that > > have multiple users trying to send

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 09.02.10 03:16, Markus Rechberger (mrechber...@gmail.com) wrote: > > On Tue, Feb 9, 2010 at 3:01 AM, wrote: > > Bill Cox: > >> While the "right" way is not system-wide mode, in practice, I find > >> system-wide mode to be very stable and usable on Ubuntu systems that > >> have multiple

Re: [pulseaudio-discuss] system-wide daemon

On Sun, 07.02.10 22:54, Bill Cox (waywardg...@gmail.com) wrote: > Finally, disable group-based authentication to use the sound system. > Edit /etc/pulse/system.pa. Find the line that reads: > load-module module-native-protocol-unix > and change it to read: > load-module module-native-protoc

Re: [pulseaudio-discuss] system-wide daemon

The power savings on a laptop will be so close to zero, you couldn't measure the improvement in battery life. 40 interupts per second (what raw ALSA does) compared to streaming 22KB per seccond to the sound card is too small to care. You wont notice any improvement. On Wed, Feb 10, 2010 at 2:26

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Arun Raghavan at 10/02/10 19:26 did gyre and gimble: > On Wed, 2010-02-10 at 11:16 -0500, Bill Cox wrote: >> Ok, the new "glitchless" code sounds cool. Reducing the interrupts >> seems close to pointless from a power savings view, unless we're in an >> embedded environment where

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 2010-02-10 at 11:16 -0500, Bill Cox wrote: > Ok, the new "glitchless" code sounds cool. Reducing the interrupts > seems close to pointless from a power savings view, unless we're in an > embedded environment where we slow down the CPU and lower it's power > on sub-second intervals. Otherw

Re: [pulseaudio-discuss] system-wide daemon

2010/2/10 samuel : > On Wed, 10 Feb 2010 10:45:33 +0100 > Maarten Bosmans wrote: >> Perhaps the confusion stems from the fact that PulseAudio has two >> different modes. The normal per-user mode, which should almost always >> be used, uses the model of a single user having access to the hardware >

Re: [pulseaudio-discuss] system-wide daemon

Ok, the new "glitchless" code sounds cool. Reducing the interrupts seems close to pointless from a power savings view, unless we're in an embedded environment where we slow down the CPU and lower it's power on sub-second intervals. Otherwise, copying the data the data to the sound buffer will hea

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Bill Cox at 10/02/10 10:50 did gyre and gimble: > Here's what I don't understand. Why doesn't PA run in system-wide > mode, but still do all the same user-permission checks it does now, > and only authorize the current user to access the sound card? Is > there any advantage in

Re: [pulseaudio-discuss] system-wide daemon

Here's what I don't understand. Why doesn't PA run in system-wide mode, but still do all the same user-permission checks it does now, and only authorize the current user to access the sound card? Is there any advantage in running the whole PA daemon in user space? Why have multiple PA processes

Re: [pulseaudio-discuss] system-wide daemon

On Wed, 10 Feb 2010 10:45:33 +0100 Maarten Bosmans wrote: > 2010/2/9 : > > Maybe I'm wrong. I can't figure out *what* the model is, really. > > When I click on padevchooser's "Configure Local Sound Server" > > entry, I get a window whose "Network Server" tab lets me "enable > > network access to

Re: [pulseaudio-discuss] system-wide daemon

Bah, wrong thread 2010/2/10 Maarten Bosmans : > 2010/2/9  : >> Maybe I'm wrong. I can't figure out *what* the model is, really. When I click >> on padevchooser's "Configure Local Sound Server" entry, I get a window whose >> "Network Server" tab lets me "enable network access to local sound devices

Re: [pulseaudio-discuss] system-wide daemon

2010/2/9 : > Maybe I'm wrong. I can't figure out *what* the model is, really. When I click > on padevchooser's "Configure Local Sound Server" entry, I get a window whose > "Network Server" tab lets me "enable network access to local sound devices." > Furthermore, I can set or clear a checkbox for

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 10/02/10 08:59 did gyre and gimble: > On Wed, Feb 10, 2010 at 9:54 AM, Colin Guthrie wrote: >>> Here's another analogy; what about the printer? If printers were >>> considered a part of the seat, then user Bar wouldn't have more right to >>> print a document

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 10/02/10 06:51 did gyre and gimble: > Also imagine TV tuners, webcams are basically handled the same way. > One user might want to capture a TV movie, while the other one doesn't > need access to it. The user may want to do that but it doesn't mean that they

Re: [pulseaudio-discuss] system-wide daemon

On Wed, Feb 10, 2010 at 9:54 AM, Colin Guthrie wrote: > 'Twas brillig, and David Henningsson at 10/02/10 06:14 did gyre and gimble: >> Colin Guthrie wrote: >>> 'Twas brillig, and David Henningsson at 09/02/10 21:52 did gyre and gimble: I wrote down a few use cases here, I'm sure there are mor

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and David Henningsson at 10/02/10 06:14 did gyre and gimble: > Colin Guthrie wrote: >> 'Twas brillig, and David Henningsson at 09/02/10 21:52 did gyre and gimble: >>> I wrote down a few use cases here, I'm sure there are more: >>> >>> https://wiki.ubuntu.com/BluePrints/multiuser-soun

Re: [pulseaudio-discuss] system-wide daemon

On Wed, Feb 10, 2010 at 7:14 AM, David Henningsson wrote: > Colin Guthrie wrote: >> 'Twas brillig, and David Henningsson at 09/02/10 21:52 did gyre and gimble: >>> I wrote down a few use cases here, I'm sure there are more: >>> >>> https://wiki.ubuntu.com/BluePrints/multiuser-soundcards-pulseaudio

Re: [pulseaudio-discuss] system-wide daemon

Colin Guthrie wrote: > 'Twas brillig, and David Henningsson at 09/02/10 21:52 did gyre and gimble: >> I wrote down a few use cases here, I'm sure there are more: >> >> https://wiki.ubuntu.com/BluePrints/multiuser-soundcards-pulseaudio > > For user Foo, the sound card sounds like it's dedicated for

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and David Henningsson at 09/02/10 21:52 did gyre and gimble: > I wrote down a few use cases here, I'm sure there are more: > > https://wiki.ubuntu.com/BluePrints/multiuser-soundcards-pulseaudio For user Foo, the sound card sounds like it's dedicated for Foo. If this is the case the

Re: [pulseaudio-discuss] system-wide daemon

Colin Guthrie wrote: > 'Twas brillig, and Jeremy Nickurak at 09/02/10 19:24 did gyre and gimble: > This whole thing has been discussed to death, and I really don't feel > like being drawn into the whole thing again. >From what I've read here, I'm afraid it's going to keep coming up until we solve

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Michał Sawicz at 09/02/10 20:57 did gyre and gimble: > Dnia 2010-02-09, wto o godzinie 19:31 +, Colin Guthrie pisze: >> I wouldn't call this overdesign. Quite the opposite. Yes to get this >> rather bizarre scenario working it would be complex, but to make it >> work >> out o

Re: [pulseaudio-discuss] system-wide daemon

Dnia 2010-02-09, wto o godzinie 21:57 +0100, Michał Sawicz pisze: > 4. there's a dialog on the active user's session with 'User tries > to access your audio equipment with application , allow / deny?' > 5. if the active user agrees, the remote user is able to play, > otherwise > it remains

Re: [pulseaudio-discuss] system-wide daemon

Dnia 2010-02-09, wto o godzinie 19:31 +, Colin Guthrie pisze: > I wouldn't call this overdesign. Quite the opposite. Yes to get this > rather bizarre scenario working it would be complex, but to make it > work > out of the box in this way in PA itself is far from simple. I've > already > listed

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Jeremy Nickurak at 09/02/10 19:24 did gyre and gimble: > On Tue, Feb 9, 2010 at 09:41, Tanu Kaskinen > wrote: > > That's easier said than done. Only one process can have direct access to > the sound card at a time. Each user has his own pulseaudio i

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 09/02/10 19:07 did gyre and gimble: >>> How about a FM USB Transceiver which uses UAC (USB Audio Class) >>> Why the heck should only the person sitting infront of it be allowed to use >>> it >>> The person sitting infront of it could listen to audio while an

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 09:41, Tanu Kaskinen wrote: > That's easier said than done. Only one process can have direct access to > the sound card at a time. Each user has his own pulseaudio instance > running. How do you implement constant access in such scenario? I fear > it would require a major r

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 7:51 PM, Colin Guthrie wrote: > 'Twas brillig, and Markus Rechberger at 09/02/10 18:25 did gyre and gimble: >>> iTunes *requests* nothing. It simply *adheres* to what it has been told >>> is happening. The same would be true of any application that listens to >>> the PulseAu

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 09/02/10 18:25 did gyre and gimble: >> iTunes *requests* nothing. It simply *adheres* to what it has been told >> is happening. The same would be true of any application that listens to >> the PulseAudio generated cork notifications (IOW what iTunes and VLC a

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 6:54 PM, Colin Guthrie wrote: > 'Twas brillig, and Markus Rechberger at 09/02/10 14:52 did gyre and gimble: >>> Can you demonstrate this? >>> >>> In the past when I've tested this behaviour on OSX (it was quite a while >>> ago) it behaves exactly as I described above, and I'

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and olin.pulse@shivers.mail0.org at 09/02/10 00:11 did gyre and gimble: > OK, so that's X11. I cannot figure out what PA's mechanism for this is. I sort > of get the sense, from this per-user-login server model that PA has the > horrible one-persone/one-computer model of "the per

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 09/02/10 14:52 did gyre and gimble: >> Can you demonstrate this? >> >> In the past when I've tested this behaviour on OSX (it was quite a while >> ago) it behaves exactly as I described above, and I've literally just >> now re-tested this on a colleagues Mac

Re: [pulseaudio-discuss] system-wide daemon

On 9 Feb 2010, olin verbalised: > OK, so that's X11. I cannot figure out what PA's mechanism for this is. I sort > of get the sense, from this per-user-login server model that PA has the > horrible one-persone/one-computer model of "the person at the console is the > person using the computer," wh

Re: [pulseaudio-discuss] system-wide daemon

They way I worked out a similar situation (I am doing an ssh from the box into the box and sometimes from a different box into it) was to setup the PA of the user I ssh as and it IS a user that I would never login directly as to use PA over the network. So as long as someone is logged in then it's

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 5:17 PM, Bill Cox wrote: > The corking stuff in PA is very cool.  I don't think anyone objects to > it.  But couldn't we quell all the "PA stinks!" posts by just allowing > some processes/groups/users to have constant access to audio? > > Comparisons to MAC and Windows have

Re: [pulseaudio-discuss] system-wide daemon

ti, 2010-02-09 kello 11:17 -0500, Bill Cox kirjoitti: > The corking stuff in PA is very cool. I don't think anyone objects to > it. But couldn't we quell all the "PA stinks!" posts by just allowing > some processes/groups/users to have constant access to audio? That's easier said than done. Only

Re: [pulseaudio-discuss] system-wide daemon

The corking stuff in PA is very cool. I don't think anyone objects to it. But couldn't we quell all the "PA stinks!" posts by just allowing some processes/groups/users to have constant access to audio? Comparisons to MAC and Windows have been going on for a while, and the PA guys are basically r

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 4:44 PM, Ng Oon-Ee wrote: > On Tue, 2010-02-09 at 15:52 +0100, Markus Rechberger wrote: > >> 1. default Mac from a company >> 2. open a terminal and play an mp3 with mplayer as normal user >> 3. going to another PC and logging in with ssh (as root) and playing >> an mp3 ) -

Re: [pulseaudio-discuss] system-wide daemon

On Tue, 2010-02-09 at 15:52 +0100, Markus Rechberger wrote: > 1. default Mac from a company > 2. open a terminal and play an mp3 with mplayer as normal user > 3. going to another PC and logging in with ssh (as root) and playing > an mp3 ) -- works > 4. again going to another PC and in order you ca

Re: [pulseaudio-discuss] system-wide daemon

> Can you demonstrate this? > > In the past when I've tested this behaviour on OSX (it was quite a while > ago) it behaves exactly as I described above, and I've literally just > now re-tested this on a colleagues Mac (latest version): > >  1. Enable "Fast User Switching" (System Settings -> Accoun

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 09/02/10 08:43 did gyre and gimble: > On Tue, Feb 9, 2010 at 9:38 AM, Colin Guthrie wrote: >> 'Twas brillig, and Markus Rechberger at 09/02/10 02:16 did gyre and gimble: >>> On Tue, Feb 9, 2010 at 3:01 AM, wrote: Bill Cox: > While the "right" way

Re: [pulseaudio-discuss] system-wide daemon

I think this is one area where PulseAudio could be improved, though I can't quite figure out how! Surely, there must be some way to allow specific processes or users to have full sound access, while otherwise sticking to the one-user-at-a-time model. I'm trying to port SBL (another console screen

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 9:38 AM, Colin Guthrie wrote: > 'Twas brillig, and Markus Rechberger at 09/02/10 02:16 did gyre and gimble: >> On Tue, Feb 9, 2010 at 3:01 AM,   wrote: >>> Bill Cox: While the "right" way is not system-wide mode, in practice, I find system-wide mode to be very stab

Re: [pulseaudio-discuss] system-wide daemon

'Twas brillig, and Markus Rechberger at 09/02/10 02:16 did gyre and gimble: > On Tue, Feb 9, 2010 at 3:01 AM, wrote: >> Bill Cox: >>> While the "right" way is not system-wide mode, in practice, I find >>> system-wide mode to be very stable and usable on Ubuntu systems that >>> have multiple users

Re: [pulseaudio-discuss] system-wide daemon

On Tue, Feb 9, 2010 at 3:01 AM, wrote: > Bill Cox: >> While the "right" way is not system-wide mode, in practice, I find >> system-wide mode to be very stable and usable on Ubuntu systems that >> have multiple users trying to send sound to the speakers. > > So, I'm still wondering: what *is* the

Re: [pulseaudio-discuss] system-wide daemon

Bill Cox: > While the "right" way is not system-wide mode, in practice, I find > system-wide mode to be very stable and usable on Ubuntu systems that > have multiple users trying to send sound to the speakers. So, I'm still wondering: what *is* the "right way" for this use case? Is it the case th

Re: [pulseaudio-discuss] system-wide daemon

On Sun, Feb 7, 2010 at 10:54 PM, Bill Cox wrote: > To set system-wide mode: [...] The method for Jaunty/Karmic differs slightly from that for Lucid, but one can always look in /etc/default/pulseaudio for pointers. I try to keep this file updated. Best, -Dan __

Re: [pulseaudio-discuss] system-wide daemon

While the "right" way is not system-wide mode, in practice, I find system-wide mode to be very stable and usable on Ubuntu systems that have multiple users trying to send sound to the speakers. It's easy to get Ubuntu Karmic and Lucid to use PulseAudio in system-wide mode. For systems that require

Re: [pulseaudio-discuss] System-wide daemon howto/best practices

On Tue, 04.09.07 00:10, Jan Kasprzak ([EMAIL PROTECTED]) wrote: > : So in > : the end we might end up with the optional solution of running a > : tiny/dumbed-down pa system instance which sessions connect to. But > : that's way down on my TODO list, and will always stay optional since > : it is de

Re: [pulseaudio-discuss] System-wide daemon howto/best practices

Lennart Poettering wrote: : Inside RH we had a few disucssions how to handle multi-seat setups : with regards to audio best. Our conclusion was that audio cards should : be treated similar to mice and keyboards: i.e. each seat gets its own : pair of boxes (or a headphone) and they are not shared wi

Re: [pulseaudio-discuss] System-wide daemon howto/best practices

On Wed, 29.08.07 20:38, Jan Kasprzak ([EMAIL PROTECTED]) wrote: Hi! > on my home workstation I use a dual-seated setup (two monitors, two > keyboards, two VGA cards, etc. - two independent users). I am > looking for a way of using the sound card by both users > simultaneously (I have problem that