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

[xtreme sounds]

Hi there Moss

Did you see my video? Do you need something more from me to address the fire issue?

I was trying not to get seasick but I made it till the end

I can reproduce the issue and looked into it. It seems to be a Bitwig bug with layers maping. I reported it to Bitwig, so lets hope for a fix.

Thanks.

[thetechnobear]

anyone else using apple silicon yet? (mac mini M1)

Im running BWS 3.3 with latest DrivenByMoss connected to my Push2.
Im getting some wierd behaviour where the pads and buttons are not lighting up correctl (the display works perfectly)

the same combo on my MBP/Intel (albeit on Mojave not BigSur) works fine.

perhaps an issue with bitwig on apple silicon, so I'll report to Bitwig...
(and here it may just be more of a 'heads up')


note: Ableton Push 2 / Live 11 Beta on M1 seems to be working absolutely flawlessly.

[moss]

anyone else using apple silicon yet? (mac mini M1)

Im running BWS 3.3 with latest DrivenByMoss connected to my Push2.
Im getting some wierd behaviour where the pads and buttons are not lighting up correctl (the display works perfectly)

the same combo on my MBP/Intel (albeit on Mojave not BigSur) works fine.

perhaps an issue with bitwig on apple silicon, so I'll report to Bitwig...
(and here it may just be more of a 'heads up')


note: Ableton Push 2 / Live 11 Beta on M1 seems to be working absolutely flawlessly.

I have one for testing but I experienced this issue with the Intel version. I assume this is more a Big Sur issue than with ARM. I just implemented a little workaround today to flush all LEDs some seconds after startup which hopefully fixes that.

[thetechnobear]

Interesting... let me know if you’d like me to test it

[PrElektra]

Dear Mr Mossgraber,

I have previously, without any issues been using your script (for which I am most thankful to you - truly amazing work!) with the Native Instruments KK S49 mk I keyboard. Since some time back there is no way I can make the script start (the ”power” button never shifts to orange) and there is no connection to the keyboard at all. At one occasion it actually did work for some reason but I do not know what I did different to make that happen... Now it seems impossible again no matter what I do!
I have tried to go back to older versions but the problem seems to persist.
Would you have any idea what to try?

Driven by Moss 10.9.1 (from November 15)
Bitwig 3.2.8 and later 3.3 on Win 10
NiHostIntegrationAgent 1.10.1.152
NiHardwareService 2.6.1.532

Kind regards // Svante

[moss]

Dear Mr Mossgraber,

I have previously, without any issues been using your script (for which I am most thankful to you - truly amazing work!) with the Native Instruments KK S49 mk I keyboard. Since some time back there is no way I can make the script start (the ”power” button never shifts to orange) and there is no connection to the keyboard at all. At one occasion it actually did work for some reason but I do not know what I did different to make that happen... Now it seems impossible again no matter what I do!
I have tried to go back to older versions but the problem seems to persist.
Would you have any idea what to try?

Driven by Moss 10.9.1 (from November 15)
Bitwig 3.2.8 and later 3.3 on Win 10
NiHostIntegrationAgent 1.10.1.152
NiHardwareService 2.6.1.532

Kind regards // Svante

The implementation for the Mk I does directly access USB and does not use the NI services. On the contrary it can conflict with them. Try to stop them and see if it works.

[moss]

DrivenByMoss 10.9.5 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• All devices
  • Fixed: LEDs and controls did not update on Macos 11 on startup. All states are now flushed 10s after startup.
• Fire
  • New: The brightness and the color intensity of the pads can be adjusted in the settings.

Enjoy!

[artsense]

[*]Fixed: LEDs and controls did not update on Macos 11 on startup. All states are now flushed 10s after startup.

Still have LEDs problem on Windows 10 with Push2. How to reproduce:
1) Set the LEDs level to minimum (lets say 14%) on Push2 via Setup button
2) Turn Off Push2
3) Turn On Push2
4) Start Bitwig 3.3
5) LEDs are very bright
6) Go to SETUP in Push2... LEDs still shows 14%, but they are still very bright (as at 100%)
7) Move the LEDs knob on Push2
Brighness goes back to 14%

Thanks in advance!

[thetechnobear]

thanks - the buttons now seem to get lit up

unfortunately, though, still if I switch to the clips/session mode - often when I go back to notes I still have the pads illuminated with clips colours. I have to press all the pads to get the 'scale colours' back.

[moss]

[*]Fixed: LEDs and controls did not update on Macos 11 on startup. All states are now flushed 10s after startup.

Still have LEDs problem on Windows 10 with Push2. How to reproduce:
1) Set the LEDs level to minimum (lets say 14%) on Push2 via Setup button
2) Turn Off Push2
3) Turn On Push2
4) Start Bitwig 3.3
5) LEDs are very bright
6) Go to SETUP in Push2... LEDs still shows 14%, but they are still very bright (as at 100%)
7) Move the LEDs knob on Push2
Brighness goes back to 14%

Thanks in advance!

I think I know what the issue is. Could you please test this?
http://mossgrabers.de/stuff/DrivenByMos ... -Alpha.zip

[artsense]

I think I know what the issue is. Could you please test this?
http://mossgrabers.de/stuff/DrivenByMos ... -Alpha.zip

problem solved
thanks a lot man! you fixed both my problems so fast!

[PrElektra]

Dear Mr Mossgraber,

I have previously, without any issues been using your script (for which I am most thankful to you - truly amazing work!) with the Native Instruments KK S49 mk I keyboard. Since some time back there is no way I can make the script start (the ”power” button never shifts to orange) and there is no connection to the keyboard at all. At one occasion it actually did work for some reason but I do not know what I did different to make that happen... Now it seems impossible again no matter what I do!
I have tried to go back to older versions but the problem seems to persist.
Would you have any idea what to try?

Driven by Moss 10.9.1 (from November 15)
Bitwig 3.2.8 and later 3.3 on Win 10
NiHostIntegrationAgent 1.10.1.152
NiHardwareService 2.6.1.532

Kind regards // Svante

The implementation for the Mk I does directly access USB and does not use the NI services. On the contrary it can conflict with them. Try to stop them and see if it works.

That was it! Many tanks for the quick response - you are truly the king of controllers!
(Makes me feel a little ashamed that I didn’t even think of stopping the services myself...)

Best wishes,

Svante

[xtreme sounds]

hi a new Bitwig bugfix was released do you think they fixed the issue with layers in this update?

[moss]

thanks - the buttons now seem to get lit up

unfortunately, though, still if I switch to the clips/session mode - often when I go back to notes I still have the pads illuminated with clips colours. I have to press all the pads to get the 'scale colours' back.

Hmm, yes I can reproduce that but I am afraid that is one for Bitwig. On the same machine it works fine with my Reaper version, so it is not a general issue. No idea how the OS can influence the caching algorithm of Bitwig but who knows...

[thetechnobear]

thanks - the buttons now seem to get lit up

unfortunately, though, still if I switch to the clips/session mode - often when I go back to notes I still have the pads illuminated with clips colours. I have to press all the pads to get the 'scale colours' back.

Hmm, yes I can reproduce that but I am afraid that is one for Bitwig. On the same machine it works fine with my Reaper version, so it is not a general issue. No idea how the OS can influence the caching algorithm of Bitwig but who knows...

yeah, I thought this might the case - and did raise this with Bitwig, and they were interested
but of course, I could not give them any details about which part of their api you are using.
perhaps you could liase with them??! (Im not sure I can add much)