Hello everyone
I have a problem with Jack, I have 2 sound cards a Sound Blaster Live! and CMedia CMI 8738 chip.
Both sound cards once selected with a single input and single output to jack.
when you actually have 2 inputs and 3 outputs stereo.
I would understand if the problem is alsa drivers (which are upgraded to latest version) or jack that does not communicate with the ALSA drivers.
thanks for the answers
Hi!
jack messages will print your current jack setup and error messages if any. The problem could be in your setup but who knows. You should show the jack command at the very least! (line below “jack is starting…”)
Cheers! Pablo
hello
I can show the messages issued by jack when you start, so you can tell me what you think.
for the appearance of I / O missing you need to edit the file asoundrc ?
Copy and paste the messages starting jack
16:39:41.393 Startup script…
16:39:41.396 artsshell -q terminate
sh: artsshell: not found
16:39:41.820 Startup script terminated with exit status=32512.
16:39:41.822 JACK is starting…
16:39:41.823 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2
16:39:41.906 JACK was started with PID=15039.
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis 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
JACK compiled with System V SHM support.
cannot lock down memory for jackd (Cannot allocate memory)
loading driver …
apparent rate = 44100
creating alsa driver … hw:0|hw: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: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
JACK: unable to mlock() port buffers: Cannot allocate memory
JACK: unable to mlock() port buffers: Cannot allocate memory
16:39:44.027 Server configuration saved to “/home/daniele/.jackdrc”.
16:39:44.034 Statistics reset.
16:39:44.048 Client activated.
16:39:44.099 JACK connection change.
16:39:44.195 JACK connection graph change.
cannot lock down memory for RT thread (Impossibile allocare memoria)
Copy and paste the message stop jacks:
16:42:21.706 Client deactivated.
16:42:21.709 JACK is stopping…
jack main caught signal 15
16:42:21.912 JACK was stopped successfully.
16:42:21.913 Post-shutdown script…
16:42:21.915 killall jackd
jackd: nessun processo terminato
16:42:22.340 Post-shutdown script terminated with exit status=256.
thanks for ansewers
Type in the terminal: ‘ulimit -l’. (this is the memlock value, in kb of your RAM) You need “unlimited” or a high value. Check: http://jackaudio.org/faq
You are welcome. Pablo.
hello
add a further information: I do not know if memlock can cause I / O that are missing in jack.
jack in my configuration it works but I see i / o that exist physically.
means something to the configuration file asoundrc in this area?
I read the faq jack but can not find answers
thanks for the reply
This memlock thing has nothing to do with the .asoundrc file or alsa. Jack needs an unlimited or very high memlock amount. If it is very low for you, as a user, (64 or so… check with ‘ulimit -l’ (lowercase L)) you need to edit the /etc/security/limits.conf file and add the second line (see FAQ number 2), as long as you belong to the ‘audio’ group (check with ‘groups’). And then reboot. I am assuming you already have the first line (rtprio) as you are running jack with the realtime option.
Neither am I totally sure if the missing i/o are caused by this, but anyway I am afraid you haven’t set the memlock value, which you must do. “JACK: unable to mlock() port buffers: Cannot allocate memory”.
However, if you have a .asoundrc file that you think is causing the problem, you can always rename it (as .asoundrc.backup for example) and try again (no need to reboot). In fact, the .asoundrc file is not needed unless you have a reason and you know what you are doing. See the warning in: http://alsa.opensrc.org/.asoundrc
By the way, which distro are you running?
Cheers, Pablo
hello
I tried a set of jack in the setup option “no memory lock”
and messeges from this change now from this:
22:00:09.741 Startup script…
22:00:09.744 artsshell -q terminate
sh: artsshell: not found
22:00:10.221 Startup script terminated with exit status=32512.
22:00:10.227 JACK is starting…
22:00:10.231 /usr/bin/jackd -R -m -dalsa -dhw:0 -r44100 -p1024 -n2
22:00:10.275 JACK was started with PID=7585.
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis 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
JACK compiled with System V SHM support.
loading driver …
apparent rate = 44100
creating alsa driver … hw:0|hw: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: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
JACK: unable to mlock() port buffers: Cannot allocate memory
JACK: unable to mlock() port buffers: Cannot allocate memory
22:00:12.490 Server configuration saved to “/home/daniele/.jackdrc”.
22:00:12.508 Statistics reset.
22:00:12.552 Client activated.
22:00:12.567 JACK connection change.
22:00:12.773 JACK connection graph change.
The choice of this option is equivalent to modify the file limit.conf?
but still so continues to be one I / O
Using Ubuntu Studio 9:04
if you are certain that asoundrc does not interact with Jack, I’d rather not change it.
I do not know what to do …
thanks again
No, what I have said is that the memlock limit in the limits.conf file has nothing to do with the ‘.asoundrc’ file. There could be two different problems but it looks like the memlock limit is one of them. Also, this thread has nothing to do with ardour… and it is getting too long…You can open a thread at www.linuxmusicians.com, system tuning and configuration. Also you may want to ask in the ubuntustudio forums. This is interesting for other linux users who may encounter the same problem but your issue is off topic in here, I am afraid.
Cheers, Pablo
hello
I was actually going off-topic sorry