Max 8.6.3 - existing patches open with DSP off and new patchers require a dac~ object to start DSP
Is this intended behaviour? Before this I was using 8.6.2 and I'm certain these issues were not present.
Please forgive me, I've only been using Max for a little over a week! If this is intended I will delete the post to avoid any confusion towards new users.
I'm running the Windows version on 10 Pro x64.
Thanks! :)
I should clarify what "requires a dac~ object to start DSP" means - basically, the DSP is shut off until a dac~ object is present in the patcher. The 'Audio on/off' button in the bottom-right stays greyed out until one is present. Cheers!
are you sure it is dac~? what happens with a single line~ object?
in previous max versions you also needed at least 1 MSP object in order to access the sidebar button.
That makes perfect sense, yes any '~' MSP object will enable audio to be switched on an off. Thanks for clarifying that!
Any idea on why patchers don't start with audio enabled? I have a test patcher at the moment that includes a basic test synth, a stereo delay and a few adc~ objects allowing external hardware audio into Max. Every time I open it up the DSP is switched off. Obviously not a huge issue, but I can't recall it being an issue until now.
Thanks, Roman!
that always has been an "issue", mainly with application building, and there is probably not only one reason why it is made like that.
my advice would be to take it as it comes and internalize that when you want to initialize a patch to "audio on" (as well as a certain midi settings around midiinfo) that this always requires more than a simple loadbang order "first here, then there".
in an extreme case, loadbang-1-dac~ can fail if it the dac~ object is the rightmost in the canvas of the patch - or if the audio IO settings are changed after that.
so when you do not want the user to press a button when your patch is opened, try to delay the loadbang or whatever works for your situation.
during patching in max there is something else you can do when you are annoyed that the audio always goes off again when you close the last patch: just have a little patcher running in background where the audio remains on all the time, and which is always open.
That's extremely helpful - I have already experienced some similar oddities with the midiinfo and adstatus objects, but I have found some reasonable workarounds. I will take everything you've said into account. Until it becomes a bigger problem later down the line, I will just have to to re-engage audio each time I start Max. I truly appreciate the help! Many thanks.