At 01:55 AM 6/21/2016, you wrote: >>Not only that, I don't find any other application from anyone having this >>problem, so it makes my apps look stupid. You said the stalling happens as a >>result of "CoreMIDI initializing", but why is this only a problem with MBS >>and not anything else?
>Let's change it. So the plugin doesn't do the initialization when plugin is >loaded. We simply move that to the constructor of the PortMidiMBS class. And >you can now call PortmidiMBS.Initialize to do the initialization when you want. Thanks very much. I'm a little confused though; you moved it out of the entire plugin init, correct? This was the whole problem - I didn't even have to declare a PortMIDIMBS class, your stuff would init before any code of mine would even occur. So I could never code any warnings or info to the user. Apparently now I can; if it stalls, I would set an indicator beforehand and the next time the app starts it would know it stalled the previous time and warn and instruct the user. That's good. But you moved it into the Constructor of the PortMIDIMBS class, but then you said I have to call a new method Initialize - why do that if the COnstructor method does it? Also see private email. Garth Hjelte Sampler User _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list mbsplugins@monkeybreadsoftware.info https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
