Really awesome work! vannot wait to play wiith this. on hardware but aa wel on software like channel strips and fx in Ableton.
so if I understand it correctly the first 12 snapshot spots i should keep free for morphing and random goodnes?
cannot wait to try it on my Yamaha TX816.
Just installed the 4.0 beta and can confirm this works out of the box with the current version of the Ableton remote script.
Swipe gestures could be improved : my swipes fail half of the time ;-0
And canāt wait for the consolidated documentation with all the new features fully described - with that I can tweak and improve the remote scritp some more (performance page for presets, and SysEx transaction identifiers to properly match ACKs/NACKs to make the remote script more reliable)
Update: Iām running in some bug now with the preloaded presetsā¦ Setting USE_PRELOAD_FEATURE = False seems to work for the moment (but makes the script slower, of course).
I made some improvements recently. I also want to add an animation for the swipe = so that there is some visual feedback. I am sure it will help.
I am not sure I understand it correctly. Do you mean that preset changes do not work after some time when USE_PRELOAD_FEATURE = False? Pls let me know. Thx!
No, the bug appears when USE_PRELOAD_FEATURE = True and disappears (i.e. preset changes work) when USE_PRELOAD_FEATURE = False.
Some more info. While debugging, I noticed that even uploading a simple preset (4100 bytes) can take long: an ACK may only be sent after more than 1 second. That seems excessive.
Even some more info: it used to be the case that uploading a preset on MacOS using sendmidi (for sending the large sysex) would be much faster than uploading using the standard Ableton sysex MIDI functions. They now take exactly the same time! Any idea why that could be the case?
Update: after downgrading to 3.7.0 using sendmidi is again much faster than standard sysex upload (which takes roughly the same amount of time for both 3.7.0 and 4.0.0).
I did a few tests yesterday but I got rather fast responses. But I have sent the sysex from the browser. I will test it with the sendmidi and will try to downgrade to 3.7.
@martin
Iam new to the E1 and a coder. Is there any API-reference for all the LUA-classes, methodes, etc.?
The v4.0.0c is available now.
firmware-v4.0.0c.srec.zip (1.8 MB)
This has been done:
I am usually working with Electra that does not have the aluminium enclosure. I was surprised how much difference the enclosure makes when detecting the gesture. It is improved now and the swipe now adds a simple animation (so that the user gets an idea that something is happening)
It should work correctly now.
Also, note the onPotTouch() works but I marked it as a deprecated function. the onPotTouchChange() should be used instead. The main difference is that it uses 1-based index for potIds. @Phommed
Further, there were a few issues with system freezes reported when using @jhhās ableton script. I was able to reproduce it (at least some) and fixed that. @jhh please give it a try.
The controller now saves all changes made in the Settings window. It is possible to configure the UI, Preset banks, external MIDI control.
Note, the on-screen keyboard is a very early version. It still needs doing.
The controller.potFunctions table has been renamed to preset.userFunctions. The example preset has been adjusted accordingly. @Phommed
the v4.0.0c seems to be rather stable when I am testing it, I will wait for your feedback though.
To fulfill the scope of 4.0 this still needs to be done:
@christianvogel All relative controls can now have acceleration enabled / disabled.
accelerated flag can be used for that. I still need to add it to the editor.
Please take a look at Lua Extension Documentation.
Some quick testing shows that using the preloaded preset now works, but that sendmidi still takes the same (very long) time to upload presets (as long as using the native SysEx method of Live under MacOS).
I still need to take a look at that one. Do you feel that the swipe is better now? I have a bit of troubles with judging that because I exactly know what I need to do to with my fingers to active itā¦
Could that be the reason why those knob touch sensor issues were so difficult to reproduce initially on your side?
Swipes are much better now, and the visual feedback is a nice touch!
HI @martin Happy New Year to you and everyone here.
Just started testing v4.0.0c. Some observations:
The change to to preset.userFunctions seems to work OK.
The bug with previously invisible controls and onPotTouch seems to have been fixed - thanks.
I changed my preset to use the new function events.onPotTouchChange(potId, controlId, touched). The function internals do not seem to get executed and I see the deprecated warning in the log. You did not mention that the onPotTouchChange method has a different parameter list, so I simply added the word āChangeā to the code.
11:37:42.638 onPotTouch function will be deprecated. Use onPotTouchChange instead.
I just discovered another bug (in the 4.0.0.c firmware): setSlot no longer properly works. In my Echo preset, the 16th and Division that should appear in slot 1 and 7 of the first page no longer appear. In Roar, the LFO 1 Rate and LFO 1 SYNCD RT appear shifted down.
Sorry if this has been asked - have been searching unsuccessfully for an answer. Is there a way to reduce knob sensitivity with V4.0?
Iām working with a Lexicon PCM81 and the knob for scrolling patches is wayyy too sensitive. A tiny nudge will blow through a handful of patches. I thought I read this was a new feature in 4.0, but I wasnāt sure how to activate it. Thank you!
I was looking at changing the selector to jump by bank via knob/screen tap, but never fully implemented it. It would work similarly to how you tap the screen when renaming a patch and it jump through lower, upper, numbers, specials.
One issue with devices that can support a wide range of values (oscillator frequency, patch bank, MIDI CCs, etc) is trying to help the user dial things in quickly and reliably.
One option is a coarse/fine control like some gear has for frequencies/tuning. I donāt know if having 2 controls (one for bank, one for patch number in the bank) would be more of a user pain or a user help.
These are the kinds of things where getting feedback from real users in real situations can help the preset designer make it better for all.
thanks OGG! sorry I didnāt surface this in the PCM editor thread. I thought firmware 4.0 had a native way to reduce sensitivity, so fielded it here.
have you played around with the H3000 Program Change preset someone made? I have been using it in conjunction with your H3000 editor; I like how they implemented. You select a bank first, then long pressing the patch/program selector gives you a vertical menu you can scroll through either with touch or with a knob.
I guess this doesnāt quite work 1:1 with the PCM though because of how the banks are structured (more banks, fewer patches per).
I have not seen that - thanks for pointing it out.
In the past, Iāve had mixed success with double-taps and things like that. I have not installed the latest OS on purpose because I wanted to get my editors stable on a particular version and then try out new features as they seem appropriate (remapping the soft buttons and other improvements like swipe gestures).
Iām very aware of overloading controls for multiple duties because people can mistakenly be doing one thing when they mean another. One of the benefits (for me) of the Electra One is that you pretty much have a 1:1 mapping of control to parameter and a known set of functionality. For me, thatās why I tend to favor on-screen Page buttons to jump between areas rather than relying on the extra press of the soft button to bring up the list of pages.
Itās certainly flexible enough to support multiple approaches/UI philosophies, so whatever works for both the developers and the users is fine by me.
Again (and forever) - the biggest thing users can do is to provide usability feedback to the developers. Thereās no way to know ahead of time if people like my approach to a preset or if theyād rather have it some other way.
