jack / qjackctl: Could not connect to JACK server as client

classic Classic list List threaded Threaded
7 messages Options
l@c
Reply | Threaded
Open this post in threaded view
|

jack / qjackctl: Could not connect to JACK server as client

l@c

hello

when i start jack from within qjackctl
i get the following outpouring
and how can i prevent or work around it:


08:14:37.507 Patchbay deactivated.
08:14:38.025 Statistics reset.
08:14:38.034 Could not open ALSA sequencer as a client. MIDI patchbay
will be not available.
ALSA lib seq_hw.c:446:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory
08:14:47.988 Startup script...
08:14:47.989 killall esd
esd: no process killed
08:14:48.356 Startup script terminated with exit status=256.
08:14:48.358 JACK is starting...
08:14:48.359 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -n2
08:14:48.366 JACK was started with PID=7960 (0x1f18).
jackd 0.99.0
Copyright 2001-2003 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
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|
32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
08:14:50.410 Could not connect to JACK server as client.
08:14:58.681 JACK is stopping...
jack main caught signal 15
08:14:58.748 JACK was stopped successfully.

thanks
jmcs3






-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: jack / qjackctl: Could not connect to JACK server as client

Justin Heimburger
l@c wrote:

>
> hello
>
> when i start jack from within qjackctl
> i get the following outpouring
> and how can i prevent or work around it:
>
>
> 08:14:37.507 Patchbay deactivated.
> 08:14:38.025 Statistics reset.
> 08:14:38.034 Could not open ALSA sequencer as a client. MIDI patchbay
> will be not available.
> ALSA lib seq_hw.c:446:(snd_seq_hw_open) open /dev/snd/seq failed: No
> such file or directory
> 08:14:47.988 Startup script...
> 08:14:47.989 killall esd
> esd: no process killed
> 08:14:48.356 Startup script terminated with exit status=256.
> 08:14:48.358 JACK is starting...
> 08:14:48.359 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -n2
> 08:14:48.366 JACK was started with PID=7960 (0x1f18).
> jackd 0.99.0
> Copyright 2001-2003 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
> loading driver ..
> apparent rate = 48000
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|
> 32bit
> control device hw:0
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> 08:14:50.410 Could not connect to JACK server as client.
> 08:14:58.681 JACK is stopping...
> jack main caught signal 15
> 08:14:58.748 JACK was stopped successfully.
>
> thanks
> jmcs3
>
>

I'm having the same problem.  I got more detailed output from qjackctl, but
I think those "Couldn't open hw:0" errors are the thing.  If I can figure
out how to make those disappear, I have a feeling it will work.

Until then, I can't start up Ardour.  It complains that it doesn't have
direct access to the sound hardware.

Thanks
justin
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: jack / qjackctl: Could not connect to JACK server as client

Paul Davis
On Wed, 2005-08-17 at 22:24 -0500, Justin Heimburger wrote:

> l@c wrote:
> s
> > Couldn't open hw:0 for 32bit samples trying 24bit instead
> > Couldn't open hw:0 for 24bit samples trying 16bit instead
> > Couldn't open hw:0 for 32bit samples trying 24bit instead
> > Couldn't open hw:0 for 24bit samples trying 16bit instead
> > 08:14:50.410 Could not connect to JACK server as client.
> > 08:14:58.681 JACK is stopping...
> > jack main caught signal 15
> > 08:14:58.748 JACK was stopped successfully.
> >
> > thanks
> > jmcs3
> >
> >
>
> I'm having the same problem.  I got more detailed output from qjackctl, but
> I think those "Couldn't open hw:0" errors are the thing.  If I can figure
> out how to make those disappear, I have a feeling it will work.

wrong. those messages are informational. JACK tries 32bit, then 24bit,
then 16bit configurations.

> Until then, I can't start up Ardour.  It complains that it doesn't have
> direct access to the sound hardware.

there is no such complaint above. please post your error messages.

--p




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: jack / qjackctl: Could not connect to JACK server as client

Lee Revell
In reply to this post by Justin Heimburger
On Wed, 2005-08-17 at 22:24 -0500, Justin Heimburger wrote:
> l@c wrote:
>
> >
> > hello
> >
> > when i start jack from within qjackctl
> > i get the following outpouring
> > and how can i prevent or work around it:
> >

Assuming your sound card does not do hardware mixing, is another process
blocking the sound card?  Try:

fuser /dev/dsp
fuser /dev/snd/*

Lee



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: jack / qjackctl: Could not connect to JACK server as client

Justin Heimburger
In reply to this post by Paul Davis
Paul Davis wrote:

> On Wed, 2005-08-17 at 22:24 -0500, Justin Heimburger wrote:
>> l@c wrote:
>> s
>> > Couldn't open hw:0 for 32bit samples trying 24bit instead
>> > Couldn't open hw:0 for 24bit samples trying 16bit instead
>> > Couldn't open hw:0 for 32bit samples trying 24bit instead
>> > Couldn't open hw:0 for 24bit samples trying 16bit instead
>> > 08:14:50.410 Could not connect to JACK server as client.
>> > 08:14:58.681 JACK is stopping...
>> > jack main caught signal 15
>> > 08:14:58.748 JACK was stopped successfully.
>> >
>> > thanks
>> > jmcs3
>> >
>> >
>>
>> I'm having the same problem.  I got more detailed output from qjackctl,
>> but
>> I think those "Couldn't open hw:0" errors are the thing.  If I can figure
>> out how to make those disappear, I have a feeling it will work.
>
> wrong. those messages are informational. JACK tries 32bit, then 24bit,
> then 16bit configurations.
>
>> Until then, I can't start up Ardour.  It complains that it doesn't have
>> direct access to the sound hardware.
>
> there is no such complaint above. please post your error messages.
>
> --p
>
>

Thanks for your reply.  Here's my output from JACK:
--------------
20:57:31.853 JACK is starting...
20:57:31.853 /usr/bin/jackd -v -m -dalsa -dhw:0 -r48000 -p1024 -n2
20:57:31.866 JACK was started with PID=9465 (0x24f9).
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
jackd 0.99.0
Copyright 2001-2003 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
registered builtin port type 32 bit float mono audio
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x805ea08 fd = -1
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
new buffer size 1024
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
9465 waiting for signals
------------------
The error I get from Ardour is this (in a pop-up window on the GUI):

Direct Access to sound device not possible.
No Soundcard available or sound support not configured yet.  However, the
application uses or requires sound support.

I get the same error when I start up Rosegarden.

Audacity and Hydrogen both work fine.

Thanks again for your help.

justin

>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: jack / qjackctl: Could not connect to JACK server as client

Lee Revell
On Thu, 2005-08-18 at 21:00 -0500, Justin Heimburger wrote:
> ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
> capture-only mode

Some other app is probably using the sound device.

What does `sudo lsof /dev/snd/*' tell you?

What soundcard do you have?  Please post the contents
of /proc/asound/version.

Lee



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: jack / qjackctl: Could not connect to JACK server as client

Justin Heimburger
Lee Revell wrote:

> On Thu, 2005-08-18 at 21:00 -0500, Justin Heimburger wrote:
>> ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
>> capture-only mode
>
> Some other app is probably using the sound device.
>
> What does `sudo lsof /dev/snd/*' tell you?
>
triumph # lsof /dev/snd/*
triumph #    

> What soundcard do you have?
nforce2 (integrated on motherboard)

> Please post the contents
> of /proc/asound/version.

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.9a.


Thanks again,
justin

>
> Lee
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel