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

[kulacki]

Sadly the answer to both is yes, double checked now - Electra is 3.50 (just sent by Martin to solve encoder issues, didn't try 3.40 as encoders don't work at all with it in my device) and DrivenByMoss 21.20.

[moss]

Sadly the answer to both is yes, double checked now - Electra is 3.50 (just sent by Martin to solve encoder issues, didn't try 3.40 as encoders don't work at all with it in my device) and DrivenByMoss 21.20.

Ah, 3.50 I see. Seems there has been something changed. The problem is that it is currently in a beta state and the relative knobs (for which I have a prototype) are not yet ported to the MkI.
I am afraid we have to wait a bit till the dust settles...

[moss]

DrivenByMoss 21.3 is online!

Get it from https://mossgrabers.de

• All devices
  • Fixed: New clips could only be created on 1st page (slot 1-8).
• Auto Color
  • Fixed: Did crash on startup.
• Fire
  • Fixed: Do not toggle the plugin window when the select knob is pressed and turned to transpose the clip by octaves.
• Generic Flexi
  • New / Fixed: Added new relative knob mode 'Signed Bit 2'. The previously called knob mode 'Signed Bit' is actually the new 'Signed Bit 2'. IMPORTANT: This is a breaking change, so check all selected relative modes in your configurations!
  • Fixed: Selecting Send modes 1-8 from the configuration menu did not activate them.
• Kontrol Mk2
  • Fixed: More stable clip/scene/track navigation with 4D knob.
• Maschine:
  • New: When switching tracks the previous selected play mode (PAD MODE or KEYBOARD) is recalled.
• MCU
  • Fixed: Removed the no longer working browser filter settings.
• Push
  • New: Push 2/3: Clip and session modes contain now track names. The mixer layout is changed accordingly for consistency. Reset the colors in the Push settings!
  • Fixed: Adapted note pitch transpose to new Bitwig 5 range of -96 to 96 semi-tones (was -24 to 24).
  • Fixed: Accent parameter in clip mode could not be set.
  • Fixed: Removed the no longer working browser filter settings.
  • Fixed: More stable clip/scene/track navigation with large encoder.

Enjoy!

[kulacki]

I've downgraded to 3.4 and so far so good, the encoders calibration procedure is done with 3.5 and then 3.4 works with DrivenByMoss 21.2. But I think the issue will come back as other users are slowly getting this newer firmware. Anyway, thank you Moss very much, you've prompted me to investigate firmware versions and I have a stable setup for the moment!

BTW is there a way to disable somehow Position Encoder? I am messing with it while adjusting master volume. And another one, is it possible to control both Bitwig and Reaper with your scripts at the same time? My setup is just like this, and that could be handy.

Thank you, this is a fantastic controller script!

[canofolives]

hi moss,

sorry to bug you! new to bitwig and wanted to get auto-coloring working and seemed to hit a snag. tried all sorts of troubleshooting, referencing the bitwig manual, as well as yours and couldn't figure out how to fix this issue. when i add the Utility -> Auto Color, i instantly get the following notification:

Auto Color did something wrong
No scenes were specified for this track bank
[Disable] [Restart]

i am unsure how to specify scenes for the track bank (likely due to my newness to bitwig). i got the exception from the console as well, if that helps:

```
Called init()
No scenes were specified for this track bank
BmC: No scenes were specified for this track bank
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:317)
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:22)
at de.mossgrabers.bitwig.framework.daw.ModelImpl.<init>(ModelImpl.java:126)
at de.mossgrabers.bitwig.framework.BitwigSetupFactory.createModel(BitwigSetupFactory.java:55)
at de.mossgrabers.controller.utilities.autocolor.AutoColorSetup.createModel(AutoColorSetup.java:93)
at de.mossgrabers.framework.controller.AbstractControllerSetup.init(AbstractControllerSetup.java:136)
at de.mossgrabers.bitwig.framework.extension.GenericControllerExtension.init(GenericControllerExtension.java:42)
at KyO.EPm(SourceFile:24)
at xPj.Lrw(SourceFile:60)
at KuG.HRr(SourceFile:298)
at KuG.HRr(SourceFile:211)
at KuG.<init>(SourceFile:168)
at Ze1.HRr(SourceFile:327)
at Ze1.SSi(SourceFile:470)
at Ze1.HRr(SourceFile:283)
at vaN.run(SourceFile:91)
at Ze1.run(SourceFile:191)
```

bitwig version: 5.0.9
extension api version: 18
moss extension version: 21.2.0

thanks for your help!!

Thanks for reporting! Will be fixed in the next update!

Awesome thank you!

[joshuahardee]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

DrivenByMoss 21.3 is online!

Get it from https://mossgrabers.de (https://mossgrabers.de)

• All devices
  • Fixed: New clips could only be created on 1st page (slot 1-8).
• Auto Color
  • Fixed: Did crash on startup.
• Fire
  • Fixed: Do not toggle the plugin window when the select knob is pressed and turned to transpose the clip by octaves.
• Generic Flexi
  • New / Fixed: Added new relative knob mode 'Signed Bit 2'. The previously called knob mode 'Signed Bit' is actually the new 'Signed Bit 2'. IMPORTANT: This is a breaking change, so check all selected relative modes in your configurations!
  • Fixed: Selecting Send modes 1-8 from the configuration menu did not activate them.
• Kontrol Mk2
  • Fixed: More stable clip/scene/track navigation with 4D knob.
• Maschine:
  • New: When switching tracks the previous selected play mode (PAD MODE or KEYBOARD) is recalled.
• MCU
  • Fixed: Removed the no longer working browser filter settings.
• Push
  • New: Push 2/3: Clip and session modes contain now track names. The mixer layout is changed accordingly for consistency. Reset the colors in the Push settings!
  • Fixed: Adapted note pitch transpose to new Bitwig 5 range of -96 to 96 semi-tones (was -24 to 24).
  • Fixed: Accent parameter in clip mode could not be set.
  • Fixed: Removed the no longer working browser filter settings.
  • Fixed: More stable clip/scene/track navigation with large encoder.

Enjoy!

Hi Moss,

Just started using the script for Push 2, Bitwig 5.0.9 MacOS 13.6 and love it. Thank you soo much for the amazing work you put into this script!

I am running into an issue with the track navigation (even with the new DBM 21.3.0). I use a lot of groups/folders in my template and I seem to have a lot of issues selecting the groups/tracks, entering into group/track, and then selecting chains in the track.

I am usually able to navigate the default selected group (1st button) or track to get to chains and effects, but when trying to select tracks next to the default (buttons 2-8), it acts like I am long-pressing the track selection button and goes up a level on a group/folder. This happens at random, but is more likely not to work correctly and interpret a long press vs a short press.

It's almost like the short press is not registering at all when trying to select different tracks or groups on buttons 2-8.

Would there be a way to add a setting to change the length in ms of a short press and long press?

Any thoughts or ideas on this behavior? Let me know if you need more detailed info.

[joshuahardee]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

DrivenByMoss 21.3 is online!

Get it from https://mossgrabers.de (https://mossgrabers.de)

• All devices
  • Fixed: New clips could only be created on 1st page (slot 1-8).
• Auto Color
  • Fixed: Did crash on startup.
• Fire
  • Fixed: Do not toggle the plugin window when the select knob is pressed and turned to transpose the clip by octaves.
• Generic Flexi
  • New / Fixed: Added new relative knob mode 'Signed Bit 2'. The previously called knob mode 'Signed Bit' is actually the new 'Signed Bit 2'. IMPORTANT: This is a breaking change, so check all selected relative modes in your configurations!
  • Fixed: Selecting Send modes 1-8 from the configuration menu did not activate them.
• Kontrol Mk2
  • Fixed: More stable clip/scene/track navigation with 4D knob.
• Maschine:
  • New: When switching tracks the previous selected play mode (PAD MODE or KEYBOARD) is recalled.
• MCU
  • Fixed: Removed the no longer working browser filter settings.
• Push
  • New: Push 2/3: Clip and session modes contain now track names. The mixer layout is changed accordingly for consistency. Reset the colors in the Push settings!
  • Fixed: Adapted note pitch transpose to new Bitwig 5 range of -96 to 96 semi-tones (was -24 to 24).
  • Fixed: Accent parameter in clip mode could not be set.
  • Fixed: Removed the no longer working browser filter settings.
  • Fixed: More stable clip/scene/track navigation with large encoder.

Enjoy!

Hi Moss,

Just started using the script for Push 2, Bitwig 5.0.9 MacOS 13.6 and love it. Thank you soo much for the amazing work you put into this script!

I am running into an issue with the track navigation (even with the new DBM 21.3.0). I use a lot of groups/folders in my template and I seem to have a lot of issues selecting the groups/tracks, entering into group/track, and then selecting chains in the track.

I am usually able to navigate the default selected group (1st button) or track to get to chains and effects, but when trying to select tracks next to the default (buttons 2-8), it acts like I am long-pressing the track selection button and goes up a level on a group/folder. This happens at random, but is more likely not to work correctly and interpret a long press vs a short press.

It's almost like the short press is not registering at all when trying to select different tracks or groups on buttons 2-8.

Would there be a way to add a setting to change the length in ms of a short press and long press?

Any thoughts or ideas on this behavior? Let me know if you need more detailed info.

Well, looks like this may have been a user/template issue. I have tried different templates and projects and everything appears to be working as it should. Not sure what was up with my project template that was causing these navigation issues but it appears to be on my side...

Appreciate ya!

[joshuahardee]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

DrivenByMoss 21.3 is online!

Get it from https://mossgrabers.de (https://mossgrabers.de)

• All devices
  • Fixed: New clips could only be created on 1st page (slot 1-8).
• Auto Color
  • Fixed: Did crash on startup.
• Fire
  • Fixed: Do not toggle the plugin window when the select knob is pressed and turned to transpose the clip by octaves.
• Generic Flexi
  • New / Fixed: Added new relative knob mode 'Signed Bit 2'. The previously called knob mode 'Signed Bit' is actually the new 'Signed Bit 2'. IMPORTANT: This is a breaking change, so check all selected relative modes in your configurations!
  • Fixed: Selecting Send modes 1-8 from the configuration menu did not activate them.
• Kontrol Mk2
  • Fixed: More stable clip/scene/track navigation with 4D knob.
• Maschine:
  • New: When switching tracks the previous selected play mode (PAD MODE or KEYBOARD) is recalled.
• MCU
  • Fixed: Removed the no longer working browser filter settings.
• Push
  • New: Push 2/3: Clip and session modes contain now track names. The mixer layout is changed accordingly for consistency. Reset the colors in the Push settings!
  • Fixed: Adapted note pitch transpose to new Bitwig 5 range of -96 to 96 semi-tones (was -24 to 24).
  • Fixed: Accent parameter in clip mode could not be set.
  • Fixed: Removed the no longer working browser filter settings.
  • Fixed: More stable clip/scene/track navigation with large encoder.

Enjoy!

Hi Moss,

Just started using the script for Push 2, Bitwig 5.0.9 MacOS 13.6 and love it. Thank you soo much for the amazing work you put into this script!

I am running into an issue with the track navigation (even with the new DBM 21.3.0). I use a lot of groups/folders in my template and I seem to have a lot of issues selecting the groups/tracks, entering into group/track, and then selecting chains in the track.

I am usually able to navigate the default selected group (1st button) or track to get to chains and effects, but when trying to select tracks next to the default (buttons 2-8), it acts like I am long-pressing the track selection button and goes up a level on a group/folder. This happens at random, but is more likely not to work correctly and interpret a long press vs a short press.

It's almost like the short press is not registering at all when trying to select different tracks or groups on buttons 2-8.

Would there be a way to add a setting to change the length in ms of a short press and long press?

Any thoughts or ideas on this behavior? Let me know if you need more detailed info.

Well, looks like this may have been a user/template issue. I have tried different templates and projects and everything appears to be working as it should. Not sure what was up with my project template that was causing these navigation issues but it appears to be on my side...

Appreciate ya!

Well lol! I have been able to reproduce the issue now. The navigation issues appear to happen with nested groups.

Example:
Group 1/Group 2/Audio Track 1, Audio Track 2

Audio Track 1 and Audio Track 2 are inside Group 2 which is inside Group 1 at Top Project Level.

When at the project level, pressing on Group 1 enters and shows Group 2, Pressing on Group 2 enters and shows Audio Track 1 and Audio Track 2.

Pressing on Audio Track 1 selects it and allows to select Audio Track 1 chains etc.

Pressing on Audio Track 2 selects Audio Track 1 but does not select Audio Track 2.

At this point the bug will not allow me to select Audio Track 2 with Push 2.

If I do press the left or right buttons on the computer keyboard, it will navigate to Audio Track 2 and then I can use the Push 2 to navigate between Audio Track 1 and Audio Track 2 until I navigate back to Group1 (using Push 2).

Hopefully the steps above will help you reproduce the issue, let me know if you need any additional info and your thoughts.

Appreciate your time, help, and support!

[nowiamone]

DrivenByMoss 21.3 is online!

[*]Kontrol Mk2

• Fixed: More stable clip/scene/track navigation with 4D knob.

Enjoy!

Jürgen, without you, i would never have come to Bitwig, thanks alot

[lao974]

Hi, Push 3, Bitwig 5.0.4, DrivenByMoss 21.3.0: I cannot select the scale type in Push 3 scale menu, only the keys are available.

[moss]

I've downgraded to 3.4 and so far so good, the encoders calibration procedure is done with 3.5 and then 3.4 works with DrivenByMoss 21.2. But I think the issue will come back as other users are slowly getting this newer firmware. Anyway, thank you Moss very much, you've prompted me to investigate firmware versions and I have a stable setup for the moment!

Good to hear and I will for sure adapt to the new changes soon.

BTW is there a way to disable somehow Position Encoder? I am messing with it while adjusting master volume.

Sorry, no. Except, if you modify the knobs value from the template (or delete it completely).

And another one, is it possible to control both Bitwig and Reaper with your scripts at the same time? My setup is just like this, and that could be handy.

I don't thinkt that there is a way to do this (at least without huge effort).

[AuralBee]

Hi Moss,
Thanks for yet another cool update
Push3 question: would it be possible to have a mode where the big dial scrolls/presstriggers scenes ?

[Traxlayer]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

DrivenByMoss 21.3 is online!

Get it from https://mossgrabers.de (https://mossgrabers.de)

• All devices
  • Fixed: New clips could only be created on 1st page (slot 1-8).
• Auto Color
  • Fixed: Did crash on startup.
• Fire
  • Fixed: Do not toggle the plugin window when the select knob is pressed and turned to transpose the clip by octaves.
• Generic Flexi
  • New / Fixed: Added new relative knob mode 'Signed Bit 2'. The previously called knob mode 'Signed Bit' is actually the new 'Signed Bit 2'. IMPORTANT: This is a breaking change, so check all selected relative modes in your configurations!
  • Fixed: Selecting Send modes 1-8 from the configuration menu did not activate them.
• Kontrol Mk2
  • Fixed: More stable clip/scene/track navigation with 4D knob.
• Maschine:
  • New: When switching tracks the previous selected play mode (PAD MODE or KEYBOARD) is recalled.
• MCU
  • Fixed: Removed the no longer working browser filter settings.
• Push
  • New: Push 2/3: Clip and session modes contain now track names. The mixer layout is changed accordingly for consistency. Reset the colors in the Push settings!
  • Fixed: Adapted note pitch transpose to new Bitwig 5 range of -96 to 96 semi-tones (was -24 to 24).
  • Fixed: Accent parameter in clip mode could not be set.
  • Fixed: Removed the no longer working browser filter settings.
  • Fixed: More stable clip/scene/track navigation with large encoder.

Enjoy!

Hey Moss,

I am a new user of bitwig and your script, but I can't seem to get it working for my Push 2 device. The script is working for my Komplete Kontrol mk2, but with the Push 2 there are no options in the MIDI IN & MIDI OUT select dropdowns to choose the MIDI ports on the Push2 device per your instructions. The KK midi ports show in the dropdowns but not the push device ports.

Anyone have any ideas why the Push2 MIDI ports are not visible to Bitwig yet the KKmk2 ports are?

If anyone has any clues as to areas to investigate, I'm all ears.

Thanks!

[moss]

Hi Moss,

Just started using the script for Push 2, Bitwig 5.0.9 MacOS 13.6 and love it. Thank you soo much for the amazing work you put into this script!

I am running into an issue with the track navigation (even with the new DBM 21.3.0). I use a lot of groups/folders in my template and I seem to have a lot of issues selecting the groups/tracks, entering into group/track, and then selecting chains in the track.

I am usually able to navigate the default selected group (1st button) or track to get to chains and effects, but when trying to select tracks next to the default (buttons 2-8), it acts like I am long-pressing the track selection button and goes up a level on a group/folder. This happens at random, but is more likely not to work correctly and interpret a long press vs a short press.

It's almost like the short press is not registering at all when trying to select different tracks or groups on buttons 2-8.

Would there be a way to add a setting to change the length in ms of a short press and long press?

Any thoughts or ideas on this behavior? Let me know if you need more detailed info.

Well, looks like this may have been a user/template issue. I have tried different templates and projects and everything appears to be working as it should. Not sure what was up with my project template that was causing these navigation issues but it appears to be on my side...

Appreciate ya!

Well lol! I have been able to reproduce the issue now. The navigation issues appear to happen with nested groups.

Example:
Group 1/Group 2/Audio Track 1, Audio Track 2

Audio Track 1 and Audio Track 2 are inside Group 2 which is inside Group 1 at Top Project Level.

When at the project level, pressing on Group 1 enters and shows Group 2, Pressing on Group 2 enters and shows Audio Track 1 and Audio Track 2.

Pressing on Audio Track 1 selects it and allows to select Audio Track 1 chains etc.

Pressing on Audio Track 2 selects Audio Track 1 but does not select Audio Track 2.

At this point the bug will not allow me to select Audio Track 2 with Push 2.

If I do press the left or right buttons on the computer keyboard, it will navigate to Audio Track 2 and then I can use the Push 2 to navigate between Audio Track 1 and Audio Track 2 until I navigate back to Group1 (using Push 2).

Hopefully the steps above will help you reproduce the issue, let me know if you need any additional info and your thoughts.

Appreciate your time, help, and support!

I can reproduce it. Thanks!

Seems like Bitwig is somehow not clearing the selection state correctly. You can clearly see that if you create more tracks in Group 2, select e.g. the last one, then move up and enter the group again. Both tracks are selected while in the Bitwig UI only the 1st one is selected.

Will report it to Bitwig!

[moss]

Hi, Push 3, Bitwig 5.0.4, DrivenByMoss 21.3.0: I cannot select the scale type in Push 3 scale menu, only the keys are available.

Thanks for reporting! Seems black text on black background does not work that well