DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)
-
- KVRian
- 784 posts since 29 Mar, 2016
Hi I just thought of a new pad mode for akai fire. Maybe it will work for push as well. what if we had something like the 8th mode but the left side goes from low c to middle c and the right side goes from middle c to high c? Then we could have 2 separate instruments one on the left and one on the right using note filters in Bitwig with some octave shifting. Curently the 8th pad layout overlaps between left and rigtht. Im thinking a mode completely different here. left side right side
-
- KVRian
- 784 posts since 29 Mar, 2016
Hi on the akai fire or push 2 (thinking of getting one), is there a control where we can quickly change the midi channel destination as shown on the left side inspector panel? This is needed so we can record all the midi channels into 1 Tracks piano roll.
NOTE: I found my Hardware responds best when the setting is ALL SAME if I am just recording using my hardware keyboard, but when using an external controller (ie fire with this script), it will not let me change the destination channel for recording a specific part into the piano roll. Its tricky. I think we need some new setting here.
NOTE: I found my Hardware responds best when the setting is ALL SAME if I am just recording using my hardware keyboard, but when using an external controller (ie fire with this script), it will not let me change the destination channel for recording a specific part into the piano roll. Its tricky. I think we need some new setting here.
You do not have the required permissions to view the files attached to this post.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
This Bitwig parameter cannot be changed from a controller.xtreme sounds wrote: Sun Jul 28, 2024 11:13 am Hi on the akai fire or push 2 (thinking of getting one), is there a control where we can quickly change the midi channel destination as shown on the left side inspector panel? This is needed so we can record all the midi channels into 1 Tracks piano roll.
NOTE: I found my Hardware responds best when the setting is ALL SAME if I am just recording using my hardware keyboard, but when using an external controller (ie fire with this script), it will not let me change the destination channel for recording a specific part into the piano roll. Its tricky. I think we need some new setting here.
However, the midi channel for sequencer notes can be configured. Currently, only in the settings of the Fire.
-
- KVRian
- 784 posts since 29 Mar, 2016
I guess either way we have to use a mouse for this. Thanksmoss wrote: Sun Jul 28, 2024 1:02 pmThis Bitwig parameter cannot be changed from a controller.xtreme sounds wrote: Sun Jul 28, 2024 11:13 am Hi on the akai fire or push 2 (thinking of getting one), is there a control where we can quickly change the midi channel destination as shown on the left side inspector panel? This is needed so we can record all the midi channels into 1 Tracks piano roll.
NOTE: I found my Hardware responds best when the setting is ALL SAME if I am just recording using my hardware keyboard, but when using an external controller (ie fire with this script), it will not let me change the destination channel for recording a specific part into the piano roll. Its tricky. I think we need some new setting here.
However, the midi channel for sequencer notes can be configured. Currently, only in the settings of the Fire.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
DrivenByMoss 24.0.0 is online!
Get it from https://mossgrabers.de
Enjoy!
Get it from https://mossgrabers.de
- Added support for OXI One hardware sequencer.
- All devices
- Fixed: Device detection was broken on Macos ARM.
- Maschine JAM
- Fixed: Extension crashed due to an ill-formatted sysex message.
- MCU
- Fixed: Device layers could not be navigated.
Enjoy!
-
- KVRian
- 652 posts since 30 Oct, 2022
Dear Jürgen,
thanks to your OSC script, i built a Touch OSC Controller which lets me use the Bitwig Browser.
I also use your drivenbymoss SL MK3 Script, to have haptical control over device remote control parameters via the knobs.
When i'm recording VST instruments into Audio-Clips of Bitwig (Midi Track routed towards Audio Tracks), i only ever use the "live-preview" mode of Bitwigs Browser, never confirming the Browser-Instrument-Selection, but rather just playing the instrument via live-preview, then quickly switching to the next Instrument.
The problem: The SL MK3 automatically opens the Browser, when the Browser opens in Bitwig.
So while Bitwigs Browser is open, i therefore cannot reach the Parameter Pages of the Primary device via the SL MK3, because the UP Arrow confirms the Browser selection. This means i'm forced to leave the live-preview mode of the Bitwig Browser, and confirm the Browser selection, before being able to control the device-parameters.
Could you please either implement a way to reach the parameter pages of the primary device, while Bitwigs Browser is open, or give us the option to turn the SLMK3 Browser off, or give us the option to have some "NI Komplete Kontrol- esk" behavior where the SLMK3 only ever shows the primary instrument remote control of selected Tracks? (the latter option would be my favorite, because i miss that NI Komplete Kontrol Keyboard workflow, where the main purpose is to see and control the main instrument.
Also, it would be great, if the parameter page wouldn't be pink, but rather reflect the Track-Color of the selected Track. Maybe that's an idea for that possible new 'primary device' page above the 'selected device' page?
Another idea for that page would be, that instead of the Device Name (which usually is quite generic, like KONTAKT), the actual preset name is shown in the rightmost Display. Thanks alot for your consideration and work 

thanks to your OSC script, i built a Touch OSC Controller which lets me use the Bitwig Browser.
I also use your drivenbymoss SL MK3 Script, to have haptical control over device remote control parameters via the knobs.
When i'm recording VST instruments into Audio-Clips of Bitwig (Midi Track routed towards Audio Tracks), i only ever use the "live-preview" mode of Bitwigs Browser, never confirming the Browser-Instrument-Selection, but rather just playing the instrument via live-preview, then quickly switching to the next Instrument.
The problem: The SL MK3 automatically opens the Browser, when the Browser opens in Bitwig.
So while Bitwigs Browser is open, i therefore cannot reach the Parameter Pages of the Primary device via the SL MK3, because the UP Arrow confirms the Browser selection. This means i'm forced to leave the live-preview mode of the Bitwig Browser, and confirm the Browser selection, before being able to control the device-parameters.
Could you please either implement a way to reach the parameter pages of the primary device, while Bitwigs Browser is open, or give us the option to turn the SLMK3 Browser off, or give us the option to have some "NI Komplete Kontrol- esk" behavior where the SLMK3 only ever shows the primary instrument remote control of selected Tracks? (the latter option would be my favorite, because i miss that NI Komplete Kontrol Keyboard workflow, where the main purpose is to see and control the main instrument.
Also, it would be great, if the parameter page wouldn't be pink, but rather reflect the Track-Color of the selected Track. Maybe that's an idea for that possible new 'primary device' page above the 'selected device' page?
I built a Looper for Bitwig!
https://www.youtube.com/watch?v=-z5ywDo2bU0
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
I am afraid I have no control over this. Please write to Bitwig, the v5 browser is broken anyway since the API is still not updated. Complain loudly about this as wellnowiamone wrote: Thu Aug 01, 2024 3:32 pm ...
Could you please either implement a way to reach the parameter pages of the primary device, while Bitwigs Browser is open, or give us the option to turn the SLMK3 Browser off, or give us the option to have some "NI Komplete Kontrol- esk" behavior where the SLMK3 only ever shows the primary instrument remote control of selected Tracks? (the latter option would be my favorite, because i miss that NI Komplete Kontrol Keyboard workflow, where the main purpose is to see and control the main instrument.
Noted.nowiamone wrote: Thu Aug 01, 2024 3:32 pm Also, it would be great, if the parameter page wouldn't be pink, but rather reflect the Track-Color of the selected Track. Maybe that's an idea for that possible new 'primary device' page above the 'selected device' page?![]()
Not sure if that info is available since the old preset API got ditched but will check.nowiamone wrote: Thu Aug 01, 2024 3:32 pm Another idea for that page would be, that instead of the Device Name (which usually is quite generic, like KONTAKT), the actual preset name is shown in the rightmost Display. Thanks alot for your consideration and work![]()
-
- KVRian
- 652 posts since 30 Oct, 2022
The Browser API is in a sad state, i agree - i already wrote Bitwig many months ago, but will ask them again to please reflect the Browser changes in the API!moss wrote: Fri Aug 02, 2024 6:53 amI am afraid I have no control over this. Please write to Bitwig, the v5 browser is broken anyway since the API is still not updated. Complain loudly about this as wellnowiamone wrote: Thu Aug 01, 2024 3:32 pm ...
Could you please either implement a way to reach the parameter pages of the primary device, while Bitwigs Browser is open, or give us the option to turn the SLMK3 Browser off, or give us the option to have some "NI Komplete Kontrol- esk" behavior where the SLMK3 only ever shows the primary instrument remote control of selected Tracks? (the latter option would be my favorite, because i miss that NI Komplete Kontrol Keyboard workflow, where the main purpose is to see and control the main instrument.![]()
However, concerning my wish here, i think it could be solved by your grace, haha - because an option to deactivate the browsing function within the SL MK3 controller script would already lead to my desired behavior:
- browsing via touch osc or simply within Bitwig, while keeping focus on the parameter page at all times on the SL MK3 knobs. (Being able to use the knobs of the SL MK3 for controlling Cutoff/Resonance, whatever it may be at all times, even when Bitwigs Browser gets opened)
I built a Looper for Bitwig!
https://www.youtube.com/watch?v=-z5ywDo2bU0
-
- KVRer
- 3 posts since 2 Aug, 2024
Hi,
Thanks for this I just installed the latest version 24 on bitwig 5.1.9, I'm trying to configure my Faderfox UC4 so that whatever parameter I last clicked on via the mouse it will automatically be assigned to the Midi encoder on the UC4, is this possible? sorry if newb question, just starting to get my head around this.
Thanks again, appreciate any help.
Thanks for this I just installed the latest version 24 on bitwig 5.1.9, I'm trying to configure my Faderfox UC4 so that whatever parameter I last clicked on via the mouse it will automatically be assigned to the Midi encoder on the UC4, is this possible? sorry if newb question, just starting to get my head around this.
Thanks again, appreciate any help.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
I doesn't work like this. Watch the video about the Faderfox:audioalienz wrote: Fri Aug 02, 2024 9:12 am Hi,
Thanks for this I just installed the latest version 24 on bitwig 5.1.9, I'm trying to configure my Faderfox UC4 so that whatever parameter I last clicked on via the mouse it will automatically be assigned to the Midi encoder on the UC4, is this possible? sorry if newb question, just starting to get my head around this.
Thanks again, appreciate any help.
And watch these 2 videos to get a basic understand of Bitwig Remote Parameters:
-
- KVRian
- 784 posts since 29 Mar, 2016
Hi trying to use this program and the akai fire script fails. the incoming midi is feeding the next track with modified midi channel notes using a channel filter out and a channel filter in on the second track. I then have to turn monitor mode to ON on the first track and play in using the akai fire so I can record the received notes on the second.
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- 2 posts since 21 May, 2018
Hi,
Would it be possible to set the faders to return to their initial values via a double tap on the Electra One buttons? This would be a nice feature development on this controller.
Would it be possible to set the faders to return to their initial values via a double tap on the Electra One buttons? This would be a nice feature development on this controller.
-
- KVRer
- 3 posts since 2 Aug, 2024
moss wrote: Fri Aug 02, 2024 9:31 amI doesn't work like this. Watch the video about the Faderfox:audioalienz wrote: Fri Aug 02, 2024 9:12 am Hi,
Thanks for this I just installed the latest version 24 on bitwig 5.1.9, I'm trying to configure my Faderfox UC4 so that whatever parameter I last clicked on via the mouse it will automatically be assigned to the Midi encoder on the UC4, is this possible? sorry if newb question, just starting to get my head around this.
Thanks again, appreciate any help.
And watch these 2 videos to get a basic understand of Bitwig Remote Parameters:
Hey Moss!
Alrighty, Thanks a bunch, I'll study these!
Take Care,
-
- KVRian
- 784 posts since 29 Mar, 2016
ok please disregard my midi controller issue above. it is the usb hub failing which is causing me a lot of problems these days
Last edited by xtreme sounds on Thu Aug 15, 2024 12:00 pm, edited 2 times in total.
