The Electra One web app’s Editor is no longer showing me any run-time messages, either on the Lua page or the Debugger page. I would normally see print messages in the Lua script and system-generated messages.
The app is connected to my E1. I can send a preset to the E1. I’ve tried rebooting my PC. I’ve tried safe-booting my E1.
How can I get this working again? Or is there a bug?
The log / debug / Lua print messages are sent as standard Sysex messages over the USB device port by the controller. Please check with the Midi Monitor / MidiOx that you can see them. That could help to understand the issue. Note, there were no changes made to the Web editor since April.
How this may have broken. This has probably been the first time I’ve tried to connect the E1 to the web app since my PC had a new main SSD and a fresh Windows install, since when I’ve had to reconfigure many things. If it would help, I’ve got a backup of the old SSD with my appdata folder etc. Also, the last time I connected the E1 to the PC till recently would have been well before April when the last web editor changes were made.
In MIDI-Ox I can see three E1 MIDI input devices: Electra Controller, MIDIIN2 (Electra Controller) and MIDIIN3 [Electra Controller]. Electra Controller has the regular MIDI messages; MIDIIN2 has nothing; MIDIIN3 has the SysEx messages. So I expect I need to connect the web app to MIDIIN3. But how? If the E1 is turned on and physically connected when I start the web app, the E1 is automatically connected, but perhaps to the wrong MIDI devices. If the E1 is turned off or physically disconnected when I start the web app, I can manually select the input and output, but of course I don’t see the E1 MIDI devices.
Pending resolution of this issue, I have a workaround. I got an AI to provide a Python script to monitor the log messages provided by MIDIIN3.
If You mean, debugger seems like dead, i realize when making my script, there’s sometimes, freeze on procesor, and only fastest way to make it work again, is get out memory card, formate it on computer, and actualize firmwire on the website. It will make totally hard reset on electra one.
That’s problem apears when i make mistake on lua code, or changing ports to see what’s incoming to the electra on midi OX. I don’t find any other way to bring electra back to life.
Oh, almost forgot, after formating the card, i copy an manually paste all the basics data to memory card before make firmwire update.
I’m no expert. But I have the PC web editor talking to the [Electra CTRL] port connected directly to the PC via usb with no issues. IIRC, when I tried routing via a midi interface I sometimes experienced issues like you describe.
Interesting technique! I think that’s a different problem from what I’m getting though, I have no trouble seeing the log message SysExs via midi on my PC. I just can’t see the log messages in the web editor.
Thanks for the suggestion. My E1 is already connected directly to the PC via a USB cable.
it is important that the controller connection is configured correctly in the web app. It is done on the Controller page:
on Windows, there should be the MIDIIN3/OUT3 port. I assume, however, that you will have this set up correctly.
Further, the logger port can be changed using this sysex call:
But again, I do expect it will be ok.
You may want to open the JavaScript console in your browser to see if there are any errors / warnings displayed when the log messages arrive.
Lastly, I made a small command line tool that allows watching the logs and events in the “tail -f” style. You can find it here:
Note, it is work in progress and some of the commands are working only on the latest firmware that I am getting ready for releasing. Logger should work though.
Thank, Martin! That’s what I needed to change. The ports were incorrectly set to Electra Controller. Setting them to MIDIIN3 (Electra Controller), as I’m using Windows, fixes the problem. I’d always ignored these controls because it says ‘Use this option only if your controller is connected through a MIDI router or ports have been renamed.’
How this got broken. Perhaps when I could not connect the PC to the E1 and the web app allowed me to set ports manually, I selected the wrong ones: the editor then said it was connected and could update the preset; but it could not receive log messages.
That looks good, I’ll check it out!
Lua can cause nasty freezes or loops that will prevent the controller from starting up on reset. usually, the startup without loading the preset should help. (holding top-left button on th mk2 when powering up, or the left most button on the mini)
Stuck at startup | Electra One Documentation - will add mini info to that troubleshooting guide
