DrivenByMoss - Bitwig extension for lots of controller devices (and more)

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Thu Apr 30, 2020 12:28 pm

heffalumps_nwoozles wrote:
Thu Apr 30, 2020 10:28 am
Hello, Thanks so much for your scripts! I have been using them for years now.
For the first time, I'm having major problems after upgrading to version 3.1 for the Akai APC40mkII.
None of the clips launch buttons light up when they contain clips. I cannot start or stop clips from the clip launcher. The volumes work, as well as the global Play, Pan, record, solo...
But nothing from the clip pad buttons.
When reopening Bitwig, the scene launch buttons are lit (rows 1,2,4 and 5, but not 3).
Previously, I recall needing to press SHIFT+SceneLaunch(top row) in order to enter the normal clip launch mode. Now that button press combination has no effect.
Thanks for your help! I know you must be busy with version 3.2, I hope we don't get left behind on 3.1 because I can't afford to renew my Bitwig license at the moment.
Are you running Bitwig 3.1.3 and DrivenByMoss 8.98 ?

KVRist
116 posts since 6 Apr, 2020

Post Fri May 01, 2020 12:53 pm

tslays wrote:
Mon Apr 27, 2020 9:14 pm
moss wrote:
Sun Apr 26, 2020 11:12 am
I just released DrivenByMoss 8.98 as well as a 9.0 Beta version, which fixes some issues with API changes in Bitwig 3.2.

Get it from http://mossgrabers.de

8.98
  • Requires Bitwig 3.1.3
  • All devices
    • Fixed: Sometimes non-existing notes appeared when switching sequencer pages
  • OSC
    • New: Added /device/parameters {0,1}
    • Fixed: OpenStageControl template: Fixed touch commands on faders
9.00 Beta 3
  • Requires Bitwig 3.2 Beta 3
  • Known Issues: OSC User parameters are broken
  • All devices
    • Fixed: Grid pads did only play MIDI notes but did not execute secondary function - necessary adaption to API 11
  • Push
    • Fixed: User parameters did not display infomation (name, value, ...), modulated value still missing - necessary adaption to API 11
    Enjoy!
Tested with 3.2 Beta 3 and 9.00 Beta 3: Launchkey Mini MK3 and Launchpad Mini Mk3 do work again in the drum modes.

Thanks!!
Tested the Poly Sequencer on the Launchpad Mini MK3 and I cannot input any notes. This might be one more bug.

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Sun May 03, 2020 6:25 am

strovoknights wrote:
Thu Apr 30, 2020 8:40 am
Hi,Mr.Moss.
I love DrivenByMoss and MCU Devices.
I have X-Touch One and Platform Nano.but I cna't previous /next Parameter Pages.
I can move 1 parameter,not prameter Pages.
Please move next page,as Platform M+ etc like as Standard MCU Devices .
Please add previous/next parameter bank pages.
Platform Nano has 4 Knobs and swiching 5-8 knobs .
Its very usefull.
Please add new features.
Thanks for read.
I love DrivenByMoss.and thanks for your hard work!
You can already do that with the X-Touch One if you sacrifice 2 buttons, e.g. F1 and F2:

1) Press Stop + Press the edit knob to enter the configuration mode
2) Make sure that you have selected the "MCU user" mode.
3) Keep F1 pressed and select "CHAN <" with the edit knob.
4) Keep F2 pressed and select "CHAN >" with the edit knob.
5) Press the edit knob 3 times to leave configuration mode

F1 will now select the previous page, and F2 the next.

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Sun May 03, 2020 6:34 am

moss wrote:
Thu Apr 30, 2020 12:28 pm
heffalumps_nwoozles wrote:
Thu Apr 30, 2020 10:28 am
Hello, Thanks so much for your scripts! I have been using them for years now.
For the first time, I'm having major problems after upgrading to version 3.1 for the Akai APC40mkII.
None of the clips launch buttons light up when they contain clips. I cannot start or stop clips from the clip launcher. The volumes work, as well as the global Play, Pan, record, solo...
But nothing from the clip pad buttons.
When reopening Bitwig, the scene launch buttons are lit (rows 1,2,4 and 5, but not 3).
Previously, I recall needing to press SHIFT+SceneLaunch(top row) in order to enter the normal clip launch mode. Now that button press combination has no effect.
Thanks for your help! I know you must be busy with version 3.2, I hope we don't get left behind on 3.1 because I can't afford to renew my Bitwig license at the moment.
Are you running Bitwig 3.1.3 and DrivenByMoss 8.98 ?
Just to be sure I gave it a spin and it works fine here.

KVRer
2 posts since 4 May, 2020

Post Mon May 04, 2020 1:59 pm

Hi, guys!
I'm experiencing some issues when using APC40 mk2 with Bitwig 3.1.2 (win10) running Moss script 8.9.8.
So, the issue is I cant change resolution neither in Drum, nor in Sequencer mode upon clicking on "Stop all clips" button, just like manual says. Its just stop corresponding row of clips instead, which is not okay. Has anyone experienced such issues? Thanks in advance

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Tue May 05, 2020 2:55 am

Farmatique wrote:
Mon May 04, 2020 1:59 pm
Hi, guys!
I'm experiencing some issues when using APC40 mk2 with Bitwig 3.1.2 (win10) running Moss script 8.9.8.
So, the issue is I cant change resolution neither in Drum, nor in Sequencer mode upon clicking on "Stop all clips" button, just like manual says. Its just stop corresponding row of clips instead, which is not okay. Has anyone experienced such issues? Thanks in advance
Hmm, seems this feature got lost somehow. Will fix it...

KVRer
2 posts since 4 May, 2020

Post Tue May 05, 2020 11:23 am

moss wrote:
Tue May 05, 2020 2:55 am
Farmatique wrote:
Mon May 04, 2020 1:59 pm
Hi, guys!
I'm experiencing some issues when using APC40 mk2 with Bitwig 3.1.2 (win10) running Moss script 8.9.8.
So, the issue is I cant change resolution neither in Drum, nor in Sequencer mode upon clicking on "Stop all clips" button, just like manual says. Its just stop corresponding row of clips instead, which is not okay. Has anyone experienced such issues? Thanks in advance
Hmm, seems this feature got lost somehow. Will fix it...
Thanks a lot Moss, for all the effort you put in that outstanding script!

User avatar
KVRist
293 posts since 26 Mar, 2014 from Moscow

Post Tue May 05, 2020 11:25 am

Hi, Moss. A question about Play/Stop button in Flexi and OSC scripts. There only separate commands for each of action - or play or stop. I just trying to get the same behavior like Spacebar on qwerty. Also I see "/playbutton" in the OSC script (even in "OSCTest.maxpat") but it's actually not presented in script. I see "unknown OSC command" via Bitwig console. I hope the API has this command and hope you can implement it for Flexi and OSC.

Thank you for your work.

KVRer
2 posts since 6 May, 2020

Post Tue May 05, 2020 8:36 pm

Hey Moss, thank you for these. I use the APC40mkii quite a bit and it’s so awesome. I’m curious if you plan to add the Launchpad Pro mk3? It’s an awesome piece and I’d love to use it with Bitwig.

KVRer
1 posts since 4 May, 2020

Post Wed May 06, 2020 1:24 am

hey
Can you please add Presonus ATOM controller for your next update? please please please :pray:
I'm trying to map it all by myself on the general-flexi but my ADHD just wont let me do it - :dog:
there is an bitwig official extension for the atom controller but it only works with half of the features

cheers

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Wed May 06, 2020 2:33 am

mrfrenkie wrote:
Tue May 05, 2020 11:25 am
Hi, Moss. A question about Play/Stop button in Flexi and OSC scripts. There only separate commands for each of action - or play or stop. I just trying to get the same behavior like Spacebar on qwerty. Also I see "/playbutton" in the OSC script (even in "OSCTest.maxpat") but it's actually not presented in script. I see "unknown OSC command" via Bitwig console. I hope the API has this command and hope you can implement it for Flexi and OSC.

Thank you for your work.
I just tried /playbutton and it works fine here. Are you using the latest DrivenByMoss release?

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Wed May 06, 2020 2:34 am

Nastynachos wrote:
Tue May 05, 2020 8:36 pm
Hey Moss, thank you for these. I use the APC40mkii quite a bit and it’s so awesome. I’m curious if you plan to add the Launchpad Pro mk3? It’s an awesome piece and I’d love to use it with Bitwig.
Yes, hope to get one early June.

User avatar
KVRAF

Topic Starter

2862 posts since 13 May, 2004

Post Wed May 06, 2020 2:34 am

Kasper3030 wrote:
Wed May 06, 2020 1:24 am
hey
Can you please add Presonus ATOM controller for your next update? please please please :pray:
I'm trying to map it all by myself on the general-flexi but my ADHD just wont let me do it - :dog:
there is an bitwig official extension for the atom controller but it only works with half of the features

cheers
Sorry, don't have an ATOM.

KVRer
2 posts since 6 May, 2020

Post Wed May 06, 2020 6:20 am

moss wrote:
Wed May 06, 2020 2:34 am
Nastynachos wrote:
Tue May 05, 2020 8:36 pm
Hey Moss, thank you for these. I use the APC40mkii quite a bit and it’s so awesome. I’m curious if you plan to add the Launchpad Pro mk3? It’s an awesome piece and I’d love to use it with Bitwig.
Yes, hope to get one early June.
Awesome! Thanks so much.

User avatar
KVRist
293 posts since 26 Mar, 2014 from Moscow

Post Wed May 06, 2020 7:57 am

moss wrote:
Wed May 06, 2020 2:33 am
I just tried /playbutton and it works fine here. Are you using the latest DrivenByMoss release?
DrivenByMoss-9.00-Beta3-Bitwig + Bitwig Studio 3.2 Beta 3 + macOS 10.14.6. The /playbutton triggered directly from "OSCTest.maxpat". All other commands are working fine

Image

I have no idea what i'm doing wrong.


And what's about Flexi? Where can i find this action?

Return to “Controller Scripting”