Jack Control

[Komputor]

Deleting the #'s from the file only seemed to make Jack WORSE! I am not sure what is going on here, but after modifying the file(taking away the #'s for every @audio line), starting up Jack again, It almost took over my whole system! First, Jack greyed out as if it was just not responding/crashed. Next, I couldn't force close Jack, and I couldn't even open a terminal window to kill it! After that, I started losing icons on my panel(esp. the important one that allows me to restart my system)! Apps started crashing in my dock that I have set up in the lower center of my desktop, and I resolved to going through System>Shut Down and selecting restart -but it only logged me out! I was able to restart again from the login screen but WOW! What is going on???
Should I just revert the limits.conf file and enter each line separately with a reboot after each to identify the culprit, or do I have too many instances of Ubuntu on my system that may be interfering with each other?

[Komputor]

Oh and I rebooted after taking away the #'s. Hope that helps!

[Komputor]

Success at last!! I think the problem was in my code (always trust the code). Instead of setting my "memlock" to a specified number, I just changed it to unlimited. Instead of having "nice" set to -19, I set it to -10.
I am not sure what I did with having it the other way before, but now Jack message output is as follows:
p, li { white-space: pre-wrap; } 21:39:41.291 Patchbay deactivated.
21:39:41.315 Statistics reset.
21:39:41.467 ALSA connection graph change.
21:39:41.620 ALSA connection change.
21:40:33.661 Startup script...
21:40:33.662 artsshell -q terminate
sh: artsshell: not found
21:40:34.064 Startup script terminated with exit status=32512.
21:40:34.065 JACK is starting...
21:40:34.065 /usr/bin/jackd -dalsa -dhw:0,0 -r44100 -p1024 -n2
jackd 0.118.0
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
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 1052490
21:40:34.096 JACK was started with PID=4640.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
21:40:36.191 Server configuration saved to "/home/komputor/.jackdrc".
21:40:36.193 Statistics reset.
21:40:36.705 Client activated.
21:40:36.707 JACK connection change.
21:40:36.713 JACK connection graph change.
#end of msg

And now Jack is showing RT up and running!

[Komputor]

Now to see about configuring Ardour, and others to play along!

[ken78724]

Komputer & cchhrriiss121212 Many, many thanks!!!!

Can someone post a sticky. you've done most valuable work UbuStudio users are crying for. But, not enough is said for me to reach the jack control solution you've achieved. I want to hear sound and get past what blocks me/all of us.

I pray someone will write a simple 1,2,3,,, it'd be welcomed. Please someone that can ,,, I'll pore the beer... Ken

[Komputor]

Ken,
Thank you very much, but every system is different as Chris said before. With that said, I don't think I can be of much help with this thread anymore, so I am moving on with the next step in another thread. Hope this helped you and any others having this issue.

[cchhrriiss121212]

@Komputer - Glad you got things running. If you are recording live instruments with ardour then you may want to experiment with lowering the frame rate to get a lower latency. Anything <=10ms will be good but it depends on the quality of soundcard you have, so anything integrated will not handle much.

@Ken - There should definately be a sticky on jack somehwere here but for the time being you can look at the community documentation.
Try starting a new thread and post the error messages you are getting just like this thread.

[rlameiro]

I should remind, that as from Lucid, the configuration file isn't at /etc/security/limits.conf, but on /etc/security/limits.d/audio.conf

refer to the Ubuntu Studio preparation help

https://help.ubuntu.com/community/Ub...dioPreparation

[cchhrriiss121212]

Good point, I'm not using lucid yet, but the StudioPrep document says this:

Since Ubuntu 10.10, the version of Jackd write all needed informations in this file

So is that an error?

I'd also like to know why this has been changed if anyone knows

[Komputor]

rlameiro,
I am not sure about that file location, just a heads up, I am running Ubuntu 10.04, Lucid and I do have the /etc/security/lmits.conf file that Jack uses. Unless you are referring to a different app/topic altogether.

So I opened that file in limits.d/audio.conf and here's my output:
# generated by jackd's postinst.
#
# Do not edit this file by hand, use
#
# dpkg-reconfigure -p high jackd
#
# instead.
@audio - rtprio 99
@audio - memlock unlimited
#@audio - nice -19

Is there anything wrong here? Let me know, Thanks!