Ableton Live MIDI Remote Script / Control Surface

[phonaak]

i ran makedevices in the sciprt folder

[Flyweight]

1. go to the ‘ElectraOne’ dir that contains ‘makedevices’
2. when in the directory either run, python3 makedevices or ./makedevices

$> was just the command prompt, so pls ignore

3. when done check in devices.py if your devices are in it.

[jhh]

To be slightly more precies (I am on a Mac)

• open a terminal
• type cd /Users/phonaak/PHONAAK\ USR/MUSICEDITING/User\ Library/Remote Scripts/ElectraOne
• run ./makedevices
• some output should appear

[jhh]

[quote=“martin, post:379, topic:1420, full:true”]

@jhh

I am looking at it. The problem is caused by the fact that changing of the Algo Type value results in visibility changes of controls on the same page. That may result in repaint of whole current page. When that happens the system enters an infinite loop of control - page repaints. When I remove the DAMPING and MODULATION controls, it works fine.

Interesting… It does work for certain presets though

This is the topic we touched already. I am now looking at your earlier request → calling the Function on MIDI input. I guess that is what you actually need. Is that correct?

Indeed that’s what I actually need (and I could stop (ab)using the formatter for this behaviour)

[phonaak]

this

[phonaak]

this is my folder structure

PHONAAK MBP / Users / phonaak / PHONAAK USR / MUSICEDITING / User Library / Remote Scripts / ElectraOne

[jhh]

Run

chmod +x ./makedevices

And try again

Jaap-Henk

(I apologise for typos and for being terse: this mail was written on my smartphone)

[phonaak]

I found the error. a "\ " is missing from the command.

original:
cd /Users/phonaak/PHONAAK\ USR/MUSICEDITING/User\ Library/Remote Scripts/ElectraOne

good
/Users/phonaak/PHONAAK\ USR/MUSICEDITING/User\ Library/Remote\ Scripts/ElectraOne

[phonaak]

here

[phonaak]

@jhh

./makedevices

Ok.
Now works fine

[jhh]

Remote script updated to better support two E1s at the same time (one controlling the effect, and the other controlling the mixer). See the documentation for instructions. Note: mixer support is not ideal yet (labels and control visibility not updated as in single E1 setup due to current firmware limitations). Also note: configuration options changed. New option CONTROL_MODE (subsuming options DISBALE_MIXER and DISABLE_EFFECT, which have now been deleted).

[jhh]

Hm… some further testing revealed that this DOES NOT WORK yet. Something is freezing the first E1 when switching selected devices.

[jhh]

@Martin Trying to debug this. It seems the 1st E1 in the chain (connected to the computer) does not forward any SysEx messages to the second E1. Is that correct?

Somewhere before the freeze (presumably) the first E1 reports

processElectraSysex: message ignored. Not an Electra.One message

Not sure what MIDI message (from the 2nd E1) is triggering that message, although it does appear to happen when Ableton sends a value update for a parameter as a CC message, i.e. it occurs in the logs right after

ElectraMidi: processMidi: Control change midi message: parameter=2, value=19 
ElectraMidi: processMidi: Control change midi message: parameter=34, value=25 
Midi::processMidi: CC14 detected: parameter=2, value=2457

I do not see anything unusual on the MIDI to/from the first E1. Is there a way to catch whatever is sent on the connection between the 1st and 2nd E1?

[jhh]

@Martin Update: the 2nd E1 ran version 3.1 of the firmware; after updating it to version 3.1.4. I do not see the
processElectraSysex: message ignored. Not an Electra.One message
message anymore, and using two E1’s to control Live more or less works (modulo the updating of track names and visibility setting of controls)

[bob]

Hi everybody,

Some problem with instrument groupdevice :

• I create an instrumentgroupdevice with the MiniV arturia plugin inside.
• I rename the group MiniV bass. a dump is created with the name correctly (MiniV bass).
• I insert the modification lines in device.py.

The problem is that the script automatically calls Instrumentgroup device name and not MiniV bass.

Only when I point to the plugin in the groupIt recognizes the name, loads epr from miniV bass with the nice layout but the ccmap is corrupted…Strange Ableton!

I read above that there are difficulties in accessing the name devices in ableton…

Are we reaching the limit of E1 / Live integration?
Having such freedom to call a rename device would be fantastic!
Thank you again for this work which is close to perfection @jhh !

Cdlt Bobmo

[jhh]

That is strange, because that should work (and partially does work apparently as the script dumps the preset with the correct name). Could you send me the Ableton log file and the Live Set you used? (Don’t hurry as I will only be able to debug this tomorrow evening at the earliest).

[Flyweight]

what platform are you on? windows or mac?

[jhh]

That should not make a difference, really. And anyway: the logic to determine the name to dump to is exactly the same as the logic to determine the name to retrieve the preset from.

[jhh]

P.S.: I also am curious to disccover how the CC map gets mangled in your case.

[bob]

Hi,
Thank you for your answers.
I’m running live 11 on windows 10. @Flyweight
This evening, I have just methodically started the operation again and the problem remains the same, which leads me to think that it is not from me or not
A little summary (it helps me too):
With an empty dumps folder
When creating an instrument group device

• dump “InstrumentGroupDevice” create
• I rename Inst G 1
• no dump
• I point to the miniV3 plugin in the group
• dump Inst G 1 create

When I point to instr G1 E1 displays the default preset instrumentgroupe device
Then when I point to the group E1 plugin shows the preset instr G1 add to device.py .

I tested renaming a Max 4 Live plugin and E1 takes into account the name change after validation.

Attached is the live project with the logs and the device.py .thank a lot @jhh

debug instrument group.zip (115.4 KB)

For an E1 at the top of the control @martin

Cdlt Bobmo