DrivenByMoss + Push 2 on Bitwig – Anyone Else Experiencing Issues (Especially in Studio 6 Beta)?

[ozanhrc]

Hi everyone,

I’m using Push 2 with Bitwig via the DrivenByMoss extension. Overall, I really enjoy this setup and I appreciate the work behind the extension — it adds a lot of functionality and makes Push 2 feel much more integrated with Bitwig.

However, I’ve been experiencing some issues from time to time.

Especially during the latest Bitwig Studio 6 beta cycle, the problems became more noticeable. I didn’t have major stability issues before, but in the recent beta builds I started encountering inconsistent behavior and occasional glitches.

I’m trying to understand whether this is related to:
• The Bitwig Studio 6 beta itself
• The DrivenByMoss extension
• Or a specific configuration issue on my side

Is anyone else using Push 2 with DrivenByMoss on Bitwig 6 beta and experiencing similar problems?

Would love to hear your experiences.

Thanks!

[Fenrok]

I'm having issues with the latest DrivenByMoss script on Push 3 with the latest Bitwig 5.3 stable for Windows 11. It's mostly weird glitchy behaviors when pressing a button & getting no response. I have to click it multiple times to register, and then it sometimes does the action multiple times. It's very unpredictable, such as the track select buttons (bottom row buttons), metronome, Mute, Solo, and Stop clip. It's happening when selecting R/C pages from the bank select menu also. Sometimes pressing the bank pad causes the bank page options to close.

I just got a Push 3, it's updated to the latest firmware version, and it works perfectly fine without glitches in Ableton 12.3.6 Intro.

[moss]

In Bitwig 6 Beta 15/16/17 the hierarchical track navigation is broken (switch to "Flat" as a workaround).