Re: [Jack-Devel] Using Jack

PrevNext  Index
DateThu, 20 Mar 2014 19:38:53 -0400
From Yves Perron <[hidden] at gmail dot com>
To'Peter Ginneberge' <[hidden] at gmail dot com>, [hidden] at lists dot jackaudio dot org
In-Reply-ToPeter Ginneberge Re: [Jack-Devel] Using Jack
Hi peter,

I respect you point of view but what I need to do with midi data is already
working beautifully between Ableton Live and my app using Jack. Portmidi
looks like a good alternative but I won't be able to scale up with audio.

Yves, you don't need Jack, and even stronger.. you shouldn't use jack for
what you're trying to do.

As John Emmas has posted earlier, look into something like portmidi: 
http://portmedia.sourceforge.net/portmidi/

You're not looking to route audio/midi and/or connect devices, you're
looking for something to hook you up with LoopBE, which - from what I
understand - is what portmidi will allow you to do.

Like I mentioned earlier, LoopBe is on the experimental path, I don't have
the full scope (obviously) of Jack yet. I'm looking for an API that does
simple midi in/out (to start with) but that is also scalable for Audio and
Networking. So yes, I'd like to synchronize apps/devices eventually. 

On 20/03/2014 21:45, Yves Perron wrote:
> Hi John, thanks again for your interest in this topic.
>
> Please note that coming from graphic programming and I'm still very 
> fresh to all this so I'm experimenting.
>
> Lets try to be clear here.
>
> first, your app:
>
>      * receives MIDI (preferably from other applications)
>
>      * generates audio
>
> second, JACK:
>
>      * provides an API for sending and receiving MIDI and Audio
>
>      * the API is identical regardless of whether the sender/reciever 
> is an audio device or another application
>
>      * requires a server to function
>
> Boom right there, I need this guy even if I don't use the routing 
> features, for now. All I'm interested in at the moment is a way to 
> start a Jack server programmatically without the need of qjackctl.exe.
>
>      * can allow multiple applications to share a device even if the 
> device driver or hardware does not allow it
>
> So ...
>
>      * you are already using loopbe30 to route MIDI from another 
> application, so you do not need JACK for this
>
> I'll gladly get rid of loopbe30 if Jack can allow me not to use using 
> qjackctl.exe to start my app with Midi/Audio routing features.
>
>      * you haven't mentioned any desire to send audio anywhere except 
> the audio device, so you do not need JACK for this
>
> thus, either:
>
>    (a) there are some additional requirements that your application 
> has which do call for JACK
>
> OR
>
>    (b) you do not need to use JACK
>
> What did I miss?
>
> Regardless of the fact that I might not be using Jack to its full 
> extent right away. Could starting a Jack server programmatically with Midi
support be done?
> If yes, I'd be very interesting in doing just that. Even if I don't 
> need the Jack routing features ever. What's wrong with using Jack to
process the data only?
>
PrevNext  Index

1395358745.32337_0.ltw:2,a <004301cf4495$8e168490$aa438db0$ at gmail dot com>