Hi Robert! Thanks for testing :). Last 3 days i'm working on control automation. I had the same issues as you. Here is the summary of them (with status):
1. Current commit that you are testing have control loopback bug. that is: touching gui control makes host receive it and send it back again. It caused some plugins to crash (guitarix for ex.) and some not to respond after some time. This is fixed now. 2. Automation was not recorded. I've used wrong function to send gui controls to muse (addScheduledControlEvent). Now I rewrited that code and all works fine as expected. 3. GUI meters not updated in some plugs - yes, I also have this issue. I think that I'll find solution in near time. And I've added LV2_Worker__interface specification. More plugins appeared in the list :). I have not committed my changes yet, but I'll commit them soon (may be tonight. I'am on GMT+4). Best Regards, Andrew > Hi Andrew, > > My testing has been a bit less structured than I aimed for but I > wanted to share a bit more. All basics seem to work very well, > loading, saving, playing, opening guis, operating parameters. > There has been a few occasions, hard to repeat, where the gui hasn't > been responsive, as I reported earlier with the linuxDSP chorus > plugin. Upon retry it worked. > > I tested the CALF Crusher and seems to be a plug that exhibits some > gui issues with feedback to the gui that is commong to several of the > plugs. > I loaded a wave file in MusE and added a Crusher plugin to it's strip. > All fine, works great, bringing up the gui works fine and manipulating > the gui changes the audio. > The meters are however not updated, I tried it in Ardour and they > update so the plugin is ok. > > I also tried, with the CALF Crusher, to create automation from the GUI > while playing by setting the track to Write and moving the bit > reduction knob. MusE updates the automation curve but it's not > recorded. > I tried from the generated gui and automation is recorded. > Interestingly the automation curve wasn't updated during creation > though, some MusE internal issue maybe. > > I also had some crashes due to double delete while wildly operating > the bit reduction knob ;) I guess it's hard to tell where the crashes > originated without further analysis, MusE died anyway. > > That's all for now. > > I think for the moment the basics work and the plugins are quite > usable and stable (as far as I tested). > Really good work! It feels good to soon be able to check that LV2 item > off the TODO list :) > > Regards, > Robert > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > _______________________________________________ > Lmuse-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmuse-developer ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
