I presume messages like this are just informational and not telling me I have a problem:
08:36:25.621 timer.onTick of preset 36 is in trouble on its 10000 us period: last 4795 us, worst 4914 us, 25.9% of the run loop, 1868 ticks too late, 6234 could not get into the script, 0 raised an err 08:36:30.690 timer.onTick of preset 36 is in trouble on its 10000 us period: last 4795 us, worst 4914 us, 22.0% of the run loop, 1945 ticks too late, 6400 could not get into the script, 0 raised an err 08:36:35.689 timer.onTick of preset 36 is in trouble on its 10000 us period: last 4794 us, worst 4918 us, 25.4% of the run loop, 2021 ticks too late, 6568 could not get into the script, 0 raised an err
EDIT: I reduced the repaint frequency from 50ms to 100ms and those messages became significantly less frequent with no visible change in performance. The remaining occasional warning is expected I suppose, since worst-case spikes (garbage collection, MIDI I/O, etc.) can still occasionally exceed budget even with throttling.
I’ve been testing Continuum Controller, a large and complex preset, with 5.0.0f. I updated the firmware while the preset was loaded. when I then made some changes to controls on the open page, there was some corruption of the rows containing the controls I changed. I have no screenshot because the problem went away when I opened another page. I’ve not been able to reproduce the problem on subsequently reloading the preset. So I expect it happened only because I started testing a preset that was already loaded when the firmware was updated. Nothing of concern, I think.
Apart from that, the preset has been working fine. I notice there’s no longer a splash screen on start. I assume that’s either by design or temporary while in beta.
I’ve also have two comments on the beta web application.
Disconnecting the E1 while the app is connected to the E1 freezes the browser (Chrome in Windows). That’s new.
Screenshot is good. It’s evidently envisaged to be primarily for an extra image on the preset’s web page. Yet it has huge potential for diagnostics and documentation. An option to save the screenshot to file at a bigger size would be great. On the other hand, it takes a while to download even at the current size. As it is, I can still take a screenshot on my computer of the screenshot and save that to file.
The new documentation on architecture looks interesting. I had a problem where Continuum Controller would often freeze on start if the list of instrument presets was populated automatically. In the end, I removed automatic population: players now have to push a button to get the presets. I notice there are now other options for multitasking than just timer tick. So perhaps I might be able to put back the automatic population on start.
yes, it is not a real problem. I have that log message in beta to see moments when the preset could be optimized. The same information can be seen in the Controller :: System stats. The log message will not be present in the production release.
OK. What I previously successfully tried was the Take/Retake Screenshot button on the preset page, where the resulting screenshot looks fine one the preset page but is a bit small for to put in the manual.
Now I’ve tried taking a screenshot from the Controller menu, which I can see is the way to go if I I want a screenshot for something other than the preset page. At first, it did not work for me. The popup window showed an error message:
‘The controller did not say what it had saved.’
So I closed the web app, then turned off and turned back on the E1, then reloaded the web app. Then retrying screenshot from the Controller menu worked.
Much better, and of course it can be saved to file, where it looks great!
Small thing. I make use of the page access feature of a preset using the pages listed across the top of the screen. With the latest fw that list always includes the performance page at the top left of the screen. Can that be turned off? Like I said, small thing. Loving the new features!
On beta.electra.one, if I export a JSON preset, the JSON is different from the one shown when pressing the JSON button in the web editor. For example, the “font” section is missing.
Updated my E1 MkII HW3.0 via the Online Update process from beta.electra.one. All went very smooth. All of my (very basic and simple) presets work just fine.
A few questions as I am slowly exploring the new features:
V-Fader control became so much more useful now with the ability to assign the knob touch to open the detailed view just via the side menu! However (I am not sure this changed compared to 4.1.x FW, since I didn’t really try the V-Fader) I noticed that individual faders controls in the detailed view have a certain “control redundance”. I’d normally expect, that the V-Fader bars are always controlled by encoders 2-5 (the 2nd, 3rd, 4th and 5th encoders in the top row). And they do. However, depending on where on the grid those V-Faders are, the encoders that are linked to that grid slot, become “tied” to the f1 bar after the detailed view is open through a Knob Touch Begin → Open Detail command.
So, for V-Fader in the top left corner of the active row, the encoder 1 (which is linked to this grid slot and will control f1 in normal view) will control f1 in detailed view (together with the “default” encoder 2 that is logically located under f1). And the V-Fader in the top right corner of the active row will have its f1 fader “linked” to the Encoder 6. Certainly not a big deal, just a bit unexpected when you have two encoders controlling the same parameter.
Another question on the Detailed view: the ability to open it via the knob touch without being a LUA guru is huge, what would also be huge is the ability to close the detailed view in a similar fashion - without tapping that cross on the screen. Can we somehow do it? EDIT: I didn’t express my self good enough. Of course we can exit the detailed view by hitting any of the hardware buttons (at least, in its default state). I was looking for a more streamlined “toggle” way of calling up and exiting the detailed view. Will experiment more with external MIDI In messages.
Dials on E1 MkII are most welcome, but I can’t for the life of me figure out where the control name should be displayed? I can’t see it neither in the default view, nor in the detailed view. How do I identify the dial?
On 2. You will have to use a group label to show a control name until Martin figures out a way to free up real estate to fit a regular control name. The dial takes up a lot of the space in a mk2 grid. E.g.,
Just updated to 5.0 beta. Online update worked but it froze my browser on completion (Win 11, Chrome) so I had to force quit. No big deal but thought I’d report!
Hmm, Chrome crashed again when the E1 was simply plugged into the computer and I relaunched Chrome. Not sure exactly the cause, I think it was when I went to the beta site again. I’ll try and trace the cause if it happens again
I have this on my todo for today. I will finish something on Linux and will take a look at Windows then. The trouble is that there are Windows users who do not have such problem - I hope I will be able to reproduce it.
Only been using the beta site lately. With E1 connected via USB to Windows on startup Chrome locks up in the web app while trying to connect. I then kill chrome processes in task manager and restart E1. Then web app connects fine and is stable after that. Everyday routine for me.
Not sure if it is the new Windows MIDI services stack or something else. This is the endpoint device ID it reports: \?\swd#midisrv#midiu_ksa_681281586937595626#{e7cce071-3c03-423f-88d3-f1045d02552b}. IIRC the E1 serial number used to be reported but in the new stack it says that device does not report a serial number or product instance ID and so uses port number to ID it. So if the load order changes perhaps it confuses the app? Pure speculation.
I absolutely love the MIDI recording in Captures. I wonder though, would it be possible to optionally exclude certain data from being recorded? Specifically in my case just now, MIDI notes generated by a different pinned preset. I don’t (necessarily) want the MIDI notes from the other preset to be recorded in the preset in which I’m recording a capture. Pretty niche use case I guess and it would be enough in this case to simply exclude MIDI generated by other presets from being recorded…
Also (sorry!), looped playback of recordings would be amazing. Beat-synced looped playback would be even more amazing
I spent afternoon in using the windows + E1 with both 4.1.4 and 5.0.0 firmware. I do get browser freezes in both Edge and Chrome when a) I unplug the cable b) the sysex traffic between the controller and the computer is busier
I found out that there are bug reports filed on similar issues.
Would anybody try to unplug the cable on windows while working with the E1 (running 4.1.4)? If there is a freeze too, it is not - most likely - related to the firmware change.
that makes sense. But not in 5.0.0, there is a feature freeze already. The only thing blocking the release is the windows issue.
both options are there, currently you can set loops/sync using the Captures tab in the browser only. It is also possible to trigger captures using the external controller and even transpose them. Check the docs: Captures | Electra One Documentation
