pulseaudio & jack2dbus are started, but Qtractor won't start

[71GA]

Hello,

Earlier I had alsa installed together with jack2 and both worked fine - I could record my songs in Qtractor without any problems.

But I reecently bought GuitarPro software for Linux which needs a pulseaudio to work. So I installed the pulseaudio and It is
working fine by itself. I can start/stop it using commands:

Code: Select all

pulseaudio --start
pulseaudio --kill

Now the problems begin. I had to uninstall jack2 and swap it for jack2dbus which works with pulseaudio (jack2 doesn't). I allso
wrote two scripts for starting the jack2dbus in two separate configurations

Hardware default audio (Nvidia) for playback and USB audio interface (Scarlet 2i4) for recording:

Code: Select all

#!/bin/bash
jack_control start
jack_control eps realtime true 		
jack_control ds alsa 				
jack_control dps period 265 		
jack_control dps playback hw:0,0	
jack_control dps capture hw:USB	

USB audio interface (Scarlet 2i4) for playback and recording.

Code: Select all

#!/bin/bash
jack_control start
jack_control eps realtime true 		
jack_control ds alsa 				
jack_control dps device hw:USB 		
jack_control dps period 265 	

THE START PROCEDURE
I first start the pulseaudio and check if it is running.

Code: Select all

$ pulseaudio --start
$ ps aux | grep pulse
ziga      4171 48.0  0.2 520004 15328 ?        S<l  14:22   0:00 pulseaudio --start
ziga      4176  0.0  0.0  76628  2552 ?          S    14:22   0:00 /usr/lib/pulse/gconf-helper
ziga      4179  0.0  0.0  10820  1076 pts/2    S+   14:22   0:00 grep pulse

then I start the jack server using one of the scripts above and check if jack is running.

Code: Select all

$ jack_control status
--- status
started

At this instance when everything seems to be running when I start Qtractor or Ardour I allways get the error.
The audio/MIDI engine could not be started! In the image check allso the console in the background.

So why isn't Qtractor working?

[AndreeeCZ]

Because jack isn't running?

The code you pasted differs from the on in the screenshot.

[bluebell]

Did you try to run Pulseaudio on top of jack?

http://www.marzen.de/Holger/pulseaudio_and_jack/

[71GA]

Did you try to run Pulseaudio on top of jack?

http://www.marzen.de/Holger/pulseaudio_and_jack/

Not yet. I have been trying the other way arround. To run JACK on top of the pulseaudio like described here (check the "new new way" which is a bit sloppy): https://wiki.archlinux.org/index.php/Pu ... rough_JACK

[tnovelli]

I tried that "new new way"... sounds promising but I ran into too many headaches. IIRC it requires jackdbus which hasn't been reliable.

Then I looked to see what AVLinux does... it uses JACK *instead of* Pulse, i.e. redirects ALSA apps to JACK. It's not perfect but close enough for most purposes - you can use youtube, soundcloud, etc without stopping JACK.

[bluebell]

I don't run jackdbus. I simply run a script on session's start that starts jackd. On my notebook it looks for available interfaces before, on my desktop it always uses my Scarlett 2i2.

That's all.

For Pulseaudio apps you can decide if you start the pulseaudio daemon in a script before the application gets startet, e.g. like this:

pulseaudio -D
skype $*
pulseaudio --kill

Or clients start pulseaudio automagically by having autospawn=yes in /etc/pulse/client.conf

You have to configure jack audio sink in /etc/pulse/default.pa. Then pulse is simply a jack client.