Thread issue maybe? #168
Description
I'm using handleNotification() in your StateObserver class (just copied from your example) to update things in realtime and create automations (this includes modifying things in the engine, ex. changing a parameter on an fx step 3-6). When just calling the relevant objects I get occasional null pointer dereference crashes. Calling them from the UI-thread is way more stable. I'm not good at threads, I guess I just vaguely get the concept, but it seems engine updates should execute in whatever thread the engine used to call them to avoid conflicts like this? Or does it get weird C -> Java? Or am I completely wrong here and just need to write better applications =)? (that last happy face does not mean I don't see it as an option, as I said I don't know threads).