[LAU] using Jack an interface to ecasound

[edogawa]

Hi John,

Am 21.01.2017 um 08:26 schrieb john gibby:
> I booted my LiveCD and saw that the dpkg output there is just the same 
> as for my regular system (on solid-state drive).  I'm glad to know 
> that I have jack1 and not jack2, though I'm still not really sure I 
> understand completely, since the jack process I get is named 
> jackdbus.  For now, I stopped using the jack_control shell script and 
> am just using qjackctl to bring jack up, and still, the process name 
> is jackdbus.  I thought jackdbus was jack2...

As this has become more and more of a mystery, I have investigated a 
little more. reading the AVLinux user manual, particularly the section 
on software management, I was able to locate where the jackd packages 
come from, and that is in fact the kxstudio repos. once I found that out 
I was able to inspect the build logs for the jack package here:

https://launchpadlibrarian.net/229691222/buildlog_ubuntu-xenial-amd64.jack-audio-connection-kit_2%3A0.124.2~20151211-2~xenial1_BUILDING.txt.gz

and it turns out that it has the jackdbus patch applied.

So this part of the mystery is resolved, and your system seems to be in 
good shape.

I have to apologize for adding to confusion and leading you on the wrong 
track, just remember I'm not familiar with AV Linux (have looked at it 
several times in the past 15 years but never regularly used it...) and 
this 2016 version is significantly different from previous ones in that 
it incorporates the kxstudio repos as a core part, which i didn't 
realize at first. I'm really sorry for that.

As for your crossover filter network, I've never tried to do such a thig 
in software, so I have to pass that on to more knwledgable folks...

Cheers, Edgar