jack_test2

this is some client for the core team at lac2008 to testify some jackd
problems

eg. how to test:

0. compile jack_test2
   gcc -o jack_test2 jack_test2.c -ljack

1. start jackd from one terminal window as
   jackd -vR -dalsa -dhw:0 -r48000 -p64 -n3

2. on another window, just start the given test program
   ./jack_test2

byee
--

-- 
rncbc aka Rui Nuno Capela
rncbc <at> rncbc.org

/* jack_test2.c */
/****************************************************************************
   Copyright (C) 2007, rncbc aka Rui Nuno Capela.

   This program is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License
   as published by the Free Software Foundation; either version 2
   of the License, or (at your option) any later version.

   This program is distributed in the hope that it will be useful,

[Jackit-devel] Upgraded JACK version, now have connection issues?

Hi all,

I just upgraded JACK from version 0.102.20 to 0.109.2.
Before i upgraded everything was working perfectly.
After upgrading, i recompiled my apps that use JACK (mplayer & brutefir).

Now when i try to connect the JACK ports, i have connection issues...
i have no idea why.

[root <at> splat installed]# jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2
system:playback_3
system:playback_4
system:playback_5
system:playback_6
system:playback_7
system:playback_8
brutefir:input-0
brutefir:input-1
brutefir:output-0
brutefir:output-1
brutefir:output-2
brutefir:output-3
brutefir:output-4
brutefir:output-5

[root <at> splat installed]# jack_connect brutefir:output-0 system:playback_3

jackmp scons patch

Hi all,

Here's a small patch for a few fixes I found so far in the SCronstruct file.

Cheers,
__________________
Marc-Olivier Barre,
Marc no Chapeau... 

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Jackit-devel] SVN Version 0.109.4

Version 0.109.4 : Nedko Arnaudov log patch

Stephane 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: [Jackit-devel] Upgraded JACK version, now have connection issues?

Hi Mark,

> I just upgraded JACK from version 0.102.20 to 0.109.2.
> Before i upgraded everything was working perfectly.
> After upgrading, i recompiled my apps that use JACK (mplayer & brutefir).
> 
> Now when i try to connect the JACK ports, i have connection issues...
> i have no idea why.
> 
> [root <at> splat installed]# jack_lsp
> system:capture_1

In Jack 0.109.0 onwards, ALSA ports are named 'system' rather than 
'alsa_pcm', and this has caused a lot of connection problems with apps 
that weren't ready for the name change. For example, Hydrogen can no 
longer connect to output ports on startup (which is the default preference).

In the Jack 0.109.2 changelog, there's a mention that a fix was made so 
that applications could use the traditional 'alsa_pcm' port names. 
However the default port names appear to be the same as in 0.109.0, so 
the automatic connection problem remains.

I took a look in the 0.109.2 tarball, but couldn't see any documentation 
on how to re-enable the 'alsa_pcm' port names. Any pointers from the 
list would be appreciated 

Cheers!

Daniel

Re: [Jackit-devel] Upgraded JACK version, now have connection issues?

On Tue, Mar 04, 2008 at 03:34:16PM +0000, Daniel James wrote:

> I took a look in the 0.109.2 tarball, but couldn't see any documentation 
> on how to re-enable the 'alsa_pcm' port names. Any pointers from the 
> list would be appreciated 

Using the alsa_pcm: names *does* work with 0.109.2, as I just tested.
The jack_connect demo client sort of cheats by first looking up the
ports and then using their official 'system:' names, but even if you
don't do this jack_connect() still works.

You must be having a different problem.

--

-- 
FA

Laboratorio di Acustica ed Elettroacustica
Parma, Italia

Lascia la spina, cogli la rosa.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: [Jackit-devel] Upgraded JACK version, now have connection issues?

Daniel James wrote:
> Hi Mark,
> 
>> I just upgraded JACK from version 0.102.20 to 0.109.2.
>> Before i upgraded everything was working perfectly.
>> After upgrading, i recompiled my apps that use JACK (mplayer & brutefir).
>>
>> Now when i try to connect the JACK ports, i have connection issues...
>> i have no idea why.
>>
>> [root <at> splat installed]# jack_lsp
>> system:capture_1
> 
> In Jack 0.109.0 onwards, ALSA ports are named 'system' rather than 
> 'alsa_pcm', and this has caused a lot of connection problems with apps 
> that weren't ready for the name change. For example, Hydrogen can no 
> longer connect to output ports on startup (which is the default preference).
And which is "broken by design" since it's never mentioned that the 
default outputs are named alsa_pcm:XXX. This also broke for any freebob 
user.

> 
> In the Jack 0.109.2 changelog, there's a mention that a fix was made so 
> that applications could use the traditional 'alsa_pcm' port names. 
> However the default port names appear to be the same as in 0.109.0, so 
> the automatic connection problem remains.
> 
> I took a look in the 0.109.2 tarball, but couldn't see any documentation 
> on how to re-enable the 'alsa_pcm' port names. Any pointers from the 
> list would be appreciated 

Re: [Jackit-devel] Upgraded JACK version, now have connection issues?

On Tue, Mar 04, 2008 at 03:34:16PM +0000, Daniel James wrote:
> Hi Mark,
> 
> > I just upgraded JACK from version 0.102.20 to 0.109.2.
> > Before i upgraded everything was working perfectly.
> > After upgrading, i recompiled my apps that use JACK (mplayer & brutefir).
> > 
> > Now when i try to connect the JACK ports, i have connection issues...
> > i have no idea why.
> > 
> > [root <at> splat installed]# jack_lsp
> > system:capture_1
> 
> In Jack 0.109.0 onwards, ALSA ports are named 'system' rather than 
> 'alsa_pcm', and this has caused a lot of connection problems with apps 
> that weren't ready for the name change. For example, Hydrogen can no 
> longer connect to output ports on startup (which is the default preference).

hmm.  I recently got jack working on OpenBSD, where nothing is/was named
alsa_pcm.  hydrogen-0.9.3 did not work (crashed) with 0.103.0, same with
0.109.2.  there is better jack support in hydrogen's svn.

but, most other jack apps I've tried (fluidsynth/ardour/xine-lib/mplayer
to name a few) have been fine, either with 'oss' in 0.103.0 or 'system'
in 0.109.2'.  so, I don't think alsa_pcm -> system is the cause of your
problems.

--

-- 
jakemsr <at> sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

[Jackit-devel] jack_set_port_connect_callback and counting connections

Hi all,

it seems that when a JackPortConnectCallback is set up,
jack_port_connected gives strange results. The following code prints
"connected 2 times" if the (dummy) callback is registered, and prints
"connected 1 times" if the jack_set_port_connect_callback is commented
out:

#include <stdio.h>
#include <jack/jack.h>

void portConnectCallback(jack_port_id_t ida, jack_port_id_t idb, int
c, void* arg) {}

int main(int argc, char**argv) {
        jack_client_t* client = jack_client_open("testclient",
JackNullOption, NULL);
        jack_port_t* in = jack_port_register(client, "in",
JACK_DEFAULT_AUDIO_TYPE, JackPortIsInput, 0);
        jack_port_t* out = jack_port_register(client, "out",
JACK_DEFAULT_AUDIO_TYPE, JackPortIsOutput, 0);
        jack_set_port_connect_callback(client, portConnectCallback, NULL);
        jack_activate(client);
        jack_connect(client, "testclient:out", "testclient:in");

        printf("connected %d times\n", jack_port_connected(out));
}

Also, the jack_port_get_connections report the connection twice.

Re: [Jackit-devel] Upgraded JACK version, now have connection issues?

Hi all,

>  > In Jack 0.109.0 onwards, ALSA ports are named 'system' rather than
>  > 'alsa_pcm', and this has caused a lot of connection problems with apps
>  > that weren't ready for the name change. For example, Hydrogen can no
>  > longer connect to output ports on startup (which is the default preference).
>
>  hmm.  I recently got jack working on OpenBSD, where nothing is/was named
>  alsa_pcm.  hydrogen-0.9.3 did not work (crashed) with 0.103.0, same with
>  0.109.2.  there is better jack support in hydrogen's svn.
>
>  but, most other jack apps I've tried (fluidsynth/ardour/xine-lib/mplayer
>  to name a few) have been fine, either with 'oss' in 0.103.0 or 'system'
>  in 0.109.2'.  so, I don't think alsa_pcm -> system is the cause of your
>  problems.

You are correct, i dont think it is the cause either.
Neither of the apps im using with jack have hard-coded ports they try
to connect to and rely on manual connection by the user.
If the ports are listed by jack_lsp (as they are, as shown in my first
email), shouldnt jack_connect be able to connect them?

Thanks.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/