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

[matthieu87]

Hey, I'm experiencing some strange behaviors with the launchpad pro mk3 when I use the drum sequencer.

When I press the red button on the bottom right of the launchpad and it opens the options of the drum rack, then I press note and come back again to the drum sequencer pressing the "chord" button, the pages of the sequencer don't give a correct visual feedback, and the bar | that marks where the sequence is will not give a correct visual feedback as well.

Thanks, will be fixed in the next update.

Thanks for fix it, brother!

Another weird behavior is when I press cursor up or down + pad to increase or decrease the note repeat. When I press the cursor up or down, even if a hold it, it will change the page of the drums so I can not press cursor + pad.

That's how it works. To change the note repeat, enable the 2nd pad on the bottom of the extra functions (light blue). Then use the Scene buttons to set the repeat period. Same for the repeat length, use the 3rd button.

I think you did not understood the problem.

Sequencers
NOVATION LAUNCHPAD
• Cursor Up+Pad: enables and increases note repeat by 1. <---I cant use it
• Cursor Down+Pad: enables and decreases note repeat by 1.<--- I cant use it too

The problem is in this command.

And finally a request. Would be good if we could enable "Overdub playing launcher clips" and "Write clip launcher automation" at the same time. It would help us to record automations in clip launcher in live performances.

Yes, automation is still missing. Any ideay were to put it?

I think we could have some options in the controller settings.
Maybe enable launcher automation with the overdub automation.
Or change the behavior of the record or shift+record button.
Or even change the behavior of the play button. In a Live Performance the Play/Stop function is very risk.
All that could be selected in the settings menu.
On this very moment I have the "WRITE CLIP LAUNCHER AUTOMATION" mapped to my Play button, but unfortunately it gives no visual feedback on the launchpad.


And I think I found another bug. When I press the Fixed Length button it should create a new clip with the length set in settings, but in reality it is starting a clip record on the next scene and create the blank clip with the predefined length on the first empty scene of the clip. The two things at the same time.
To reproduce this bug you can not have your "square scene marker" at the top, it must be somewhere else.

Hi Jürgen,

For the note repeat fonction, I think hadoso was talking about the « ratchet », the fonction that controle the bitwig operator note repeat.
In the manual it says that to be able to use it we have to hold the up/down arrow and the pad we want to ratchet.
But we cannot hold the arrows without cycling through the pad bank.


Also is it possible to toggle on and off the mute and solo fonction inside the drum sequencer like the note repeat, instead of having to press the fonction for each time we want to mute or solo a pad ?
That would be great

thank a lot

[moss]

And I want to take the opportunity, if you allow me, to make one more suggestion on how to make this wonderful script even better.

Maybe we could control the operators with the launchpad. That's the only advantage I see in the original mapping over yours.
Perhaps we could use shift for an additional function in sequencer scene triggers to control probability of the notes.

What do you mean by "the original mapping"?

[hadoso]

And I want to take the opportunity, if you allow me, to make one more suggestion on how to make this wonderful script even better.

Maybe we could control the operators with the launchpad. That's the only advantage I see in the original mapping over yours.
Perhaps we could use shift for an additional function in sequencer scene triggers to control probability of the notes.

What do you mean by "the original mapping"?

Sorry if it wasn't clear. By "original mapping" I mean the mapping that comes from the factory and is designed to work primarily with ableton.

In my opinion, your mapping, which works on our beloved bitwig, is much better, because your mapping does much more than the "original" one.

But the "original mapping" has an advantage over yours, which is the possibility of controlling the probability of the notes being played or not. From what I saw in your manual, apparently these controls are possible in other controllers, so I gave you a suggestion on how to implement this in launchpad pro mk3.

If you think it's a good idea and want to implement it, I'm sure all of us who use this controller would be very grateful.

Thanks again, man!

[moss]

And I want to take the opportunity, if you allow me, to make one more suggestion on how to make this wonderful script even better.

Maybe we could control the operators with the launchpad. That's the only advantage I see in the original mapping over yours.
Perhaps we could use shift for an additional function in sequencer scene triggers to control probability of the notes.

What do you mean by "the original mapping"?

Sorry if it wasn't clear. By "original mapping" I mean the mapping that comes from the factory and is designed to work primarily with ableton.

In my opinion, your mapping, which works on our beloved bitwig, is much better, because your mapping does much more than the "original" one.

But the "original mapping" has an advantage over yours, which is the possibility of controlling the probability of the notes being played or not. From what I saw in your manual, apparently these controls are possible in other controllers, so I gave you a suggestion on how to implement this in launchpad pro mk3.

If you think it's a good idea and want to implement it, I'm sure all of us who use this controller would be very grateful.

Thanks again, man!

Ah, OK. It sounded a bit like there would be a script which supports operators and expressions.

[krazzmann]

At the moment I‘m using an Akai APC 40 mkII and a Launchpad X but I still have to grab the mouse and keyboard quite often. In your opinion which controller supported by Moss is the most comprehensive for a mouse-less workflow? Push 1/2? Maschine mk2 / mk 3?

[moss]

At the moment I‘m using an Akai APC 40 mkII and a Launchpad X but I still have to grab the mouse and keyboard quite often. In your opinion which controller supported by Moss is the most comprehensive for a mouse-less workflow? Push 1/2? Maschine mk2 / mk 3?

Push has still the largest function set.

[Hez]

Hi moss,

Quick question about the flexi - is it possible to map a knob to a remote control slot on the first device (regardless of what the device is) on a specific track?

E.g. I want to have a template where tracks 5-8 are my generic percussion tracks and I want the first 4 columns of my Faderfox to always control the first device on those tracks, regardless of what device I load and regardless of where I happen to currently be navigating in the project (so not based on a cursor that follows the view like e.g. the Push script).

Cheers

[moss]

Hi moss,

Quick question about the flexi - is it possible to map a knob to a remote control slot on the first device (regardless of what the device is) on a specific track?

E.g. I want to have a template where tracks 5-8 are my generic percussion tracks and I want the first 4 columns of my Faderfox to always control the first device on those tracks, regardless of what device I load and regardless of where I happen to currently be navigating in the project (so not based on a cursor that follows the view like e.g. the Push script).

Cheers

Currently not. Will add it to the wish list.

[Hez]

Cool thanks so much! So this behaviour is theoretically possible with the current API?

[moss]

Cool thanks so much! So this behaviour is theoretically possible with the current API?

Yes. Monitoring the first device of the selected track is no problem.

[docam28]

This DrivenByMoss is fantastic! it saves my life for my Komplete Kontrol S61 MK2 and Bitwig Studio 4.4.3 (Windows): no more mandatory macros, now I can do exactly what I want with MIDI CC messages. Thanks a million to developer.

[moss]

This DrivenByMoss is fantastic! it saves my life for my Komplete Kontrol S61 MK2 and Bitwig Studio 4.4.3 (Windows): no more mandatory macros, now I can do exactly what I want with MIDI CC messages. Thanks a million to developer.

You are welcome!

[Hempmaster]

Hello, Jürgen!
Many thanks and huge respect for your invaluable work

I have a little issue with TouchOSC controller. The 8 user parameters in the provided template don't seem to respond to mapping. Everything else works as expected. I've searched this thread and it looks like they were broken earlier, so just wanted to check if they're supposed to work now. Not big of a deal if they don't)

Win11, Bitwig 4.4

[moss]

Hello, Jürgen!
Many thanks and huge respect for your invaluable work

I have a little issue with TouchOSC controller. The 8 user parameters in the provided template don't seem to respond to mapping. Everything else works as expected. I've searched this thread and it looks like they were broken earlier, so just wanted to check if they're supposed to work now. Not big of a deal if they don't)

Win11, Bitwig 4.4

The template is a bit outdated, I guess I will remove it. There is a pretty extensive new one from a user some pages back in this thread. Or simply use Open Stage Control instead.

[Hempmaster]

Hi,

I released another version, which fixes some errors/cosmetic, enables animations, and adds the layer mixer

https://github.com/ylmrx/ludwig

see a demo here : https://www.instagram.com/p/Cklo6M4PrTR/

Do not hesitate to report on any issue

Wow! Looks great! Thank you so much!!

The template is a bit outdated, I guess I will remove it. There is a pretty extensive new one from a user some pages back in this thread. Or simply use Open Stage Control instead.

Thank you, Jürgen