Admittedly, the on-line manual only shows cabbageCreate being used in an instr > 0. But since cabbageCreate only works at i-time and is needed when app/plugin starts, it seem superfluous to drop those calls inside a numbered instr instead of the top-level orchestra code (aka instrument 0). However cabbageCreate does nothing if called from the (top-level) instrument zero orchestra code. This is slightly confusing.
By the way, when cabbageCreate is called from a numbered instrument, that instrument can be turned off (with turnoff) right away after cabbageCreate without affecting the generated widgets. So, being in a running instrument doesn't seem essential for cabbageCreate.
(I'd have guessed that maybe cabbageCreate and friends are injected by Cabbage as UDOs at the end of instrument 0, but in that case they'd give an explicit error when used before definition in instrument 0.)
Admittedly, the on-line manual only shows
cabbageCreatebeing used in aninstr> 0. But sincecabbageCreateonly works at i-time and is needed when app/plugin starts, it seem superfluous to drop those calls inside a numberedinstrinstead of the top-level orchestra code (aka instrument 0). HowevercabbageCreatedoes nothing if called from the (top-level) instrument zero orchestra code. This is slightly confusing.By the way, when
cabbageCreateis called from a numbered instrument, that instrument can be turned off (withturnoff) right away aftercabbageCreatewithout affecting the generated widgets. So, being in a running instrument doesn't seem essential forcabbageCreate.(I'd have guessed that maybe
cabbageCreateand friends are injected by Cabbage as UDOs at the end of instrument 0, but in that case they'd give an explicit error when used before definition in instrument 0.)