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

[SVRVDX]

Hey. A quick question - is it possible to use a pair of Push 2s with this Bitwig Extension? Thanks

Are you me?

[moss]

- I cannot get my controller's endless encoders to work for scrolling the columns in the pop-up browser. They work perfectly (set to Offset Binary in the options) for the other modes like Volume and Parameter control, but when the popup Browser is open, turning them only scrolls down, never up. (Controller is a Behringer X-Touch Mini.) Is there anything I can/need to configure to make them work as intended?

I noticed that the scroll filter functions crash. But since you did not experience this crash I guess you did select the wrong function. You need "scroll filter" not "select next".

Thanks for answering, much appreciated!

Unfortunately I must be missing something obvious here, sorry ... how can I select "Scroll filter" in Flexi's UI? I use my encoders in parameter mode and have them set to "Set Param n". Then when I open the popup browser, they behave incorrectly. Somehow I was hoping the script would miraculously recognize that the popup browser is open and make the encoders do the right thing ...

Ah, sorry, seems I misread your first post. This revealed another bug
Will be fixed too in the next update (soonish)!

[moss]

I have been trying to map the track output selection for the crossfader (A/B) using Flexi or even bitwig's shortcuts but I can't seem to nail this, can someone please point out if this is even possible without using the standard bitwig's midi mapping option? I see the APC40 script is able to do this, so I'm assuming I may be missing something

Nobody asked for that, so far. I can add it to the wishlist. But mapping in Bitwig works fine.

Also on Flexi, was wondering how to assign user controls to the available user parameters? I'm able to map the controller to a user parameter on flexi, but it does nothing, I'm thinking there should be another action to take, like letting bitwig know what user parameter 1 for example should do.

Click on any parameter in Bitwig with the right mouse button and select MIDI Learn. Then move/press the knob/fader/button to which you assigned "User: Set Parameter N". Works for the A|B selection as well (just tested it).

[moss]

Hello Moss! Its me again. )) I built the bitwig browser ... for TouchOSC and this is what I found! From the documentation, for example, "/browser/filter/{1-6}/item/{1-16}/name" turns out {1-7} is a device type, but "/browser/filter/7/{+-}" does not switch them. And I would also like "/browser/filter/{1-16}/{+,-}" => "/browser/filter/{1-16}/selected" and "/browser/result/{+,-}" => "/browser/result/{1-16}/selected" as with tracks.

Nice! Just take a look at the Open Stage Control template that comes with DrivenByMoss. It contains a similar browser.

[moss]

Hi, is it possible to easily switch between Bitwig and Ableton Live using Push2?

If you mean running both in parallel. No.

Thanks for letting me know. Would it be possible to use two Push2? One for Live, one for Bitwig at the same time? I want to use Ableton Live for its sampling workflow and Bitwig for everything else.

Your script makes it the best controller for Bitwig, but it's also the best controller for Ableton Live – hence the idea of using two of them

I cannot tell since I have only 1 Push 2.

[moss]

Moss it seems I found a bug with /browser/result/{+,-} cursor in the bitwig browser does not reach the end and is reset somewhere above here is the video

I tested with Open Stage Control but cannot reproduce that.

[moss]

For the Launchpad mini mk3, would it be possible to, whenever a background of white pads are mostly filling the space, to not have them so bright ? Like for instance in the Play Scale mode. When used in dim lighting they come across way too bright.

I am not aware of any option to dim the pads.

Or maybe instead have them of colour grey.

Good news. It is actually possible on the "X" and "Mini Mk3". Will be added to the next update.

[moss]

DrivenByMoss 19.0.0 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 4.3+
• Added support for Electra One controller.
• Generic Flexi
  • Fixed: Browser - Scroll Filter Column did crash.
  • Fixed: Browser - Scrolling in browser mode did always scroll down.
  • Fixed: Last selected mode was not set after restart.
• Launchpad
  • New: Set the default for Shift+Record to 'New clip + enable automation'.
  • New: Added a brightness setting for the pads. Only available on Mini Mk3 and X.
  • Fixed: New record command configuration was broken on non-pro models.
• MIDI Monitor
  • New: Added number of bytes to system exclusive message logs.

Enjoy!

[Insearch]

Nobody asked for that, so far. I can add it to the wishlist. But mapping in Bitwig works fine.

That would be great! would really appreciate that as it would be really nice to have it as part of a script

Click on any parameter in Bitwig with the right mouse button and select MIDI Learn. Then move/press the knob/fader/button to which you assigned "User: Set Parameter N". Works for the A|B selection as well (just tested it).

This action does not appear save the MIDI learn assignment to the mapping on Flexi, also i could still assign a control using MIDI map without having to set a user parameter on Flexi. would it be possible to have flexi store the manual mapping to the script? Or to be able to define a custom user parameter on Flexi & have it stored in the controller script? Not sure if this is possible, but would be a great option to have

Thanks,

[moss]

This action does not appear save the MIDI learn assignment to the mapping on Flexi, also i could still assign a control using MIDI map without having to set a user parameter on Flexi. would it be possible to have flexi store the manual mapping to the script? Or to be able to define a custom user parameter on Flexi & have it stored in the controller script? Not sure if this is possible, but would be a great option to have

You can store them in a Bitwig template.

[dynup]

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 19.0.0 is online!

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

Hello Jürgen,

the zip file still contains the old DrivenByMoss-Manual.pdf for v1.8.5 (date from December 19, 2022) ... seems to be a mistake?

BIG thanks for your tireless work on the (open source!) scripts!

[Insearch]

You can store them in a Bitwig template.

I'm aware that this is an option, but will loose all the goodies of having a script, like parameter recognition when switching tracks, clips etc. i.e. this means that I need to have more knobs & buttons to spare which is something I'm trying to avoid really..

[moss]

DrivenByMoss 19.0.0 is online!

Get it from https://mossgrabers.de

Hello Jürgen,

the zip file still contains the old DrivenByMoss-Manual.pdf for v1.8.5 (date from December 19, 2022) ... seems to be a mistake?

BIG thanks for your tireless work on the (open source!) scripts!

Thanks for letting me know! It seems there was something broken in my build pipeline.

Everybody, please download again since also the extension file might not have been fully up to date!

[mevla]

Or maybe instead have them of colour grey.

Good news. It is actually possible on the "X" and "Mini Mk3". Will be added to the next update.

Super cool ! Very nice.

Cheers.

[CereberalDonkey]

Hello,

I don't know if this has been covered, or I cannot find it, but is there a "take over" option for midi potentiometers in the Flexi mode? I want to map some of the knobs on my controller to the device pannel and cycle between devices, but I don't want to loose the settings until the knob has caught up to where the parameter was set once I select a device. Is this possible?

Thank you.