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

[gExpectations]

As I failed to find the answer myself, I hope you dont mind another question: If I have a controller with a display, when do I get parameter names displayed? Is sending of parameter names and values a function of specific scripting, a feature of MCU/HUI or would I also get these names, when I use generic flexi? Also, under which condition do I get LED color information sent from Bitwig?

I finally figured out what controller would be best for my workflow and it would probably be the ATOM SQ. I'm just wondering if I can get use out of the screen. Else I probably will just get a small footprint 8 encoder + transport section controller like the X-touch mini.

[moss]

I have a miniscule feedback point considering your Midi Monitor event naming: it displays CC 0 as "CC Bank Change" (conventionally used as MSB part of bank change message) and CC 32 as "CC 32" (conventionally used as LSB part of bank change message).

Not that it really matters but I thought Id mention it, as it confused me as I was trying to understand how to change presets with my keyboard and I thought something is broken. Now at least, I know how a MIDI Message is structured and how MSB/LSB messages work .

You are aboslutely right! My list of CC names is pretty bad, not sure where I copied this from.
Will improve it in the next update!

[moss]

As I failed to find the answer myself, I hope you dont mind another question: If I have a controller with a display, when do I get parameter names displayed? Is sending of parameter names and values a function of specific scripting, a feature of MCU/HUI or would I also get these names, when I use generic flexi? Also, under which condition do I get LED color information sent from Bitwig?

I finally figured out what controller would be best for my workflow and it would probably be the ATOM SQ. I'm just wondering if I can get use out of the screen. Else I probably will just get a small footprint 8 encoder + transport section controller like the X-touch mini.

Displays are difficult. Nearly all controllers which have programmable displays are directly supported by DrivenByMoss.
With Generic Flexi the LEDs are only lit if they work with the same command they are sending when used. If a controller reflects these values on its' display this will work too.

[trostiflex]

Hello,
Quick question : is it possible with the Push 2 and Bitwig to do some kind of step automation ? When I press a step I see that I can adjust velocity, gain, etc... per step but I'm not able to tweak a parameter of my Vst per step. Am I missing something here or is it only possible with Ableton ?
Thanks !

[moss]

Hello,
Quick question : is it possible with the Push 2 and Bitwig to do some kind of step automation ? When I press a step I see that I can adjust velocity, gain, etc... per step but I'm not able to tweak a parameter of my Vst per step. Am I missing something here or is it only possible with Ableton ?
Thanks !

No, the Bitwig API currently has no support to implement this.

[lijsterbes]

Hi, not sure what is going on using a drum machine In Bitwig and using the Push2 ; it seems that all is working fine till 16 slots. As soon as I want to fill a second set of 16 slots in that same drum machine, things like giving each pad a different color is no longer working. Not to mention the Push 2 is not following the drum machine any more as soon as I use octave up/down on the Push. Navigating gets confusing and not 'in sync' anymore. Known issue? Any thoughts?

Thanks.

[moss]

Hi, not sure what is going on using a drum machine In Bitwig and using the Push2 ; it seems that all is working fine till 16 slots. As soon as I want to fill a second set of 16 slots in that same drum machine, things like giving each pad a different color is no longer working. Not to mention the Push 2 is not following the drum machine any more as soon as I use octave up/down on the Push. Navigating gets confusing and not 'in sync' anymore. Known issue? Any thoughts?

Thanks.

There is one long-standing bug: if you used the browser to set the content of a pad. After that everything freaks out. Selecting another track and back fixes this.
Is this your issue?

[lijsterbes]

Ok, step by step. Trying to guide what goes wrong. As soon as I start filling the 2nd 16 drum pads with sounds on my Push2 (which is in layout mode for 64 pads) the 'select' + pad does not show the option to give a color to the pad, none of the options as a matter of fact, the push screen is empty : when pressing 'select' on the Push, the screen on the Push keeps saying 'Please select a layer', while I already added a sound to the pads. That's the first I thing I'm bumping into. Whether or not sounds are added through the 'browser' in Bitwig, not sure yet if this makes a difference. Does it?

Edit: Turns out my Push2 does not allow me to control a drum machine as soon as I load a sound on any pad E2 or higher. In short: I can only control the first 16 pads. The pads above I need to adjust (color, mute, solo) from BW itself using the mouse etc. I can play all the pads thats the good news, just not 'select' them for further control from the Push2. Is this a known issue or is it my system / configuration?

[Prefader]

Greetings all,
I'm trying to build a TouchOSC layout that lets me jump around in my setlist. What I've done is to create a single project with all of my songs in it as scenes. I'd like to be able to select a scene and have it ready to launch from another controller. I see that the extension can send a "/scene/x/selected" message, but there doesn't appear to be a way to receive a "scene select" message. Am I overlooking something?

Edit: I think I've misunderstood how Bitwig treats selected scenes. It appears that what I'm asking for wouldn't actually work for what I'm trying to do. It looks like what I need to do is queue all clips within a scene, then simply start the transport rolling.

[moss]

Greetings all,
I'm trying to build a TouchOSC layout that lets me jump around in my setlist. What I've done is to create a single project with all of my songs in it as scenes. I'd like to be able to select a scene and have it ready to launch from another controller. I see that the extension can send a "/scene/x/selected" message, but there doesn't appear to be a way to receive a "scene select" message. Am I overlooking something?

Edit: I think I've misunderstood how Bitwig treats selected scenes. It appears that what I'm asking for wouldn't actually work for what I'm trying to do. It looks like what I need to do is queue all clips within a scene, then simply start the transport rolling.

The scene state is a bit fake since the intention of a scene is only for starting the clips in that row. What I did in a setup, was to put empty scenes in front of the "song scene" to setup some sounds.

[Prefader]

Got it! I could use empty scenes between "songs" and the "Launch next/previous scene" actions to get this working the way I want.

Thanks!

[killmaster]

Hi moss, Not sure if you want comments on much older devices, but this functionality on the Komplete Kontrol S61 Mk1 does not work for me here:

• SHIFT+PLAY - Create new clip, start playback and activate overdub

I just went over every function and all the rest seem to work fine except for this one thing!

Bitwig 4.2 Beta 1
DrivenByMoss 15.5.0

Thanks so much!

Greg

[smoldesu]

Not sure if this one has been solved/reported yet, but using Push 1 on Bitwig 4 exhibits some strange behavior. Transport controls and pads are extremely laggy and unreliable, most of the buttons seem to be non-functional, and the rotary encoders don't appear to change anything on the display or the DAW. I tried the "New Template" trick that others had suggested and it didn't appear to fix it.

I'm fairly sure it's not a hardware issue (opened the Push up and cleaned it inside-and-out, same behavior) and I'm using Arch Linux if that means anything.

Thanks in advance to the community for being so helpful, and to Moss for making such an incredible piece of software!

[killmaster]

Hi moss, Not sure if you want comments on much older devices, but this functionality on the Komplete Kontrol S61 Mk1 does not work for me here:

• SHIFT+PLAY - Create new clip, start playback and activate overdub

I just went over every function and all the rest seem to work fine except for this one thing!

Bitwig 4.2 Beta 1
DrivenByMoss 15.5.0

Thanks so much!

Greg

O, noticed one more small thing FWIW. SHIFT+ARP turns on the metronome and the arp when using Komplete Kontrol.

[moss]

Ok, step by step. Trying to guide what goes wrong. As soon as I start filling the 2nd 16 drum pads with sounds on my Push2 (which is in layout mode for 64 pads) the 'select' + pad does not show the option to give a color to the pad, none of the options as a matter of fact, the push screen is empty : when pressing 'select' on the Push, the screen on the Push keeps saying 'Please select a layer', while I already added a sound to the pads. That's the first I thing I'm bumping into. Whether or not sounds are added through the 'browser' in Bitwig, not sure yet if this makes a difference. Does it?

Edit: Turns out my Push2 does not allow me to control a drum machine as soon as I load a sound on any pad E2 or higher. In short: I can only control the first 16 pads. The pads above I need to adjust (color, mute, solo) from BW itself using the mouse etc. I can play all the pads thats the good news, just not 'select' them for further control from the Push2. Is this a known issue or is it my system / configuration?

Ah, now I see. Good catch! Seems the select screen needs to use different banks. Let's see how I can fix this...