Re: [Jack-Devel] major change in jack1 MIDI handling

PrevNext  Index
DateSat, 12 Oct 2013 12:59:01 +0200
From Christian Schoenebeck <[hidden] at crudebyte dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToStéphane Letz Re: [Jack-Devel] major change in jack1 MIDI handling
Follow-UpPaul Davis Re: [Jack-Devel] major change in jack1 MIDI handling
Follow-UpJeremy Jongepier Re: [Jack-Devel] major change in jack1 MIDI handling
Actually I don't understand the overall situation. For a while JACK2 was 
advertised by main JACK developers as (upcoming) successor of JACK1. But now 
it seems like as major development efforts are once again solely put on JACK1. 
Were there some personal disputes that caused this? Because from technical 
point of view I cannot find good reasons to continue maintaining JACK1.

Besides some of the already mentioned major advantages of JACK2 (IIRC I would 
also add "lower idle CPU load" to that list), there were bugs in JACK1 (i.e. 
dead locks) which by language & design could not even happen in JACK2. Plus, 
adding new features to JACK2 can be achieved in far less time (and higher 
quality) than adding them to JACK1.

Sorry, not intended to step on anybody's toes here. I just have the impression 
that non rational, emotional reasons are involved in current overall situation 
rather than constructive ones. But who knows, maybe I missed something.

CU
Christian

On Saturday 12 October 2013 09:20:55 Stéphane Letz wrote:

> > people who want:
> >     * multiple cores for parallel data flow
> >     * interfacing with PulseAudio
> >     * interfacing with D-Bus
> >     * click-free connections (and don't mind the larger latency that this
> >     causes)
> 
> Again, again, again, and again : click-free connections connections are
> *nothing* to do with larger latency.
> 
> jack2 has one more buffer latency in the so called "asynchronous mode",
> when the server does the wait for graph end in a given cycle, and write
> the output buffers from the previous cycle, and is absolutely similar to
> jack1 regarding latency in the so called "synchronous mode", where the
> server waits for graph end in a given cycle and write the output buffers
> produced by the graph in the given cycle
> 
> This was explained like 8 years ago in this paper: 
> http://www.grame.fr/ressources/publications/Jackdmp-lac2005.pdf
> 
> History is *not* going to be rewritten…. ((-;
> 
> Stéphane
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
PrevNext  Index

1381575221.21756_0.ltw:2, <201310121259.01807.schoenebeck at crudebyte dot com>