From: Chris C. <ca...@al...> - 2004-07-16 08:54:50
|
On Thursday 15 Jul 2004 6:21 pm, Silvan wrote: > I have two copies of both plugins in the combo box That would happen if you'd managed to install them to two places, e.g. /usr/lib/dssi and /usr/local/lib/dssi. > when I closed RG and restarted to get the fluid plugin going, the > same thing happened I described a moment ago. Raunchy sounds out > of the synth plugin engine until I hit play on the transport. Yes, I haven't managed to suss that one yet. I get the same thing: start up a new session, load a plugin synth, play something to it and it just _judders_. Only after the first play proper does it start sounding right. > GTK though? Why'dja use GTK for the plugin UI? It's so fugly. > Bleah. Whine whine whine. Ah, well, that's rather the point of the DSSI UI mechanism -- the plugin author can use whatever they like. I didn't write these GUIs, Sean Bolton did, and he writes in C and uses GTK. It might not go perfectly with Rosegarden, but at least you get a GUI. You can in fact override it -- you can provide more than one GUI for a plugin. That _gtk extension on the GUI executable name is recognised by Rosegarden: if it sees that you have two executables in the same directory and one's called something_qt and the other something_gtk, it'll pick the _qt one. (And it'll prefer something_kde to either, and something_rg to any of the above. As you may imagine, there's plenty of potential for overriding things using symbolic links too -- there's no reason you shouldn't have a single overarching GUI that acts for a whole set of plugins either. The possibilities are highly confusing, in fact.) Anyway, if you want a Qt GUI for one of these plugins, just read the DSSI RFC, start with the code in examples/ less_trivial_synth_qt_gui.cpp, and go ahead and write your own. Chris |