[ardour-dev] build from last evening's tarball fails
markknecht at gmail.com
Mon Nov 8 20:07:38 PST 2004
On Mon, 08 Nov 2004 21:27:31 -0500, Paul Davis
<paul at linuxaudiosystems.com> wrote:
> >Humm....looks like a bad idea on Ardour's part:
> >ardour: [INFO]: detecting VST plugins along /home/mark/vst_dir
> you built it with VST support ... what else is it supposed to do?
What it's doing, but a bit more gracefully.
> it might be better to put VSTi's in /home/mark/vst/instruments and
> regular plugins in /home/mark/vst/plugins and just tell ardour to use
> the latter diretory.
Yep, that's what I've done.
> and btw, i very much doubt if synths are the mostly widely used
> VST's. VSTi's are recent, and there were lots of sound generating
> plugins for VST before the VSTi interface was defined. the classic
> VST's are all just FX plugins.
OK, you win round 1. For me the more interesting ones are VSTi's, but
I'd change my tune if I bothered to run my Waves plugins as VSTs. I'm
too Pro Tools/RTAS oriented. If I ran Cubase or some other program I
would have thought of that.
> >Nah...come on, I'm sure we can do better than that. Waves manages to
> >recognize that I don't have a plugin available at a given time and
> >then just gray it out. The plugin stays positioned for further use but
> >is just skipped in the current session.
> that's because Waves uses a blacklist.
I either don't agree or don't follow your point, but that's OK. No big deal.
> >I suspect that the segfault is caused because you might be using a
> >version of jack_fst inside of Ardour that doesn't have my
> >wine-20041019 memory hack? If so then that would cause this since I
> >now use new versions of Wine that the opfficially released version of
> >jack_fst won't work with. If you point me toward the jack_fst code
> >within Ardour I could throw in my hack and see if that eliminates the
> you would put your hack into gtk_ardour/main.cc:main()
Thanks. I'll go looking.
More information about the Ardour-Dev