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

[DanRamone]

I have following issues with Push2:
if I'm on a different window that is not bitwig the display is turning on and off...if I press the play button while the screen is off it will send the play signal only when the display is on again.
If I switch back to Ableton 10.1.14 the colors of the push are messed up, if I'm correct it has changed everything that is white lit to green

[ThomasHelzle]

Awesome Jürgen!
Thanks a ton for the MK3 support - let's see how my GF will like it...

Cheers,

Tom

[moss]

I have following issues with Push2:
if I'm on a different window that is not bitwig the display is turning on and off...if I press the play button while the screen is off it will send the play signal only when the display is on again.

Can only guess that one of the other programs you are running is somehow interfering. The display goes black if it does not get an update for some seconds, which means the connection is broken.

If I switch back to Ableton 10.1.14 the colors of the push are messed up, if I'm correct it has changed everything that is white lit to green

Turn the device on and off to reset the color table.

[deailes]

Hiya Jurgen..

Loving your work !!

I am having small bug using Komplete Kontrol M32 keyboard.

When starting BITWIG. now on 3.2 but it also did it on 3.1. i get a midi output Error.

KOMPLETE KONTROL M£" MIDI: could not open midi output. There is not enough memory available for this task.

When checking settings it has added 5 versions of the controller. 3 of them enabled and 2 of them disabled. I delete them all and then manually add 1 back in. Close and reopen bitwig. Same thing happens. Some times its 5 instances of the controller, sometimes less.

I tried deleting the extension completely and reinstalling the script. Now on the latested 9.10 But its still not playing ball. the weird thing is that it still works but i conintue to get this error and the multiple instances loaded.

Request:
I love the workflow of the large control knob on the M32 where you can jump the playhead back to previous bar or to the next bar. This for me only works though when the transport is stopped and not playing. I would like the ability to have it jump whilst transport is playing. (similar to how the M32 works in Ableton). Is my functionality broken? or is this something that could be considered for future version? IE the behaviour works when using the standard keyboard/controller shortcuts to jump back/forward a bar whilst transport is playing.

Thanks for all your hardwork !!!

Cheers

John

[aMUSEd]

Are there any new features in 3.2 for Komplete Kontrol users?

[moss]

Are there any new features in 3.2 for Komplete Kontrol users?

You can now hide deactivated tracks.

[moss]

I am having small bug using Komplete Kontrol M32 keyboard.
When starting BITWIG. now on 3.2 but it also did it on 3.1. i get a midi output Error.
KOMPLETE KONTROL M£" MIDI: could not open midi output. There is not enough memory available for this task.
When checking settings it has added 5 versions of the controller. 3 of them enabled and 2 of them disabled. I delete them all and then manually add 1 back in. Close and reopen bitwig. Same thing happens. Some times its 5 instances of the controller, sometimes less.

Never heard of such an issue so far but also don't have a M32 for testing.
Is that happening on each start of Bitwig? What is your OS? Have you checked if there is no other application which might have grabbed the port?
Maybe you could also ask Bitwig about it.

Request:
I love the workflow of the large control knob on the M32 where you can jump the playhead back to previous bar or to the next bar. This for me only works though when the transport is stopped and not playing. I would like the ability to have it jump whilst transport is playing. (similar to how the M32 works in Ableton). Is my functionality broken? or is this something that could be considered for future version? IE the behaviour works when using the standard keyboard/controller shortcuts to jump back/forward a bar whilst transport is playing.

This is prevented by Bitwig. You can send a feature request to them.

[Raketenbauer]

When checking settings it has added 5 versions of the controller. 3 of them enabled and 2 of them disabled. I delete them all and then manually add 1 back in. Close and reopen bitwig. Same thing happens. Some times its 5 instances of the controller, sometimes less.

I have the exact same MIDI error and behavior. The error occurs on every start of Bitwig and Bitwig is the only application running.

Could it be that the controller detection algorithm get's stuck in an endless loop and at one point runs out of memory and then exits the loop?

I'm on a Windows 10 machine with an NI M32 with the latest firmware.

[moss]

When checking settings it has added 5 versions of the controller. 3 of them enabled and 2 of them disabled. I delete them all and then manually add 1 back in. Close and reopen bitwig. Same thing happens. Some times its 5 instances of the controller, sometimes less.

I have the exact same MIDI error and behavior. The error occurs on every start of Bitwig and Bitwig is the only application running.

Could it be that the controller detection algorithm get's stuck in an endless loop and at one point runs out of memory and then exits the loop?

I'm on a Windows 10 machine with an NI M32 with the latest firmware.

Can you please check what are the exact names of the in-/output ports? But not in Bitwig but in e.g. MIDI-OX. And then please compare to the ones showing up in Bitwig.

[Yokai]

DrivenByMoss 9.10 tends to crash the audio engine in Bitwig 3.2 (and generate a Bitwig crash report) if I turn off my Push2 while Bitwig is still running. This happened all throughout the 3.2 beta period too with the earlier 8.9x DrivenByMoss.

I'm guessing it's a thing on Bitwig's side, but just so you're aware.

Windows 10, i9 9900K, 64 GB RAM, MOTU M4, Geforce RTX 2070

[Raketenbauer]

Can you please check what are the exact names of the in-/output ports? But not in Bitwig but in e.g. MIDI-OX. And then please compare to the ones showing up in Bitwig.

I checked the ports with NI Komplete Kontrol.

MIDI Inputs

• KOMPLETE KONTROL M32 MIDI

• Komplete Kontrol M DAW

MIDI Outputs

• KOMPLETE KONTROL M32 MIDI

• Komplete Kontrol M DAW

The names in Bitwig are exactly the same, although in reverse order.

The message I get from Bitwig is:
MIDI Output Error: KOMPLETE KONTROL M32 MIDI: Could not open MIDI output: There is not enough memory available for this task.

[srzorro]

Hi Jürgen,
First of all, I just wanted to say that I really appreciate your work, you have fastened my workflow in so many ways, and made my interaction with Bitwig awesome.

I'm having an issue that is driving me crazy with the Novation SLMK3, whatever parameter I move on the DAW or on the controller, the refresh rate of the value of the position of the parameter in the controller has a lot of latency. The position of the knob shows just fine, but the value of the position just drags a lot. It is terrible specially when I have an automated parameter with lots of fast movement. I have to wait till it goes mad up and down till it finishes until I can do whatever else with the controller. Don't know if I f**ked up some configuration at some point, or is it an issue with something else.

Thanks a lot in advance,

[moss]

DrivenByMoss 9.10 tends to crash the audio engine in Bitwig 3.2 (and generate a Bitwig crash report) if I turn off my Push2 while Bitwig is still running. This happened all throughout the 3.2 beta period too with the earlier 8.9x DrivenByMoss.

I'm guessing it's a thing on Bitwig's side, but just so you're aware.

Windows 10, i9 9900K, 64 GB RAM, MOTU M4, Geforce RTX 2070

By coincidence I reported this issue as well. Answer is that this is a longstanding Windows bug, which likely will never be fixed. The issue appeared there before in Bitwig but was not notified. So, I am not sure if this will/can be fixed.

[moss]

Can you please check what are the exact names of the in-/output ports? But not in Bitwig but in e.g. MIDI-OX. And then please compare to the ones showing up in Bitwig.

I checked the ports with NI Komplete Kontrol.

MIDI Inputs

• KOMPLETE KONTROL M32 MIDI

• Komplete Kontrol M DAW

MIDI Outputs

• KOMPLETE KONTROL M32 MIDI

• Komplete Kontrol M DAW

The names in Bitwig are exactly the same, although in reverse order.

The message I get from Bitwig is:
MIDI Output Error: KOMPLETE KONTROL M32 MIDI: Could not open MIDI output: There is not enough memory available for this task.

Thanks, but does look OK. Will try to get a device for testing.

[moss]

Hi Jürgen,
First of all, I just wanted to say that I really appreciate your work, you have fastened my workflow in so many ways, and made my interaction with Bitwig awesome.

I'm having an issue that is driving me crazy with the Novation SLMK3, whatever parameter I move on the DAW or on the controller, the refresh rate of the value of the position of the parameter in the controller has a lot of latency. The position of the knob shows just fine, but the value of the position just drags a lot. It is terrible specially when I have an automated parameter with lots of fast movement. I have to wait till it goes mad up and down till it finishes until I can do whatever else with the controller. Don't know if I f**ked up some configuration at some point, or is it an issue with something else.

Thanks a lot in advance,

What is you OS? Bitwig 3.2?