23 May
2012
23 May
'12
6:15 p.m.
On 05/23/2012 06:05 PM, Paul Davis wrote:
On Wed, May 23, 2012 at 12:05 PM, Paul Davis
<paul(a)linuxaudiosystems.com>wrote;wrote:
>
>
> On Wed, May 23, 2012 at 12:04 PM, Paul Davis
<paul(a)linuxaudiosystems.com>wrote;wrote:
>
>>
>>
>> On Wed, May 23, 2012 at 11:58 AM, Robin Gareus <robin(a)gareus.org> wrote:
>>
>>> On 05/23/2012 03:40 PM, Paul Davis wrote:
>>>> It it true that I skipped over the proposal for dynamic/on-the-fly
>>> backend
>>>> switching. This has already been discussed and yes, it would be great
>>> to
>>>> add it.
>>>
>>> It's working just fine in jack2, already since over two years. requires
>>> dbus though.
>>>
>>
>> had a feeling that was true but didn't want to embarass myself again by
>> mis-remembering. good to know (again)
>>
>
> of course, "full" support for this requires some semantics to define what
> to do if after the switch some ports are missing.
>
..or new ports are available. but even if the number of ports stays the
same, the actual pinout may be different.
Currently all connections to and from the backend are lost when
switching backends. JACKd (currently) has no clue and it's the only sane
thing to do.
Here's a bash script that can re-connect or re-map connections after
switching backends. It's a bit hacky but works for me.
http://rg42.org/blog/jack2dbus
http://rg42.org/wiki/jack2contol
which is another place where port metadata comes into
play.
+1
Cheers!
robin