Burkhard Ritter wrote: Yes, you can change the default sound chip/card in PulseAudio. You'll need to redo this every time you reboot. However, that didn't solve my problems with applications using PulseAudio under Fedora 9. For some reason which I don't understand, the applications were not picking up on my changed PulseAudio default. I then tried to find which configuration files I could change in PulseAudio to make my selected sound chip/card/device the default so that all sound applications would use it, as you can do with ALSA. I was never successful. And I was never able to find good documentation telling me how to change the configuration files in PulseAudio. After a month of trying, I said 'to hell with it' and disabled my motherboard sound chip. That solved my problems. If you know how to tell PulseAudio what order of sound card/chip/devices to use and have PulseAudio pass this on to sound applications, please tell me. But don't tell me changing the default by right mouse click in that one applet (sorry, I can't tell you now which applet that is because I've removed PulseAudio from my system) works-- it didn't work for my vanilla Fedora 9 system with PlanetCCRMA applications. I wasn't even running a real time kernel. Best, Stephen.

On Sat, May 16, 2009 at 02:32:27PM +0200, Esben Stien wrote: Let the gods protect us from that. I'm having enough misery with 'desktop integration' in jack2 as it is. Ciao, -- FA Io lo dico sempre: l'Italia è troppo stretta e lunga.

On Sat, May 16, 2009 at 08:59:27AM -0400, Dave Phillips wrote: Whenever I find such a persistent daemon that I don't need and don't want, I feel a strong urge to do something very persistent to those who write or integrate these things. And it's getting worse with each new release. Anyone knows how to get rid of that ~/.gvfs thing and its associated daemons ? Permanently ? I don't run Gnome so I don't want it any more than I want DesktopDirs, console session managers and other hideous things that slowly but surely are turning Linux into something that is even worse than Windows. According to my book the .gvfs thing is malware, as it even prevents root from cleaning up the mess. Ciao, -- FA Io lo dico sempre: l'Italia è troppo stretta e lunga.

I'm running Gentoo and fluxbox for precisely the reasons you describe. Alex. On Sat, May 16, 2009 at 6:03 PM, Joe Hartley <jh(a)brainiac.com> wrote: -- Parchment Studios (It started as a joke...)

Dave Phillips wrote: Thanks for bringing this up, Dave. I wasn't going to say anything more about PulseAudio, but now I can add another data point to the discussion. Vanilla Fedora 9, PlanetCCRMA audio repositories, DangerMouse's RealPlayer 11 install, Yamaha MG10/2 mixer, HP workstation x4000 tower, Sound Blaster Audigy2 ZS PCI card, Crown D-45 power amp, and Event 20/20 (un-powered) studio reference monitors. Line ins and outs from the HP motherboard sound chip and the Audigy2 card routed to the Yamaha mixer. Setting PulseAudio to default to the Audigy2 card. If memory serves, XMMS played to the Audigy2 line out. The Yamaha saw the output and music played through the Event 20/20 monitors. Real Player 11 played to the HP tower case speaker. Nothing showed up on the line out from the motherboard chip at the Yamaha mixer. Fedora 9 had this very annoying habit of trying to speed up the boot process (possibly by cutting down on wait time for devices to show up, I don't know for certain.) As a result the IDE hard drive was always detected before the SCSI hard drive (since Linux and the GRUB boot information was on the SCSI drive, I had to pull the IDE drive out of the tower), the tower's floppy drive was never usable under Fedora 9 (I had to get a USB floppy drive), and about 1 reboot time in 10 the Audigy2 card was detected before the motherboard sound chip. In those times when the Audigy2 was detected first, all sound applications would use the Audigy2. I was happy. Then the power would go off, and it was reboot time with a very low likelihood the Audigy2 would get spotted before the motherboard sound chip. I'll see what happens with Fedora 11 when it's out soon. And I would like to hear what the original poster of this thread finally did to solve his problem with PulseAudio. Or perhaps it hasn't been solved? Best, Stephen.

On Sat, May 16, 2009 at 8:11 PM, Esben Stien <b0ef(a)esben-stien.name> wrote: Or you can simply configure Alsa to use Jack with an .asoundrc. Plenty of examples on the interlink for most sound devices, including multiple devices. A config file is a config file This has been a distro fault for sometime, if indeed this is the case. And i'd dare venture that if distros had embraced Jack as quickly and enthusiastically as that had Pulse (with almost no warning to users) we wouldn't know what pulse was. I can't believe app builders would have anymore difficulty writing audio pugins for Jack, than they did with Pulse. Again, as a 'power' user, i'm mystified by the apparent lack of ongoing enthusiasm in the debian/ubuntu world for unifying into a linux sound management system that would serve both domestic and professional users. Did the Jack team run over someone's cat? Why? Surfing the interlink brings countless tales of woe, with users struggling to build a decent setup to cater for their musical needs, be it just listening or creating, because removing pulse shreds their setup, and toasts just about anything worthwhile. While the dependencies invoked by the debian/ubuntu builders may be justified in an attempt to provide as smooth and easy a setup for new and otherwise users, again, we could have done all this with jack, and saved a lot of pain all round, had app builders considered modernising their fine programmes to use jack as the primary server by default. Alsa provided, and continues to provide a sound device management system equal to or greater than anything in a commerical sphere, but Jack also provides users of all ilks with the means to enjoy the freedoms of unlimited ports and multiple apps running at the same time. Again, who ran over who's cat? And add another layer of complexity for the user, who, when something goes wrong, has even more to figure out, and is even more reliant on the generosity and patience of devs and experienced users, if the time is available. Please don't say Pulse works automatically, or even just works. Because the interlink says otherwise. Not at all. I dumped Pulse in Hardy when it declined to recognise Jack as a valid alternative, and wouldn't shut down, or give way. Those that know me know i pursue solutions, and ask questions, relentlessly, to find an answer for not only myself, but users less experienced in working in linux. (The slightly less blind leading the blind) But in this case i got multiple versions of: "Sounds like your OS is corrupted. You'll have to reinstall." Windows thinking. Yes? Not a good sign then. You may not recognise it as an issue Esben, but others do. What is more disturbing is the determination to feed compulsory Pulse to all whilst still in a still maturing state, and still with much to do. And let's not forget here, you're a highly experienced user, who knows how to find a solution. For poor little Sally Singalong trying to record her first tune, it's a world of mystery, and beyond her capacity to fix. I'm pleased to here you have a working setup that just goes. But i wonder, if we were to do a straw poll, how many users actually enjoy the same experience as you, and if not, why. Jack's not perfect in this regard either, but at least there's a chance to quickly narrow down the problem, and identify possible solutions. I'm with Fons on this one. Too much like chasing Windows, instead of finessing the wonderful attributes Linux already has to offer. Alex. p.s. Did the Jack team really runover someone's cat? -- Parchment Studios (It started as a joke...)

On Saturday 16 May 2009 11:52:18 alex stone wrote: I love jack. Especially the routing flexibility. But I just switched one of my station loggin boxes from rotter which uses jack to darkice because I wanted to go from loggin one station on the box to loggin two. The box is a 1u rack mount machine with no onboard sound card. I hooked up two different usb sound cards to it. To do what I wanted with jack and rotter, I would have needed to be able to run two instances of jack on the box at the same time and have rotter designed to deal with that possibility. (Hmmm, I just had an idea. I will hold off until after I ask the list though.) So, does anyone know how I could have done what I needed to with jack in the mix and the hardware I had on hand? all the best, drew

On Saturday 16 May 2009 22:24:33 Justin Smith wrote: I will have to experiment with this. (perhaps my only one instance was bad memory and rdairplay and not jack... hmmm) In the particular instance I am intersted in here, I would want two different jackds running and two different instances of rotter, one to connect to each jack. I will have to see if rotter can deal with this and if not if I can patch it or get Nicholas intersted in making the change. (If needed.) http://www.aelius.com/njh/rotter/ for those interested. Thanks for the info. all the best, drew

And in a moment of irony, the Renoise team have just announced the release of Renoise 2.1. RC1. New feature? Jack Transport. :) Alex.

Fons Adriaensen schrieb: I thought I used to be able to enable/disable pulse audio from the gnome session configuration dialogue. Not any longer, in fact I just discovered that everything gnome session is completely broken in Ubuntu Intrepid. I have no idea how things do get started up when I log in and this used to be pretty transparent. So this seems to be a gnome issue. Note though, that I can kill pulse without any problems and that's exactly what I do for the occasional (increasingly rare) audio sessions I do. I agree that it should be simple to disable pulse audio or any other service; also, at least on Ubuntu, audio related configuration dialogues and control applications are scattered everywhere; without the pulseaudio applet (which wasn't enabled by default) I'd be lost. Nevertheless pulse solves issues: switching between onboard and usb card is easy (I used to edit asoundrc regularly), I have an overall volume for my usb card (which doesn't have a hardware mixer), I can play audio from firefox while listening to something else (don't ask me why, but it didn't work before). I can play audio over my friend's computer's soundcard over the network with two mouse clicks, which comes in handy. So all in all problems with pulseaudio seem to boil down to bad/scattered gui/configuration stuff and integration/distribution issues. Burkhard

Esben Stien wrote: To add to your response below... What I don't understand is why this process is not already an automated feature in the pulse applets? Was it a case of not enough time or was it purposefully left out of the mix? FWIW, I am running qjackctl and stopping pulse from the config cmd line settings. Once qjackctl has started jack it then allows pulse to connect. However I still have a problem with pulse not actually knowing that it has got jack inputs for other apps to access. It knows that it has jack outputs so why not the jack inputs? qjackctl tells me that I have two pulse ins and two pulse outs so I consider that a pulse bug or config issue. Either way why do I even have to think about this? Pulse can be made to work seamlessly with jack so why not add that feature to the automated toolset?