28 Apr
2004
28 Apr
'04
7:39 a.m.
Hi all,
Initially posting on Tim Orford's Linux VST Compatibility Page, my quest has
been to test all Win-only FreeVSTi's featured on the K-v-R database under Linux
thanks to some of Kjetil Matheussen's apps and to report the way they work in my
language, to speed up things a bit!
I've posted the list on the K-v-R forum:
http://www.kvr-vst.com/forum/viewtopic.php?t=42640
Because that's where i've found most of the plugins:
http://www.kvr-vst.com/get.php
Alternatively, until the nodes change while I update my bookmarks, you can
browse all links to devs there:
http://theremin.free.fr/hunchback/index.php?nodes=|0|461|897|1098|1103|/
Let me quote one of the first answers to the thread: "The stuck notes in some SE
VSTi are most likely due to CK's Unison modules that are a little twitchy."
Have your copy saved on a text file, so that you can emulate a database search.
Ex: getting all interesting working plugins among all plugins stored on a text
file named "VSTi":
cat VSTi | grep ': W!'
NB:
Do you want to practise your french?
http://fr.audiofanzine.com/apprendre/mailing_forums/index,idtopic,60705.html
Cheers,
Mr°Freeze
28 Apr
28 Apr
8:40 a.m.
Hi Christian:
I would consider a kindness if you added a link on Tim Orford's page
that would direct readers to your list. I understand the list is too
lengthy to post on Tim's site, but I'm sure many readers of that page
would like to know about the existence of your (very impressive!) list &
screenshots.
VST/VSTi under Linux... What will they think of next... ! :)
Best,
dp
Christian Frisson wrote:
Hi all,
Initially posting on Tim Orford's Linux VST Compatibility Page, my quest has
been to test all Win-only FreeVSTi's featured on the K-v-R database under Linux
thanks to some of Kjetil Matheussen's apps and to report the way they work in my
language, to speed up things a bit!
I've posted the list on the K-v-R forum:
http://www.kvr-vst.com/forum/viewtopic.php?t=42640
Because that's where i've found most of the plugins:
http://www.kvr-vst.com/get.php
Alternatively, until the nodes change while I update my bookmarks, you can
browse all links to devs there:
http://theremin.free.fr/hunchback/index.php?nodes=|0|461|897|1098|1103|/
Let me quote one of the first answers to the thread: "The stuck notes in some SE
VSTi are most likely due to CK's Unison modules that are a little twitchy."
Have your copy saved on a text file, so that you can emulate a database search.
Ex: getting all interesting working plugins among all plugins stored on a text
file named "VSTi":
cat VSTi | grep ': W!'
NB:
Do you want to practise your french?
http://fr.audiofanzine.com/apprendre/mailing_forums/index,idtopic,60705.html
Cheers,
Mr°Freeze
5 May
5 May
11:36 a.m.
New subject: [linux-audio-user] Re: [PlanetCCRMA] The Linux FreeVSTi Compatibility List
On Wed, 28 Apr 2004, Christian Frisson wrote:
Hi all,
Initially posting on Tim Orford's Linux VST Compatibility Page, my quest has
been to test all Win-only FreeVSTi's featured on the K-v-R database under Linux
thanks to some of Kjetil Matheussen's apps and to report the way they work in my
language, to speed up things a bit!
I've posted the list on the K-v-R forum:
http://www.kvr-vst.com/forum/viewtopic.php?t=42640
Because that's where i've found most of the plugins:
http://www.kvr-vst.com/get.php
Alternatively, until the nodes change while I update my bookmarks, you can
browse all links to devs there:
http://theremin.free.fr/hunchback/index.php?nodes=|0|461|897|1098|1103|/
Very nice work. However, I think you may have misunderstood how the
vstserver works:
I quote from the web-board:
I've just restricted myself on VSTi's. The
list is already long enough ,-)
The app I used, vsti, is aimed at launching one VSTi plugin at a time yet,
because it relies on a single-thread VST server, VSTserver.
The vstserver does acutally work by setting up a bounch of processes and
threads, and are very very far from being single-threaded. There are no
limitations on how many vsti's you run simultaniously.
Surely some VST's do work, but I'm waiting for
FST (the app whose
announcement I quoted) which seems more suitable to call more than one
effect, in hosts this time, like ardour. It's still interesting to use
vsti for VST effects that can handle MIDI CC's (tell me which ones?).
The difference between the vstserver and the new fst-library made by
Torben Hohn and Paul Davies is that the fst-library runs the vst-plugin
in the same process, while using the vstserver-system you run the
vst-plugin inside a new process set up by the vstserver.
What this means is that you get less contex-switches and therefor
better performance when running many (something like more than 8 according
to Paul) vst-plugins simultaniously using the fst-library.
--
8:54 p.m.
New subject: [linux-audio-user] Re: [PlanetCCRMA] The Linux FreeVSTi Compatibility List
Hi,
Kjetil Svalastog Matheussen wrote:
Very nice work. However, I think you may have
misunderstood how the
vstserver works:
The vstserver does actually work by setting up a bounch of processes and
threads, and are very very far from being single-threaded. There are no
limitations on how many vsti's you run simultaniously.
My apologies... My dev knowledge is too low to be mentionned. Additionally,
French people like me don't always speak English very well ,-) I've definitely
made this thread confusion during my tests, as I tried to launch two plugins
simultaneously, both with vsti, and had VSTserver return errors... Had just
another go today, works perfectly! Mea culpa.
When it comes to limit the number of opened console windows, how should I define
my paths correctly system-wide? On Fedora Core 1 - seems to be relevant in this
case - appending "export VST_PATH=..." to the file /etc/profile and sourcing it
afterwards does only define the path for console use. When using the launcher
(Alt+F2) to start plugins with "vsti plugin_name", it doesn't seem to
recognize
VST_PATH.
The difference between the vstserver and the new
fst-library made by
Torben Hohn and Paul Davies is that the fst-library runs the vst-plugin
in the same process, while using the vstserver-system you run the
vst-plugin inside a new process set up by the vstserver.
What this means is that you get less contex-switches and therefor
better performance when running many (something like more than 8 according
to Paul) vst-plugins simultaniously using the fst-library.
What kind of features are already planned for the next releases of both projects?
Cheers,
Christian
6 May
6 May
8:49 a.m.
New subject: [linux-audio-user] Re: [PlanetCCRMA] The Linux FreeVSTi Compatibility List
On Thu, 6 May 2004, Christian Frisson wrote:
I need to get the vstserver to compile with wine again. I haven't
succeeded with that yet. (not without linking with pthread at least).
--
Hi,
Kjetil Svalastog Matheussen wrote:
Good to hear.
Very nice work. However, I think you may have
misunderstood how the
vstserver works:
The vstserver does actually work by setting up a bounch of processes and
threads, and are very very far from being single-threaded. There are no
limitations on how many vsti's you run simultaniously.
My apologies... My dev knowledge is too low to be mentionned. Additionally,
French people like me don't always speak English very well ,-) I've definitely
made this thread confusion during my tests, as I tried to launch two plugins
simultaneously, both with vsti, and had VSTserver return errors... Had just
another go today, works perfectly! Mea culpa.
When it comes to limit the number of opened console
windows, how should I define
my paths correctly system-wide? On Fedora Core 1 - seems to be relevant in this
case - appending "export VST_PATH=..." to the file /etc/profile and sourcing
it
afterwards does only define the path for console use. When using the launcher
(Alt+F2) to start plugins with "vsti plugin_name", it doesn't seem to
recognize
VST_PATH.
Strange. What if you replace "vsti plugin_name" with
"export VST_PATH=... vsti plugin_name" or
"xterm -e vsti plugin_name" or
"bash -c "vsti plugin_name"" ?
The difference
between the vstserver and the new fst-library made by
Torben Hohn and Paul Davies is that the fst-library runs the vst-plugin
in the same process, while using the vstserver-system you run the
vst-plugin inside a new process set up by the vstserver.
What this means is that you get less contex-switches and therefor
better performance when running many (something like more than 8 according
to Paul) vst-plugins simultaniously using the fst-library.
What kind of features are already planned for the next releases of both projects?
1:48 p.m.
New subject: [linux-audio-user] Re: [PlanetCCRMA] The Linux FreeVSTi Compatibility List
Kjetil Svalastog Matheussen wrote:
"xterm -e vsti plugin_name"
The only working choice out of the three mentionned, being equivalent to
invoking "vsti plugin_name" directly on a console.
Christian
7518
days inactive
7526
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Christian Frisson -
Dave Phillips -
Kjetil Svalastog Matheussen