Honestly? I didn’t learn by going through tutorials, but more by working goal based.
The tutorials you should cover first is not on the Electra One itself . Foremost :
- how good is your understanding of MIDI ? CC? NRPN ? Clock ? SysEx ?
- how good is your understanding of lua in general, so not specific to the E1?
Once you can say to yourself, “reasonable” , then the next question is: what is it you want to do with it?
For me personally it is and was about:
- providing older 80’s and 90’ synth hardware, typically deprived of buttons and faders themselves, of an interface to control them physically and make them musically attractive
- parsing synth data so I can visualize how sounds are made and learn from it
- adding features to synths they don’t have themselves, like additional lfo’s, mod matrices, clock sync
With these goals in mind, I then select a synth (an easy one to begin with), read the synth’s MIDI (CC ànd SysEx) capabilities found in their MIDI implementation guides, then set for myself how I’m going to use Electra One to control it. Usually there are new things I want to try, so then I resort to two main sources:
- I check the lua guide for the E1 (it is the “lua extension” beneath the “developers guides” Lua extension | Electra One Documentation) to find out what function or callback could be useful for what I’m about to do
- I ask the forum (like you do) for ideas, tips and tricks and this helps a lot
I made a kind of guide on parsing synths, which can be found in the forum. It’s not perfect, but can be of help if that is what you want to do: Adding patch parsing to a preset. Step by step
Also relevant is having a MIDI monitor (like MIDI-Ox) so you can see the communication going on between the Electra One and the Device you try to control. That ensures you are not working blindly.