11 Oct
2006
11 Oct
'06
11:56 a.m.
Hi list.
How do I compile VST-support into Ardour2 beta?
VST=yes, but after that?
Where should i put the VST SDK 2.3 directory? Or have i got it totally
backwards and the only way to do it is as according to the doc at
http://joebutton.co.uk/fst ? If so, I don't succeed at all.
I've searched on the Ardour site and the web, but I cannot find anything useful.
I'm
probably just stupid, but hey, I was born this way. :)
Help?
Regards
Mathias
11 Oct
11 Oct
1:41 p.m.
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)
Put the vstsdk2.3 directory in the lib dir of the ardour source tree, IIRC.
(scons will complain and tell you where it expects it if that's the wrong
place)
Run 'scons VST=yes' (and other options if needed) and 'scons install'
assuming the compile succeeds.
Put some VST-dll's ,
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)
Start ardour, display the mixer, right-click on the effect box,
select "New plugin" and you should see a VST tab as well as the
LADSPA tab.
- Peder
3:37 p.m.
On Wed, 2006-10-11 at 17:41 +0200, Peder Hedlund wrote:
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.
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) 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.
18 Oct
18 Oct
12:17 p.m.
Paul Davis wrote:
On Wed, 2006-10-11 at 17:41 +0200, Peder Hedlund
wrote:
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.
hi,
i think that i did everything like mentioned here, but ardour wants not
to start up:
nowhiskey@murija2:~$ ardour2
///usr/lib/ardour2/ardour.bin: Symbol `_ZTV7Command' has different size
in shared object, consider re-linking
///usr/lib/ardour2/ardour.bin: Symbol `_ZTVN6ARDOUR8LocationE' has
different size in shared object, consider re-linking
Ardour/GTK 2.0beta5.1
(built using $Rev: 943 $ and GCC version 4.0.4 20060507 (prerelease)
(Debian 4.0.3-3))
Copyright (C) 1999-2006 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel
Baker
Achtung: Es gibt zu Ardour KEINERLEI Gewährleistung!
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Dies ist freie Software und Sie dürfen sie gerne weiterverbreiten,
under certain conditions; see the source for copying conditions.
Loading ui configuration file /etc/ardour2/ardour2_ui.rc
(ardour.bin:20020): Gtk-WARNING **: Im Modulpfad »clearlooks« konnte
keine Themen-Engine gefunden werden,
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/nowhiskey/.ardour2/ardour.rc
OSC @ osc.udp://localhost.localdomain:3820/
///usr/lib/ardour2/ardour.bin: symbol lookup error:
///usr/lib/ardour2/libardour.so: undefined symbol: fst_init
nowhiskey@murija2:~$
---------------
or if i try to start with "ardourvst":
nowhiskey@murija2:~$ ardourvst
Ardour/GTK 2.0beta5.1
(built using $Rev: 943 $ and GCC version 4.0.4 20060507 (prerelease)
(Debian 4.0.3-3))
Copyright (C) 1999-2006 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel
Baker
Achtung: Es gibt zu Ardour KEINERLEI Gewährleistung!
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Dies ist freie Software und Sie dürfen sie gerne weiterverbreiten,
under certain conditions; see the source for copying conditions.
Loading ui configuration file /etc/ardour2/ardour2_ui.rc
(ardour_vst.exe.so:20023): Gtk-WARNING **: Im Modulpfad »clearlooks«
konnte keine Themen-Engine gefunden werden,
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/nowhiskey/.ardour2/ardour.rc
OSC @ osc.udp://localhost.localdomain:3820/
Enabling SSE optimized routines
ardour: [INFO]: detecting VST plugins along /home/nowhiskey/vst/
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 0xfffff514 at address
0x7e5df970 (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
0xb7e4a40f
nowhiskey@murija2:~$
---------------------------------
i just updated wine to 0.9.23 but still no success.
does anybody has an idea how i get this running?
cheers,
doc
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)
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.
12:38 p.m.
Dragan Noveski wrote:
Paul Davis wrote:
ok, strange enough, i had to try to start several times and now it works?!
sorry for wasting space on the list,
cheers,
doc
On Wed, 2006-10-11 at 17:41 +0200, Peder Hedlund
wrote:
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.
hi,
i think that i did everything like mentioned here, but ardour wants
not to start up:
nowhiskey@murija2:~$ ardour2
///usr/lib/ardour2/ardour.bin: Symbol `_ZTV7Command' has different
size in shared object, consider re-linking
///usr/lib/ardour2/ardour.bin: Symbol `_ZTVN6ARDOUR8LocationE' has
different size in shared object, consider re-linking
Ardour/GTK 2.0beta5.1
(built using $Rev: 943 $ and GCC version 4.0.4 20060507 (prerelease)
(Debian 4.0.3-3))
Copyright (C) 1999-2006 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren,
Joel Baker
Achtung: Es gibt zu Ardour KEINERLEI Gewährleistung!
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Dies ist freie Software und Sie dürfen sie gerne weiterverbreiten,
under certain conditions; see the source for copying conditions.
Loading ui configuration file /etc/ardour2/ardour2_ui.rc
(ardour.bin:20020): Gtk-WARNING **: Im Modulpfad »clearlooks« konnte
keine Themen-Engine gefunden werden,
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/nowhiskey/.ardour2/ardour.rc
OSC @ osc.udp://localhost.localdomain:3820/
///usr/lib/ardour2/ardour.bin: symbol lookup error:
///usr/lib/ardour2/libardour.so: undefined symbol: fst_init
nowhiskey@murija2:~$
---------------
or if i try to start with "ardourvst":
nowhiskey@murija2:~$ ardourvst
Ardour/GTK 2.0beta5.1
(built using $Rev: 943 $ and GCC version 4.0.4 20060507 (prerelease)
(Debian 4.0.3-3))
Copyright (C) 1999-2006 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren,
Joel Baker
Achtung: Es gibt zu Ardour KEINERLEI Gewährleistung!
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Dies ist freie Software und Sie dürfen sie gerne weiterverbreiten,
under certain conditions; see the source for copying conditions.
Loading ui configuration file /etc/ardour2/ardour2_ui.rc
(ardour_vst.exe.so:20023): Gtk-WARNING **: Im Modulpfad »clearlooks«
konnte keine Themen-Engine gefunden werden,
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/nowhiskey/.ardour2/ardour.rc
OSC @ osc.udp://localhost.localdomain:3820/
Enabling SSE optimized routines
ardour: [INFO]: detecting VST plugins along /home/nowhiskey/vst/
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 0xfffff514 at address
0x7e5df970 (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
0xb7e4a40f
nowhiskey@murija2:~$
---------------------------------
i just updated wine to 0.9.23 but still no success.
does anybody has an idea how i get this running?
cheers,
doc
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)
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.
3:18 p.m.
Paul Davis wrote:
On Wed, 2006-10-11 at 17:41 +0200, Peder Hedlund
wrote:
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.
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
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)
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.
4 p.m.
On Wed, 2006-10-18 at 19:13 +0200, Dragan Noveski wrote:
nothing above this point is relevant:
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
my wine config doesn't even try to open ALSA devices. not sure how you
stop this, but Wine should not be attempting to get access to any audio
devices.
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine
the type (alsa
type is 100000) of this midi device. Assuming FM Synth
ditto for MIDI.
wine: Unhandled page fault on read access to
0xf746d4e4 at address
this is almost certainly a segfault in a VST plugin.
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?
you are loading random win32 code into ardour, some of which will crash
wine. so of course its less stable, just like there still a few LADSPA
plugins which can do the same thing.
the thing to do is to remove all vst plugins from wherever VST_PLUGINS
or VST_PATH points to. then start it up. see if it works. if thats OK,
the issues are entirely to do with specific plugins. then add back ones
you are interested one by one to verify that they work.
--p
5:39 p.m.
New subject: [ardour-users] [linux-audio-user] VST support in Ardour2 beta.
Paul Davis wrote:
tried removing all the vst plugins from the directory called vst, than
running ardour without any plugins, but than trying to "close session" i
get the same behavior that i am only able to kill ardour.
console output:
...
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
actually writing state
actually writing history
(ardour_vst.exe.so:3770): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
actually writing state
actually writing history
wine: Unhandled page fault on read access to 0xf790fae4 at address
0x7d95fe0a (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
0xb7ded40f
Speicherzugriffsfehler
nowhiskey@murija2:~$
....
i just realized that wine dont complain about alsa/midi stuff anymore.
now i copied back the vst´s to the vst directory, and still wine is not
complaining about any alsa stuff anymore:
...
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
actually writing state
actually writing history
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
wine: Unhandled page fault on read access to 0xf78fade4 at address
0x7d956e0a (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
0xb7e6940f
nowhiskey@murija2:~$
-------------
any other suggestion what i could try to do?
cheers,
doc
On Wed, 2006-10-18 at 19:13 +0200, Dragan Noveski
wrote:
nothing above this point is relevant:
dont know at all, ll try to get some information at the wine webpage
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
my wine config doesn't even try to open ALSA devices. not sure how you
stop this, but Wine should not be attempting to get access to any audio
devices.
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type (alsa
type is 100000) of this midi device. Assuming FM Synth
ditto for MIDI.
wine: Unhandled page fault on read access to
0xf746d4e4 at address
this is almost certainly a segfault in a VST plugin.
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?
you are loading random win32 code into ardour, some of which will crash
wine. so of course its less stable, just like there still a few LADSPA
plugins which can do the same thing.
the thing to do is to remove all vst plugins from wherever VST_PLUGINS
or VST_PATH points to. then start it up. see if it works. if thats OK,
the issues are entirely to do with specific plugins. then add back ones
you are interested one by one to verify that they work.
--p
_______________________________________________
ardour-users mailing list
ardour-users(a)lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
6:22 p.m.
New subject: [ardour-users] [linux-audio-user] VST support in Ardour2 beta.
On Wed, 2006-10-18 at 21:39 +0200, Dragan Noveski wrote:
any other suggestion what i could try to do?
wait for the next beta or use SVN. crash-on-session-close-or-shutdown
has seen a lot of work recently.
7:15 p.m.
New subject: [ardour-users] [linux-audio-user] VST support in Ardour2 beta.
Paul Davis wrote:
On Wed, 2006-10-18 at 21:39 +0200, Dragan Noveski
wrote:
yepp!
well i tried now the rev992.
building with vst i have the same problem when closing the session, but
building without vst, ardour closes very normally, no problems on this.
thanks for the support and cheers,
doc
any other suggestion what i could try to do?
wait for the next beta or use SVN. crash-on-session-close-or-shutdown
has seen a lot of work recently.
11 Oct
11 Oct
2:42 p.m.
Interested in the same thing.....
thanks...
tag
Mathias Friman wrote:
Hi list.
How do I compile VST-support into Ardour2 beta?
VST=yes, but after that?
Where should i put the VST SDK 2.3 directory? Or have i got it totally
backwards and the only way to do it is as according to the doc at
http://joebutton.co.uk/fst ? If so, I don't succeed at all.
I've searched on the Ardour site and the web, but I cannot find anything useful.
I'm
probably just stupid, but hey, I was born this way. :)
Help?
Regards
Mathias
--
<a href="http://www.expressmart.com/"title="ExpressMart
Petr-all">
<img
src="http://www.expressmart.com/images/logosmall.gif"width="…
height="70" border="0" alt="ExpressMart.com"></a>
<br>
Timothy A Gorman<br>
IT Dept.<br>
ExpressMart <br>
Petr-all Petroleum<br>
office 315 446 0125 x 126<br>
cell 315 415 8108 <br>
![src="http://www.expressmart.com/images/logosmall.gif"width="…](http://src="http://www.expressmart.com/images/logosmall.gif%22width=%2270%22){kind=link}
6422
days inactive
6429
days old
linux-audio-user@lists.linuxaudio.org
10 comments
5 participants
participants (5)
-
Dragan Noveski -
Mathias Friman -
Paul Davis -
Peder Hedlund -
Timothy Alan Gorman