Re: [Jack-Devel] The Situation(s) With JACK

Le 9 déc. 2011 à 04:40, Devin Anderson a écrit :

> On Thu, Dec 8, 2011 at 10:24 AM, Stéphane Letz <[hidden]> wrote:
>>> I'll go out on a rather shaky looking limb and say that I'd like to
>>> see JACK become a library that is used to route audio and MIDI data
>>> 'inside' an application (e.g. between plugins), and continues to
>>> provide bindings to hardware.
>> 
>> Hugh ?? So basically you don't have understood the *basic* real
>> power of JACK ?? What make JACK so *unique*?
> 
> A few points:
> 
> 1.) I don't understand how you came to this conclusion.
> 2.) I see your criticism of my ideas, but I don't see your ideas on
> how to solve the proposed problem.
> 3.) "Unique" does not mean "best", "optimal", or any of a whole slew
> of adjectives that you might be trying to imply above.
> 

Sorry for being a bit harsh...what makes JACK unique is that it is a "inter-process" communication and scheduling system. Nothing existing can be compared to that. Any other in-process plug-in or API system is... another in-process plug-in or API system.

This is all what I mean.

Stéphane 

1323413170.32029_0.ltw:2,a <D406557B-3E22-41F5-8074-3FDBFB02FEA0 at grame dot fr>