Re: [Jack-Devel] Using Jack

Hi Paul, the idea is to use midi inputs from a specific API, Abelton live that is and route it to my API. Nothing more, nothing less for now. Avoiding extra steps of the jack installation/dependencies/setup for the and user is somewhat a good thing.

Sent from my iPhone

> On Mar 19, 2014, at 10:31 AM, Paul Davis <[hidden]> wrote:
> 
> 
> 
> 
>> On Wed, Mar 19, 2014 at 10:15 AM, Yves Perron <[hidden]> wrote:
>> Greetings Jack masters, think you for your inputs.
>> 
>> [quote] setting your app up as a Jack server is NOT a good idea - because if
>> other apps use Jack (like Mixbus, for example) they would use the version
>> provided by your app.  So, when your app eventually shuts down, anything
>> else that was using Jack would break!  The correct way to use Jack is to
>> launch it as an external server and let Jack decide whether & when to shut
>> itself down. [/quote]
>> 
>> I am not worry about this. The whole point is precisely not to install jack
>> at all but to embed Jack's client/server libraries into our API. That said,
>> I'm trying to start a Jack server programmatically but little info is
>> available on this and I do understand why now.
>> 
>> Before going any further. Regardless of if it is a good practice or not. Is
>> running a Jack server via our API even possible without the need for the end
>> user to installing Jack in the first place?
> 
> It is very hard to see why you want to do this.
> 
> There are two benefits to using JACK:
> 
>    (1) inter-app audio routing, using the same API for device audio routing
>    (2) a simple, powerful cross-platform API for audio
> 
> If you embed the JACK client/server into a specific application/bundle, then (1) becomes impossible. 
> 
> Why do you want to use JACK at all?
>  

1395240576.11643_0.ltw:2, <FF3F5FF8-C424-40C1-BB4A-DCF35F47E89E at gmail dot com>