Re: [Jack-Devel] Using Jack

PrevNext  Index
DateWed, 19 Mar 2014 11:25:13 -0400
From Neosettler <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] Using Jack
Follow-UpPaul Davis Re: [Jack-Devel] Using Jack
See below,

Sent from my iPhone

> On Mar 19, 2014, at 10:57 AM, Paul Davis <[hidden]> wrote:
> 
> 
> 
> 
>> On Wed, Mar 19, 2014 at 10:49 AM, Neosettler <[hidden]> wrote:
>> 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.
> 
> I think is some terminology confusion there. Do you mean "use MIDI inputs from a specific application (Ableton Live) and route it to my application" ? (API = Application Programming Interface, definitely not equivalent to "App").

My bad for the confusion, I'm using midi outputs from Ableton live and route them to my app midi inputs. Hope that clears things up.
> 
> OK, so as it turns out that can work since Live doesn't use JACK directly at all. It just sees the "fake" ASIO device that JackRouter creates, which is visible regardless of whether the JACK server or libjack are visible/accessible.

The way I do it is through loopbe30 which makes the sound card midi channels available to Albleton live and my app. Which would technically work for routing any app to mine.
>  
PrevNext  Index

1395242723.15554_0.ltw:2, <FDCF6DC9-1C9F-44CD-A5CD-5CC7A6B12A15 at gmail dot com>