I just started exploring E1 and made my first experiences. My really small first tests with CC messages, SysEx MIDI learning and the work with the App went pretty good so far.
Apologies if I overlooked something. But I can’t find any description about this area…
I even combined the current online manual to a PDF file to be able to search through it entirely but without any matches. I even couldn’t find a screenshot containing this area so I guess it has been added after the most recent documentation change.
I also searched the forums but without a match as well.
Thanks in advance for some enlightening.
Hi, Wellcome to the forum !
You’re right. The explanation should be in the “Electra Editor” section under “Grid” but that part is a bit outdated.
So let me bring you up to speed about this typical attribute set you get when you select a fader.
The minimum and maximum value are the values you want to see shown on your electra One.
If you don’t fill those in, the E1 will take the min and max MIDI value as the values to show.
You can use those for instance to make a range between 0 and 100, while the MIDI value is actually between 0 and 127 if you like that better. Mind you, the E1 will still use the full range of MIDI values between 0 and 127 but it would skip like about 1 value after each 4 and only use 101 values of the 128 available.
Another way to use the min and max value is for instance for a pan or tune fader. If the tune MIDI is going from 0 tot 127 with 64 as the center, then by assigning -64 as min value and 63 as max value you will get the following control
Now here comes the nice part: the “default” is the default shown value you want the control to start with. In the previous control I want the tune control to start right in the middle. As the middle is shown as ‘0’, that is the default you need to give. When tweaking the control, double tapping it will make it return to that default value. Always fill one in !!!
So the values in the example would look like
The next two fields are for advanced use, in which case you will need to use lua scripting. If these are your first steps, I would not go there today yet. Get acquanted with the non lua part first.
the formatter will allow you to show something completely different than what you can realise with those min and max values. To see examples of this. check this preset: Electra One App
See also here Preset Lua extension | Electra One Documentation
the function allows you to trigger a user defined function, written in lua, every time you tweak the control. What it does is up to you, by what you code in such a function. It could for instance send an additional midi message, hide or show other controls, change the name of a control etc…
For this you first need to learn lua a bit , before starting to use it. There’s lots of lua information and free tutorials to be found on the internet.
Thanks so much @NewIgnis for the clarification. Much appreciated.
I experimented a bit with the min/max values. In my particular case they don’t only affect the shown value but also have impact on the sent ones. That’s what was confusing me most. As soon as I had values inserted the turn of the referring knob led to weird behavior. But I need to check again with this new information in mind.
The “DEFAULT” already works as expected.
That was the main part I was wondering about. Now I know and will avoid start using scripts at this stage because I don’t have any experiences with scripting.
Thanks again and have a great weekend.
I now figured out the issue I experienced. Possibly a bug?
It seems to be not possible to use all value combinations for the fields “MIN VALUE” and “MAX VALUE”. For example the combination MIN = 20, MAX = 80, DEFAULT = 64 lead to the following behavior:
When turning the knob all the way down to the left and then moving the knob slowly E1 sends just the values 2 and 0 intermitting.
Moving it more fast then creates higher values at some point but it is unreliable and surely not how it should behave. It seems to me that it just affects the positive direction but I didn’t test that much. I even shoot a video (sorry for the bad quality) where I demonstrated the behavior with two different scenarios (software and hardware). Each starting without using the MIN/MAX values and then with the mentioned values.
Unfortunately I figured out the details afterwards so the video is more or less no longer necessary. I Created a project " Min/Max Value Test" which has just one control using the settings. Conneting a MIDI monitor should give the same result as shown in the screenshot so it should be reproducible (hopefully).
BTW: some other MIN/MAX value combinations seems to work fine. But I don’t have the time to check this all in detail.
I hope this makes sense. Thanks!
I will take a look at that. It seems the be the same issue that @jhh reported earlier. The fix will be in the upcoming release. Thanks for reporting!
Thanks so much for the confirmation.