Upgraded JACK version, now have connection issues?

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgraded JACK version, now have connection issues?

Mark Williams-13
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@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@splat installed]# jack_connect brutefir:output-0 system:playback_3
engine sample rate: 44100
cannot connect ports

new client: jack_connect, id = 13 type 2 @ 0xb6963000 fd = 12
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
client brutefir: start_fd=5, execution_order=0.
client jack_connect: in subgraph after brutefir, execution_order=1.
client brutefir: wait_fd=14, execution_order=2 (last client).
-- jack_rechain_graph()
removing disconnected client jack_connect state = Not triggered errors = 0
removing client "jack_connect"
removing client "jack_connect" from the processing chain
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
client brutefir: start_fd=5, execution_order=0.
client brutefir: wait_fd=7, execution_order=1 (last client).
-- jack_rechain_graph()

Any ideas??

Thanks in advance!
Mark.

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Daniel James-2
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@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

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Pieter Palmers
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@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 :-)

JACK 0.109.0 introduces the concept of port aliases. Next to the normal
name displayed for a port, it can now have two aliases. These aliases
can be used to make connections as if they were the normal name.

The port names of a backend were by default renamed to system:xxx, but
they still have the old name as an alias. Therefore the (broken)
autoconnect clients should still work with the current jack.

The problem introduced in 0.109.0 was that the ALSA backend was renamed
to 'ALSA' instead of 'alsa_pcm'. Hence the backend aliases became
"ALSA:xxx" instead of "alsa_pcm:xxx". Aside from breaking the
autoconnect-to-hardcoded-port apps, this also rendered all saved
sessions in polite apps useless. This was corrected in 0.109.2.

To summarize: you can still use the old names since they are still
present as aliases. So
"jack_connect alsa_pcm:capture_1 myprog:myport"
and
"jack_connect system:capture_1 myprog:myport"
are equivalent.

Greets,

Pieter

PS: jack_lsp -A lists the aliases

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Fons Adriaensen-2
In reply to this post by Daniel James-2
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

j4nKy
In reply to this post by Daniel James-2
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@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.

--
[hidden email]
SDF Public Access UNIX System - http://sdf.lonestar.org

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Mark Williams-13
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Lee Revell
On Tue, Mar 4, 2008 at 9:35 PM, Mark Williams <[hidden email]> wrote:
>  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?

Do you have multiple jack versions installed?  It sounds like you
didn't upgrade, but installed a newer version alongside the old one.

What does "which jackd" output?

Lee

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Mark Williams-13
On Fri, Mar 7, 2008 at 1:19 PM, Lee Revell <[hidden email]> wrote:
> On Tue, Mar 4, 2008 at 9:35 PM, Mark Williams <[hidden email]> wrote:
>  >  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?
>
>  Do you have multiple jack versions installed?  It sounds like you
>  didn't upgrade, but installed a newer version alongside the old one.

I always install jack with a prefix of "/usr/local/jack", so such
things cant happen.
There are no other jack files in any of the other std lib or bin dirs.

For now ive gone back to 103.0 which has fixed the problem.
I dont really have a need to run anything newer at the moment either,
so it think ill leave it this way.
That is unless you do want to find the cause of the problem, in which
case ill try any other possible solutions you guys can come up with?


On Fri, Mar 7, 2008 at 1:19 PM, Lee Revell <[hidden email]> wrote:

> On Tue, Mar 4, 2008 at 9:35 PM, Mark Williams <[hidden email]> wrote:
>  >  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?
>
>  Do you have multiple jack versions installed?  It sounds like you
>  didn't upgrade, but installed a newer version alongside the old one.
>
>  What does "which jackd" output?
>
>  Lee
>

-------------------------------------------------------------------------
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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Stéphane Letz

Le 7 mars 08 à 04:46, Mark Williams a écrit :

> On Fri, Mar 7, 2008 at 1:19 PM, Lee Revell <[hidden email]>  
> wrote:
>> On Tue, Mar 4, 2008 at 9:35 PM, Mark Williams <[hidden email]> wrote:
>>> 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?
>>
>> Do you have multiple jack versions installed?  It sounds like you
>> didn't upgrade, but installed a newer version alongside the old one.
>
> I always install jack with a prefix of "/usr/local/jack", so such
> things cant happen.
> There are no other jack files in any of the other std lib or bin dirs.
>
> For now ive gone back to 103.0 which has fixed the problem.
> I dont really have a need to run anything newer at the moment either,
> so it think ill leave it this way.
> That is unless you do want to find the cause of the problem, in which
> case ill try any other possible solutions you guys can come up with?

It would help if you can describe quite precisely what you're trying  
to do and what error you get.

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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel
Reply | Threaded
Open this post in threaded view
|

Re: Upgraded JACK version, now have connection issues?

Stéphane Letz

Le 7 mars 08 à 10:42, Mark Williams a écrit :

>>> On Fri, Mar 7, 2008 at 1:19 PM, Lee Revell <[hidden email]>
>>> wrote:
>>>> On Tue, Mar 4, 2008 at 9:35 PM, Mark Williams <[hidden email]>  
>>>> wrote:
>>>>> 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?
>>>>
>>>> Do you have multiple jack versions installed?  It sounds like you
>>>> didn't upgrade, but installed a newer version alongside the old  
>>>> one.
>>>
>>> I always install jack with a prefix of "/usr/local/jack", so such
>>> things cant happen.
>>> There are no other jack files in any of the other std lib or bin  
>>> dirs.
>>>
>>> For now ive gone back to 103.0 which has fixed the problem.
>>> I dont really have a need to run anything newer at the moment  
>>> either,
>>> so it think ill leave it this way.
>>> That is unless you do want to find the cause of the problem, in  
>>> which
>>> case ill try any other possible solutions you guys can come up with?
>>
>> It would help if you can describe quite precisely what you're trying
>> to do and what error you get.
>
> I do so in my first post to the mailing list...
>
> See:
> http://boudicca.tux.org/hypermail/jackit-devel/2008-Mar/0000.html


What the jack_connect tool do is the following:

- it uses the "jack_port_by_name"  to get the port ID given the name.  
The correct port ID is correctly retrieved if the "official" name is  
given (like system:playback_1), or an "alias" name is given (like  
alsa_pcm:playback_1). Then jack_connect(client,  
jack_port_name(input_port), jack_port_name(output_port) is use to do  
the connection.
So basically using either name is supposed to work:

jack_connect myport system:playback_1 or jack_connect myport  
alsa_pcm:playback_1.

Note that you can use -A to see alias names in jack_lsp : jack_lsp -A,  
and you can see already established connection using -c like: jack_lsp  
-c

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/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel