Firmware / Web editor beta testing

[jhh]

Optional indeed, please Can such options be set through a SysEx command? Then the remote script can make sure the setting is correct.

[jhh]

P.S. it would perhaps be good then any case to ensure that presets maintain their CURRENT state, so that people can actually switch between two presets.

[martin]

@jhh

Indeed. However, something else goes wrong now: for some reason when switching presets with the top right button from the effect to the mixer preset, the first group label (“Track X”) is not updated on the Main page (and also doesn’t magically get updated after switching pages). It does get updated when loading an empty Ableton live set (so that the mixer preset is visible straight away)

The first Lua execute call is missed on Electra’s side

remote script:

Electra:

I am looking at that…

[jhh]

Perhaps I could/should add a small delay, to ensure that loading of the preset internally in the E1 has settled before sending updates?

[martin]

Let me first check what is happening. Maybe I can tweak it on my side. That would be better way to take.

[martin]

I tried to load all public presets to fw 3.0. Everything seemed to work fine but Access Virus from @joris.roling. I will review what is happening there. If I remember that correctly, it is quite a complex preset.

[joris.roling]

Can’t remember what you are responding to

Maybe i can help with that virus preset. Yes it’s big!

[joris.roling]

But I tried latest beta, but I’m getting a lot of rogue CC’s after startup or preset changes. Also the device seem to crash when switching presets via touch knobs.

This I tried with a private preset, should I share it with you?

[martin]

@joris.roling

But I tried latest beta, but I’m getting a lot of rogue CC’s after startup or preset changes. Also the device seem to crash when switching presets via touch knobs.

The messages are actually ok. l mentioned that earlier today. They will not be there eventually, but it is an intended thing.

@joris.roling

This I tried with a private preset, should I share it with you?

please share it with me.

@joris.roling

Can’t remember what you are responding to

Maybe i can help with that virus preset. Yes it’s big!

I was not response to anything I just wanted to see that all public presets can be loaded. I had troubles with that one…

[martin]

@oldgearguy

3.0-a.7. In general it’s nice to see the controls look upgraded without me needing to make many changes. However, in my tc 2290 preset, I have a page that displays calculator-style keys and when you press Enter, it jumps back to Page 1, Control Set 0. That is locking up the E1.

This should work now too…

[oldgearguy]

Martin - when I have more than 2 free minutes, I’ll check it out.
I have so many projects half-started and right now, family and work has sucked up every second of my days.

I hope things in your world are going as well as possible.

Thanks for putting so much effort into reworking and expanding the entire Electra One environment.
It has been a pleasure to use it and watch it mature into this excellent platform for external control and more.

(E1 projects: tc 2290, finishing the Alesis Micron, Symetrix 606 started, Waldorf XT partially started, plus making daughterboards with an Arduino + CD4066’s to add MIDI control to Schrittmacher sequencers, consulting on a new hardware sequencer, beta testing for Conductive Labs, and sometimes even just sitting down and playing a synth or two…)

I need to retire so I can get more done.

lol

[martin]

3.0-a.13 is available on beta.

@jhh

Indeed. However, something else goes wrong now: for some reason when switching presets with the top right button from the effect to the mixer preset, the first group label (“Track X”) is not updated on the Main page (and also doesn’t magically get updated after switching pages). It does get updated when loading an empty Ableton live set (so that the mixer preset is visible straight away)

I checked everything and made a few adjustments. I still miss the first Lua execute SysEx message. Adding extra sleep before calling _mixer_controller.refresh_state() resolved that. I need to review it more. For now, this extra delay fixes that. @jhh would you take a look at that?

@jhh

Thanks, that indeed works. However, this introduced a new bug When switching presets, the E1 now also sends out the defualt values for the controls in the preset over the MIDI channel. This causes the values in the Ableton Live set (for either the mixer or the currently selected device) to be reset.

Default values are not send when the preset is loaded.

Changes:

• tried to improve layout and visual of the screens
• redesigned the bottom info bar. It uses bigger font now and shows information about used RAM and allows users to add a custom text (see bellow)
• it is possible to use a lua function to display a custom text in the right part of the bottom info bar. eg. info.setText("Hello World"). The text is limited to 20 chars.
• fixed a few issues with electra locking up when changing pages, presets, etc. There is still work to do.

For those who have troubles with web update …
firmware-3.0-a.13.img.zip (306.2 KB)

[jhh]

@martin

3.0-a.13 is available on beta.

I checked everything and made a few adjustments. I still miss the first Lua execute SysEx message. Adding extra sleep before calling _mixer_controller.refresh_state() resolved that. I need to review it more. For now, this extra delay fixes that. @jhh would you take a look at that?

I added a short delay to fix the issue for now. (It is a bit strange because actually the remote script first updates the return track names and only then the normal track names. But perhaps the issue is that the normal tracks are actually visible on the E1 and the return tracks aren’t.)

Default values are not send when the preset is loaded.

Excellent! Thanks!

As soon as the documentation is updated I will try to see whether it is possible to send the actual values Ableton reports for parameters as strings to the E1 (which would solve the issue that the values for complex paramaters like Volume faders or frequency ranges as displayed in Live do not exactly match the values shown on the E1).

[jhh]

@martin

• it is possible to use a lua function to display a custom text in the right part of the bottom info bar. eg. info.setText("Hello World"). The text is limited to 20 chars.

That message disappears as soon as you change preset.

Also, what exactly is the used RAM indicator showing? When changing presets it also changes: with large presets it is a few bars wide, with small presets no bar is shown at all.

[martin]

@jhh

That message disappears as soon as you change preset.

That is intended. The idea you can add your own text there in the context of given preset. eg. patch name (that is actually where the idea comes from). If the text was left there after the preset change it could easily become invalid - yet staying on the screen.

If you are asking because you would like to maintain some “state” across the presets - I am thinking about how to do that.

@jhh

Also, what exactly is the used RAM indicator showing? When changing presets it also changes: with large presets it is a few bars wide, with small presets no bar is shown at all.

it is showing percentage of used memory out of all memory available for a preset. ie. no white bars, = close to none memory used, white bars only = memory fully utilized.

I am not sure if this will stay there till the production release. It makes my life easier now when testing public presets and and reloading presets frequently.

[martin]

@jhh

I added a short delay to fix the issue for now. (It is a bit strange because actually the remote script first updates the return track names and only then the normal track names. But perhaps the issue is that the normal tracks are actually visible on the E1 and the return tracks aren’t.)

I am still puzzled too. Your part of the software sends the messages after it receives the “preset switched” confirmation. I send that one, when the preset is up and running and Electra is basically idle.

@jhh

As soon as the documentation is updated I will try to see whether it is possible to send the actual values Ableton reports for parameters as strings to the E1 (which would solve the issue that the values for complex paramaters like Volume faders or frequency ranges as displayed in Live do not exactly match the values shown on the E1).

I will be travelling next week. I will not be able to do any serious programming. I will work on the docs instead.

[jhh]

I am going to be away for three+ weeks after next Saturday July 16.

[markus.schloesser]

@jhh

will try to see whether it is possible to send the actual values Ableton reports for parameters as strings to the E1

Have a look at replace __generate_6_char_string with adjust_string (was str_for_value) · Issue #55 · markusschloesser/MackieC4_P3 · GitHub, might be helpful if I understood correctly

[jhh]

Thanks. To be honest I don’t understand what Live.MidiMap.map_midi_cc_with_feedback_map
does; in particular what does the feedback rule do?

Not sure it is relevant though for what I need, which is a LUA command implemented by the E1 that accepts a string as parameter and uses that as the value to display for a particular control.

[martin]

@jhh

Not sure it is relevant though for what I need, which is a LUA command implemented by the E1 that accepts a string as parameter and uses that as the value to display for a particular control.

Yup, I know. I am about to add it but I have need to understand it a little bit more. It is quite easy to overwrite the visible display value (ie. what you see on the screen). But how about the underlying midi value? I assume you will still use it for the communication with the Ableton, right? And will the, eg. fader value bar, be set correctly? Or do you need a relative control where the fader does not maintain its internal value and just sends increments/decrements to the Ableton?