problems with jack

You're new to the LinuxSampler world? You don't know where to start and nothing works? Here's the place to ask for help.
Post Reply
waverider
Newbie
Posts: 2
Joined: Sat Oct 24, 2009 1:17 am

problems with jack

Post by waverider » Sat Oct 24, 2009 1:25 am

Hi! i'm new here. I'm testing Linuxsampler through Qsampler and Jsampler. With ALSA there aren't problems!, but with jack appears these issues:

02:19:45.697 Client connecting...
02:19:45.699 Server is starting...
02:19:45.699 linuxsampler
02:19:45.702 Server was started with PID=21860.
lscp_client_create: cmd: connect: Conexión rechazada
LinuxSampler 1.0.0
Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck
Copyright (C) 2005-2009 Christian Schoenebeck
Detected features: MMX SSE SSE2
Automatic Stacktrace: Off
Creating Sampler...OK
Registered sampler engines: 'GIG'
Registered MIDI input drivers: ALSA,JACK
Registered audio output drivers: ALSA,JACK
Loading instrument editor plugins...OK
Registered instrument editors: 'gigedit'
Starting LSCP network server (0.0.0.0:8888)...OK
02:19:48.906 Client connecting...
02:19:48.907 Client receive timeout is set to 1000 msec.
02:19:48.909 Client connected.
02:19:48.914 Sent fine tuning settings.
02:19:48.917 New session: "Untitled1".
LinuxSampler initialization completed. :-)

LSCPServer: Client connection established on socket:4.
LSCPServer: Client connection established on socket:5.
02:19:56.231 New Channel setup...
02:20:17.368 Channel 0 added.
02:20:17.380 Channel 0 lscp_set_channel_audio_type: Failure during receive operation (errno=-1)
02:20:17.381 lscp_list_channels: Failure during send operation (errno=-1)
lscp_client_recv: recv: Conexión reiniciada por el par
_lscp_client_evt_proc: recv: Conexión reiniciada por el par
lscp_client_call: send: Tubería rota
02:20:17.391 Client disconnecting...
02:20:17.392 Client disconnected.
02:20:17.394 Server was stopped with exit status 1.
02:20:17.399 Could not get current list of channels. Sorry.
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
_lscp_client_evt_request: send: Tubería rota
02:20:19.043 Channel 0 Some channel settings could not be set. Sorry.

I've tried to recompile from source and from SVN but don't progress. I use jackd 0.116.2 and ubuntui studio 8.04 32bits with a RT kernel.

anyone could help me please??

Thanks in advance!

regards,

Jaime

waverider
Newbie
Posts: 2
Joined: Sat Oct 24, 2009 1:17 am

Re: problems with jack

Post by waverider » Sat Oct 24, 2009 1:27 am

ahh! by the way: Tubería rota = Broken Pipe.
;)

User avatar
cuse
Developer
Posts: 366
Joined: Wed Jan 23, 2008 10:07 pm
Location: Germany

Re: problems with jack

Post by cuse » Sun Oct 25, 2009 9:38 pm

Did linuxsampler crash? Check the running processes.

Youhn
Newbie
Posts: 2
Joined: Thu Dec 24, 2009 8:53 pm

Re: problems with jack

Post by Youhn » Thu Dec 24, 2009 9:07 pm

I think the same problem arises here. Qsampler and Linuxsampler do work with ALSA, but when I try to add a JACK device, it breaks a pipe and crashes linuxsampler (only qsampler keep running). Everything *sampler installed from CVS.

Linux slack 2.6.29.6-smp #2 SMP Mon Aug 17 00:52:54 CDT 2009 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
alsa-lib-1.0.18
jackd version 0.118.2

Running jackd realtime from ROOT account with options "unlock memory" and "soft mode" using ALSA.
hw:0 as input device
plughw:0 as output (seems to be the only one that does not crash jackd)
LinuxSampler 1.0.0.cvs2
Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck
Copyright (C) 2005-2009 Christian Schoenebeck
Detected features: MMX SSE SSE2
Automatic Stacktrace: Off
Creating Sampler...OK
Registered sampler engines: 'GIG','SF2','SFZ'
Registered MIDI input drivers: ALSA,JACK
Registered audio output drivers: ALSA,JACK
Loading instrument editor plugins...OK
Registered instrument editors: 'gigedit'
Starting LSCP network server (0.0.0.0:8888)...OK
20:58:24.428 Client connecting...
20:58:24.431 Client receive timeout is set to 1000 msec.
20:58:24.435 Client connected.
20:58:24.440 Sent fine tuning settings.
20:58:24.447 New session: "Untitled1".
LinuxSampler initialization completed. :-)

LSCPServer: Client connection established on socket:4.
LSCPServer: Client connection established on socket:5.
ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
20:59:15.237 New Audio device lscp_create_audio_device: Failure during receive operation (errno=-1)
lscp_client_recv: recv: Connection reset by peer
20:59:15.242 New Audio device Could not create device. Sorry.
_lscp_client_evt_proc: recv: Connection reset by peer
20:59:15.248 Client disconnecting...
20:59:15.254 Client disconnected.
20:59:15.260 Server was stopped with exit status 1.
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
I really need JACK to connect to Ardour and record stuff. :(

User avatar
cuse
Developer
Posts: 366
Joined: Wed Jan 23, 2008 10:07 pm
Location: Germany

Re: problems with jack

Post by cuse » Fri Dec 25, 2009 5:40 pm

Youhn wrote:ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
Since this is an error on ALSA level, complaining that the supplied card name is wrong, this more seems to be a problem either with JACK or with ALSA, not with LinuxSampler. LinuxSampler does not select a sound card to be used.

Youhn
Newbie
Posts: 2
Joined: Thu Dec 24, 2009 8:53 pm

Re: problems with jack

Post by Youhn » Fri Dec 25, 2009 11:22 pm

This part:
LSCPServer: Client connection established on socket:4.
LSCPServer: Client connection established on socket:5.
ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1399:(_snd_pcm_hw_open) Invalid value for card
Show, when I press the "Device configuration" icon in Qsampler. Nothing crashed, everything seems to be OK.
No device are show, so I have to add them.

Then, two options for AUDIO. Either add ALSA devices, or add JACK devices.

1. adding ALSA dev: everything seems to work, despite the previous error, no crash
OR
2. adding JACK dev: qsampler says "Could not create device. Sorry" and linuxsampler crashes.

Then this part follows in the messages part of Qsampler :
23:17:03.058 New Audio device lscp_create_audio_device: Failure during receive operation (errno=-1)
lscp_client_recv: recv: Connection reset by peer
_lscp_client_evt_proc: recv: Connection reset by peer
23:17:03.065 New Audio device Could not create device. Sorry.
23:17:03.087 Client disconnecting...
23:17:03.093 Client disconnected.
23:17:03.096 Server was stopped with exit status 1.
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
_lscp_client_evt_request: send: Broken pipe
And linuxsampler crashes. Other apps work fine with JACK (or alsa).
So how can this be a JACK or ALSA related problem ... ?

User avatar
cuse
Developer
Posts: 366
Joined: Wed Jan 23, 2008 10:07 pm
Location: Germany

Re: problems with jack

Post by cuse » Sat Dec 26, 2009 2:26 pm

I'm not a mind reader. I didn't assume that you created an ALSA device before you created a JACK device.

About "other apps work with JACK": this does not imply a bug in LinuxSampler. Often LinuxSampler is linked against another libjackX then "the other apps" in such cases. You can check that with:

Code: Select all

ldd /usr/lib/linuxsampler/liblinuxsampler.so
If that's also not the problem, then you should investigate it by recompiling LinuxSampler with debugging symbols turned on and creating a stack trace of the crash.

Post Reply