Re: [Lmuse-developer] Bug in DSSI Host Implementation

[Tim E. R. <ter...@ro...>]

On June 29, 2012 9:38:56 PM Florian Jung wrote:
> Hi
> 
> i just want to encourage you to get back to this problem ASAP. we want
> to release muse, well, _now_, and if you're right with that bug, we'd
> need to fix it before. as i said, i couldn't reproduce. can you please
> give detailed steps?
> 
> thank you :)

I read Jeff's post, haven't had time to investigate.
But he's probably right about multiple instances, he's quoting from
 the docs. I believe this would not be something easily fixed 
 at this exact moment.
Will try to check more...

Tim.

> 
> greetings
> flo
> 
> Am 29.06.2012 10:20, schrieb Florian Jung:
> > Am 28.06.2012 04:30, schrieb Jeffrey Hubbard:
> >> Hello,
> >> 
> >> I know you guys are super busy right now with the 2.0 release(you're
> >> doing a fine job, BTW), but I wanted to bring this to your
> >> attention:
> >> 
> >> From dssi.h :
> >> 
> >> * Calls to configure() are not automated as timed events. * Instead,
> >> a host should remember the last value associated with * each key
> >> passed to configure() during a given session for a * given plugin
> >> instance, and should call configure() with the * correct value for
> >> each key the next time it instantiates the * "same" plugin instance,
> >> for example on reloading a project in * which the plugin was used
> >> before.  Plugins should note that a * host may typically instantiate
> >> a plugin multiple times with the * same configuration values, and
> >> should share data between * instances where practical.
> >> 
> >> From http://dssi.sourceforge.net/RFC.html#toc14:
> >> 
> >> 
> >> And these are the methods the UI may support:
> >> 
> >> ....
> >> 
> >> * <base path>/configure
> >> 
> >> Used to notify a UI of the current configure state of the plugin. If
> >> the host has set any configure data on the plugin at startup (as
> >> remembered from a previous invocation), it will call this function
> >> once for each piece of configuration data following the UI's update()
> >> request, e.g. on startup.  Takes two string arguments for key and
> >> value.  (required method)
> >> 
> >> It would appear that Muse2 is calling configure() in the plugin
> >> itself, but not in the plugin's GUI(alternately, if it is calling
> >> it, then there's something else wrong with the implementation, but as
> >> far as I can tell it's not being called).
> >> 
> >> 
> >> 
> >> 
> >> Test Case:
> >> 
> >> My sampler DSSI plugin's GUI uses that feature to recall the  list of
> >> samples it has loaded between sessions.  It works as expected in
> >> Rosegarden, but it does not work in Muse2.
> > 
> > can you please specify "my sampler" and "works [not] as expected"?
> > 
> > i just tried the following with the fluidsynth-dssi synth:
> > 
> > start muse, create instance, load a soundfont (via configure()) in the
> > native gui. save song, exit, restart muse, reopen the native gui. the
> > settings are remembered,  no bug.
> > 
> > does your synth behave differently, or are we talking about a different
> > issue?
> > 
> > greetings
> > flo
> > 
> >> Thanks, Jeff
> >> 
> >>