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

[xtreme sounds]

Hi sir on the fire script for User 1. Is there a way when on that option or perhaps in perform or overview section that we can change the track focus? Im trying to quickly turn a knob affecting the filter on one track then switch to another track and play notes live. It seems I have to quickly switch back to the channel option then press alt and turnthe select knob. Maybe there is a way to include more performance controls on this thing

[moss]

Hi Moss,

Would it be possible in the future to use the up/down arrow buttons on the right of the Push 2 to change the Mode (major/minor, mixolydian,etc.) in "Scale" mode on the Push 2? I ask this knowing that there are up/down buttons that change the mode above and below the screen on the left, but they are hard to access if your playing keys on the push in real time like I tend to do, and if the buttons to change modes was on the right I could do it more smoothly while playing with my right hand while I hold the a chord with my left. Currently, when i'm in "scale" mode (the screen with the key's and modes listed) which is virtually all the time, the up/down buttons don't serve any other function to my knowledge and are deactivated. This is my humble dream, but I would literally pay for this feature (i'm not kidding)


This is the default behavior in Ableton when in "Scale" mode where the up/down arrow near the right (it is the up/down/left/right arrows in a square basically) changes the "mode" in Scale mode. Basically what the button above and below the screen are set to do now. I would even be willing to go so far as to customize my own version of the script if I could get a few tip as to how so I could change any future versions as well.

Thanks for even considering as always.

Hmm, difficult. I am sure if I change this, someone will complain as well

[moss]

Hi sir on the fire script for User 1. Is there a way when on that option or perhaps in perform or overview section that we can change the track focus? Im trying to quickly turn a knob affecting the filter on one track then switch to another track and play notes live. It seems I have to quickly switch back to the channel option then press alt and turnthe select knob. Maybe there is a way to include more performance controls on this thing

I guess the easiest solution is to map the parameter to USER 2 and stay in the play mode for the track you want to play.

[jaaypeso24]

Hi Moss,

Would it be possible in the future to use the up/down arrow buttons on the right of the Push 2 to change the Mode (major/minor, mixolydian,etc.) in "Scale" mode on the Push 2? I ask this knowing that there are up/down buttons that change the mode above and below the screen on the left, but they are hard to access if your playing keys on the push in real time like I tend to do, and if the buttons to change modes was on the right I could do it more smoothly while playing with my right hand while I hold the a chord with my left. Currently, when i'm in "scale" mode (the screen with the key's and modes listed) which is virtually all the time, the up/down buttons don't serve any other function to my knowledge and are deactivated. This is my humble dream, but I would literally pay for this feature (i'm not kidding)


This is the default behavior in Ableton when in "Scale" mode where the up/down arrow near the right (it is the up/down/left/right arrows in a square basically) changes the "mode" in Scale mode. Basically what the button above and below the screen are set to do now. I would even be willing to go so far as to customize my own version of the script if I could get a few tip as to how so I could change any future versions as well.

Thanks for even considering as always.

Hmm, difficult. I am sure if I change this, someone will complain as well

Thanks for your reply Moss. Maybe I did a poor job of explaining what I was asking for. In this case, I wouldn't asking for the other buttons to be removed, but for currently unused buttons to be give the same functionality. Currently the up/down arrow buttons don't do anything (they are deactivated in "Scale" mode). So I would just want them do perform the same function as the current buttons that change the mode (currently above and below the screen). So users who like that setup would still be able to use those keys without any changes. Hopefully that explanation makes more sense.

[moss]

Hi Moss,

Would it be possible in the future to use the up/down arrow buttons on the right of the Push 2 to change the Mode (major/minor, mixolydian,etc.) in "Scale" mode on the Push 2? I ask this knowing that there are up/down buttons that change the mode above and below the screen on the left, but they are hard to access if your playing keys on the push in real time like I tend to do, and if the buttons to change modes was on the right I could do it more smoothly while playing with my right hand while I hold the a chord with my left. Currently, when i'm in "scale" mode (the screen with the key's and modes listed) which is virtually all the time, the up/down buttons don't serve any other function to my knowledge and are deactivated. This is my humble dream, but I would literally pay for this feature (i'm not kidding)


This is the default behavior in Ableton when in "Scale" mode where the up/down arrow near the right (it is the up/down/left/right arrows in a square basically) changes the "mode" in Scale mode. Basically what the button above and below the screen are set to do now. I would even be willing to go so far as to customize my own version of the script if I could get a few tip as to how so I could change any future versions as well.

Thanks for even considering as always.

Hmm, difficult. I am sure if I change this, someone will complain as well

Thanks for your reply Moss. Maybe I did a poor job of explaining what I was asking for. In this case, I wouldn't asking for the other buttons to be removed, but for currently unused buttons to be give the same functionality. Currently the up/down arrow buttons don't do anything (they are deactivated in "Scale" mode). So I would just want them do perform the same function as the current buttons that change the mode (currently above and below the screen). So users who like that setup would still be able to use those keys without any changes. Hopefully that explanation makes more sense.

You are talking about the cursor keys, right? They are active. They scroll the scenes and tracks.

[jaaypeso24]

You are talking about the cursor keys, right? They are active. They scroll the scenes and tracks.

Ah I see! I know a little about Java, and creating/compiling the .bwextension files from source code using Maven (i've been watching your Youtube videos on API/dev most of the day. Is it possible for me to just flip the functions and make a custom .bwextension just for my own personal use? I never use the up/down arrow keys for navigation, so for me it would be perfect to just make the up/down arrow do what the "row1_button_1" and "row2_button_1" do currently while in "Scale" mode to change the scale. Any idea which file(s) in the source code directory I would start if I wanted to make that change. I'm in the PushControlSurface.java file in Visual Studio Code and can see the parameters for all 4 buttons. If I switched them there and then created an alternate .bwextension would it flip the functions, or would I need to make changes in other places.

I understand if its a bit too time consuming for you to direct me as I see the code is quite involved from your years of development effort. Thanks.

[moss]

You are talking about the cursor keys, right? They are active. They scroll the scenes and tracks.

Ah I see! I know a little about Java, and creating/compiling the .bwextension files from source code using Maven (i've been watching your Youtube videos on API/dev most of the day. Is it possible for me to just flip the functions and make a custom .bwextension just for my own personal use? I never use the up/down arrow keys for navigation, so for me it would be perfect to just make the up/down arrow do what the "row1_button_1" and "row2_button_1" do currently while in "Scale" mode to change the scale. Any idea which file(s) in the source code directory I would start if I wanted to make that change. I'm in the PushControlSurface.java file in Visual Studio Code and can see the parameters for all 4 buttons. If I switched them there and then created an alternate .bwextension would it flip the functions, or would I need to make changes in other places.

I understand if its a bit too time consuming for you to direct me as I see the code is quite involved from your years of development effort. Thanks.

As you already mentioned I do not have time to guide people through the code. But as a starter look at the PushCursorCommand.

[mitchellmhanson]

Hello Moss, I need some help, I've tried almost everything I can think of. let me start by saying thank you for these awesome scripts. I use both Reaper and Bitwig with my Maschine Mikro and k.kM32 works flawlessly in reaper the integration is beautiful. I have had quite a few problems with Bitwig unfortunately. the Mikro works great. but not the m32. 2 problems. M32 MIDI OUT error, sometimes it works, most times it crashed upon startup. solution was to choose M-DAW as both outputs instead. tried to fix everyway I can imagine but nothing works longer than a day. but what breaks the almost flawless integration for me is there is no automatic track plug-in focus for instances of Komplete . it works in Reaper, and in Ableton so I know its not my PC. even making sure first instance is NIKB00 and second is NIKB01, 02 etc as you shown in your video. still will not automatically focus on Komplete Kontrol instance on the selected track, plug-in hosting mode doesn't affect the keyboards "plug-in" button function. I have to use my mouse to open and click the keyboard button on each instance of Komplete kontrol or Shift+Track(instance) to scroll through a list and select the correct one. Im really hoping to fix these last 2 problems, look forward to hearing back from you.

[moss]

DrivenByMoss 17.0 is out!

Get it from https://mossgrabers.de

Note: it requires now Bitwig 4.3+!

• Fire
  • New: Added a new drum mode, see manual for details.
  • New: The last selected note/sequencer view is remembered when switching to session/mix and back.
  • New: All LEDs are full turned off on shutdown and a Goodbye message is displayed.
  • New: Session mode: ALT + pad selects clip (without starting playback).
  • New: Bank button + Touch knob: Resets the knobs value to the default value.
  • Fixed: Black pads were not fully turned off.
  • Fixed: Do not leave Mix mode on track selection.
• Fire, Maschine JAM, Push
  • New: In Session mode hold Select to immediately launch a clip. Release the clip pad while holding Select, to return immediately to the last playing clip. To select a clip use long pressing the clip pad instead.
• Fire, Launchpad, Push
  • New: Shift+Record turns off the recording of the selected slot on the selected track, if it is recording (instead of toggling clip launcher overdub). Enable 'Select clip/scene on launch' and 'Flip arranger and clip record' to make this work best.
• Komplete Kontrol MkI
  • New: Works now on Apple Silicon.
  • Fixed: USB resources were not freed on shutdown.
• Launchkey
  • New: Added detection for Launchkey 88
• MCU
  • Fixed: Knob LEDs went off when panorama was panned fully left.

Enjoy!

[xtreme sounds]

Awesome!!! I was pleasantly surprised watching Youtube and your video on the update for fire came up. Thanks for your hard work on this stuff.

[soulmedia]

Thanks so much for this update Moss - the new drum sequencer mode is brilliant!

An initial feedback from me is I'd prefer the drum sound's 'alt' behaviour (at 4:50 in the video) to be the opposite way round, so 'alt' enables preview rather than disabling it - could that be a setting perhaps?

Also would it be possible to implement a 'flip session' option as with other controllers in your extension (e.g. as a preference setting)?

[x.iso]

Hello, Moss! I've tried out Gamepad script and noticed that it seems like because it doesn't have midi out port used, I can't use it's CC bindings to map anything in Shortcuts for example. Am I wrong in that assumption or is it possible to add out port to use for this? I'm aware that I can use HW Instrument device on some proxy track to send CC's on another virtual midi port and bind CC's that way, but it's a bit of a hassle to set up every time. But I think opening up access to all shortcuts via CC mappings would extend use cases for gamepad usage.

Also, I've noticed a problem with analog stick controls, it doesn't do bipolar CC modulation which is understandable, since MIDI is unipolar 0-127 range, but can we at least have it use 64 as middle point with 0 and 127 being extreme ends of each axis? otherwise it's much less usable. or at least it would me more usable if there was separate CC/mapping for negative and positive X/Y movement.

[angelodonorio]

Hi There,

Thanx for your great work, I'm loving it

I have a question, How can I get to the hardware settings, I try to set the brightness of the pads but in the manual it doesn't specify what actions I have take. At least I don't see it, only that is possible

Thnx in advance
Angelo

[reflekshun]

I've been practicing and becoming more comfy with Bitwig & Push 2 for live stuff, I gotta say I'm loving it the more I use it. I really love the ease and freedom to start new layers and swap between playing live and controlling launch clips. Also push4bitwig allows for really direct access to tweaking things like filter sweeps on plugins on the fly. Still SO much more to learn but it's nice to be on the journey! I hope you enjoy this highlight of one night of jamming with it.

HUGE thanks to Moss for making these scripts for us!

Any questions about this setup / push 2 live workflows just ask! Happy to help

[moss]

An initial feedback from me is I'd prefer the drum sound's 'alt' behaviour (at 4:50 in the video) to be the opposite way round, so 'alt' enables preview rather than disabling it - could that be a setting perhaps?

I was afraid someone would say that
Noted.

Also would it be possible to implement a 'flip session' option as with other controllers in your extension (e.g. as a preference setting)?

I am afraid this will not happen (this would require many internal changes since x/y is different with that device).