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

[teknoman]

Hi Moss,
Great update on 20.3.0 with the User modes controlling the Project macros!! I'm using a Push 2 and had a suggestion. I have a lot of groups in my project and would like to control the group level (parent) macros of the selected track instead/in addition to the track macros in User mode. If there is more than one nested group, there could be a macro page(s) for each group in the User mode. The track controls can still be in User mode, but be at the far right in the page hierarchy. So the macro/parameter page listing in User mode would be 'Project/parent group/parent group/.../selected track'. Of course this only applies if the track belongs to one or more groups. If there are no groups present, the current behavior is great.

With this, we not only have direct access to the Project macros, but also any group parameters without having the group/parent track selected. I want to say that you already thought of this but BW won't allow this behavior . Let me know if this is clear. Thanks.

p.s. I have a Push 3 (controller only) that I'm not using since the DBM script doesn't support it yet. I think I am finally done using Ableton (latest update is just so slow), so I'm not using the Push 3 with Ableton either. If you need a Push 3 to help DBM development, I can send you mine to use for research.

[nowiamone]

DrivenByMoss 20.3.0 is online!
[*] OSC

• New: There is now a setting to choose between flat and hierarchical track navigation.
• New: Increased the number of configurable actions to 20.
• New: /automationWriteMode also dis-/enables clip automation record.
• New: /user commands are replaced with according /project and /track commands. OpenStageControl template got updated to reflect this (but only with /project commands).
• Fixed: Send attributes could not be changed (except volume).
• Fixed: Device page name was missing the 'name' part.

Enjoy!

Thanks alot! This is really awesome!

Now it's a real joy to use groups with a big OSC interface!

Since i was testing my project with groups now, i found an unexpected behavior:
When moving the navigation-button of the Komplete Kontrol S49MK2 to navigate through Tracks, the Group Track is like a "border", not letting the navigation through, unless the navigation-button gets double-tapped quickly. Not sure if that's "normal/expected" behavior.
How i encounter this behavior:
- Bitwig 5 Beta 13, drivenbymoss 20.3.0
- ARRANGE View.
- Project has several Tracks, including at least one Group Track
- i click on a Clip in the Clip Launcher, to focus it
- i use the Komplete S49MK2 4-Direction-Button to navigate from a non-grouped Track to the Grouptrack
-> Result: The Grouptrack doesn't get selected. Instead, it's only in focus for a millisecond, then the focus switches back to the non-grouped Track. (="invisible border")

Since i wasn't sure if that was also the case in the past, I checked it with Bitwig 4.4.10 with DrivenByMoss-19.2.2 : there, the navigation-button switches through group-tracks without effort.

Thanks alot for your work

[moss]

Re Bitwig 4 and Push 2 - Keyboard layout:
Am I missing the option to change the keyboard layout from 3rd, 4th and sequent., as well as horizontal/vertical or does this not exist? cheerio

Press the Scale button to enter scales mode, then hold the Shift button for additional options.

[moss]

DrivenByMoss 20.3 Video is online:

[moss]

Hi Moss,
Great update on 20.3.0 with the User modes controlling the Project macros!! I'm using a Push 2 and had a suggestion. I have a lot of groups in my project and would like to control the group level (parent) macros of the selected track instead/in addition to the track macros in User mode. If there is more than one nested group, there could be a macro page(s) for each group in the User mode. The track controls can still be in User mode, but be at the far right in the page hierarchy. So the macro/parameter page listing in User mode would be 'Project/parent group/parent group/.../selected track'. Of course this only applies if the track belongs to one or more groups. If there are no groups present, the current behavior is great.

Nice idea but as you expected not possible (but not 100% sure, it might with some serious head-scratching and ugly code).

p.s. I have a Push 3 (controller only) that I'm not using since the DBM script doesn't support it yet. I think I am finally done using Ableton (latest update is just so slow), so I'm not using the Push 3 with Ableton either. If you need a Push 3 to help DBM development, I can send you mine to use for research.

That is very generous! Many thanks for the offer! But I have one on order already, which just as a high delivery time.

[mevla]

20.3.0 : Does it mean that on the Launchpad it's no longer possible to program our own controls ?

[moss]

20.3.0 : Does it mean that on the Launchpad it's no longer possible to program our own controls ?

That's what you now use the Project Parameters for.

[AFranke]

Hi Jürgen,
thank you for the new version at first.

Acrobat_OGL7fyCxze.png

Toggeling on my SLMK3 with the "Up button" only works for device mode 1 and 2 here. The new additional modes 3 and 4 can't be selected this way. The alternative selection (holding the "Up button") method works. Mode 3 is white, like discribed in the manual, but mode 4 is colored brown?/Orange?, so not white as discribed in the manual.

[mevla]

20.3.0 : Does it mean that on the Launchpad it's no longer possible to program our own controls ?

That's what you now use the Project Parameters for.

I'm not running version 5, waiting for the official release, so I cannot frame what this actually means outside of the new Project Parameters or for that matter what is the full functionality of those.

If I want to control several parameters from a Melda FX plugin on a track, will these fit in the new Project Parameters ?

[moss]

20.3.0 : Does it mean that on the Launchpad it's no longer possible to program our own controls ?

That's what you now use the Project Parameters for.

I'm not running version 5, waiting for the official release, so I cannot frame what this actually means outside of the new Project Parameters or for that matter what is the full functionality of those.

If I want to control several parameters from a Melda FX plugin on a track, will these fit in the new Project Parameters ?

Yes. You can map any parameter in Bitwig to the Project parameters.

[moss]

Toggeling on my SLMK3 with the "Up button" only works for device mode 1 and 2 here. The new additional modes 3 and 4 can't be selected this way. The alternative selection (holding the "Up button") method works. Mode 3 is white, like discribed in the manual, but mode 4 is colored brown?/Orange?, so not white as discribed in the manual.

Thanks for the info. Yes, it is amber/orange, will update the manual. The mode selection is basically as it was before with the User mode.

[xtreme sounds]

hi sir on the akai fire is there a way to add a 4x4 drum square colored pads set for use with any drum machine plugin? I know the pads only light up when using with the Bitwig Drum Machine (the loaded samples load up in a 4x4 grid).

You can use the Drum 64 mode. Make sure that "Turn off empty drum pads" in is disabled in the settings.

Hi I did those things and the pads containing samples are still not lit up using XO. its ok no biggie

I forgot to mention: simply put an empty drum machine before XO.

Hi I did that but the only pad that lights up is the one I play.

[moss]

hi sir on the akai fire is there a way to add a 4x4 drum square colored pads set for use with any drum machine plugin? I know the pads only light up when using with the Bitwig Drum Machine (the loaded samples load up in a 4x4 grid).

You can use the Drum 64 mode. Make sure that "Turn off empty drum pads" in is disabled in the settings.

Hi I did those things and the pads containing samples are still not lit up using XO. its ok no biggie

I forgot to mention: simply put an empty drum machine before XO.

Hi I did that but the only pad that lights up is the one I play.

Did you disable "Turn off empty drum pads"?

[BitwigStarter599]

Hi Moss,
using your extension for years to connect my PSR 6700 to Bitwig Studio, happened to work all the time perfect. Thanks. To extend my setup I found an akai mpd32 usb for a low budget and tried to connect this one by Flexi Script (Bitwig 5 Beta 11 and Script 20.2.1) to Bitwig Studio. First hand no midi was transferred. Then I tried the MPC 40 Script and all of a sudden there was response to fader movements. As I cannot change the MPC 40 configuration for my purpose I switched back to Flexi Controller. And aha, there it was sending midi data. Then I started configuration and all went perfect until ... an usb stick was connected to the computer. This ended the midi connection until ... yes you guess it right, the mpc 40 controller was startet again.
Is there an other choice to keep the connection stable?
Somewhere in the thread (jan 14th of 21) I found a hint that there might be a dedicated Bitwig driver for MPD, but I could not find one.
Edit: The MPC 40 Script starts the Pad Controller only when in Bitwig Studio 4.4.8. After that first start the Flexi Script works in Bitwig Studio 5, too. That remains stable, even when restarting Bitwig Studio 5 several times, until USB reconfiguration.

I am afraid you have an USB issue somewhere. Try different cables, different hub (if any) or a different port.

Hi Moss,
changed USB ports and cables. No difference seen. Using a midi monitor app, I found that MPC40 Script is the only one who makes the MPD32 work. Works in V5, too, as I experienced in between. After that "initializing" the pad is working as expected, even when switching to "generic flexi" script, which I would prefer for its flexibility. Is there an additional (less complex) way to achieve that result?
BTW: What about your "Midi Monitor" script. This seems no longer operable. The start button for opening the data display window is missing in V5.
Conclusion: MPD32 is operable, but initializing is somewhat difficult. As I need an expression pedal input, I have to stick to the MPD32. Other devices, like the MPC40 series, no longer offer that functionality at all. Looks like the interface chips needed have disappeared from the market.

[moss]

changed USB ports and cables. No difference seen. Using a midi monitor app, I found that MPC40 Script is the only one who makes the MPD32 work. Works in V5, too, as I experienced in between. After that "initializing" the pad is working as expected, even when switching to "generic flexi" script, which I would prefer for its flexibility. Is there an additional (less complex) way to achieve that result?

I guess that controller needs some kind of activation or mode change command to make it work.

BTW: What about your "Midi Monitor" script. This seems no longer operable. The start button for opening the data display window is missing in V5.
Conclusion: MPD32 is operable, but initializing is somewhat difficult. As I need an expression pedal input, I have to stick to the MPD32. Other devices, like the MPC40 series, no longer offer that functionality at all. Looks like the interface chips needed have disappeared from the market.

the JavaScript console can now only be opened via the commander or by assigning a shortcut to it. To open the commander press Ctrl+Return and Console.