From: <doo...@ya...> - 2009-05-15 02:34:29
|
Hi there I'm fairly new to Linux and RG, but recently managed to move from 64studio 2.1 to the new 3 beta, but now I can't see the Fluidsynth plugin in RG. I've also posted this to the 64studio forum - http://www.64studio.com/node/1138 - not sure if it's a distro or RG issue. Apologies if this is the wrong place! When I left-click an empty track in RG, choose "synth plugin", then go to "Instrument Parameters" and click "no synth", I used to be able to choose Fluidsynth from the drop-down list. Now I only see Oscilloscope, wsynth, xsynth, hexter and nekobee. Could someone please point me in the right direction to help get Fluidsynth added as a plugin again in RG ?? Many thanks for any help! Rich |
From: D. M. M. <ros...@gm...> - 2009-05-15 04:56:37
|
On Thursday 14 May 2009, doo...@ya... wrote: > Could someone please point me in the right direction to help get Fluidsynth > added as a plugin again in RG ?? The most likely explanation is that the plugin is not installed on your system. Do you have a package called "fluidsynth-dssi" installed? If not, there's your answer. Another common problem is that distros have been releasing Rosegarden packages without liblo support built in, so you can't run the external plugin GUIs. If that happens, you get no "editor" button That is a real problem for Fluidsynth-DSSI, because it's totally useless without its external GUI. I'm not sure what would happen for an external-editor-only plugin where we couldn't display the editor button. It *might* not show up on the list of available plugins in that case, so you *might* have a broken Rosegarden package built without liblo support. You can test for this by running (from a command line): $ ldd `which rosegarden`|grep liblo It should return something like: liblo.so.0 => /usr/lib/liblo.so.0 (0xb7423000) If it doesn't, your package is broken. If we should happen to establish that to be the case, we'll discuss what to do about it in more detail. Finally, another common DSSI problem involves not having localhost in /etc/hosts If it's none of the above, then I'm stumped. -- D. Michael McIntyre |