Paul Davis wrote:
On Wed, 2006-10-11 at 17:41 +0200, Peder Hedlund wrote:
How do I compile VST-support into Ardour2 beta?
VST=yes, but after that?
Where should i put the VST SDK 2.3 directory?
Make sure you have wine installed. (I tried with the latest).
You have to copy the vstsdk2.3/source/common/*.h to /usr/include/vst
(I think this is a bug. You shouldn't have to be root to install ardour)
unnecessary too.
unpack the VST 2.3 SDK into libs/fst
then mkdir libs/fst/vst
then copy the contents of libs/fst/vstsdk2.3/source/common/*.h to
libs/fst/vst
done.
like these : http://www.kjaerhusaudio.com/classic-series.php,
in a "vst" directory in your home dir and make a symbolic link to that
from /usr/local/lib (I think there's a varaiable you can use to point to
your directory as well)
ardour uses the VST_PLUGINS environment variable, same name as used on
win32 and OSX, to define a search path for plugins. VST_PATH is also
supported.
hi,
just builded ardour2 rev991, with prefix=/usr vst=yes and fftw=yes.
i am able o start ardour, bur ardour will not exit in a way i am expecting.
so when i go to "close session" ardour just "freezes", and i am only
able to kill it.
the machine is responding in the normal way, only ardour is "frozen".
here is the console output, it seems to me that it is something about wine:
............
Loading history from '/home/nowhiskey/Ardour/proba003/proba003.history'.
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
Transport:Loop is not a toggle
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
ALSA lib pcm_dmix.c:862:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dsnoop.c:556:(snd_pcm_dsnoop_open) unable to open slave
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type (alsa
type is 100000) of this midi device. Assuming FM Synth
wine: Unhandled page fault on read access to 0xf746d4e4 at address
0x7d95de0a (thread 0009), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> |
file.mdmp | --help ]
........................
and this is after pressing ctrl+c which will stop ardour:
.........
Loading history from '/home/nowhiskey/Ardour/proba003/proba003.history'.
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3827): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
Transport:Loop is not a toggle
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
ALSA lib pcm_dmix.c:862:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dsnoop.c:556:(snd_pcm_dsnoop_open) unable to open slave
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type (alsa
type is 100000) of this midi device. Assuming FM Synth
wine: Unhandled page fault on read access to 0xf746d4e4 at address
0x7d95de0a (thread 0009), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> |
file.mdmp | --help ]
err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xb7dfb40f
nowhiskey@murija2:~$
...............
and also generally, it looks for me that building ardour with vst
support, makes the appi much more "fragile" than when built without vst.
does anybody else has made similar experience?
cheers,
doc
