27 May
2004
27 May
'04
3:53 p.m.
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/