Im having an issue whereby I manually bang values in subpatches and develop code...all runs fine. When I reopen the patches to work on them later, the Live UI values are not making to the right spots...as a newb, what is best practice for getting the values to init properly?
Whats more is that its inconsistent, some identical modules seem to have varying results as far as init goes.
Eg The Track and Scene groups were the first 2 I programmed, I copied the Track and updated the parameters etc and it just doesnt start with init values and I can only get it working if I manually bang in the subpatch.
What is best practice?
https://drive.google.com/file/d/1PWJsyl ... sp=sharing
https://drive.google.com/file/d/1PWJsyl ... sp=sharing
Cheers
Mark
Patch UI values not initialising: Best practice for init?
-
- Posts: 152
- Joined: Sat Jun 07, 2008 10:38 pm
- Location: Sydney, Australia
Re: Patch UI values not initialising: Best practice for init?
use "live.thisdevice" instead of "loadbang"
copy the text, open Live > drag in empty M4L device > open Max editor > paste > save M4L device
https://docs.cycling74.com/max8/vignett ... ng_patches
https://doubleUG.bandcamp.com/releases
https://docs.cycling74.com/max8/vignett ... ng_patches
https://doubleUG.bandcamp.com/releases
-
- Posts: 152
- Joined: Sat Jun 07, 2008 10:38 pm
- Location: Sydney, Australia
Re: Patch UI values not initialising: Best practice for init?
Thank you @doubleUG...doubleUG wrote:use "live.thisdevice" instead of "loadbang"
Tough migrating from Pure Data...both have their strengths.