27 May
2004
27 May
'04
2:50 p.m.
James Stone:
The vsti program implements a standard alsa sequencer (just as the
jack_fst program, which infact use the code from vsti (which again use
the code from jack-rack :))), so it is definitely possible to get access
from seq24. Just use aconnect, kaconnect, qjackctl or something to
connect the vsti instrument and seq24. Infact, it should be much simpler
than from pd. I think one of us must have misunderstood something here.
--
You probably want "vsti" from Kjetil Matheussen (using vstserver) or
"jack_fst" from Paul Davis and Torben Hohn (using libfst). Either of
these will run a VSTi with GUI as a standalone JACK/ALSA app that can
then be driven as an ALSA sequencer client from a MIDI source.
You can get vsti at http://www.notam02.no/arkiv/src/, or jack_fst at
http://linuxaudiosystems.com/fst/ . I have never tried vsti, but I
have used both vstserver-for-plugins and jack_fst with good results.
Chris
I use vsti for auditioning vsts but I find that the k_vst~ plugin for pd
offers more functionality, and also is accessible from seq24 (which is
not the case with vsti). 
27 May
27 May
3:24 p.m.
New subject: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
On Thu, May 27, 2004 at 06:42:14PM +0200, Kjetil Svalastog Matheussen wrote:
James Stone:
The vsti program implements a standard alsa sequencer (just as the
jack_fst program, which infact use the code from vsti (which again use
the code from jack-rack :))), so it is definitely possible to get access
from seq24. Just use aconnect, kaconnect, qjackctl or something to
connect the vsti instrument and seq24. Infact, it should be much simpler
than from pd. I think one of us must have misunderstood something here.
--
The problem is that seq24 will not start with vsti running.
Another problem is in muse, if I have two vsti s running they are only
selectable as one instrument... the pd plugin seems to offer more
flexibility with respect to these problems, but I agree it is quite
fiddly.
James
You probably want "vsti" from Kjetil Matheussen (using vstserver) or
"jack_fst" from Paul Davis and Torben Hohn (using libfst). Either of
these will run a VSTi with GUI as a standalone JACK/ALSA app that can
then be driven as an ALSA sequencer client from a MIDI source.
You can get vsti at http://www.notam02.no/arkiv/src/, or jack_fst at
http://linuxaudiosystems.com/fst/ . I have never tried vsti, but I
have used both vstserver-for-plugins and jack_fst with good results.
Chris
I use vsti for auditioning vsts but I find that the k_vst~ plugin for pd
offers more functionality, and also is accessible from seq24 (which is
not the case with vsti). 
3:53 p.m.
New subject: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
torsdagen den 27 maj 2004 19.22 skrev James Stone:
On Thu, May 27, 2004 at 06:42:14PM +0200, Kjetil
Svalastog Matheussen wrote:
Interesting, I haven't succeeded in trying this yet, any idea why it is so?
Only one alsa interface exported?
/Robert
James Stone:
The vsti program implements a standard alsa sequencer (just as the
jack_fst program, which infact use the code from vsti (which again use
the code from jack-rack :))), so it is definitely possible to get access
from seq24. Just use aconnect, kaconnect, qjackctl or something to
connect the vsti instrument and seq24. Infact, it should be much simpler
than from pd. I think one of us must have misunderstood something here.
--
The problem is that seq24 will not start with vsti running.
Another problem is in muse, if I have two vsti s running they are only
selectable as one instrument... You
probably want "vsti" from Kjetil Matheussen (using vstserver) or
"jack_fst" from Paul Davis and Torben Hohn (using libfst). Either of
these will run a VSTi with GUI as a standalone JACK/ALSA app that can
then be driven as an ALSA sequencer client from a MIDI source.
You can get vsti at http://www.notam02.no/arkiv/src/, or jack_fst at
http://linuxaudiosystems.com/fst/ . I have never tried vsti, but I
have used both vstserver-for-plugins and jack_fst with good results.
Chris
I use vsti for auditioning vsts but I find that the k_vst~ plugin for
pd offers more functionality, and also is accessible from seq24 (which
is not the case with vsti). the pd plugin seems to offer more
flexibility with respect to these problems, but I agree it is quite
fiddly.
James
--
http://spamatica.se/music/
4:40 p.m.
New subject: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
Okay, I tried to get some VSTi's working but I get this error always.
VSTSERVER/main: Going to try to start vst plugin "JX220.dll".
wine: cannot find 'JX220.dll'
This is with VST_PATH set to the place where JX220.dll is, so vstserver finds
it but wine does not.
I have a feeling I have seen this type of error mentioned recently, name
problem?
Wine is apparently from february, could this be it?
(apologies if this just has been discussed, I missed a bunch of messages
yesterday)
/Robert
--
http://spamatica.se/music/
6:30 p.m.
New subject: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
Robert Jonsson wrote:
Okay, I tried to get some VSTi's working but I get
this error always.
VSTSERVER/main: Going to try to start vst plugin "JX220.dll".
wine: cannot find 'JX220.dll'
This is with VST_PATH set to the place where JX220.dll is, so vstserver finds
it but wine does not.
I have a feeling I have seen this type of error mentioned recently, name
problem?
Wine is apparently from february, could this be it?
(apologies if this just has been discussed, I missed a bunch of messages
yesterday)
/Robert
I cannot (so far) get vstserver to run these things directly, but if
you're using JAck then try vsti from Kjetil's web site.
1) Create two directories in your home:
a) vst-dir
b) vst-JX200
2) Export vst-dir but have nothing in it
3) Place the JX200.dll file in vst-JX220
4) Start Jack (using QJC or whatever)
5) Start vstserver
6) Start vsti
vsti ../vst-JX200/JX200.dll
(this path is referenced from vst-dir)
This is working for me, although I have not tried JX200 itself.
Good luck,
Mark
28 May
28 May
5:27 a.m.
New subject: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
On Thursday 27 May 2004 22.22, Mark Knecht wrote:
Robert Jonsson wrote:
Sorry, I should have been clearer. I had already tried this approach, pretty
much the same thing happens. The answer must be somewhere else, if I have
time I will try to compile a new wine tonight.
/Robert
Okay, I tried to get some VSTi's working but
I get this error always.
VSTSERVER/main: Going to try to start vst plugin "JX220.dll".
wine: cannot find 'JX220.dll'
This is with VST_PATH set to the place where JX220.dll is, so vstserver
finds it but wine does not.
I have a feeling I have seen this type of error mentioned recently, name
problem?
Wine is apparently from february, could this be it?
(apologies if this just has been discussed, I missed a bunch of messages
yesterday)
/Robert
I cannot (so far) get vstserver to run these things directly, but if
you're using JAck then try vsti from Kjetil's web site.
1) Create two directories in your home:
a) vst-dir
b) vst-JX200
2) Export vst-dir but have nothing in it
3) Place the JX200.dll file in vst-JX220
4) Start Jack (using QJC or whatever)
5) Start vstserver
6) Start vsti
vsti ../vst-JX200/JX200.dll
(this path is referenced from vst-dir)
This is working for me, although I have not tried JX200 itself.
Good luck,
Mark
--
http://spamatica.se/music/
6:15 p.m.
New subject: Patch for port naming, Re: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
Hi,
I finally got it working by upgrading my Wine install. And it is working quite
nicely at that, tried a bunch of synths fro kvr-vst that work pretty good.
But this mail isn't about that.
>
> The problem is that seq24 will not start with vsti running.
>
> Another problem is in muse, if I have two vsti s running they are only
> selectable as one instrument...
This happens since because vsti always exported them with the same port name,
which MusE doesn't like.
This vsti patch makes vsti add the client_name to the port name (it can be
argued if the Input/Output prefix needs to be there but I guess some hosts
like it).
--- oldjc.c 2004-05-28 21:53:00.000000000 +0200
+++ jackclient.c 2004-05-28 21:55:43.000000000 +0200
@@ -66,7 +66,14 @@
snd_seq_set_client_name (seq, client_name);
- err = snd_seq_create_simple_port (seq,
isinput==true?"Input":"Output",
+
+ char portName[100];
+ if (isinput)
+ sprintf(portName,"Input/%s", client_name);
+ else
+ sprintf(portName,"Output/%s", client_name);
+
+ err = snd_seq_create_simple_port (seq, portName,
Regards,
Robert
Interesting, I haven't succeeded in trying this yet, any idea why it is so?
Only one alsa interface exported?
/Robert
> the pd plugin seems to offer more
> flexibility with respect to these problems, but I agree it is quite
> fiddly.
>
> James
--
http://spamatica.se/music/
7:54 p.m.
New subject: Patch for port naming, Re: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
On Fri, May 28, 2004 at 10:07:21PM +0200, Robert Jonsson wrote:
Hi,
I finally got it working by upgrading my Wine install. And it is working quite
nicely at that, tried a bunch of synths fro kvr-vst that work pretty good.
But this mail isn't about that.
Nice work.. will have to try this.
James
>
> The problem is that seq24 will not start with vsti running.
>
> Another problem is in muse, if I have two vsti s running they are only
> selectable as one instrument...
This happens since because vsti always exported them with the same port name,
which MusE doesn't like.
This vsti patch makes vsti add the client_name to the port name (it can be
argued if the Input/Output prefix needs to be there but I guess some hosts
like it).
--- oldjc.c 2004-05-28 21:53:00.000000000 +0200
+++ jackclient.c 2004-05-28 21:55:43.000000000 +0200
@@ -66,7 +66,14 @@
snd_seq_set_client_name (seq, client_name);
- err = snd_seq_create_simple_port (seq,
isinput==true?"Input":"Output",
+
+ char portName[100];
+ if (isinput)
+ sprintf(portName,"Input/%s", client_name);
+ else
+ sprintf(portName,"Output/%s", client_name);
+
7275
days inactive
7276
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
James Stone -
Kjetil Svalastog Matheussen -
Mark Knecht -
Robert Jonsson