DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)

[unsaph3]

The editor for the controller does allow for different CCs for each direction but as I dug through the keyboard shortcuts the closest I could find to "nudge" was the Nudge command under general. When I mapped that to one of the CCs, it only appeared to work on the arranger timeline. Is that the expected behavior or should it work anywhere there are events?

[moss]

The editor for the controller does allow for different CCs for each direction but as I dug through the keyboard shortcuts the closest I could find to "nudge" was the Nudge command under general. When I mapped that to one of the CCs, it only appeared to work on the arranger timeline. Is that the expected behavior or should it work anywhere there are events?

If you cannot find an action which does what you are looking for there is none. What I can tell is that there are no methods in the API which can change note selections.

[TrechControl]

Hi,

Normally when opening Reaper it would automatically connect the Push but this stopped working for some reason.
Detect doesn't work either. I have to manually add it via the configure menu. This is probably some user error but can't seem to figure it out. Everything else works perfect. I'm on macOS Sequoia Reaper 7.
Any help is appreciated.

Thanks

[smcc]

Hey all, I've been playing with an ICON V1-M with BitWig Studio using drivenbymoss. It works... but... there is some unreliability in relation to the displays on the V1-M. Sometimes the wrong channel name displays (on one or other of the two displays per channel), sometimes weird stuff happens like names split across more than one channel. I'd say it's about 60% reliable. Definitely using the MCU Universal by Moss (ie not the Bitwig ICON profile). It's kinda like MIDI data gets slightly corrupted or something. I've spent many hours searching for solutions, rechecking configurations, trying little tweaks etc but no luck. I guess my question is... do others have similar problems with the V1-M or other ICON controllers or is it just mine? Is there some magic solution I just haven't stumbled across?

Mac OS 15.7.3, Bitwig Studio 5.3.13, V1-M firmware 1.26, drivenByMoss 26.6

PS... thanks Jurgen for all your great work on driveByMoss ... it's pretty amazing!

[Russell_Nash]

Hi,
I am currently working with TouchOSC and the DrivenByMoss OSC controller. I noticed that, when switching devices, the only information on the selected page is send via ‘/device/page/selected/name’. Would it be possible, that Bitwig sends out ‘device/page/{1-8}/selected’?
It would really help with my current project.
Cheers,
Torsten

[t0gg1e]

I'm using a Push 3 with DrivenByMoss. I have never used Ableton Live. I went straight to Bitwig and then when I started looking for a non-keyboard controller for Bitwig I came across Jürgen's excellent work and decided to go with the Push 3.

I have learned a lot by going through Jürgen's YouTube video's in his playlist for the Push devices multiple times ().

I am struggling a little with the various sequencers that the DrivenByMoss + Push 3 combination provides though. Are there videos on Jürgen's YouTube site, outside of the Push playlist, that I should watch to get a better grip on them? Maybe there are Ableton Live + Push 3 videos I should watch to get a better understanding? Is knowing how Ableton Live works with Push 3 something that is assumed people will know before using Bitwig + DrivenByMoss + Push 3?

Thanks for your time.

[moss]

I am struggling a little with the various sequencers that the DrivenByMoss + Push 3 combination provides though. Are there videos on Jürgen's YouTube site, outside of the Push playlist, that I should watch to get a better grip on them? Maybe there are Ableton Live + Push 3 videos I should watch to get a better understanding? Is knowing how Ableton Live works with Push 3 something that is assumed people will know before using Bitwig + DrivenByMoss + Push 3?

The first appearance was for Push 1 and back then the extension was pretty identical to what you could do with Ableton. Therefore, you can still refer to the Ableton Push 1 manual (or videos) for an introduction to the sequencers and play modes as well.

[Max Trau]

Hello,
First and foremost : thank you Jürgen for the work and efforts you offer to the bitwig (and reaper) community.
I'm using your script with Bitwig 6 and Maschine Jam.

On the clip launcher, we have to press [MUTE] + [CLIP] to stop a playing clip. Is there a way to reverse this behaviour to the default (press [CLIP] to launch and stop a clip) ?
I find the default setting for clip launching easier for my use case (live performance), but overall, your script is better.
Thank you
Max

[moss]

Hello,
First and foremost : thank you Jürgen for the work and efforts you offer to the bitwig (and reaper) community.
I'm using your script with Bitwig 6 and Maschine Jam.

On the clip launcher, we have to press [MUTE] + [CLIP] to stop a playing clip. Is there a way to reverse this behaviour to the default (press [CLIP] to launch and stop a clip) ?
I find the default setting for clip launching easier for my use case (live performance), but overall, your script is better.
Thank you
Max

Sorry, no.

[bmrzycki]

Hello Jürgen and team, thank you for your hard work and support! I love using DBM with Bitwig 6 beta and my Dualo Exquis. Recently I purchased an Electra One Mini and was surprised to see it causes the plugin to crash: I'm guessing because it's trying to see the device as a supported One MkI/MkII and something is falling over. I know it's very early in the release process for the One Mini and was wondering if I could generate any debug output for you to assist in this. I currently can't use the One Mini with Bitwig or I have to disable all the features DBM gives me under Bitwig.

[moss]

Hello Jürgen and team, thank you for your hard work and support! I love using DBM with Bitwig 6 beta and my Dualo Exquis. Recently I purchased an Electra One Mini and was surprised to see it causes the plugin to crash: I'm guessing because it's trying to see the device as a supported One MkI/MkII and something is falling over. I know it's very early in the release process for the One Mini and was wondering if I could generate any debug output for you to assist in this. I currently can't use the One Mini with Bitwig or I have to disable all the features DBM gives me under Bitwig.

Support is upcoming! Until then you could e.g. use Generic Flexi.

[bmrzycki]

Support is upcoming! Until then you could e.g. use Generic Flexi.

Thank you! The E1M is absolutely amazing and I can't wait to use some of the features the larger E1 has. Just knowing you're working to support it makes me very happy.

[Blork]

Hey Jurgen,

First of, much thanks for the amazing scripting you do. I am working on the push2 and recently switched to Bitwig and actually prefer your version above Ableton. I still have a few questions for on the wishlist though

I went through all your video tutorials and encountered the same problem that you mentioned in some videos. Accidentally touching the tempo button and then changing the tempo of the project. This is mega annoying and takes out the flow of working. Is there some work around to turn this off? I would even prefer to be able to turn off the whole button and losing the possibility for arrangement controls for example, since the only time I use this button is when I accidentally press it and once I go into the arrange I put the Push aside. (Edit: or maybe that it is only usable for tempo change together with tap tempo pressed, for me would be beneficial since I have never used this button since I make music in DAWs)

Another option that I miss is to add track in a group. I have the display in "flat" mode, and when I add a track it always becomes the last one beneath all of them outside all groups. When I add tracks in Bitwig directly through keyboard shortcuts, they are added underneath the current selected track and inside the group. This would save a lot of reorganizing while setting up new tracks.

Also, I work in Bitwig 6 beta (and didn't work in 5). I am assuming the V0, V1, V8 and V9 drum are new in this version. So I guess you will add them to the list for "favorite devices" when 6 is out of the beta.

Again thanks a lot for the great work!

[skylanderlad]

Hello

Thanks for your scripts - amazing amount of work you do.
I am using the Bitwig Extension for the Akai Force - Latest version of Bitwig 5.3.13 and also tested on Beta 6.0 13.
Latest version of Bitwig Extension.
Akai Professional Network MIDI version 1.4.1
Also on Windows 11.
I have tried connecting both via Ethernet cable and via Wi-Fi.
It does occasionally connect - maybe one in 5 or 6 attempts, but mostly the Force just stays on the "Waiting for communication from Ableton Live" screen.
I'm completely at a loss - it seems that everything is set up correctly but for the most part it will not connect.
I would appreciate any thoughts.

Thanks very much in advance.
Alan

[moss]

I went through all your video tutorials and encountered the same problem that you mentioned in some videos. Accidentally touching the tempo button and then changing the tempo of the project. This is mega annoying and takes out the flow of working. Is there some work around to turn this off?

You can map the MIDI event of the touch to something meaningless in Bitwig and store the mapping in the your Project template.

Another option that I miss is to add track in a group. I have the display in "flat" mode, and when I add a track it always becomes the last one beneath all of them outside all groups. When I add tracks in Bitwig directly through keyboard shortcuts, they are added underneath the current selected track and inside the group. This would save a lot of reorganizing while setting up new tracks.

I am afraid I cannot change this behaviour.

Also, I work in Bitwig 6 beta (and didn't work in 5). I am assuming the V0, V1, V8 and V9 drum are new in this version. So I guess you will add them to the list for "favorite devices" when 6 is out of the beta.

Oh, yes. Need to check.