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

[moss]

Congratulations, you found a bug! Will be fixed in the next update!

FLIP Mode for PAN is also broken, it also jumps back to the faders previous position.

Yes, will be fixed in all modes.

[moss]

Does the Generic Flexi no longer work for Program Changes? I watched the YouTube vid, but I don't see it in the panel like it's displayed in the video. Perhaps I'm setting up the Flexi incorrectly?

In Bitwig 5, it is now located in the little icon which shows up for each controller in the title bar.

[moss]

Hi,
Is it possible with the Push 2 to change the loop length and the start position of multiple clips at the same time ? Or to change these parameters at the Scene level and not only for individual clips ?
Thanks !

No, that is currently not possible (and cannot be implemented).

[moss]

Hi @moss

I know this could be a big ask. For your OSC implementation, would it be possible to select to send color information in either RGB or HEX format, with a switch on the settings to choose which? Currently color info is sent in the format STRING(rgb(67,210,185)) - if the HEX switch was chosen it would send STRING(43D2B9) instead.

Reason for asking is that TouchOSC expects the HEX format. I'm aware that it may be possible to reformat using LUA script within TouchOSC, but don't know how and think it would also need to be manually repeated for every individual element in TouchOSC. So think the best approach would be to implement in the sending script?

Please let me know your thoughts.

Thanks,

Martin

I got similar requests, which means there are quite some variations. Therefore, please use a LUA function.

[moss]

Hey, I googled for a kind of easy question (I thought)... but didn't find a valid source.
Which SDK is Bitwig ( 4 / 5 ) now supporting, is it still 1.8, or could I use Java SDK 17 (LTS) now?

It is 17. You can always check yourself if your run "java -version" from the command line in the folder of Bitwigs' JVM.

[moss]

Hi @Moss, first I'd like to thank you for your excellent work. I hope that the folks at bitwig understand that many of us purely choose their product due to the work you've put into extensions.

Regarding the OSC implementation, is there any way to delete track data or recent recording (ie such as an 'undo') from the arranger view? - Maybe I'm missing something obvious??

Cheers!
Troy

You mean the recorded audio files? Only thing you can do is call "undo" (not specific to OSC).

[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!

[gwen333]

hello, and thank you for your driver
I use a push 1 and bitwig 4.xx with linux, I pluged a Footswitch 2, so this don't work.
I tested this on with live ableton on windows, the Footswitch run.
or I can not use it or there is a bug I guess. Thanks for your help.

[malephonk]

Hey, I googled for a kind of easy question (I thought)... but didn't find a valid source.
Which SDK is Bitwig ( 4 / 5 ) now supporting, is it still 1.8, or could I use Java SDK 17 (LTS) now?

It is 17. You can always check yourself if your run "java -version" from the command line in the folder of Bitwigs' JVM.

Wow, thank you so much for this prompt answer / explanation.

[questionaire]

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.

Just as a side note the above described applies also when you go first to a custom mode and then back to session mode adding instrument track and device after that will revert to the custom mode. I suppose with all other modes like scale chord and user chord aswell but not tested.

[troy808]

You mean the recorded audio files? Only thing you can do is call "undo" (not specific to OSC).

Ahh, yep the recorded audio or midi on the track in the arranger view. Was hoping I could use OSC to select a range and delete it.
All good though, I'll come up with some workaround, maybe such as your undo suggestion.

Thanks!
Troy

[moss]

hello, and thank you for your driver
I use a push 1 and bitwig 4.xx with linux, I pluged a Footswitch 2, so this don't work.
I tested this on with live ableton on windows, the Footswitch run.
or I can not use it or there is a bug I guess. Thanks for your help.

Seems to work fine. What function did you configure for it in the settings? Default is Sustain pedal.

[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? (the same method of ableton)

[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?

[Mantras]

I guess it was unnecessary to create a new post and that I should have posted inside this topic instead. So here goes:

I tried the Push 1 with moss script before and there was a problem with the screen becoming completely unresponsive in MacOS, like data messages where getting stuck and gathering up.
The screen would process things you where doing a long time ago and one had to wait to get it responsive. I was contacted by another kvraudio member who had the exactly same issues with Push1+Moss+MacOS.
When I tried the Push 1 in Linux Bitwig with the same computer everything ran smoothly.
Since I am using MacOS as the standard audio system I had to give up on the Push 1 since it just would not work normally and I sold it.

Now I am on another system, Monterey with M1 and I am curious if other people are running their Push 1 problem free in Bitwig with MacOS these days. If the script would work it would be a great controller since it can be found quite inexpensive second hand.