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

[moss]

Hi Moss
First of all I wanted to thank you for the enormous work you have done with the integration of the Akai Fire in Bitwig. Is awesome.

Now I wanted to ask if a couple of functions could be added to Shift mode.
Could you put two buttons to Duplicate Clip and duplicate content?
This is something that can greatly improve the workflow when we work on the Clip Launcher.

Thanks for all this great work.

Noted. But no promises

[moss]

Hello !
I have a request .
Would it be possible to make a "pseudo" gate function on the session pads ?
So that the clip play immediately (or depending the quantification) as long as i have my finger on a pad and stop immediately or depending on the quantification when i remove it ?
I really miss the gate function of Ableton ....
And we can activate it as an option (in the parameters of the push 2 ?)
Thanks for all Moss !
Have a good day !

That's an interesting idea but it would mean that I would need to remove the feature to select the clip by long pressing the pad. So I am afraid other people were quicker And no, I will not make this an option since the code area already contains many options and alternative which makes it easy to brake stuff.

[zengel]

Hello !
I have a request .
Would it be possible to make a "pseudo" gate function on the session pads ?
So that the clip play immediately (or depending the quantification) as long as i have my finger on a pad and stop immediately or depending on the quantification when i remove it ?
I really miss the gate function of Ableton ....
And we can activate it as an option (in the parameters of the push 2 ?)
Thanks for all Moss !
Have a good day !

That's an interesting idea but it would mean that I would need to remove the feature to select the clip by long pressing the pad. So I am afraid other people were quicker And no, I will not make this an option since the code area already contains many options and alternative which makes it easy to brake stuff.

ok but there is alreasy the "select" + the pad ? but why not .
there is another thing to : the clip launch on the release(the moment when we release the pad) of the pad and not on the "on" (the moment when we touch the pad) . then when it's not a quantified launch you have think to launch the clip when your finger live the the pad. you have to think on the release and not on the moment you touch the pad... hard to do
Whatever . Thanks for all moss !

[mattaudio]

Hello, i've found an issue when playing chords on bitwig.
Sometimes, some notes quickly light off after being triggered.
it's only visual because notes are correcly triggered but it can be annoying because seeing notes played on the layout are a great help when improvising for constructing harmony.

It happen with push 2 and with launchpad x (less often) but not in ableton or in bitwig when launchpad x is in its original mode.

here is a quick video showing the issue.


thanks for your awesome job on bitwig controllers.

[Wavethings]

Noted. But no promises

Thanks

[xtreme sounds]

Hi there. Heres a request for the fire, but not sure if it can be done. Is there a way to lock the displayed pattern to a specific track so that selecting another track with the mouse that is not receiving midi from the fire will not altar the note display as it is locked to a specific track already? I was playing with 2 controllers - the fire and my keyboard and when I clicked the other track under keyboard control the fire changed displayed notes even though that track is not receiving from the fire.

[maschinelf]

The features that (all of) the Kontrol Keyboards provide are very limited. On the Mk2 I did the trick via the Delete button but on the smaller devices (A-series, M32) this is simply not possible. Up to my knowledge also not in Ableton. What missing features of the M32 do you mean?

Has anything significant changed in regards to the depth/level of control in Bitwig? Obviously you can't get around hardware limitations but just wondering if there have been any significant improvements and how it compares to the Novation Launchkey Mini Mk3. From the documentation it seems the level of control is still fairly sparse compared to the Launchkey.

Trying to choose between the two, the advantages of the M32 being the extra keys and nks support, but seeing NI's track record of support with the Jam (among others) I'm not in a hurry to support or buy any hardware from them.

[moss]

Hi there. Heres a request for the fire, but not sure if it can be done. Is there a way to lock the displayed pattern to a specific track so that selecting another track with the mouse that is not receiving midi from the fire will not altar the note display as it is locked to a specific track already? I was playing with 2 controllers - the fire and my keyboard and when I clicked the other track under keyboard control the fire changed displayed notes even though that track is not receiving from the fire.

Yes, pinning of tracks and devices is possible. Lets see if I can squeeze it in somewhere. Note, that you can already pin the track in Bitwig from the document pane on the right.

[moss]

The features that (all of) the Kontrol Keyboards provide are very limited. On the Mk2 I did the trick via the Delete button but on the smaller devices (A-series, M32) this is simply not possible. Up to my knowledge also not in Ableton. What missing features of the M32 do you mean?

Has anything significant changed in regards to the depth/level of control in Bitwig? Obviously you can't get around hardware limitations but just wondering if there have been any significant improvements and how it compares to the Novation Launchkey Mini Mk3. From the documentation it seems the level of control is still fairly sparse compared to the Launchkey.

No, there is nothing new and I do not expect any extensions to the M32 in the future. From my side I already did what is possible with the hardware.

Trying to choose between the two, the advantages of the M32 being the extra keys and nks support, but seeing NI's track record of support with the Jam (among others) I'm not in a hurry to support or buy any hardware from them.

The M32 makes only sense if you mainly work with the Komplete plugin. Also build quality is a bit better but the device is also larger.

[maschinelf]

Thanks moss, think I will go for the launchkey mini.

[IllusionCatalyst]

Hello Moss, thanks for the great work with the Launchpad Pro MK III integration!

I have noticed that when the driver is active, one of the CPU cores goes up to 100% and stays there until the driver is disabled. This is a performance issue, in particular for low power machines. I hope it can be fixed.

When in Session mode, clicking the Session button multiple times reorients the clips, horizontal or vertical. It would be nice if the arrows' behavior to navigate the clips would update accordingly, by matching the scroll direction.

I would also like to have the ability to turn off the pads' light, same as pressing the Setup button and the bottom right pad.

Thank you very much!

[porkloin]

I don't have a Mk3, but my understanding is that the MIDI config is more complicated given that the Mk3 is designed to allow multiple MIDI out/in channels. Are you sure the Launchpad is communicating with Bitwig on the correct MIDI channel?

Yeah, in fact the extension *forces* the correct MIDI out/in channels to be used (if you try to choose a different one, it automagically creates a new "controller" entry in Bitwig using the correct one).

I am getting MIDI messages in Bitwig (again, some notes actually work), but none of the advertised extra functionality of the extension works, and the note values seem scrambled (and some are ignored...).

I also tried doing this on Windows, same bug.

The LP works on Ableton on that same Windows machine, so it's something specific to the extension....

I actually just got a LP Pro Mk3 myself, and I'm 99% sure I know what your problem is. Until I updated the firmware on my device, the extension wouldn't recognize it.

Visit https://components.novationmusic.com/ in a compliant browser (Chrome, some others) and you should be able to run the firmware upgrade. Make sure to remember to click "accept" when the browser asks permission to access MIDI devices!

[porkloin]

Given that I just got a Pro Mk3 device, I'm going to spend some time over the next week updating all of my LPX diagrams for a set of dedicated LP Pro Mk3 diagrams. @moss you should see a github PR from me on that soon - I may also try to clarify some of the points you have about firmware updates being required specifically for the Pro Mk3, as I got tripped up for a minute figuring that out just like @brunobeltran did.

[moss]

I don't have a Mk3, but my understanding is that the MIDI config is more complicated given that the Mk3 is designed to allow multiple MIDI out/in channels. Are you sure the Launchpad is communicating with Bitwig on the correct MIDI channel?

Yeah, in fact the extension *forces* the correct MIDI out/in channels to be used (if you try to choose a different one, it automagically creates a new "controller" entry in Bitwig using the correct one).

I am getting MIDI messages in Bitwig (again, some notes actually work), but none of the advertised extra functionality of the extension works, and the note values seem scrambled (and some are ignored...).

I also tried doing this on Windows, same bug.

The LP works on Ableton on that same Windows machine, so it's something specific to the extension....

I actually just got a LP Pro Mk3 myself, and I'm 99% sure I know what your problem is. Until I updated the firmware on my device, the extension wouldn't recognize it.

Visit https://components.novationmusic.com/ in a compliant browser (Chrome, some others) and you should be able to run the firmware upgrade. Make sure to remember to click "accept" when the browser asks permission to access MIDI devices!

Yes, that was the reason. I now also added a note to the manual to first make sure you have the latest Firmware installed.

[moss]

Hello Moss, thanks for the great work with the Launchpad Pro MK III integration!

I have noticed that when the driver is active, one of the CPU cores goes up to 100% and stays there until the driver is disabled. This is a performance issue, in particular for low power machines. I hope it can be fixed.

I do not see that on my system. What is your OS and hardware?