lash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lash-dev] Re: [LAD] [ANN] lash-0.6.0 release candidate 2


From: alex stone
Subject: [Lash-dev] Re: [LAD] [ANN] lash-0.6.0 release candidate 2
Date: Tue, 11 Nov 2008 18:58:38 +0300

Nedko, if you're lost in this then i have no chance. :)

With everything still intact, and the visible cable connections still active in the lpatchage pic i posted before, this is what qjackctl shows me.

http://shup.com/Shup/80256/jack1.png

http://shup.com/Shup/80256/jack.png

And here's the lpatchage pic of RG, my midi keyboard, and LS, all lashed together, reflecting the connections shown in Qjackctl.

http://shup.com/Shup/80261/patch3.png

This tells me i have connections in both alsa, and a2j, at the same time.
If lpatchage shows me a connection(s) then what is it? a2j? You've already written that lpatchage can't patch alsa, so it must be a2j, yes?
If lpatchage won't show me alsa connections at all, then all of what we see is a2j midi, and raw. (nice advice, thanks.)

I will admit here i don't understand how i can connect RG in lpatchage, if RG is static bridge and won't respond to a2j. The pics seem to say otherwise, and the connection to Linuxsampler as well has me thoroughly mystified, if this is the case. (And i'll be the first to admit i'm a complete wizard at the gentle art of user error.)

Alex.

:)


On Tue, Nov 11, 2008 at 6:11 PM, Nedko Arnaudov <address@hidden> wrote:
"alex stone" <address@hidden> writes:

>> >BTW I'm surprised that you managed to connect Rosegarden trough
>> >a2jmidid. I was under impression that it needs static alsa<->jack
>> >bridges,
>
>
> I may not have explained this properly. In the pic you can see RG midi
> cabled to LS midi. Both are Alsa. I couldn't use the a2jbridge.

lpatchage cannot patch ALSA. Thus I really dont how you did that :]

>> >This indeed sounds strange. Maybe it is some bug in jackdbus patchbay
>> >code. As test, can you please check whether those audio connections
>> >appear through libjack interface, either using qjackctl or jack_lsp with
>> >-c option?
>
>
> Qjackctl confirms the  ports are cabled together. They simply don't show as
> connected in lpatchage, even with a refresh, or restart.

Can you please create simple test case for reproducing the issue?

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]