Hi Martin,
I confirm that freeze is still happening with 4.1.2a firmware.
Maybe more quickly than before .
2 Likes
that does not make me happy 
I will talk to Jurgen, I need his assistance. I found some issues (these resolved in 4.1.2a). With that version, however, I am unable to crash it in my environment. Are on windows or mac?
I suggest for you to stay on v3.6.1 for any serious work. I am 100% on trying to resolve that.
1 Like
I’m on win11.
I wish you good luck for the bug hunt !
2 Likes
@moss reviewed the issues and provided very good pointers on what to adjust in the firmware. I am busy with it now.
1 Like
@moss Is there any chance the electra-one might get an on-device browser similar to the push devices?
@moss @ElVicente @v.rtx_void would you give it a try to firmware-v4.1.2c.srec.zip (2.2 MB)? I understand the issue now (I hope it is the same as you are experiencing). This 4.1.2c tries to address that. It still needs doing but I would like to check if it resolves your problems too. Just to know that I am going in the right direction…
The problem I found (with a great help of @moss) is present on windows 11 only and it is caused by much higher rate of the song position updates - in comparison to MacOS.
Thanks!
1 Like
Thanks for the support Martin,
I’ll try it this afternoon.
I don’t think that this is possible currently.
Looking good! Just had it run for 1,5h without any crash!
2 Likes
It seems to be working here too !
Thank you.
2 Likes
also for me it works like a charm on Windows 11, all the lag etc. is gone and it is stable for about 2h now, thank you so much 
1 Like
I was away from the computer for over a week and have not managed to finalize this into an official release - there have been some more problems reported. I am back in the workshop and I will try to get it out asap. Thanks @moss @ElVicente @v.rtx_void thanks for testing and confirming that it works ok now.
1 Like
Hello, I installed DrivenByMoss for Bitwig on my Mac using a Mk1 Electra One today. Unfortunately I am experiencing loads of lag across all functions on the Electra One (turning knobs, pressing buttons and so forth). This is with Bitwig 6 Beta (I’ve not tried with Bitwig 5). Is this a known issue with the Mk1 Electra One and Bitwig 6 maybe? Thanks!
I should add that things work better, though still a bit sluggish, when the transport isn’t on but idling. Once I hit play, the controls on the E1 become pretty much unusable.
(fwiw - i also run a script to control my Nord Drum 2 on the same Electra One and this runs flawlessly)
Yes, the update of the transport position is the issue. It was hugely sped up in the Firmware for Mk2 abd works fine there. @martin Could you improve this for Mk1 as well?
Will there also be a script for the new mini? @moss
Ordered one and would be amazing if that were possible!
@InferiorOlive I am afraid that mk1 does not have enough resources to run the script with fast responses. The running song position indicator adds extra 50+ sysex messages per second that must be processed. While mk2 can handle that for mk1 it is a little bit too much.
I saw you email coming in, I will respond early next week.
@moss will receive his unit next week. I will be working with him on getting it going. Mini offers some features that E1 does not have - such vertical fades and hardware buttons mapped to preset buttons. I think it would be great tailor the drivenByMoss integration to it
@moss - will get in touch with you shortly.
PS: @Claudio - your message was delayed as the forum software marked it as spam.
2 Likes
Hi Folks,
Anyone else here using this with Reaper?
I’ve been playing with this and unfortunately for me the preset itself seems to have some very strange behaviour;
Selecting the SENDS page shows the sends per channel but the fader values for the sends are a mirror of the fader values in the MIXER page. As an example if I have a track with fader set at -10db and a send set @ 0db then the send value on the preset page shows the -10db (MIXER page fader value) and not the 0db send value?
If I go to the TRANSPORT page my markers are shown correctly but pressing one has no effect. That’s not strictly true however; if I select a marker and where I touch on the E1 is where a mixer track is on the MIXER page it actually selects a track? i.e. the touch is influencing the MIXER page rather than the TRANSPORT page.
I do see similar general behaviour everywhere that looks like any page other than the mixer seems to inherit values on their control display from the MIXER page (i.e. the controls that would appear in exactly the same place in the grid) and not the actual controls for the page itself. Likewise touching on any other page than the MIXER seems to influence the MIXER controls.
Shame as it has so much potential and I’d really like to drive Reaper from the E1. I’m guessing that the coding of the actual E1 preset has some issues.
Not sure if Moss drops by here at all? @moss
Si
Just answered in the Reaper forum.
Today DrivenByMoss 26.6.1 came out. No E1 Mini support. Are there any news on when E1 Mini will be included?
Sorry if that was answered elsewhere already, I couldn’t find any recent updates on that. 