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

[vrobot]

Hi Moss,

OK, thanks for confirming.
I'm having fun with the Fire!

Cheers
Rob

[Mikey_J197]

Hi Moss, anyplans for the K2?
Would make a wicked drum sequencer with 4 track volumes..

I wish I knew how..

Anywhere you could point me to in order to learn such things sir?

Cheers,

Mikey

[moss]

Hi Moss, anyplans for the K2?
Would make a wicked drum sequencer with 4 track volumes..

That one? https://en.wikipedia.org/wiki/K2

I wish I knew how..

Anywhere you could point me to in order to learn such things sir?

Sure:

[PGAudioworks]

Hey Moss,

I'm unable to get my MIDI controller (Sparrow 4x100) to send MIDI data in write mode. It does send in Record mode however.

I'm able to automate remote controls that I have mapped with another controller though.

Any idea what's going on? Here's my settings:

Screenshot 2024-12-01 at 8.05.51 AM.png

Screenshot 2024-12-01 at 8.05.59 AM.png

[moss]

Hey Moss,

I'm unable to get my MIDI controller (Sparrow 4x100) to send MIDI data in write mode. It does send in Record mode however.

I'm able to automate remote controls that I have mapped with another controller though.

Any idea what's going on? Here's my settings:

You need to use remote controls not pure MIDI CC. Using MIDI CC as a function makes only sense for hardware synths (but you could also use the MIDI CC device instead).

[christian_rabin]

Hello Moss (thanks in advance)

I am trying to get the driven by moss controller script for maschine mk3 to work in bitwig 5.7. I am running this on windows 11 Pro. I tried to follow the instructions in the manual, including loading the script into the controller editor (I think this is where I am maybe doing things incorrectly). At present the script seems to partially work in bitwig; the transport controls, volume, panorama function. But the drum pads, shift control, and many of the other functions do not. Appreciate any help.

[christian_rabin]

I apparently needed to update to the latest version of bitwig. Works now. Just one additional question if I may. I notice that the mk3 has sone latency with the script whereas my M32 thats not doesn't have any latency. Is there any adjustments that you know of that I can make to improve this aspect of performance?

[wwaver]

Hello. Trying out the OSC extension for the first time. Bitwig 5.2.7 and DrivenByMoss download 24.5.1. I can see the option to add a controller, chose OSC, but no dialog windows appear. The video guide is a little different but I get nothing in drop down or when clicking the enable button or show settings. Am I missing something simple?

Windows 11 Pro, brand new install for Windows and Bitwig.

[moss]

I apparently needed to update to the latest version of bitwig. Works now. Just one additional question if I may. I notice that the mk3 has sone latency with the script whereas my M32 thats not doesn't have any latency. Is there any adjustments that you know of that I can make to improve this aspect of performance?

I am not aware of such an issue. How does the latency show? When playing the pads?

[moss]

Hello. Trying out the OSC extension for the first time. Bitwig 5.2.7 and DrivenByMoss download 24.5.1. I can see the option to add a controller, chose OSC, but no dialog windows appear. The video guide is a little different but I get nothing in drop down or when clicking the enable button or show settings. Am I missing something simple?

Windows 11 Pro, brand new install for Windows and Bitwig.

You need to select a MIDI input to make it work. Doesn't matter which one, this is needed to get MIDI into Bitwig (I know it is stupid). If you have no MIDI device connected, install a virtual MIDI cable (that's the best solution anyway). E.g. https://www.nerds.de/en/loopbe1.html

[kazakore]

2. What about a fully rotated view? Where you rotate the physical Push device so the screen is on the left then tracks and clips on the device line up with those on the screen. The touchstrip is then in exactly the right position to use as a crossfader too.

That's already possible: When in Session mode, press the Session button again, which will open the configuration mode. Select "Flipped".

I know full well about Flipped mode, that is not what I mean. I clearly described how this is different. If you rotate the controller with it in Flipped mode you get the first track at the bottom and the last track at the top on the controller. This is even more confusing that having to reorientate 90 degrees to the normal mode. I know that thinking to work with an actually rotated controller does make this a rather weird request though....

4. Is a rotated view possible? Four cells/scene of sixteen tracks seems a weird choice as the only layout when most controllers are 8x8 and on the Oxi you could have 8 tracks by 12 scenes, with the four buttons going to the left side. To be able to switch between these two views live could be quite powerful for the way I've been working.

Don't think that a flipped mode makes sense on devices which do not have the same number of pads in both directions.

I partially agree with you, but what I really don't understand is the choice of 16 tracks by 4 scenes, over 8 tracks by 12 scenes. As nearly all other controllers give you 8 tracks by 8 scenes keeping the same 8 tracks and extending the number of controllable scenes to 12 would much closer match the rest of the units. It seems an even more logical choice as this would also make the pads align with what is on the screen, rather than be offset from the screen by 90 degrees.

Can you please give the reasoning for choice, as I really struggle to see it. Although I have a fair few song segments over 8 tracks I don't think I have a single one that is 4 or less scenes in length. I guess if you only queue and play from intro it may make things easier, but it pretty much makes it impossible to set up scenes/cells for live chopping (eg jumping between a variety of breakbeats) well at least any more than 4 at once.

[moss]

2. What about a fully rotated view? Where you rotate the physical Push device so the screen is on the left then tracks and clips on the device line up with those on the screen. The touchstrip is then in exactly the right position to use as a crossfader too.

That's already possible: When in Session mode, press the Session button again, which will open the configuration mode. Select "Flipped".

I know full well about Flipped mode, that is not what I mean. I clearly described how this is different. If you rotate the controller with it in Flipped mode you get the first track at the bottom and the last track at the top on the controller. This is even more confusing that having to reorientate 90 degrees to the normal mode. I know that thinking to work with an actually rotated controller does make this a rather weird request though....

Ah, I see. I read this wrong since I could not imagine that someone is really turning the controller itself Since you are the first asking for this in 10 years, I guess it really a bit special.

4. Is a rotated view possible? Four cells/scene of sixteen tracks seems a weird choice as the only layout when most controllers are 8x8 and on the Oxi you could have 8 tracks by 12 scenes, with the four buttons going to the left side. To be able to switch between these two views live could be quite powerful for the way I've been working.

Don't think that a flipped mode makes sense on devices which do not have the same number of pads in both directions.

I partially agree with you, but what I really don't understand is the choice of 16 tracks by 4 scenes, over 8 tracks by 12 scenes. As nearly all other controllers give you 8 tracks by 8 scenes keeping the same 8 tracks and extending the number of controllable scenes to 12 would much closer match the rest of the units. It seems an even more logical choice as this would also make the pads align with what is on the screen, rather than be offset from the screen by 90 degrees.

Can you please give the reasoning for choice, as I really struggle to see it. Although I have a fair few song segments over 8 tracks I don't think I have a single one that is 4 or less scenes in length. I guess if you only queue and play from intro it may make things easier, but it pretty much makes it impossible to set up scenes/cells for live chopping (eg jumping between a variety of breakbeats) well at least any more than 4 at once.

One of the reasons is that it is a bit complicated programming wise. Since this needs to be configured during the startup of the extension, it would either require a restart (which would not bew nice from a usability standpoint) or duplicate the data which would have a performance impact.

[g3eck0]

Hey and thanks for the great progress on DbM/Bitwig.

I'd like to suggest a slight ergonomics/accessibility type of an improvement.

As an Ableton Push 2 user I would very much like that all the Push 2 pad lights in the Note entry modes to follow the MIDI Clip colour for all pads, instead of just the root notes. Currently other than the root notes appear to be white in all configurations I can think of.

For comparison in Ableton, all the pads follow the color scheme of the Clip with the root note being darker and the rest of the pads being a slightly lighter shade.

For me this would be a significant eyesaver & usability improvement, especially when using the controller in low light situations. And just in case: I'm referring to the Note entry mode in any of the configurations Play/Chords/Piano/Drum64.

Thanks in advance if you can spare this some attention!

[moss]

Hey and thanks for the great progress on DbM/Bitwig.

I'd like to suggest a slight ergonomics/accessibility type of an improvement.

As an Ableton Push 2 user I would very much like that all the Push 2 pad lights in the Note entry modes to follow the MIDI Clip colour for all pads, instead of just the root notes. Currently other than the root notes appear to be white in all configurations I can think of.

For comparison in Ableton, all the pads follow the color scheme of the Clip with the root note being darker and the rest of the pads being a slightly lighter shade.

For me this would be a significant eyesaver & usability improvement, especially when using the controller in low light situations. And just in case: I'm referring to the Note entry mode in any of the configurations Play/Chords/Piano/Drum64.

Thanks in advance if you can spare this some attention!

I just introduced a new option "Turn off scale pads", which might help.

[smi1bit]

Hello, Moss.

Could you please make a DrivenbyMoss for Launchkey MK4? The default Step Sequencer mode in Launchkey MK4 is inconvenient because you can't go from Drum Pad Mode to Sequncer Mode and have to use the keyboards, and the Clip Launcher mode is more limited than when I applied Drivenbymoss to MK3.

And MK4's step sequencer not support triplet function, MK4's clip launcher not support second line's play.