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

[moss]

I am entirely new to the DAW world. I have a Linux machine (Ubuntu) running a trial installation of Bitwig. I have purchased the Mackie Big Knob Studio package and am trying to get it to work with Bitwig before I decide whether to drop the money on a full license.
I have installed all packages offered by Bitwig using their default source. I have installed the DrivenByMoss extension, and I am able to see the additional controllers after installing the extension. Bitwig has never indicated that it recognized any controller was connected. I have tried manually adding all of the Mackie and Generic controllers, and none of them give me any options in the input or output menus other than "none".
The Mackie is plugged in via USB and working fine as an output device for the machine, meaning music played on the computer can be heard across the speakers connected to the Mackie interface.
I have tried rebooting everything multiple times.
I think that covers everything. I welcome any help or advice, and apologize in advance for my admitted ignorance on the entire topic of DAW software and digital interfaces in general.
Thank you!

The Mackie big knob is an audio interface not a controller. It is not a MIDI interface, so you will not see any MIDI in-/outputs.

[orenmi]

I am trying to create a kind of hardware synth from a controller and a VST.
So I use Akai midimix and Fabfilter One synth (because its mostly one page of knobs).
I would like to save the midi knobs to the default vst template.
So each time I open a track with FF One, the midimix will control all its parameters.

I am using the flexi script for this, as I understood this cant be done directly in Bitwig. Each project I have to learn midi again.
First I set 2 pages of remote control to control 16 knobs.
then I use the flexi script to control the first page with the first 8 knobs.
Then I set one of the midimix buttons on the right to switch to the second page of controllers, and now the 8 knobs control the second page.

Is this the best I can do in this setup?
because what I really want to do is first 8 knobs to control the first page and 2nd row of knobs to control the second page. (or any other way to fix the control permanently to work with 16 or more knobs).
Is there an option to do that?

Also, is there a way to make the script light the button lights? (as they have a light inside)

WhatsApp Image 2022-12-25 at 11.02.08.jpeg

[moss]

I am trying to create a kind of hardware synth from a controller and a VST.
So I use Akai midimix and Fabfilter One synth (because its mostly one page of knobs).
I would like to save the midi knobs to the default vst template.
So each time I open a track with FF One, the midimix will control all its parameters.

I am using the flexi script for this, as I understood this cant be done directly in Bitwig. Each project I have to learn midi again.
First I set 2 pages of remote control to control 16 knobs.
then I use the flexi script to control the first page with the first 8 knobs.
Then I set one of the midimix buttons on the right to switch to the second page of controllers, and now the 8 knobs control the second page.

Is this the best I can do in this setup?
because what I really want to do is first 8 knobs to control the first page and 2nd row of knobs to control the second page. (or any other way to fix the control permanently to work with 16 or more knobs).
Is there an option to do that?

Also, is there a way to make the script light the button lights? (as they have a light inside)

WhatsApp Image 2022-12-25 at 11.02.08.jpeg

Yes, that is the best you can do with Remote Control Pages.
Lights do only work if the MIDI message is identical in both directions (see the manual for a more detailed explanation).

For this use case there are 2 better solutions:
1) Program your own script which uses the IDs of the parameters of this synth plugin (a bit of work)
2) Use the Bitwig MIDI mapping. To have this ready in each new project, store it in a project template. Disadvantage of this is that you can control only one instance of the synth plugin.

[orenmi]

got it, thank you!

[mevla]

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.

[jaytwoeight]

I just discovered the Slot feature & I'm really excited because I was thinking about writing a custom script to do something the Slot feature already does. But I am wondering if Slot > Launch Scene can be expanded to launch up to 128 scenes instead of only 8?

Here is my use case:
I am switching patterns in my Analog Rytm MK2 & sending a MIDI Program Change to Bitwig when I do that. I would like to be able to launch up to 128 scenes in Bitwig from the AR because I have 128 available patterns in the AR.

EDIT: I just realized the numbers are be based on banks not absolute numbers...

Is it possible to have an absolute mode (in addition to or instead of bank mode)?

[mushrouxm]

hi there! another question, hopefully a more basic one. i'm using drivenbymoss for the first time, & using the generic flexi script to squeeze as much functionality as i can out of my akai lpd8, but i cannot figure out how to get the drivenbymoss script to respect bitwig's takeover mode, specifically i need to use the catch mode as the knobs are absolute and will cause huge parameter jumps otherwise as i cycle thru different script modes for the knobs

if i set things up using bitwig's generic controller script the catch mode works, so i know it's something with the drivenbymoss script, but i can't figure out what setting to change to make this work

thank you for any help you can give and all the work & support you're doing with these scripts!

[mushrouxm]

ok i did a bit more poking around, i restarted and thought the issue was gone until it recurred, and it seems to happen only when jumping back and forth between different script modes (not takeover modes)

so everything will work as expected if i restart the script and stay in volume mode and just adjust track volumes, and then if i switch to device mode and start adjusting some macros it still works as expected, but then when i switch back to track mode that knob will start behaving as if it's in immediate mode

and the getting stuck in immediate mode is per-knob, so if you do "track mode, touch knob 1, device mode, touch knob 1, track mode, touch knob 1", then knob 1 will behave as immediate, but knobs 2-8 will still behave as catch (until you fiddle with them too much)

which is a shame because the whole point of catch mode is to be able to switch the knob functionality around like this but then it's what causes the bug! i tried an older verison of drivenbymoss (14.10) as well and it exhibits the exact same specific behavior so im guessing it's a subtle bug that's been hanging around for a while but i'm surprised no one else has run into it!

otherwise everything is working great so far (other than browser mode which i assume just doesn't make sense with absolute knobs)

edit: ok so it's not just to do with script modes, since they weren't working i tried to just use different programs on the akai as modes (so the knobs of program 1 are manually assigned to "set track volume", knobs on program 2 to "set device param" etc), which again works fine on script start but if i change program, push knob, change program back then it's back to immediate. but if i stop the script, move the knob, restart the script then it'll catch properly. i just really can't figure out how to get any kind of soft knob assignments working so i'm hoping it's just some obvious config i'm missing

edit2: well clearly i'm fixated, fiddled a bit more and thinking now that maybe it's a bitwig bug :/ i set up the generic controller script again, with different programs on the akai setting different ccs for the knobs. i change a device parameter with a knob, and catch or relative scaling are both working, then i change programs and reset the knob, change programs back to the original and it behaves as immediate again seems like bitwig's takeover setting is unable to understand any soft control behavior besides its own. any help still appreciated but might need to take this to the bitwig forums!

[Tj Shredder]

This is The Bitwig forum…; - )

[x.iso]

Thanks for the video. Was there a crash log?

To clarify: the issue appears when you change the "Right X" to "Note"?

Oh, I actually forgot to look for crash log, where is it located usually? I know where to find Bitwig studio log and engine log, but that's not a crash dump. it refers to creating one, but not sure where to look for it.

Issue happens after some time of using the controller script. All drop-down boxes in Bitwig stop working, as well as context menus. Just additionally to that, if I try remapping some controls while script is still running, it maps to some odd notes or CC's that shouldn't been sent by anything.

[SVRVDX]

Dear Moss! I already wrote to you on the forum about OSC. Constantly looking at Changes
DrivenByMoss. Very concerned about the lack of OSC updates. Is everything ok?
I build my preset with TouchOSC. It works on your OSC. It would be nice to share ideas and perhaps to ask for some features to be added. This is a video with my test preset. I tried to make it similar in control and visually as Bitwig. I would like to share an idea though I'm sure you have thought about it for other controllers.

I'm using config.json which adds a new item Copy Device ID to Clipboard to the context menu of devices and also to the context menu of handles devices Copy Parameter to Clipboard Could you add new addresses to OSC for all devices built into Bitwig based on this data? Using Polysynth /device/a9ffacb5-33e9-4fc7-8621-b1af31e410ef/F1FREQ as an example, it looks not good for OSC, device/polysynth/f1freq looks better. It would be great to manage the entire device not through remote controls, but on TouchOSC screen directly.
Hope you consider this idea!

[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.

[moss]

I just discovered the Slot feature & I'm really excited because I was thinking about writing a custom script to do something the Slot feature already does. But I am wondering if Slot > Launch Scene can be expanded to launch up to 128 scenes instead of only 8?

Here is my use case:
I am switching patterns in my Analog Rytm MK2 & sending a MIDI Program Change to Bitwig when I do that. I would like to be able to launch up to 128 scenes in Bitwig from the AR because I have 128 available patterns in the AR.

EDIT: I just realized the numbers are be based on banks not absolute numbers...

Is it possible to have an absolute mode (in addition to or instead of bank mode)?

You could write your own script with a page size of 128 (or larger). But with Generic Flexi the number needs to be limited otherwise the number of functions would explode.

[moss]

edit2: well clearly i'm fixated, fiddled a bit more and thinking now that maybe it's a bitwig bug :/ i set up the generic controller script again, with different programs on the akai setting different ccs for the knobs. i change a device parameter with a knob, and catch or relative scaling are both working, then i change programs and reset the knob, change programs back to the original and it behaves as immediate again seems like bitwig's takeover setting is unable to understand any soft control behavior besides its own. any help still appreciated but might need to take this to the bitwig forums!

I am not sure if I followed everything you did but if I understand correctly you have a keyboard controller with a soft takeover in hardware? I guess this will simply not work since Bitwig is not aware of these values stored on the hardware device.

[moss]

Thanks for the video. Was there a crash log?

To clarify: the issue appears when you change the "Right X" to "Note"?

Oh, I actually forgot to look for crash log, where is it located usually? I know where to find Bitwig studio log and engine log, but that's not a crash dump. it refers to creating one, but not sure where to look for it.

Issue happens after some time of using the controller script. All drop-down boxes in Bitwig stop working, as well as context menus. Just additionally to that, if I try remapping some controls while script is still running, it maps to some odd notes or CC's that shouldn't been sent by anything.

In the same folder there are 2 sub-folders "engine-crash-report" and "queued-crash-reports" but they only appear if a crash happened and I think they get cleared when you choose to send the report or not.