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

[osaga]

Hello Everyone

I have two LaunchControl XL's that are configured with Flexi. I want to pin the first unit to track 1-8 and the second unit to tracks 9-16, regardless of what tracks are selected.

These controllers are not showing up in the top right corner of Bitwig where you usually could pin them to a track. If I could get them to show up here that would be great, but they just won't show up.

I have been trying hard to find the answer, but am stumped. Any help would be appreciated.

Thanks so much!

[moss]

Hello Everyone

I have two LaunchControl XL's that are configured with Flexi. I want to pin the first unit to track 1-8 and the second unit to tracks 9-16, regardless of what tracks are selected.

These controllers are not showing up in the top right corner of Bitwig where you usually could pin them to a track. If I could get them to show up here that would be great, but they just won't show up.

I have been trying hard to find the answer, but am stumped. Any help would be appreciated.

Thanks so much!

Report this bug to Bitwig. If you can replicate it even better. I have this issue randomly. After rebooting / restarting Bitwig it normally shows up.

[osaga]

I will do this, and Thanks so much Moss. You're help and guidance is always appreciated.

[osaga]

Hey Moss.

So turns out (at least for me). The max number of icons that will show up in the controller icons toolbar is 9.

I had to turn off a bunch of the controllers (via the controller setup page), then my Launch Control XL's shows up at the top right. Then I turned the other ones back on and my Launch Control XL's stayed in the top 9. So it seems it's the first controllers to be available/installed will show up first.

Thought you'd like to know. Bug reported to BW.

Thanks! Oshine

[FatmanthGreat]

Hi, I’m trying to use Push 3 with Bitwig 6 with your script, but I encounter a few problems. Firstly, all pad presses are register as two presses, e.g. I press one pad and independently of it another pad registers a press even though I’m not touching it. Moreover, the second pad seems to be random, there’s no set pitch difference between them. Secondly, instruments don’t get displayed on the push 3 screen. I can’t control any parameters on the screen. Do you know how can I solve these problems?

[B HEM]

Hey will the DrivenByMoss work on this new Fedora 44 (Workstation Edition) loaded with all the Audio files from jam rpm with Native installed Bitwig 8-track onto this edition? Previously, I tried same bitwig 8-track on windows10 followed your instructions and my Maschine+ was good to go. Seen your vendor name after i dragged the bwex...extension files to the bitwig extensions folder and there it was. I'm having some issue now that i'm on fedora linux 44 which just came out 2 days ago. I grabbed it because of the promising better features then fedora jam when it comes to kde and pipewire latency(truly clean less hassle install). And I'm curious if i might have missed a step somewhere. Let me know. Overall, I want to thank you for the template and even though they say NI isn't working on Linux versions yet, this workflow for bitwig really sparked my interest. I'm attempting to completely do production on linux and escape th bloatware OS. IyKyK.

[greta]

Hey Moss (or if anyone else can help me),
I searched but can't seem to find this answer - does anyone know if you can run two APC40 mk2s at once within Bitwig properly, using Moss' script? (Ie: in Ableton when you use 2 APC40s simultaneously, one will show the clips of tracks 1-8 and the other one will be tracks 9-16). Thanks in advance!

[moss]

Hi, I’m trying to use Push 3 with Bitwig 6 with your script, but I encounter a few problems. Firstly, all pad presses are register as two presses, e.g. I press one pad and independently of it another pad registers a press even though I’m not touching it. Moreover, the second pad seems to be random, there’s no set pitch difference between them. Secondly, instruments don’t get displayed on the push 3 screen. I can’t control any parameters on the screen. Do you know how can I solve these problems?

I never heard of such problems. The Firmware of the Push is up to date? Did you try to lower the pad sensitivity for the first issue?

[moss]

Hey will the DrivenByMoss work on this new Fedora 44 (Workstation Edition) loaded with all the Audio files from jam rpm with Native installed Bitwig 8-track onto this edition? Previously, I tried same bitwig 8-track on windows10 followed your instructions and my Maschine+ was good to go. Seen your vendor name after i dragged the bwex...extension files to the bitwig extensions folder and there it was. I'm having some issue now that i'm on fedora linux 44 which just came out 2 days ago. I grabbed it because of the promising better features then fedora jam when it comes to kde and pipewire latency(truly clean less hassle install). And I'm curious if i might have missed a step somewhere. Let me know. Overall, I want to thank you for the template and even though they say NI isn't working on Linux versions yet, this workflow for bitwig really sparked my interest. I'm attempting to completely do production on linux and escape th bloatware OS. IyKyK.

Should work but since I have no Fedora install I cannot confirm. Maschine will not work on Linux since there is no driver.

[moss]

Hey Moss (or if anyone else can help me),
I searched but can't seem to find this answer - does anyone know if you can run two APC40 mk2s at once within Bitwig properly, using Moss' script? (Ie: in Ableton when you use 2 APC40s simultaneously, one will show the clips of tracks 1-8 and the other one will be tracks 9-16). Thanks in advance!

Not to extend the channels. It is possible but you need to implement it (I only did it for the Mackie protocol). What you can do is use the 2 units in different modes, e.g. session view on one device and a sequencer on the 2nd.

[FatmanthGreat]

Hey Moss. My Push 3 is up to date with firmware. This problem has not occurred, while using the controller with Ableton. All the double presses happen when using different instruments, both built-in and external. I don’t think it’s a problem with pad sensitivity since nothing’s wrong when I press the first 5 pads, it only starts when I press pads after these. There’s also no specific interval between those double presses - sometimes it’s an octave, sometimes a neighbouring pad and sometimes a completely random other pad. But what’s interesting is that those press stay the same - when I press each pad a different one is triggered and it doesn’t change even if I switch layouts.

[mfny]

Hi all,

So I have a Nektar Panorama CS12 id like to use with Bitwig. Ive installed Moss and selected the Flexi script, but I am at a loss as to what to do next as trying to map things does not work, the CS12 presents itself as 4 different midi devices making thing more complicated as I'm not sure which to select, in addition the CS12 stays in "Screensaver" mode and does not seem to get activated at all for normal use, which makes sense as there is no support for Bitwig in the CAS12 software and it needs the software to work.

Anyone have specific instructions on how to get the CS12 working so I can assign things, if it even will work ?

[moss]

Hey Moss. My Push 3 is up to date with firmware. This problem has not occurred, while using the controller with Ableton. All the double presses happen when using different instruments, both built-in and external. I don’t think it’s a problem with pad sensitivity since nothing’s wrong when I press the first 5 pads, it only starts when I press pads after these. There’s also no specific interval between those double presses - sometimes it’s an octave, sometimes a neighbouring pad and sometimes a completely random other pad. But what’s interesting is that those press stay the same - when I press each pad a different one is triggered and it doesn’t change even if I switch layouts.

Sorry, no idea. Haven't heard of such an issue so far.

[moss]

Hi all,

So I have a Nektar Panorama CS12 id like to use with Bitwig. Ive installed Moss and selected the Flexi script, but I am at a loss as to what to do next as trying to map things does not work, the CS12 presents itself as 4 different midi devices making thing more complicated as I'm not sure which to select, in addition the CS12 stays in "Screensaver" mode and does not seem to get activated at all for normal use, which makes sense as there is no support for Bitwig in the CAS12 software and it needs the software to work.

Anyone have specific instructions on how to get the CS12 working so I can assign things, if it even will work ?

I have no experience with this device. I had a quick look at their website and it is not really that helpful. I understood that Bitwig comes with a script for it but could not spot it?! What I also understood is that you need to set it to a MIDI mode to e.g. use it with Generic Flexi. Try the Nektar support.

[JimDiGritz]

Great work as always! Are there any plans to support syncing/changing the Prohect Key in Bitwig 6.x from the controller? Eg selecting modes/key on the controller doesn't affect the Key Signature in Bitwig. This could also be bi-directional - if I change the Key in Bitwig say to E Minor it would be great if the controller Key was also updated to match

I think this would need to be optional/toggle-able for situations where you didn't want to sync.