FST midi port is in JACK-MIDI namespace, but MusE doesn't support it, it works with ALSA Sequencer. Try a2jmidi, this should help.

There are two branches: muse and muse_qt4_evolution. First steel have no jack midi support (or I didn't see some option?), qt4 version: it is usable with audio disabled (-m option), but steel not so convenient, as stable branch. Also, it is not known, is qt4 branch should be complete somewhen. ----- 0.x -------- 1.x (qt3, autotools, alsa-midi) | \---------- 2.x (qt4, cmake, jack-midi) -- this may never be concluded. Active development is in 1.0

Thanks guys,for your ideas and further help. Robert, sounds interesting. When I select "seq" as MIDI Device in QJackCtl, I can control the VST with my keyboard (starting it with FST), however I still cannot record it in MusE. Robert provided an alternative option to run windows VSTs, namely dssi-vst. I just installed the newest version from source, there is one thing left to solve. When I type this in my terminal: pieter@s061123:~$ export DSSI_PATH=/usr/local/lib/dssi pieter@s061123:~$ export VST_PATH=/home/pieter/.wine/dosdevices/c:/Programme/Steinberg/Vstplugins/Soundbytes pieter@s061123:~$ jack-dssi-host dssi-vst.so:HurdyGurdyLE.dll This message is printed: jack-dssi-host: Error: Plugin label "HurdyGurdyLE.dll" not found in library "dssi-vst.so" Even though the dll is present in the directory specified as VST_PATH! I assume this is due to the presence of a colon-character in the VST_PATH? When I move the dll to /home/pieter/vst (default VST_PATH, after I cleared the VST_PATH variable), it is found but it complains it isn't installed yet (because I installed the VST with Wine in some wine directory). I doubt it whether it is a good idea to install the VST in the /home/pieter/vst directory...? Should I configure dssi-vst in some way, such that it actually uses the path in the VST_PATH? Best regards, Pieter

Ah, I didn't know that possibility. Simple yet effective. However, it doesn't work yet. Jack-dssi-host can now find the dll, but it complains about the file "liblo.so.7": ... /usr/local/lib/dssi/dssi-vst/dssi-vst_gui: error while loading shared libraries: liblo.so.7: cannot open shared object file: No such file or directory ... However, this file is present on my system: pieter@s061123:~$ locate liblo.so.7 /home/pieter/Desktop/MusE/VST/liblo-0.26/src/.libs/liblo.so.7 /home/pieter/Desktop/MusE/VST/liblo-0.26/src/.libs/liblo.so.7.0.0 /usr/local/lib/liblo.so.7 /usr/local/lib/liblo.so.7.0.0 Any ideas? On Mon, 2010-05-17 at 15:26 +0100, Peter Nelson wrote:

Did you tried 'ldconfig'?

On Mon, 2010-05-17 at 17:16 +0200, Philipp Überbacher wrote: Hmm after I copied the file liblo.so.7 to /usr/lib, the GUI became visible (but there is - of course... - another problem). On Mon, 2010-05-17 at 19:28 +0400, Mike Cookson wrote: No I didn't, but out of curiosity I removed the copied liblo.so.7 file from /usr/lib again and ran ldconfig, I'm not completely sure (briefly checked the manpages) what it does but after running the command the GUI started as well. On Mon, 2010-05-17 at 19:31 +0400, Mike Cookson wrote: Ok thanks for the idea, I will check it out. --- Well, the VST appears in MusE now, but the VST itself says "Audio Engine is not Active". Jack and MusE are both running, how can it be not active? When I ran the VST with FST, the message didn't appear. Argh, it becomes frustrating. I don't want to give up, it should work with dssi-vst too. Are there any ideas why the VST would print this message? Sorry to bother you with such beginner-questions, I'm still a bit of a Linux newb :)

It I am right, MusE maps multiple devices MIDI ports (plugins and other alsa clients) to single alsa ports (one - input, another - output). If I will connect by hands MusE a2jmidi ports with other jack-midi ports, how I will assign them to according midi tracks? :)