Re: [Jack-Devel] same jack version, but different protocol versions (revisited)

PrevNext  Index
DateThu, 04 Dec 2014 17:02:19 +0200
From Athanasios Silis <[hidden] at gmail dot com>
ToChris Caudle <[hidden] at chriscaudle dot org>
CcDevelopers JACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToAthanasios Silis Re: [Jack-Devel] same jack version, but different protocol versions (revisited)
Adrian,
I got round to following your instruction,
They worked like a charm.

I would offer to write the wiki, but have little knowledge of the debian
packaging management workflow.
I also have little time to invest in learning this right now.
Should anyone choose to append this information in the wiki, it would be
extremely helpful to have detailed information about what each step does,
for those of us that come from slackware, or otherwise non debian
environment:)

thanks again!

On Tue, Dec 2, 2014 at 7:47 PM, Athanasios Silis <[hidden]
> wrote:

> i was referring to jack runnnig with -dnet, not the effect and synth
> clients connecting to jack (but jack as a client connecting to jack master)
>
> On Tue, Dec 2, 2014 at 5:28 PM, Chris Caudle <[hidden]>
> wrote:
>
>> On Tue, December 2, 2014 8:31 am, Athanasios Silis wrote:
>> > i'd have to find all dependencies to compile jackd with dbus support ,
>> and
>> > do that  across all the linux jack clients, too.
>>
>> You should not need to recompile the jack clients.  The intent is for jack
>> implementations to be interchangeable, so it should not matter to the
>> client applications which version of jack you have installed.
>>
>> --
>> Chris Caudle
>>
>>
>>
>
PrevNext  Index

1417705732.1666_0.ltw:2,a <CADgchnspFNhBCQMHGbi=49U=YXZG14Ep23SaRho_1PBaphHxmg at mail dot gmail dot com>