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

[JohannesTress]

Hi there, is there a way to narrow the pitchbend Range on the Push 2? Thanks and all best

[srzorro]

I wrote to you earlier regarding issues with the visual values of the SL MK3 being laggy. Have you found what could be wrong? I'm using a macbook pro 2017 15' inch with OS Mojave with the latest version of bitwig. I made a video showing the issue.

I can reproduce it and already looked into it. The issue is related to sysex messages sent by Bitwig but only for certain devices. I have a similar issue with the Akai Fire which I am working on which renders the device useless. Strangely it does not happen with the Push 1, which also uses sysex for the display. It is not a general issue of Macos since it works fast on my Reaper port, which uses the same code (but a different MIDI layer).
I am in touch with Bitwig about the issue but I am not sure if there is a solution soon or at all.

Wow, would be a shame if it has no solution at all. I love the integration of the SL with bitwig, and I'm even using both to perform live, which can become more of an issue than in the studio. One of the reasons I bought it was because I saw your amazing work you did with the script. Hope it works out well.

Thanks for your awesome work.

[AFranke]

Hi,
wouldn't it be nice to have the LEDs of the Keys (wich are showing the actual scale etc.) on the Novation SL MK3 follow the track colors in BWS? Like in its sequencer mode, this would be very nice I think. Is this possible?

Best regards.

The light guide is sadly not programmable.

Hmm. Looked into the Novations SL MK 3 programmers guide and found this:

AcroRd32_ARjnoKRoMo.png

[moss]

Hi,
wouldn't it be nice to have the LEDs of the Keys (wich are showing the actual scale etc.) on the Novation SL MK3 follow the track colors in BWS? Like in its sequencer mode, this would be very nice I think. Is this possible?

Best regards.

The light guide is sadly not programmable.

Hmm. Looked into the Novations SL MK 3 programmers guide and found this:AcroRd32_ARjnoKRoMo.png

Ah, thanks for the info! Totally, overlooked that.

[AFranke]

Next problem with mapping parameters to a device page. Mapped the midi channel selector of a hardware device to a device page. If I move the knob it shows and set up wrong values.

The right Values should be:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

What the script show in the display:
Ch 1,Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15

What the script sets up in the hardware device:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

Talked with the BWS Support about this:

was auf dem Display angezeigt wird, kommt aus dem Script, evtl. ist da einfach ein Eintrag verrutscht.

Mit freundlichen Grüssen,
Bitwig Technical Support Team

[moss]

Talked with the BWS Support about this:

was auf dem Display angezeigt wird, kommt aus dem Script, evtl. ist da einfach ein Eintrag verrutscht.

No. I reported it now as well as a bug...

[AFranke]

Talked with the BWS Support about this:

was auf dem Display angezeigt wird, kommt aus dem Script, evtl. ist da einfach ein Eintrag verrutscht.

No. I reported it now as well as a bug...

[moss]

Hi there, is there a way to narrow the pitchbend Range on the Push 2? Thanks and all best

Sorry, no.

[moss]

Next problem with mapping parameters to a device page. Mapped the midi channel selector of a hardware device to a device page. If I move the knob it shows and set up wrong values.

The right Values should be:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

What the script show in the display:
Ch 1,Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15

What the script sets up in the hardware device:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

Talked with the BWS Support about this:

was auf dem Display angezeigt wird, kommt aus dem Script, evtl. ist da einfach ein Eintrag verrutscht.

Mit freundlichen Grüssen,
Bitwig Technical Support Team

The bug is confirmed now and (hopefully) will be fixed soon.
BTW all parameters which map to a list are affected.

[soehngenetic]

Hi Moss,
I'm in the process of setting up my VST(i)s for Push2 in Bitwig at the moment. - First of all big thanks an respect for the amazing script making Push2 so valuable in Bitwig! (In the end this is the main reason, why I chose Bitwig over Studio One for getting back into music making after several years.)

I have two question regarding the controller mapping:
1. Some VSTis (TAL UNO LX for example) have quite long and weird paramter names. Now I figured out, that it's possible to rename the controls in the mapping dialogue in Bitwig while setting up the VSTis. But unfortunately these individuel names aren't reflected on the Push2s screen. - Is this not possible because of the API or is it just not implemented yet?

2. Is there a nicer / more elegant way to setup switches and toggles with Push 2 than using the encoders for that?

Best regards and thanks in advance from the Odenwald ,
Christoph

[moss]

Hi Christoph,

1. Some VSTis (TAL UNO LX for example) have quite long and weird paramter names. Now I figured out, that it's possible to rename the controls in the mapping dialogue in Bitwig while setting up the VSTis. But unfortunately these individuel names aren't reflected on the Push2s screen. - Is this not possible because of the API or is it just not implemented yet?

It should work like this but I think there is a bug in Bitwig in that area, could be caching or update issue. Could you please check if it is working after restarting Bitwig?
If you can reproduce it reliably, please report to Bitwig.

2. Is there a nicer / more elegant way to setup switches and toggles with Push 2 than using the encoders for that?

Sorry, no.

Best regards and thanks in advance from the Odenwald ,

Cheers from close to the Pfälzerwald

[soehngenetic]

It should work like this but I think there is a bug in Bitwig in that area, could be caching or update issue. Could you please check if it is working after restarting Bitwig?
If you can reproduce it reliably, please report to Bitwig.

Thanks for your fast reply! - I just checked it. If the VSTi is on a track and I push the device button on Push2, the individual names of the first controller page are shown like I modified them. But as soon as I activate the button named "Banks" to show the other controller pages, the names of the individual controllers switch back to the original controller-names of the VSTi.

By deactivating the "Banks" button, the names remain the original ones.

To get the individually changed names of page 1 back, I have to deactivate "Banks" first, then move to the Mix page and then back to Device.

So, should I report this to Bitwig or do you have an idea, what the problem could be?

Cheers from close to the Pfälzerwald

Ah, that clarifies the very personal English accent in your videos!

Thanks again

[BitwigStarter599]

Installation:
Downloaded DrivenByMoss 8.98 and extracted zip file on my windows 7 Pro computer.
Copied bwextension file to Bitwig 3.1.3 installation in Users/Documents/Bitwig Studio/extensions.
Started Bitwig 3.1.3, went to Settings Controllers. There I found the additional Generic Flexi, a super extension. But this was the only one extra to be found. No other controllers listed and no Midi Monitor which I am very interested in. The add Controller function as well did not list any additional content.
Where is the fault in my installation? Any hint?
Thanks.

You are aware that you can/need to change the "Hardware Vendor" with the drop down list?
If yes, I can only imagine that the file is somehow damaged or there might be an issue with Windows 7.

Hi Moss,
thanks for the above advice. It helped a lot. But now I encounter another problem: The midi monitor continuously reports and lists events of the kind FE 254 0 0 0 , last number 15, commented as 'active sense'. This prevents me from watching single events as the display continuously scrolls up. Is there a chance to stop the scrolling for a while or to keep away event FE 254 from being displayed? Otherwise I will not be able to recognize the 'wanted' events from the recpective keys or other controls.
Thanks, Herbert.

[moss]

Installation:
Downloaded DrivenByMoss 8.98 and extracted zip file on my windows 7 Pro computer.
Copied bwextension file to Bitwig 3.1.3 installation in Users/Documents/Bitwig Studio/extensions.
Started Bitwig 3.1.3, went to Settings Controllers. There I found the additional Generic Flexi, a super extension. But this was the only one extra to be found. No other controllers listed and no Midi Monitor which I am very interested in. The add Controller function as well did not list any additional content.
Where is the fault in my installation? Any hint?
Thanks.

You are aware that you can/need to change the "Hardware Vendor" with the drop down list?
If yes, I can only imagine that the file is somehow damaged or there might be an issue with Windows 7.

Hi Moss,
thanks for the above advice. It helped a lot. But now I encounter another problem: The midi monitor continuously reports and lists events of the kind FE 254 0 0 0 , last number 15, commented as 'active sense'. This prevents me from watching single events as the display continuously scrolls up. Is there a chance to stop the scrolling for a while or to keep away event FE 254 from being displayed? Otherwise I will not be able to recognize the 'wanted' events from the recpective keys or other controls.
Thanks, Herbert.

Oh, you mean the MIDI monitor of Generic Flexi?

[moss]

It should work like this but I think there is a bug in Bitwig in that area, could be caching or update issue. Could you please check if it is working after restarting Bitwig?
If you can reproduce it reliably, please report to Bitwig.

Thanks for your fast reply! - I just checked it. If the VSTi is on a track and a push the device button on Push2, the individual names of the first controller page are shown like I changed them. But as soon as activate the button named "Banks" to show the other controller pages, the names of the individual controllers switch back to the original controller-names of the VSTi.

Ah, great. Fixed!