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

[moss]

1) The problem is - APC40mk2+Moss script opens clip editor panel each time when I trigger clip. Even if I press "E" shortcut to hide it and launch another clip (or the same clip) it opens clip editor panel again and again. It was not present in BW5 or any BW6 betas until beta12. With BW script for APC40mk2 everything works as usual.
and the answer from BW beta support is
...please be sure to report this bug to Moss.
It seems the script always does select + showInEditor together, but only beta 12 now contains a fix for a bug that made showInEditor not work for scenes, so it did not happen before.

Noted. Will look into remaining Bitwig 6 issues when the final version is released.

3) FR horizontal scrolling by page/clip - please can u add option (like in BW script setting for APC40mk2) in your script setting or some hw shift switch for clip launcher scrolling (horizontal and vertical) by page/clip. Now the vertical scrolling scrolls by clip and +shift up/down by page, but horizontally it scrolls only by clip (the +shift left/right does nothing)

Will check.

[moss]

Hi Jürgen,
Have you come across Yamaha's new CC1 device? It looks really cool and apparently works with Cubase out of the box. Do you think it would be a big job to get it to work with Bitwig?
Here's a YT video all about it...

I saw the video. But that's it.

[moss]

Hi there,
I have a Novation Launchpad Mini MK2 that I'd like to integrate into Bitwig.
As far as I understand, that specific controller is not supported by DrivenByMoss, but I'd imagine it would be possible to maybe start from a script for a similar model and tweak it?
Would you suggest going that route or rather writing a new script from scratch?
Thanks!

Not sure if the Mini Mk2 is up to the task to use the same code, I have no experience with the device.
The rest depends on your programming skills.

[icaria36]

• Added support for OXI One Mk2

This is fantastic! Thank you so much. I will try it tonight.

[HPKVR]

3) FR horizontal scrolling by page/clip - please can u add option (like in BW script setting for APC40mk2) in your script setting or some hw shift switch for clip launcher scrolling (horizontal and vertical) by page/clip. Now the vertical scrolling scrolls by clip and +shift up/down by page, but horizontally it scrolls only by clip (the +shift left/right does nothing)

Will check.

Sorry Moss,
of course I meant PAGE (not clip) "...but horizontally it scrolls only by PAGE (the +shift left/right does nothing)

[drsyncenstein]

I have both an iCon P1-M and P1-Nano mackie mixer units. The P1-Nano does not update the small screen beside the fader as tracks are changed, when using DrivenByMoss. The top 8 screens update fine, but the single screen requires manual moving. This is a problem, because the single fader controls the currently selected track, but you can't tell which track is selected on the screens (only in Bitwig).

The P1-M works flawlessly as expected with DrivenByMoss. The P1-Nano single screej works as expected with Bitwig's default script, but it's missing DrivenByMoss extra functions.

Could you please update the script to fix this bug with the single display? I tried changing all the settings in the deivenbymoss Mackie settings, but none of them helped.

Thank you!

Those devices are controllers that are officially supported by Bitwig, they don't use MOSS templates.
In other words; wrong forum, wrong thread.

They are on mentioned on the Bitwig support list, so you should contact Bitwig support.
https://www.bitwig.com/support/technica ... studio-28/

The icon manual says you need to be at firmware 1.21, make sure you did that before contacting support.

[icaria36]

• Added support for OXI One Mk2

This is fantastic! Thank you so much. I will try it tonight.

I'm very excited about this. I plan to use the Oxi One mk2 as a DAW controller together with the Roto. The idea is to use the Oxi for transport, track mode, and clip launcher, leaving the device mode (and probably the mixer) for the Roto, where it excels. I don't think I'll use Driven by Moss for the sequencer and play modes, for that I prefer the original Oxi, but it's good to have them there for the casual test.

I have spent my first couple of hours going through the features described in the documentation. All good, I like how easy is to use the track mixer mode (collapsing and expanding groups: great) and the clip launcher amb tracks, scenes, and their alternative modes.

The documentation doesn't say how to enter some of the modes but well, after a bit of trieal and error you learn. But there is something that I think it isn't working:

Press the Back button to leave it.

I can't leave the modes with the Back button. Well, you can always leave one mode by pressing the button to activate another, but sometimes "Back" is exactly what you want, and at least for me it isn't working. Shift+Back works fine.

I'll continue playing around. Thank you again!

[esq1]

Hello @moss,
hello controller users,

I have a few questions about whether it would be possible to add the following features:

a) Integrating the audio capture function that Bitwig has offered since version 5 into the controller.

b) A sequencer that displays two octaves of the piano layout in the lower section, with the notes being entered in the upper section.

c) When a note is pressed and held in the sequencer, an additional function should appear that displays the device's performance page, allowing me to set a P-lock similar to Elektron.

What do you think?

[moss]

Press the Back button to leave it.

I can't leave the modes with the Back button. Well, you can always leave one mode by pressing the button to activate another, but sometimes "Back" is exactly what you want, and at least for me it isn't working. Shift+Back works fine.

I'll continue playing around. Thank you again!

Will check.

[moss]

Hello @moss,
hello controller users,

I have a few questions about whether it would be possible to add the following features:

Which specific controller are you talking about?

a) Integrating the audio capture function that Bitwig has offered since version 5 into the controller.

Yes, would be possible.

b) A sequencer that displays two octaves of the piano layout in the lower section, with the notes being entered in the upper section.

Interesting idea but I am not sure if this would add a new benefit in contrast to the already exisitng sequencers and you could only see one note at a time.

c) When a note is pressed and held in the sequencer, an additional function should appear that displays the device's performance page, allowing me to set a P-lock similar to Elektron.

You cannot change device parameters per step. As a workaround you can assign note parameters like pressure and assign it to the paramers you want to modulate.

[xtreme sounds]

HI i have been using the akai fire with your script for some time. great job as always. But I am wondering in your opinion, is there a controller that works even better using your scripts (looking to possibly upgrade)

[moss]

HI i have been using the akai fire with your script for some time. great job as always. But I am wondering in your opinion, is there a controller that works even better using your scripts (looking to possibly upgrade)

Only the Push but it is much larger and maybe the OXI One.

[esq1]

Hello @moss,
hello controller users,

I have a few questions about whether it would be possible to add the following features:

Which specific controller are you talking about?

a) Integrating the audio capture function that Bitwig has offered since version 5 into the controller.

Yes, would be possible.

b) A sequencer that displays two octaves of the piano layout in the lower section, with the notes being entered in the upper section.

Interesting idea but I am not sure if this would add a new benefit in contrast to the already exisitng sequencers and you could only see one note at a time.

c) When a note is pressed and held in the sequencer, an additional function should appear that displays the device's performance page, allowing me to set a P-lock similar to Elektron.

You cannot change device parameters per step. As a workaround you can assign note parameters like pressure and assign it to the paramers you want to modulate.

Hallo Jürgen,
Audio capture (and maybe playback) from the controller would be great.

I wasn't thinking of anything specific; I use a PUSH1 and PUSH2 controller.

Regarding the piano layout sequencer... it would certainly be customizable. I find a "classic" layout quite clear, and who actually uses one of those?

I already suspected that P-Locks wouldn't be so easy to implement. Using expressions is a good idea. Perhaps something like that will be added in the future.

Schönes Wochenende!

[unsaph3]

Hey @Moss, I love the extension - the Launchpad version took me a couple hours of playing with to get used to, and now that i'm used to it I can't imagine making funky music without it.

I bought a couple of InTech Grid modules - the TEK2 and ENC16 (detented encoders with push buttons), got all of them mapped to individual MIDI CC's, and using the generic flexi extension was able to map the encoders to what I want but I'm REALLY struggling with the jog wheels on the TEK2. In the detail editor, I'd like one to nudge notes back and forth, and the other to move the selection to the previous/next note. Is that possible with the generic flexi extension?

[moss]

Hey @Moss, I love the extension - the Launchpad version took me a couple hours of playing with to get used to, and now that i'm used to it I can't imagine making funky music without it.

Great!

I bought a couple of InTech Grid modules - the TEK2 and ENC16 (detented encoders with push buttons), got all of them mapped to individual MIDI CC's, and using the generic flexi extension was able to map the encoders to what I want but I'm REALLY struggling with the jog wheels on the TEK2. In the detail editor, I'd like one to nudge notes back and forth, and the other to move the selection to the previous/next note. Is that possible with the generic flexi extension?

Only if there are Bitwig functions for it (didn't check) and the encoder can send different MIDI commands for both directions.