I usually set Audio Driver with messages,
like sampling rate, overdrive, takeover, vector size etc.
All that can be done with messages, and controlled by delayed loadbang.
Starting dsp after that has allways worked for me.
My only problem ever was that Max sometimes sets Audio Driver
to none, if Prefered Audio Device is not present.
Not a big deal for using Max to do some work,
but can be a problem in case of Standalone.
Here one example :
delay will not really work for me. i dont know how long the patch takes to open.
then i could as well leave it to the user.
which is normally not a big isssue in max7 if i should be honest; people are used to use the button on the sidebar.
but i´d like to have certain patches to start playing audio after they are opened.
eventually i need to geet back to the trick which i always recommended for vst: request something from the object in order to find out when the task has finished, then trigger the next step from there.
One can't trust 100 % that whatever method will allways work.
I prefer to have dsp auto loaded upon start, that works in most cases
for standalone, cause it creates own preferences which remain unchanged
till one wants to change them.
And a good visible button dark for Off, red for On, indicating dsp state.
I don't like that ezdac look.
If You are a bit away from the screen on stage, You can't really tell
if it's on or off.
Here is a patch waiting till iovs and sigvs match :