From: Guilherme Longo <grlongo.ireland@gmail.com>
To: Patrick Shirkey <pshirkey@boosthardware.com>,
alsa-devel@alsa-project.org
Subject: Re: [Jack-Devel] Says: server is not connected, even though it has been!
Date: Fri, 10 Jul 2009 11:18:28 -0300 [thread overview]
Message-ID: <4A574DB4.7010906@gmail.com> (raw)
In-Reply-To: <4A5722F1.6060707@boosthardware.com>
Yes Patrick.... same user for both
Really strange, isn't it!
Patrick Shirkey wrote:
>
> On 07/10/2009 05:20 PM, Guilherme Longo wrote:
>> Hi all!
>>
>> I couldn't find where this problem comes from.
>
> Hi,
>
> Sorry, to ask the obvious but, are you running as the same user for
> the server and the simple_client?
>
>
> Patrick Shirkey
> Boost Hardware Ltd
>
>
>
>> I am connecting jack with the command:
>>
>> jackd -d alsa -d default
>>
>> and appears right below:
>>
>> bash-3.1# jackd -d alsa -d default
>> jackdmp 1.9.2
>> Copyright 2001-2005 Paul Davis and others.
>> Copyright 2004-2008 Grame.
>> jackdmp 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 server starting in non-realtime mode
>> creating alsa driver ...
>> default|default|1024|2|48000|0|0|nomon|swmeter|-|32bit
>> Using ALSA driver EMU10K1 running on SB Live [Unknown] (rev.10,
>> serial:0x80671102) at 0xd000, irq 18
>> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2
>> periods
>> ALSA: final selected sample format for capture: 32bit float
>> little-endian
>> You appear to be using the ALSA software "plug" layer, probably
>> a result of using the "default" ALSA device. This is less
>> efficient than it could be. Consider using a hardware device
>> instead rather than using the plug layer. Usually the name of the
>> hardware device that corresponds to the first soun
>> ALSA: use 2 periods for capture
>> ALSA: final selected sample format for playback: 32bit float
>> little-endian
>> You appear to be using the ALSA software "plug" layer, probably
>> a result of using the "default" ALSA device. This is less
>> efficient than it could be. Consider using a hardware device
>> instead rather than using the plug layer. Usually the name of the
>> hardware device that corresponds to the first soun
>> ALSA: use 2 periods for playback
>>
>>
>> In another terminal, I am running a simple_cliente, and when I run it
>> with the code:
>>
>> quart$: simple_client audiofile
>> jack server not running?
>>
>> It is resulting of:
>>
>> if ((client = jack_client_open(argv[1], JackNoStartServer, NULL)) ==
>> 0) {
>> fprintf (stderr, "jack server not running?\n");
>> return 1;
>> }
>>
>>
>> Plz, can I get som help here.
>> Tks.
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel@lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
parent reply other threads:[~2009-07-10 14:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4A5722F1.6060707@boosthardware.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A574DB4.7010906@gmail.com \
--to=grlongo.ireland@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=pshirkey@boosthardware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox