You can take the latest git by using:git clone git://distrho.git.sf.net/gitroot/distrho/distrho --depth 1
but I don't but I recommend it right now. The current build system (premake) uses static build flags, and would require a lot of manual editing to set it differently.
one of my targets once I get everything working with the latest juce-git is to port the build system to cmake. when that happens it will be much easier to compile the plugins.
(juce itself is not needed, it pre-included in the repo - and has custom patches)
Did you also tested the loomer plugins? how do they behave compared to the disthro ports?
On 02/21/2012 07:46 AM, Filipe Lopes wrote:Hi Filipe,Hey Dave,
I've been working with juce plugins a lot recently, and one of my projects handles precisely that:
http://distrho.sourceforge.net/
juce has not been very linux-friendly in it's early days, and still has a few issues right now (but it's now much better than before).
I plan to move all plugins from the old jucetice project to DISTRHO (which most is already done, only missing Jost).
these changes are not yet ready though, as I'm updating all the plugins to the very latest juce-git modules branch, and also working on a serious juce-linux issue with realtime kernels.
once everything is done, I'll post to the linuxaudio planet as usual (through KXStudio news)
if you're using plugins from here:
http://www.anticore.org/jucetice/
or
http://code.google.com/p/juced/
you'll have issues for sure. Old loomer plugins had issues too, but the new ones seem to work fine now.
Thanks for the reply. Alas, some of the problematic plugins I tested were from the DISTRHO collection (specifically the TAL reverbs 2 and 3 and the TAL vocoder. I tested the prebuilt binaries, btw. Perhaps a local build would be preferable ? I have the latest JUCE framework and the VST 2.4 SDK, on an Arch 64-bit system.
Also, I wanted to add a "Thank you" for those ports and I hope you're inspired to make more of them. :)
Best,
dp
On Tue, Feb 21, 2012 at 12:34 PM, Dave Phillips <dlphillips@woh.rr.com> wrote:
Greetings,
I notice that whenever I use any Juce-based native Linux VST plugin - fx or instrument - in Ardour3 the plugin produces dramatically more xruns than any LV2 or LADSPA plug. Does anyone else have that problem ? If so, can anything be done about it, apart from raising my latency settings ?
Thanks,
dp
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev