Page 1 of 1
Jack updated not working anymore
Posted: Tue Apr 16, 2013 6:18 am
by Bernd
Hello,
I am pretty new in this forum, but while I produce digital music with hydrogen, rosegarden and Ardour, I think I am quite at the right place to talk to you about many themes, I am very interested in. But now I have a fundamental problem. I can't make digital music any longer.
Yesterday I installed Ardour 3 on my ubuntu studio system (10.04). Ardour 2 was working with Jack satisfying. Ardour 3 was a chellenge. But now Jack server seems to be running, but the client is not able to connect to it. I was asked for update to jackd 0.121.3 and I did from the resource.
Starting Jack audio connection kit fails in connecting to the server.
I would be very happy, if anybody coud give me a hint.
I am sorry, the log is German.
Code: Select all
08:09:06.847 Protokollierung gestartet --- Di. Apr 16 08:09:06 2013 ---
08:09:06.871 Steckfeld deaktiviert.
08:09:06.918 Statistik zurückgesetzt.
08:09:06.939 Schaubild der ALSA-Verbindungen geändert.
08:09:07.134 ALSA-Verbindung geändert.
08:09:11.297 JACK startet...
08:09:11.298 /usr/bin/jackd -v -t9999 -dalsa -dhw:0 -r44100 -p128 -n2 -zs
08:09:11.325 JACK wurde mit PID = 3409 gestartet.
08:09:11.327 JACK wurde angehalten mit Rückgabewert = 1.
08:09:11.328 Post-shutdown script...
08:09:11.328 killall jackd
jackd 0.121.3
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
getting driver descriptor from /usr/lib64/jack/jack_oss.so
Unknownage with option 'd'
Options for driver 'alsa':
-C, --capture capture ports. Optionally set device (default: none)
-n, -- ports. Optionally set device (default: none)
--- un handling (default: none)
-m, -- r the output (default: none)
-jackd: Kein Prozess gefunden
08:09:11.738 Post-shutdown script terminated mit Rückgabewert = 256.
08:09:13.363 Keine Verbindungsaufnahme als Client zum JACK-Server möglich. - Overall operation failed. - Verbindungsaufnahme zum Server gescheitert. Bitte sehen Sie im Meldungsfenster nach weiteren Informationen.
The limits.conf tells this part:
Code: Select all
@audio - rtprio 99
@audio - memlock 3084192
@audio - nice -10
The audio group has the current user (oslt) as member:
audio
29:pulse,oslt,timidity
Re: Jack updated not working anymore
Posted: Tue Apr 16, 2013 7:32 am
by autostatic
Try lowering your timeout setting (-t9999) to something below 5000:
Code: Select all
-t, --timeout int
Set client timeout limit in milliseconds. The default is 500 msec. In realtime mode the client
timeout must be smaller than the watchdog timeout (5000 msec).
Re: Jack updated not working anymore
Posted: Tue Apr 16, 2013 7:13 pm
by Pablo
Welcome to the forum!
Note that for diagnosis and asking help you can run software in the default, English language by exporting LANG=C. For example, you have qjackctl in English by doing in a terminal:
This language change only affects the apps you run from this terminal.
Re: Jack updated not working anymore
Posted: Wed Apr 17, 2013 1:58 pm
by Bernd
Hello Paplo,
thank you for your info about Englisch Logfile.
Here you are.
Code: Select all
15:55:04.879 JACK is starting...
15:55:04.881 /usr/bin/jackd -v -t5000 -dalsa -dhw:0 -r44100 -p128 -n2 -zs
jackd 0.121.3
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_firewire.so
15:55:04.894 JACK was started with PID=3110.
no message buffer overruns
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
getting driver descriptor from /usr/lib64/jack/jack_oss.so
Unknownage with option 'd'
Options for driver 'alsa':
-C, --capture capture ports. Optionally set device (default: none)
-n, -- ports. Optionally set device (default: none)
-
15:55:04.914 JACK was stopped with exit status=1.
15:55:04.914 Post-shutdown script...
15:55:04.914 killall jackd
jackd: no process found
15:55:05.323 Post-shutdown script terminated with exit status=256.
15:55:07.025 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Note that for diagnosis and asking help you can run software in the default,
Which Software do you mean?
Thank you!
Re: Jack updated not working anymore
Posted: Wed Apr 17, 2013 2:05 pm
by Bernd
AutoStatic wrote:Try lowering your timeout setting (-t9999) to something below 5000:
Code: Select all
-t, --timeout int
Set client timeout limit in milliseconds. The default is 500 msec. In realtime mode the client
timeout must be smaller than the watchdog timeout (5000 msec).
Thank you, AutoStatic,
but there is no change. Still the same.
Code: Select all
15:53:57.037 /usr/bin/jackd -v -t5000 -dalsa -d(voreinst.) -r44100 -p128 -n2 -zs
Bernd
Re: Jack updated not working anymore
Posted: Wed Apr 17, 2013 2:10 pm
by Bernd
I changed driver in setup. And voila Jack is running. I changed ALSA to OSS.
Is this well done?
Bernd
Re: Jack updated not working anymore
Posted: Wed Apr 17, 2013 4:56 pm
by Pablo
You are welcome!
Which Software do you mean?
I meant that any piece of software will run in English if you previously export LANG=C.
Back to the issue, what does the terminal say to these commands?
cat /proc/asound/cards
arecord -l && aplay -l
Re: Jack updated not working anymore
Posted: Sat Apr 20, 2013 6:41 pm
by Bernd
Solved, in the setup of jack control I changed ALSA to OSS and voila: solved.
Thank you for your patience.
Bernd
Re: Jack updated not working anymore
Posted: Thu May 09, 2013 5:16 am
by Bernd
I don't know if it was a good idea to chance als to oss interface, there are some quality losses with Rosegarden, but worst of all, the usb microphone isn't routed to ardour. But if i change to also interface again (in jack control) jack crashes again,
What can I do?
I like making music production a lot, but I need microphone input.
Here are my settings:
- jack control
- jack.gif (40.81 KiB) Viewed 1821 times
Thanks for any help!
Bernd
Re: Jack updated not working anymore
Posted: Thu May 09, 2013 5:03 pm
by Pablo
Quoting myself:
What does the terminal say to these commands?
cat /proc/asound/cards
arecord -l && aplay -l
Re: Jack updated not working anymore
Posted: Thu May 09, 2013 7:21 pm
by autostatic
You're using different audio interfaces for input and output. This can cause issues.
29:pulse,oslt,timidity