@d-healey said in Multi Instance DAW Crash Issue Guide:
Are you setting attributes only in deferred scripts?
Synth.deferCallbacks(true);
This is the second line on my onInit. I don't need to call this on my separate "include" scripts, right? Those should be considered part of the Interface script.
@orange said in Multi Instance DAW Crash Issue Guide:
Number one cause is the amount of used setAttribute APIs
@orange @Christoph-Hart does this also include setValue()? If not, I might use scripts to set the value of panels, and then us the Panel Property Editor to assign Processor/Parameter IDs.
Can panels even do that?...
@d-healey This specific DAW is protools, but I'm also seeing the issue in Logic.
I'm trying to track down a MAC core graphics issue that is making the DAW GUI sluggish.
Without OpenGL, the DAW will creep to a halt as soon as the plugin is inserted. With OpenGL enabled, the DAW is only slow when the plugin is visible.
It seems to only effect slightly older MacOS users.
Time Profiler points to an error in Core graphics while drawing pixels
ERROR_CGDataProvider_BufferIsNotBigEnough+0x31
Any tips or tricks with this?
@Christoph-Hart said in Expansion Tutorial:
I just want people to get acquainted with the basic functionality before taking the next step.
Ready! 
I think it depends on the OpenGL version installed on your computer.
https://forum.juce.com/t/opengl-not-working-black-screen/31182/3
from the link: (I haven't tried it yet)
you can add in your own OpenGL version check before doing any rendering with something like this:
auto ver = String::fromUTF8 ((const char*) glGetString (GL_VERSION));
and then fall back to the software renderer if it’s too old.
@orange said in Multi Instance DAW Crash Issue Guide:
Instead, use as jpeg
Are we able to use JPG? I thought PNG was the only option.