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

[moss]

Launchpad
Fixed: In session mode playing pads were not green and recording pads not red.
Fixed: Pro Mk3: Selected Play/Sequence modes were not restored correctly when switching back from Session.

Great fixed and confirmed!

Moss i hope you do not get me wrong but i found another issue which needs some improvements on the Launchpad pro mk3:

The Pan and the Sends sliders work arbitrarily sometimes they slide nice sometimes they are stuck sometimes they jump.
The volume sliders seem to work correctly it looks like. I thought it could be related to simultaneously using the Launchkey but i disconnected the Launchkey and exactly the same behaviour i had.

I hope this can be improved?

Hmm, don't think so, since this is the same code.

[moss]

Hello.

I have a problem with Akai fire and launchpad pro script, when I want to delete a clip, if I have the start recording option activated by pressing rec arm in the menu, this does not delete the clip, but starts recording the clip again in place, this did not happen in previous versions like 19.2.2.

Good catch! WIll be fixed in the next update!

I would also like to know if it would be possible to return the momentary shift option instead of leaving it active or toggle, this would make it easier to play live and return to the screen you were on without having to press again, although I understand that the option was released for the new bitwig alt options. A way to choose between the two in the menu from akai fire, launchpad pro and maschine mk3 would be great.

Cheers!

This would make my head explode

[AuralBee]

Moss, thanks so much for your amazing work, I am thrilled to use Push 3 in Bitwig now.
I am somewhat confused how to activate Push’s cv outs when using Bitwig (in Ableton you have to make a deliberate choice for the ports) Should this just work when choosing audio outputs 5 thru 8 in Bitwig? (When using Push as an audio interface of course)
I had it working once, after that it did not it seemed.

[moss]

Moss, thanks so much for your amazing work, I am thrilled to use Push 3 in Bitwig now.
I am somewhat confused how to activate Push’s cv outs when using Bitwig (in Ableton you have to make a deliberate choice for the ports) Should this just work when choosing audio outputs 5 thru 8 in Bitwig? (When using Push as an audio interface of course)
I had it working once, after that it did not it seemed.

That is on my todo list to investigate.

EDIT: Looking good! Can be configured via SysEx.

[Oku]

Hey there Mr. Moßgraber - thanks for all.
Just downloaded/installed 21.1.0 - running version 5.0.4 (Win 10)...

And I get this 'red box' on startup...

Was running your 15.4.0 script on the same BW release previously and all was well..


Any ideas maestro?

[moss]

Hey there Mr. Moßgraber - thanks for all.
Just downloaded/installed 21.1.0 - running version 5.0.4 (Win 10)...

And I get this 'red box' on startup...

Was running your 15.4.0 script on the same BW release previously and all was well..


Any ideas maestro?

It shows the current page of clips. Nothing surprising here. If you for any reason do not want to see it you can switch it of in the controller settings. Also watch this:

[Oku]

Aaahh ha!
Thank You.

[balroj88]

Hello.

I have a problem with Akai fire and launchpad pro script, when I want to delete a clip, if I have the start recording option activated by pressing rec arm in the menu, this does not delete the clip, but starts recording the clip again in place, this did not happen in previous versions like 19.2.2.

Good catch! WIll be fixed in the next update!

I would also like to know if it would be possible to return the momentary shift option instead of leaving it active or toggle, this would make it easier to play live and return to the screen you were on without having to press again, although I understand that the option was released for the new bitwig alt options. A way to choose between the two in the menu from akai fire, launchpad pro and maschine mk3 would be great.

Cheers!

This would make my head explode

Thank you for your fast response, also on Akai fire would be nice to light up the stop button when enabling automation in clip launcher or a legend in the screen saying something like "automation enabled" or even a button in the shift menu because when you press shift + stop button it's not giving visual feedback, and you don't know if its activated or not without having to look on your computer screen. Could be something similar to activating the clip overdub, there you can see the record button lights up and stays in yellow when pressing shift.

Cheers!

[x.iso]

I added this already in version 20.3.1.

oooh! I see, somehow it wasn't updated on my side when I unpacked version 21, thought this specific script just wasn't updated. deleted everything, unpacked newest release and now I see it!
Thanks!

[questionaire]

Launchpad
Fixed: In session mode playing pads were not green and recording pads not red.
Fixed: Pro Mk3: Selected Play/Sequence modes were not restored correctly when switching back from Session.

Great fixed and confirmed!

Moss i hope you do not get me wrong but i found another issue which needs some improvements on the Launchpad pro mk3:

The Pan and the Sends sliders work arbitrarily sometimes they slide nice sometimes they are stuck sometimes they jump.
The volume sliders seem to work correctly it looks like. I thought it could be related to simultaneously using the Launchkey but i disconnected the Launchkey and exactly the same behaviour i had.

I hope this can be improved?

Hmm, don't think so, since this is the same code.

Do you mean you confirm?

[questionaire]

Launchpad
Fixed: In session mode playing pads were not green and recording pads not red.
Fixed: Pro Mk3: Selected Play/Sequence modes were not restored correctly when switching back from Session.

Great fixed and confirmed!

Moss i hope you do not get me wrong but i found another issue which needs some improvements on the Launchpad pro mk3:

The Pan and the Sends sliders work arbitrarily sometimes they slide nice sometimes they are stuck sometimes they jump.
The volume sliders seem to work correctly it looks like. I thought it could be related to simultaneously using the Launchkey but i disconnected the Launchkey and exactly the same behaviour i had.

I hope this can be improved?

Hmm, don't think so, since this is the same code.

Do you mean you confirm?

The sliders really do not work fluent in my case

[nowiamone]

Hi Jürgen,
is there any chance, that the OSC script adresses the normal EQ-5, instead of the EQ+? [Or gets an additional adress for the EQ-5, like /eq5 or something]
That would be awesome! Because the EQ+ has its disadvantages, sadly (which are discussed in length on KVR and other forums). And it's just super-duper convenient to adress EQ via OSC messages!
And someone on the touch osc community built a touch EQ controller, which would fit perfectly with the EQ-5 of Bitwig! It's just waiting to be connected to OSC adresses

eq 5.jpg

Thanks alot!

[moss]

Thank you for your fast response, also on Akai fire would be nice to light up the stop button when enabling automation in clip launcher or a legend in the screen saying something like "automation enabled" or even a button in the shift menu because when you press shift + stop button it's not giving visual feedback, and you don't know if its activated or not without having to look on your computer screen. Could be something similar to activating the clip overdub, there you can see the record button lights up and stays in yellow when pressing shift.

Noted.

[moss]

Launchpad
Fixed: In session mode playing pads were not green and recording pads not red.
Fixed: Pro Mk3: Selected Play/Sequence modes were not restored correctly when switching back from Session.

Great fixed and confirmed!

Moss i hope you do not get me wrong but i found another issue which needs some improvements on the Launchpad pro mk3:

The Pan and the Sends sliders work arbitrarily sometimes they slide nice sometimes they are stuck sometimes they jump.
The volume sliders seem to work correctly it looks like. I thought it could be related to simultaneously using the Launchkey but i disconnected the Launchkey and exactly the same behaviour i had.

I hope this can be improved?

Hmm, don't think so, since this is the same code.

Do you mean you confirm?

Sorry, no. I played with it for a bit but could not reproduce it.

[moss]

Hi Jürgen,
is there any chance, that the OSC script adresses the normal EQ-5, instead of the EQ+? [Or gets an additional adress for the EQ-5, like /eq5 or something]
That would be awesome! Because the EQ+ has its disadvantages, sadly (which are discussed in length on KVR and other forums). And it's just super-duper convenient to adress EQ via OSC messages!
And someone on the touch osc community built a touch EQ controller, which would fit perfectly with the EQ-5 of Bitwig! It's just waiting to be connected to OSC adresses
eq 5.jpg
Thanks alot!

This is on my (longish) todo list to make this configurable.