Daniel James wrote: > Hi Ralf, > > >> I don't >> know the reason, why most major distros now switch to JACK 2 >> > > It's hard to say if that's true, without a proper survey. Ubuntu Lucid > has JACK1 (0.118) but Debian Squeeze will have JACK2 (1.9.5 or later). > > I assumed that because of the numbering, all JACK developers would be > working on JACK2 from now on. However it seems that some people (like > Torben Hohn and Florian Faber) prefer to continue work on JACK1 - it is > a different implementation in a different language, after all. > > Fortunately, the API is kept synchronised, although if you take a binary > app compiled against an older version of JACK1 and try to run it on a > system with current JACK2, it may or may not work. For example, we found > that amsynth needed to be rebuilt for it to work with JACK2. > > Cheers! > > Daniel >
Hi Daniel :) I guess that more and more people got issues when using JACK1 on a multi-core machine. JACK2 is (was?) very good. I nearly left Linux for audio, but then 3.0 beta came with JACK2 and I was surprised, that I could use Linux to make music. At the moment I'm a "hardcore fan" (might be a German idiom, pardon) of Rakarrack, but when using it with 3.3 alpha for a production with some audio and MIDI tracks, I'll end in a "cul-de-sac" (might be a "German only" idiom too, but I guess you do understand). I guess tonight I'll have the time to check if I'm able to build JACK1 for 3.3 alpha, perhaps I missed a mistake I made, when I tried to build it. I don't have any objections, if I could install JACK1 from the repositories tonight ;). To be continued :). Ralf _______________________________________________ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
