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

[moss]

Morning Juergen,

There is a small issue with latest script 19.2.2 and i guess also with the 20 version, i'm using Launchkey mk3 and when i have once chosen to go into drum mode and then go back to session mode the following happens: Whenever i choose a new instrument track with right click mouse and add a new device into the instrument track the script will change to drum mode instead of staying into session mode. So somehow the script is not resseting the drum mode after changing to session mode and keeps it in memory it looks like it is remembering the drum mode and keeps on reverting to it with each new added new device?

I would expect that whatever and no matter how you add a newly device, it would stay in the mode you are working in?

When i draw a device directly from the browser and drop it into the working area the session mode stays active by the way so that works fine.

Hope this one can be fixed? It is not a dealbreaker ofcourse but it would be cool to have this corrected.

Using Bitwig 4.4.10 windows 10.

By the way totally agree with what troy 808 said one post above.

Regards,
Wilfred.

This should not be the case. Will check.

EDIT: Will be fixed in the next update!

Thanks for that! May it be possible to fix it in 19.2.2 aswell? To keep Bitwig version 4 compatible?
Otherwise i'm forced to update my subscription with another year, and i'm not ready for that yet.
It is not your problem ofcourse but it would be great if the 19 version could get this fix!

I am sorry but it is just beyond my available time. But the code is open on GitHub and everyone can feel free to do it.

[moss]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

Hm, I fear that's not the solution, since I have the same behaviour on Windows and Mac consistently on BW. On other DAWs I just tested Ableton and Logic up until now, where it works correctly. It's a BW problem. On both scripts (stock and Moss), the truck change just doesn't bring the right Komplete instance on the HW. In the meanwhile, I have found, that some other guys have the same problem and the workaround is, that you can press a button in the Komplete plugin, to make this the active instance on the keyboard.

But do you want to say that track changing and right instance gets active on Keyboard works for you in BW?

I cannot test it right now but it worked in the past. Could be that NI broke it in any of their multiple recent updates...

[moss]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

Hm, I fear that's not the solution, since I have the same behaviour on Windows and Mac consistently on BW. On other DAWs I just tested Ableton and Logic up until now, where it works correctly. It's a BW problem. On both scripts (stock and Moss), the truck change just doesn't bring the right Komplete instance on the HW. In the meanwhile, I have found, that some other guys have the same problem and the workaround is, that you can press a button in the Komplete plugin, to make this the active instance on the keyboard.

But do you want to say that track changing and right instance gets active on Keyboard works for you in BW?

Hello,
For me, changing tracks with the Komplete Kontrol S49mk2 is working properly, changing the Display-content of each plugin, too. So i think your problem might be a wrong Plugin Hosting Mode. Go to Settings -> Plugins -> Plugins Hosting Mode, and choose "Together".
If it's still not working, i don't know the solution for you.

Ah! Good one!

[SamDi]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

Hm, I fear that's not the solution, since I have the same behaviour on Windows and Mac consistently on BW. On other DAWs I just tested Ableton and Logic up until now, where it works correctly. It's a BW problem. On both scripts (stock and Moss), the truck change just doesn't bring the right Komplete instance on the HW. In the meanwhile, I have found, that some other guys have the same problem and the workaround is, that you can press a button in the Komplete plugin, to make this the active instance on the keyboard.

But do you want to say that track changing and right instance gets active on Keyboard works for you in BW?

Hello,
For me, changing tracks with the Komplete Kontrol S49mk2 is working properly, changing the Display-content of each plugin, too. So i think your problem might be a wrong Plugin Hosting Mode. Go to Settings -> Plugins -> Plugins Hosting Mode, and choose "Together".
If it's still not working, i don't know the solution for you.

Yeah, that was it. Thank you very much for the hint. One needs to come on the idea first to think in this direction. Afterwards it's kind of logical.

[SamDi]

BTW, does anybody know, where the script terminal is gone in version 5 (for e.g. MIDI Monitor)? Thought they smashed it, but an employee at Superbooth told me, that it should still be there.

[moss]

Hey Moss! As I understand it, the problem with choosing the first device in the device panel has broken on all controllers and is still limited by the API. There is another problem, I consider it as a "step back" above, this new method of launching clips was written about it is very bad. The Clip Launcher stops working if you disable the Selecting clips in Clip Launcher checkbox in the Behavior settings. In version 19.2.2 it still works correctly, the old method could be added to new versions.

That's a conceptual issue (or call it a bug) in version 5 Beta 6. In the new drop down area for your controller (the icon on the title bar of the main window) switch the mode setting from "Any track / device selection" to "device selection" to get the previous behaviour. I already reported this.

[moss]

BTW, does anybody know, where the script terminal is gone in version 5 (for e.g. MIDI Monitor)? Thought they smashed it, but an employee at Superbooth told me, that it should still be there.

It is still there, only the button got removed. You can access it via the commander (press Ctrl+Return on Windows to open it), type "console" and execute the command. I suggest to assign a keyboard shortcut to it (e.g. I use Ctrl+Shift+J).

[SVRVDX]

That's a conceptual issue (or call it a bug) in version 5 Beta 6. In the new drop down area for your controller (the icon on the title bar of the main window) switch the mode setting from "Any track / device selection" to "device selection" to get the previous behaviour. I already reported this.

Thank you!!! There was a problem with Clip launcher. And for some reason, Moss does not work for me midi cc, bitwig does not react to them in any way and nothing is assigned.

[Greenplums]

Hope I am not being mega dim here. Komplete S61 Mk 1, Driven by Moss manual states that to Exclude deactivated items go to Settings-Controllers- Workflow options and make sure its activated. There is no such option under Workflow in 5.6 Beta. Sorry if this has been previously covered but I could not see it after a search. Help appreciated and many thanks for this fabulous software.

[gwen333]

Hello, ok,
I didn't see the option, sorry. how to adjust it? I want to record on a new clip with one click, then on the next click end the loop, then double click to create a new clip next to it?

That's not available. Closest is either "New clip" or the "Clip Based Looper" (see explanation in the manual).

ok thanks for the info, when I select an empty clip on a track armed with the mouse and I leave the pedal pressed, the clip is recorded, it's ok, when I release the pedal, the clip is played. The problem is that when I select an empty clip with the push (select + clip), the clip records when I would like it to do the same as the mouse. Is it possible ? THANKS.

[AFranke]

Moin Jürgen,
is there a way to prevent a track to activate the recording mode if you select it, but activate just monitoring instead? It would be really nice for live performing, when you don't want to record and so you could also stop a running clip by just clicking an empty slot.

Gruß Andreas

Not that I am aware of.

Damn, I really hoped so.

Thanx

[moss]

DrivenByMoss 20.2.1 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.0+
• Fire
  • New: Names of drum pads are now displayed when switching selection in drum mode.
• Generic Flexi
  • Fixed: MIDI feedback from on/off values did sent 1/0 instead of 127/0.
• Launchkey Mk3
  • Fixed: Wrong mode was set after closing the browser.
• MCU
  • Fixed: Fader flip did not work in Instrument mode.

Enjoy!

[moss]

Hope I am not being mega dim here. Komplete S61 Mk 1, Driven by Moss manual states that to Exclude deactivated items go to Settings-Controllers- Workflow options and make sure its activated. There is no such option under Workflow in 5.6 Beta. Sorry if this has been previously covered but I could not see it after a search. Help appreciated and many thanks for this fabulous software.

Just checked and it is there:

Exclude option.png

[Greenplums]

Hope I am not being mega dim here. Komplete S61 Mk 1, Driven by Moss manual states that to Exclude deactivated items go to Settings-Controllers- Workflow options and make sure its activated. There is no such option under Workflow in 5.6 Beta. Sorry if this has been previously covered but I could not see it after a search. Help appreciated and many thanks for this fabulous software.

Just checked and it is there:
Exclude option.png

I was looking under Workflow LOL plus I obviously need glasses. Many thanks.

[tommy1979]

New to moss and I am really struggling to get the drum machine to work correctly on my push 2, when i press pad a1 and then press any other pad it makes the note of a1 the length to that 2nd note, i can not figure out how to stop this behaviour, strangely it does not do this on drum 4 or drum 8 and i can program per pad as normal. Any help appreciated?