Subject: Patch for port naming, Re: [linux-audio-user] Any instructions about for running a Win VSTi under vstserver
From: Robert Jonsson (rj_AT_spamatica.se)
Date: Fri May 28 2004 - 23:07:21 EEST
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/
This archive was generated by hypermail 2b28 : Fri May 28 2004 - 23:02:09 EEST