Sorry for my monologue: I found the cause of slowness when loading a custom preset. I need to manually upload my aalto-.epr and .ccmap to the hardware in the ctrlv2 folder to avoid uploading it to the device whenever aalto is selected. Is this documented somewhere? If my approach is acceptable for speeding up the loading process, I am happy to help with adding it to the document (btw. I can’t find the instruction for makedevices anymore, is it still on the github page?)
This might be related to the slowness observed on my E1 - E1 shows a dark screen when I select a rack or a VST without predefined presets stored in the hardware. In Log.text it stuck at this line:
Hi @jhh I just changed the config file as you suggested and restarted Ableton. However, now it’s working fine again. I will keep the config setting and report back if it happens again.
Thanks!
Considering the Electra One and – is there no video of how this script works? I’d love to be able to see even a short clip about how things work with the Electra One in Ableton.
How’s the script in its current state? I gather that autopopulating parameters works now? Anything major still missing?
The script is pretty polished with most functionality implemented as described in the README. Nothing major missing persé, although I do have ideas for future versions No video unfortunately; perhaps should make one…
Loving it so far. I’ve created/modified a bunch of presets for Fors devices already.
Just two questions:
The first one is related to the quote - is this still on the cards, switching devices from the E1?
Another - Seems that on the script, touching the encoders prevents you from using the left buttons to change focus. Is this something that can be changed by myself?
Thanks, what a wonderful script. Feels like I have a bunch of new almost-hardware synths now
when knobs are touched, the left side buttons changed their function. They can be used to display full screen version of the control and switch active parameter for mutli-parameter controls (envelopes). At present time there is no way to disable that
It might be nice to be able to disable the feature. I’m thinking, for instance, of live performances, where you’d have to do some ’hot knobs’ action to reliably switch knob focus
I’ve been manufacturing presets - working on the Fors suite of M4L devices. It’s going to be nice!
One issue: A device called Glänta does not populate a preset for me. Is it because of the scandinavian letter, or some other issue? If I rename the ‘container’ instrument rack to Glanta, it populates macro controls for me, but the actual M4L device doesn’t yield anything even if I rename that one to Glanta.
I can try and troubleshoot if there’s something specific I could try.
You did add a hyphen (-) to the preset name that you manufactured? If the rack is called Glanta and you select a plugin inside it, then the remote script loads the preset named Glanta- to manage the plugin.