M4L - initial load time (standalone & from within Ableton)
Hi all,
I'm hoping for some input on M4L.
I use a number of fun step sequencer devices I've downloaded from the maxforlive.com library.
Multiple devices ‘forget’ their settings when I reopen the project I am working on. For example, the pitch steps in a sequencer will all play the same tone despite having different values. Inconvenient, but not a huge problem.
I am able to circumvent this by opening the 'device edit' pop-out in Ableton (which launches M4L), then closing M4L. The device then functions as per normal, playing the different pitches. However the pitches are then reset again when I re-open a project.
Secondly, and most frustratingly, when doing this it takes minutes the first time I launch M4L (I just timed this at 2m06s). For obvious reasons this is frustrating. After the initial launch, this process is almost instantaneous until I close Live and reopen it. Any ideas how to improve this scenario?
For context, I’m using the following kit:
Ableton Live Suite 11.2.11
M4L 8.5.4
Windows 11, Intel 13th gen CPU, 32GB DDR5 RAM
Any input would be valued.
FCT.
Yes, loading large devices can be slow. Don't know any solutions there! If the device forgets its settings, that has to do with how they coded it so I think you could only change that be editing the device!
An unfortunate side effect of making a low-bar-for-entry programming environment and distribution hub ends up being loads of inadequately tested/maintained gadgets. Stuff that works 95% of the time is borderline unusable in practice due to #$%! like this. I envy your patience in dealing with it...
One suggestion on a more permanent change you could make which might help is adding this code to the devices that are giving you problems. It's a lazy way to try to nudge out the values of stored parameters and it might help in these cases.