On 01/31/2013 01:24 PM, D. Michael McIntyre wrote: > On 01/31/2013 12:15 PM, Aere Greenway wrote: > >> It would be more useful to me if there were a way of firing up a >> collection of DSSI instruments, each with their own configuration >> restored (and saved), that I could access using the ALSA sequencer >> interface. > When I think about it at some length, I think you and I are both > probably just caught up in a more traditional MIDI mindset. > > You could almost use one instance of Rosegarden as a plugin rack and > talk to it with another instance of Rosegarden, but that seems really > silly, doesn't it? > > The reasons why it probably wouldn't work are a lot of the same reasons > why it would be challenging to write a synth plugin rack generally. How > do you talk to it from outside when it has such a wildly and infinitely > variable configuration? Rosegarden's device definitions would need to > be updated to be specific to each particular permutation of some > particular combination of plugins, for each and every permutation you > wanted to use. There would need to be some way in place for Rosegarden > (or any other sequencer MIDI emitter) to get in deep inside whatever was > going on with that rack on an intimate level. > > Just doing the plugins inside Rosegarden starts to make vastly more > sense when you think about the mechanics of making it all fit together > using MIDI as the bridge. > > I think it's just a mindset thing, but I do sympathize with where you're > coming from. I've never really used synth plugins for much of anything > other than demonstration purposes myself. I'm not very comfortable > working that way, as opposed to the familiar and traditional way. > > It probably is the way to go though. Holger has a very good point; > especially concerning latency. > > But hey, I just woke up and I'm still three quarters asleep, so I could > be babbling. Michael, and all:
Thank you for your time brainstorming and coming up with ideas on this. After sending my last e-mail, I searched around a bit, and found a software package called "ghostess". I tried it with the following statement (executed in a terminal window), which created a sort of custom synthesizer, having two MIDI channels (1, and 2), each with an instance of the Fluidsynth DSSI. It creates a GUI with a single button for each channel (that allows you to activate the DSSI plug-in's editor), which let me load a different soundfont in the two instances, testing their sounds: ghostess -2 /usr/lib/dssi/fluidsynth-dssi.so My MIDI device was able to communicate with it, and it had low latency. It could save its configuration. It has a lot of command-line options I didn't delve into very deeply. I will experiment more with it. It's author(s) said it wasn't a polished product, but a quick hack. But it seemed to work well in the hour I played with it. There is a similar package (at least, the documentation for using it seems similar), called jack-dssi-host. I haven't tried that one yet, but ghostess seemed to work for what I was looking for. -- Sincerely, Aere ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
