Edit: Does anyone have or not have this issue?
Keen to know if it's just me
Thanks for the confirmation Arjan, I’ll lodge a ticket reporting the problem.
Thanks for letting me know Rastko, I’ve found that it only happens for me when the E2 is being powered by the supplied power supply. When being powered by my pc in low power mode Eraelab works fine in bitwig so it is something to do with the power being supplied to it
I just unpacked and setup my Erae 2 this weekend. I have exactly the same behaviour when using Reaper. I'm also using the power supply. At first I couldn't get the Erae 2 to trigger anything in Reaper at all and spent a while trying to trouble shoot the issue. By chance the next morning I tried again, before opening EraeLabs, and it started working. After that, I worked out that EraeLabs causes the problem.
Did you hear back from your ticket, Jay?
A few more details:
EreaLab will not connect to the device when Reaper is open. As soon as the DAW is closed, it will connect (and pull the current project) automatically.
If EreaLab is open before opening Reaper, Reaper will see the device (the Erae 2) in Settings, but it will not appear in the list of selectable inputs on a track and Reaper will not detect any MIDI coming from the device on "All Channels". However, [Hardware Tester - Online MIDI Keyboard Tester](https://hardwaretester.com/midi) _will_ both see the device and detect/visualise MIDI coming from it, implying that the fault isn't in Windows more generally, but in the interplay between the Erae software and Reaper.
Once Reaper is behaving like this (seeing the device in settings but not getting MIDI from it), closing EreaLab can fix the problem, sometimes. On some occasions, tracks/instruments will start playing on a keypress of the E2 the moment EreaLab is closed. Other times, I need to turn the E2 off and on for Reaper to start getting MIDI from it. Closing and re-opening Reaper doesn't seem to have an effect. The action "reset all midi devices" (that often helps in similar glitchy situations) also has no effect in this case. So it either works as soon as EreaLab is closed, or you have to power cycle the E2. I haven't worked out a pattern beyond that.
Jay Bryan
Hi all, just wanted to bring attention to an issue that I'm having with the Eraelab software interfering with my DAW (Bitwig).
If I have Eraelab open when opening Bitwig the Erae 2 is'nt recognised and also when it is connected (without Eraelab open) if I try to open Eraelab it will not connect with the Erae2 whilst it's connected as a controller in Bitwig.
Does anyone else have this issue? Is there a workaround or solution? Not being able to edit the layouts etc whilst the Erae 2 is connected as a controller seems to be counter intuitive to me.