Thanks but I must be missing something..
I reinstalled your script this morning and the default flag for dump is set in config.py as DUMP = FALSE (with spaces). I haven’t modified this after reinstall as I wanted to check everything at default to see if it fixed the issue.
Even after the reinstall with everything at default it isn’t working.
Sorry for being such a pain.
Si
The spaces are not the issue. It’s the capitalisation. After reinstall, config.py should say DUMP = False (and not DUMP = FALSE). If that’s not the case, let me know, because then something goes wrong during (re)install.
I’ve updated the installer electraone.pkg to ensure existing files are overwritten.
Oh… and there was a horrible bug in the installscript that improperly generated the upload-to-E1.zip. If anybody used that feature, please rerun and upload to the E1 again. My apologies.
Thanks for the insight on my stupid mistake on the DUMP flag..
I’ve re-run the latest installer but unfortunately I’m still in the same position and nothing works. I’ve looked at the Ableton log and can’t see any errors on execution. The config.py file has updated and the DUMP = False flag is correct.
I’ve checked E1 is working with my other presets and all seems fine so I’m assuming it’s not an E1 issue per se.
Anything else I can do to try and isolate the issue?
Si
Did you re-enable the ElectraOne remote script in Live’s MIDI preferences? Remote scripts are disabled there after Live encounters a compile time (e.g. caused by miswriting true) error in them.
Thanks.
Finally sorted. Embarrassed to say that when I recreated all of the midi config I had forgotten to pick ElectraOne from the list of Control Surfaces. Sorry..
I do have one other question however as I was reading the installation docs again and your post about the E1 upload folder. I hadn’t done this part in my install in the past. Popping the E1 into Disk mode I can see that I data in ctrlv2 folder for your script (LUA and Presets). Instructions say to pop the zip file into ctrlv2 and unpack but when I do this I just get a folder in ctrlv2 with all of the files unpacked; can I just copy these into the relevant subfolders to update?
Si
Ah, you are probably unpacking the zip file by double clicking on it. It then indeed creates a folder upload-to-E1 with all the subfolders and files. This is my fault - and I hadn’t noticed because I always use the terminal and run unzip upload-to-E1.zip which does not create the additional folder (and thus puts everything in the right place on the E1). I’ll add a note to the documentation to warn about this.
Thanks for updating the docs. All seemed to go fine using Terminal as per the instructions.
Right, where was I.. oh yes.. time to set Dump = True this time and have a go at a preset 
Appreciate the support.
Si
You are more than welcome. Your inquisitiveness helped me spot an obscure bug in the installer. In fact you may have to upload upload-to-E1.zip one more time, per the latest instructions, to properly upload the presets. There could be a spurious file lua/xot in the ctrlv2 folder on the E1 that would prevent the installation of lua/xot/default.lua.
Note: this may be relevant for other users of the remote script as well. I you have an E1 mkII, please check that lua/xot/default.lua exists in the ctrlv2 folder on the E1. If not, reinstall per the latest instructions in the repository.
@Martin please verify this for the preinstalled images on the E1s you ship as well!
will do
Ok…
Just checking the script over again to make sure everything is back where it should be and noticed that If I select the ‘Device selection’ or ‘R/M Device selection’ areas I’m just getting a bunch of PAD MOMENTARY buttons (and Option Selectors at the bottom) for each track or return channel.
If I select a device in Ableton and just press the top right button on E1 I get the correct preset for the device in question.
What have I cocked up this time
Si
No idea 
Works over here. Only one way to find out: please send me your latest log file. I’ll have a look later (now out for shopping and cooking).
Will do.. sorry!
In relation to your post above about the spurious file I ran Terminal again to update the files on E1. I did notice in Terminal that I got this at the start when running the command: ‘error cannot delete old lua/xot operation not permitted’. The rest of the files appear to have been extracted/inflated.
Just wanted you to know!
Si
That’s for the command rm -fd lua/xot right? Hm… that’s not good. Can you run the command ls -la lua/xot in the ctrlv2 folder on the E1, and send me the results?
I got the error when I ran ‘unzip ~/Documents/upload-to-E1.zip’ after CD’ing to ctrlv2
The ls command gives the following;
drwx------@ 1 simongreen staff 32768 11 Jun 2024 .
drwx------@ 1 simongreen staff 32768 11 Jun 2024 ..
-rwx------ 1 simongreen staff 4096 8 Jan 2024 ._default.lua
-rwx------@ 1 simongreen staff 2463 13 Oct 2023 default.lua
Hope this helps.
Si
Strange. The default.lua has clearly not been updated (as it is very old).
Best is to use Finder to complete delete the folders lua/xot and presets/xot on the E1, and run the unzip command again.
Ignore this until later @jhh
As per post above I deleted the relevant folders on E1 and then unzipped again as per the commands.
Rather than getting ‘ctrlv2/lua/xot/default.lua’ as per your docs online, I ended up with ‘ctrlv2/lua/xot with xot being an executable file.
The script seems to be working however..
Si
Too bad; seeing this now
You unzipped not the most recent version of upload-to-E1.zip, which still contains the bug I spotted earlier today (namely that it creates lua/xot and not lua/xot/default.lua, as you are now seeing). The script will work. But the predefined device presets will not.
Fix: download the latest version of upload-to-E1.zip here: https://xot.nl/Sound/Plugins/ElectraOne/upload-to-E1.zip, delete the relevant folders on the E1 again, and install upload-to-E1.zip again.