Just saw your post here. Better write to the DrivenByMoss thread in the Reaper forum (or maybe you did).
Meanwhile, there is a new DrivenByMoss version 26.1 with a new MIDI backend which uses the Reaper MIDI ports directly. Watch the new installation video as well (linked on the download site).
I havent been on reaper forum so yeah thats maybe a smart idea.. first of i will test the new version (i am pretty sure it might not even be drivenbýmoss, reaper it self or the E1 causing the problem i think it might be a very extensive midi setup i made before i even got the E1 
but i hope this new version fix it
Thx for getting back to me <3
I’ve been putting this through its paces with Reaper over the last couple of days and it’s amazing!
I have a question. What does ‘Expand’ do on the devices page? I may be going insane (as I’ve being watching loads of YT stuff to get up to speed) but I’m sure I spotted something about being able to open another preset from this one if the E1 preset for the plug-in is exactly the same name as the plug in??
Only issue I have found thus far is Markers don’t seem to work.
Amazing work.
Si
Ignore me!
There appears to be a better way - using Parameter Maps to build specific controls for devices. In fact it’s even better than the dedicated preset as DBM actually updates parameters from the device.
Always been my achilles heal - the fact that a standard preset into a soft synth doesn’t support the concept of patch dump and hence great for programming from scratch (and saving a snapshot) but not so useful if you want to open and tweak a preset.
Wicked!
Si
Markers will be fixed in the next update.
I was really enjoying the Bitwig preset, but in Bitwig 6 Beta 4&5 the E1 Mk2 keeps on freezing and crashing my Bitwig session..It is with the recent DrivenbyMoss version and E1 firmwware. I will try it tomorrow again with the last stable Bitwig 5 version and report
I am currently looking at it. @ElVicente already reported the same issue.
@ElVicente @v.rtx_void would you try this beta version:
firmware-v4.1.2a.srec.zip (2.2 MB)
I am on Bitwig 5.3.13 + the latest DrivenByMoss. I had issues with with v.4.1.1. This v4.1.2a beta resolves what I was experiencing. Can you give it a try too? Thanks!
Sure !
I’ll give it a try and report what happen.
unfortunately for me the issue is still present, on both Bitwig 6 Beta 5, it freezes immediately at the beginning or after a short while, getting a “not enough memory” error message from Bitwig.
On 5.3.13 it works so far but only while no devices are attached via the USB A port (in my case a Midronome). It somehow cannot handle MIDI I/O with the DrivenByMoss script, especially clocks. When I change a page the clock from my Midronome gets overwritten by the clock from the DrivenByMoss script for a brief moment and then it eventually crashes/freezes. Same with my FH-2 connected to the E1MK2 USB A port: After a while all MIDI messages are somehow stuck or delayed, resulting in the E1MK2 freezing.
/edit: In both cases (Bitwig 6 & 5) the transport Position of the DrivenByMoss script is very laggy
The same setup runs just fine on v3.6.1?
I have to test, is there still older FW available via download?
With the v3.6.1 FW the transport position in the DrivenByMoss script now runs smooth and in real time again on Bitwig 5.3.13, but not tested with 6 Beta 5 yet. The DrivenByMoss Script does not interfere anymore with the Bitwig clock when I change its pages, but also does not reflect the correct clock from the Midronome (which in my case is okay, just weird). I have to check how the FH2 is processing data for further feedback, atm I am working on a gig for the upcoming Thursday and have to program a bit anyways 
Thanks for helping out on a Sunday evening @martin !!! This is really nice of you
I have replicated your setup. I have deluge (instead of midronome) connected to E1 USB host, It feeds E1 with the clock and stream of notes at 120BMP. The DrivenByMoss preset is running and Bitwig plays a short sequence. It looks ok so far. Position on the E1 follows the Bitwig.
Do you forward any messages to MIDI IO ports?
EDIT: are on you mac or win?
I am on Windows 11 Home Version 10.0.26200 Build 26200
in my last setup I have solely used the Midronome only sending MIDI Clock to the E1MK2
can you try the same setup but with different device than the midronome? something else that sends the clock.
With my Five12 Vector sequencer it is the same like with Midronome: Clock and transport are correctly assigned within Bitwig 6 Beta 5 and 5.3.13, just not parsed back to the E1MK2 DrivenByMoss script, which is fine, it seems to be an issue with the DrivenByMoss script, the E1MK2 is sending right clock and transport from both Midronome and Vector
That’s strange. @NewIgnis also reported lagging issues. I am unable to replicate anything of it so far.
The drum sound comes from Bitwig. The Deluge generates clock, transport, and keeps E1 busy with some extra notes on MIDI. Bitwig is synced to the clock from the deluge (via E1)
I think you misunderstood what I am refering to, sorry if I was not clear enough 
I have attached a video:
basically it works fine, its just in the DrivenByMoss script not echoing the right BPM