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

[wvshpr]

Bitwig 5.03 DBM 20.3.2 - Push 1

Project Remotes - Navigating through multiple pages on the push1

Cannot navigate between pages smoothly, presses are ignored and will suddenly jump to the end page/ first page, skip multiple pages etc...

Thanks

Same here. I don't think this ever worked as intended for me. Track Remotes are also not shown at all most of the time and if they do, changes are not shown on the display.

[guitarfrenzi]

Maybe pile on to Ticket 174664 with your experience.

[moss]

Maybe pile on to Ticket 174664 with your experience.

If someone can give some reproducable steps, this would be very helpful!

[wvshpr]

Maybe pile on to Ticket 174664 with your experience.

If someone can give some reproducable steps, this would be very helpful!

To be clear, I'm not sure if it's the script, Push 2 or Bitwig. Your script usually works flawlessly and it's mostly my own ignorance (not reading the manual) if I have a problem with it

I basically just select the "User" button on Push 2 and try to navigate throught the pages with the buttons below the display. The first button seems to always go to the very first page and the other 7 buttons seem to always go to the last one.

Track remotes are selected via the second button above the display and I usually never see the parameters. I have to click them with the mouse to have them pop up there.

[juozasg]

Hi, thank you for awesome scripts!

I'm using Bitwing 5.0.4 and having a problem that rectangle around focused scripts isn't showing up. I have used DrivenByMoss before and there was always a red rectangle around selected tracks or clips. In my controller options i've turned on "Paints a rectangle around focused clips..."

[moss]

Hi, thank you for awesome scripts!

I'm using Bitwing 5.0.4 and having a problem that rectangle around focused scripts isn't showing up. I have used DrivenByMoss before and there was always a red rectangle around selected tracks or clips. In my controller options i've turned on "Paints a rectangle around focused clips..."

Which device are you using?

[Pabloantxon]

Hello,
I think there might be a bug in the flexi controller script.
When you choose a button in your controller (for example CC 12) for "Project Remotes: Select Next Page" or "Project Remotes: Select Previous Page" and the button behaviour is to send value 127 when pushed and value 0 when released, every time you press and release the button you advance or move back two pages, one for value 127 and one for value 0.
This doesn't happen when mapping to other stuff, that's why I think it is a bug.
I've had to change the code of my controller so it doesn't send a 0 when these buttons are released, but I thought I should let you know anyway.
Cheers, and thanks for all your work Moss

[SVRVDX]

Hi Moss! What happeed to /user/ i osc? And I can't understand how /track/param/... and everything connected with it work. If I make a separate panel, for some reason it starts to control /project/param/...

[resonaural]

Hey Moss. Thanks for all the hard work you've put into this extension - can't imagine how long it has taken to get right.

I've upgraded to Bitwig 5.0.4 and I'm using an Allen & Heath Xone K2 (Generic Flexi) along with a Novation Launchpad X and Maschine MK3.
Maschine is controlling the VST in the project and the launchpad is being used as a clip launcher.

I have mapped different functions of the DAW to the K2 - using the Bitwig 'right-click menu > Map to controller or Key' and then pressing the button / moving the cc on the K2. Everything works fine, but I just can't seem to manage to get the buttons to light up.

I have RTFM, but I honestly don't know what I'm doing wrong. I haven't assigned any functions in the generic flexi settings as I want those to be mapped to specific devices / controls in my project.

If you could direct me in the right direction, that would be awesome.

Thanks in advance.

Cheers!

[moss]

Hello,
I think there might be a bug in the flexi controller script.
When you choose a button in your controller (for example CC 12) for "Project Remotes: Select Next Page" or "Project Remotes: Select Previous Page" and the button behaviour is to send value 127 when pushed and value 0 when released, every time you press and release the button you advance or move back two pages, one for value 127 and one for value 0.
This doesn't happen when mapping to other stuff, that's why I think it is a bug.
I've had to change the code of my controller so it doesn't send a 0 when these buttons are released, but I thought I should let you know anyway.
Cheers, and thanks for all your work Moss

Thanks for reporting, will be fixed in the next update!

[moss]

Hi Moss! What happeed to /user/ i osc? And I can't understand how /track/param/... and everything connected with it work. If I make a separate panel, for some reason it starts to control /project/param/...

Argh, stupid copy/paste error. Will be fixed in the next update!

[moss]

Hey Moss. Thanks for all the hard work you've put into this extension - can't imagine how long it has taken to get right.

I've upgraded to Bitwig 5.0.4 and I'm using an Allen & Heath Xone K2 (Generic Flexi) along with a Novation Launchpad X and Maschine MK3.
Maschine is controlling the VST in the project and the launchpad is being used as a clip launcher.

I have mapped different functions of the DAW to the K2 - using the Bitwig 'right-click menu > Map to controller or Key' and then pressing the button / moving the cc on the K2. Everything works fine, but I just can't seem to manage to get the buttons to light up.

I have RTFM, but I honestly don't know what I'm doing wrong. I haven't assigned any functions in the generic flexi settings as I want those to be mapped to specific devices / controls in my project.

If you could direct me in the right direction, that would be awesome.

Thanks in advance.

Cheers!

This does only work if your controller expects the exact same value for the LED as the one sent, which I guess not the case with yours.

[Skelmy]

There is absolutely no need to use Automap with Bitwig. Everything that Automap does can be done directly in Bitwig.

Yes maybe so, but sitting down and mapping out every plugin and instrument as a Bitwig map that I can only use in Bitwig would take months on end, and the point of Automap is you can use the maps in any DAW, I have so many I have saved and rearranged as far back as I've had the ZeRo SL MK 2 at that's a lot, on a new install I just load up my maps as I'm going and set them as default and very on, now I can't with Bitwig which is such a shame.

Because of this situation I looked at the MPMIDI Model 2A, as that works with it's own plugin wrapper, but it's €780 and I just don't have that to spend on replacing a controller at the moment.

Making devices mappings is easy and doesn't cost that much time. There is a device panel thread here at KVR.
I don't know the total amount of panels, but i alone uploaded at least 120 panels.

I used to use automap too, with a zero sl. But automap has'nt been supported for years. With automap you have to load the wrapped vst, with device panels the panel gets loaded automatically with the plugin.

One of the reasons i went to bitwig is the combination of push 2 and device panels, i think it's better than zero sl with automap. Better than Live because you can rearange them on the pages you choose. A used push 2 is not that expensive anymore.

What i like most with push is that you see the pot names, values and panel pages in the display and can select them in banks of eight with a dedicated switch for each page. On 2 big displays. Makes it work like a well designed hardware synth.
Generic flexi can make any controller do advanced stuff. The sl should work too.

But if you really want to work with plugin wrappers you should also look at Nektar controllers.

The device panel thread is here:
viewtopic.php?t=480998
dropbox of aMUSEd, who started the thread and contributed lots of panels:
https://www.dropbox.com/sh/ie17173tybqd ... tzeUa?dl=0
my vst3 device panels:
https://1drv.ms/u/s!At4GWiADXlnHgeRw8iR ... g?e=rW9jgf

OK so that's going to take me months, as I like my lay outs custom for me so even using your lay outs I would have to change them, which is what I have done with Automap, as I said I use a lot of plugins, so I have custom maps for Automap that I just load into it for every plugin I use.
Thing is you say it's not supported, but it works fine, and works with Reason 10 and Cubase 10, no issues?
Works with every version of Bitwig 4, no issues, so that is what I was saying. If we were to take this stance of unsupported devices half the devices out there would no longer work, and that is the point is to give support to niece devices.
But I see I am going to have to just give in and spend months doing my own lay outs, which I really didn't want to have to do.

[drsyncenstein]

Not supported by Novation. Freely translated; if a windows or mac update breaks it, you are on your own. Novation won't fix it. I've apps running that are decades old, that's fine as long as you don't rely on them.

[juozasg]

Hi, thank you for awesome scripts!

I'm using Bitwing 5.0.4 and having a problem that rectangle around focused scripts isn't showing up. I have used DrivenByMoss before and there was always a red rectangle around selected tracks or clips. In my controller options i've turned on "Paints a rectangle around focused clips..."

Which device are you using?

Arturia Beatstep. All other features seem to be working