On Sun, Feb 14, 2010 at 12:34 PM, Petrus de Calguarium wrote: That depends on what you want to do. If you are using midi just for fun, keeping pulseaudio should not hurt. Theoretically, pulseaudio should hand over the device to jack when jack needs it, and take it over when jack is done with it. I don't know if this is really the case practically. My jack runs with alsa backend and kmix' plain alsa sliders of work with jack. On the other hand, if you are using jack for low latency audio productional purposes, or if you simply want to have full control over your audio device, then it is best to get rid of pulseaudio. That's my way :) Orcan

Petrus de Calguarium wrote: If you need only MIDI, you can set up JACK to use the dummy input/output drivers, then you can continue to use PulseAudio. JACK MIDI is handled separately and (usually) forwarded to the ALSA sequencer interface (AFAIK, some sequencers like FluidSynth can also plug in directly at JACK level, but it's not the usual way), at which point it becomes the software sequencer's problem where to output the actual sound (and if you have hardware MIDI support, it doesn't reenter the system at all and should be transparently mixed in by the sound card). But if you use regular JACK sound, there's no reliable way to have JACK and PulseAudio use the same sound device at the same time, the best JACK can do is suspend PulseAudio's use of the device when it needs it, through a "device reservation" mechanism designed for this purpose. The JACK and PulseAudio developers think that's the best solution for the common use case and aren't interested in solutions like running JACK on top of PulseAudio (which would come with high latency costs) or emulating the JACK protocol in PulseAudio (quite complicated). It's possible to run PulseAudio on top of JACK, but that also comes with high latency, needs manual setup and is considered permanently experimental; the developers aren't interested in making that setup work out of the box. You also lose some PulseAudio features if you use that setup. I'm not convinced having 2 competing sound servers which can't fully interoperate is a good thing, but it's the current situation. Audio production stuff uses JACK, the rest of the applications have mostly standardized on PulseAudio (or some API which PulseAudio provides compatibility support for, like ALSA or ESD). Kevin Kofler

Petrus de Calguarium wrote: In qjackctl it's somewhere in the UI (or was last I checked), on the command line you need to pass it the correct switches. I think those are all for hardware MIDI and/or for a MIDI output port for external sequencers. The commonly-used software MIDI sequencers don't use these. Kevin Kofler

Hello Petrus, On Sunday 14 February 2010, 14:34, Petrus de Calguarium wrote: this worked for me back then http://www.harald-hoyer.de/linux/pulseaudio-and-jackd but I didn't try it with recent/current Fedora version. Regards -- Ariel Constenla-Haile La Plata, Argentina

Hello Petrus, On Monday 15 February 2010, 02:01, Petrus de Calguarium wrote: I forgot an interesting article http://www.passback.org.uk/music/fedora-music-intro/ and also to mention the Planet CCRMA repo, first thing I do after installing Fedora since a couple of versions is to enable that repo, for Fedora 12 x86_64 it will be rpm -iUv http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/... repo-1.1-2.fc12.ccrma.noarch.rpm More info on http://ccrma.stanford.edu/planetccrma/software/ [Although the CCRMA is a completely trustful source, last time there was a missing dependency I had to install manually: libffado-2.0-0.6.rc1.fc12.ccrma.x86_64 If you choose to install this repo, just to make sure, look at the different software logs for info; IIRC I've found this missing dep. on jackd log] Also notice that you may what to join the Fedora Music list https://admin.fedoraproject.org/mailman/listinfo/music There is an interesting thread in Dec. 2009 http://lists.fedoraproject.org/pipermail/music/2009-December/thread.html It's interesting also to read Orcan's [who already joined this thread] opinion about PA http://lists.fedoraproject.org/pipermail/music/2009-December/000496.html Regards -- Ariel Constenla-Haile La Plata, Argentina

On Mon, Feb 15, 2010 at 11:52 AM, Petrus de Calguarium wrote: True. But this is mostly due to the work of : The main SIG page is at https://fedoraproject.org/wiki/AudioCreation Everybody is welcome to join. Orcan

Ariel Constenla-Haile wrote: That's the "PulseAudio on top of JACK" solution. Probably the best solution if you need both PA and JACK at the same time. But: * not recommended (and AFAIK not fully supported) by upstream, * needs some setup tweaks. Having to kill PulseAudio, start JACK and restart PulseAudio manually at each session as described in those instructions is not that great, more tweaking (to your session autostart stuff) is needed to have this just work. * adds extra latency to all the PulseAudio-using apps, which tend to be the majority (but also those for which latency usually matters less; and some stuff like Phonon or those MIDI sequencers is quite flexible so you can output directly to JACK there). * loses you some of the features of PulseAudio, e.g. the support for multiple audio devices with automatic fallback to what's currently available, per-app device preferences etc. Still, yes, it's the best you can do if you need both PA and JACK simultaneously. Kevin Kofler