On Tuesday, June 28, 2016 10:53:16 PM EDT Robert Jonsson wrote: > Hi Tim, > > 2016-06-28 21:34 GMT+02:00 Tim E. Real <[email protected]>: > > On Tuesday, June 28, 2016 8:51:17 PM EDT Robert Jonsson wrote: > >> Hi Andrew, > >> > >> There has been wierd things going on with LV2 for a while and I hadn't > >> been able to understand exactly what was happening. > >> > >> Biggest problem has been that plugins have been detected but do not > >> appear in the GUI, I have a feeling they were sometimes detected > >> wrongly also. > >> > >> Well, today I got much closer. > >> After finding out that it works correctly in muse2 I managed to find > >> the checkin that causes it to fail. > >> > >> it's this one: Optimize lv2 plugin wrapper > >> https://github.com/muse-sequencer/muse/commit/e4d74a37f5e2a9b1a562d93c31e > >> 0e8 0e7345c56d > >> > >> Unfortunately I'm having a hard time understanding exactly what this > >> changes and neither what could be wrong. > >> Can you give me a hint on what to try? > >> > >> Regards, > >> Robert > > > > Hey Robert. > > > > That's Andrew's checkin but maybe I caused something too. > > It's explicitly this checkin that causes my test case to fail atleast. > > > Can you give me some examples of plugins that aren't working? > > > > I can take a look. > > It sure sounds like the old 'synth vs. effect vs. number of > > inputs/outputs' > > > > plugin listing categorization problem. > > Yeah I see a bit of that also but I think it's a different problem, see > below. > > I put yoshimi and TAL NoiseMaker in separate folder and only added > this folder to LV2 path
Just to be clear, I hope this was not the /only/ path in the LV2 path dialog. As the text warning says in the path dialog: a path to the /system/ LV2 libraries must be there as well. Otherwise weird things happen - plugins will be detected but they won't work properly because the discovery mechanism relies on some of the system LV2 components to figure out what exactly is being opened. In fact one of the weird symptoms is that some synths may not be detected as synths. They will be detected as 'bare minimum' effects because the discovery mechanism can't find a match for some of the crucial xml identifier strings in the plugin. > and then I tried stepping through the code. > Both synths are recognized (they are infact detected as plugins, not > synths, as noted I think this is a separate issue) but later when the > GUI is fully started they are nowhere to be seen. > If I roll back to the git checkin before this commit, everything works > fine, two Yoshimi versions and one TAL NoiseMaker is displayed in the > gui. > > Now, I know there is a recent bugreport about TAL NoiseMaker not > working (but being visible) with muse-3.0pre1. On my system it is not > visible with current builds. So it seems the bug could manifest itself > differently on different systems. Maybe memory corruption or list > items being lost.. or something. The checkin seems to handle the list > of plugins in various ways. > Or I might have gotten it all backwards, though since that has never > happened before I find that highly unlikely ;) OK Thanks, will check it out when I can. I'm neck-deep in code right now... Tim. > > Regards, > Robert > ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
