DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)
-
- KVRist
- 166 posts since 26 Oct, 2007
man - having such a hard time getting this working. updated to new 4.4, with DrivenByMoss 18.1.0. i plugged direct into my comp and everything was working fine. i added an extension cable to the usb, (still powered) and the display works but not the leds. i then tried my original setup, with the one cable, and now the LEDS still don't work! what could it be?
-
- KVRist
- 316 posts since 18 Sep, 2020
Not even NoteStep.isIsSelected()?moss wrote: Sun Oct 23, 2022 7:18 amSorry, no. The only access to the notes is via the sequencing API and there are no states for selected notes.trevormeier wrote: Fri Oct 21, 2022 2:33 pm Is it possible to have the transpose commands just transpose selected notes (instead of the entire clip)?
-
- KVRer
- 15 posts since 28 Feb, 2004
I went through this thread, and I am having the same challenge as this post:
viewtopic.php?p=8003069&hilit=vst#p8003069
But I don't see how that person solved the latching problem. My behavior is the same.
viewtopic.php?p=8003069&hilit=vst#p8003069
But I don't see how that person solved the latching problem. My behavior is the same.
-
- KVRian
- 517 posts since 6 Sep, 2003 from Baltimore, MD
Hi Moss,
Firstly thanks for this great update! (as always)
(This is for Push 2) I'm not sure if this is a setting on my side that I got wrong, but only the LED of the active buttons are now lighting up (even at 100% LED brightness). Before, even the inactive buttons were lit up, so you can read them.
You can see in the photo what I mean - only 'setup' and 'note' are readable because they are currently selected / active. Looks like not everyone had this issue so I'm curious what you think it might be. Thank you!
Firstly thanks for this great update! (as always)
(This is for Push 2) I'm not sure if this is a setting on my side that I got wrong, but only the LED of the active buttons are now lighting up (even at 100% LED brightness). Before, even the inactive buttons were lit up, so you can read them.
You can see in the photo what I mean - only 'setup' and 'note' are readable because they are currently selected / active. Looks like not everyone had this issue so I'm curious what you think it might be. Thank you!
You do not have the required permissions to view the files attached to this post.
http://www.youtube.com/reflekshun
Music Producer / Audio Engineer
Music Producer / Audio Engineer
-
- KVRian
- 517 posts since 6 Sep, 2003 from Baltimore, MD
Please ignore ^
For anyone who has this issue, make sure the power adapter is plugged in and turned on for your push 2. Silly me
For anyone who has this issue, make sure the power adapter is plugged in and turned on for your push 2. Silly me
http://www.youtube.com/reflekshun
Music Producer / Audio Engineer
Music Producer / Audio Engineer
-
- KVRer
- 2 posts since 7 Mar, 2022
hi moss! i have a situation with my akai fire, after bitwig's final update (4.4.2) - the controller does not turn off anymore after closing bitwig. anybody else stumbled upon this situation? any ez fix solutions?
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
Seems that's a bug. It checks for a real latching button only. Will be fixed in the next update.superboy wrote: Tue Oct 25, 2022 3:27 am Yes thank you! I did watch this, but I must have missed that part. So the only function I can assign are in the modes. But now, how do I make it latch? I tried both absolute and absolute toggle, and both behave the same way. When i press the button down it goes to 127 and when i let go it goes back to 0. BUt the toggle shouldn't do this, it should stick to one setting and then go back to 0 with another click. I did not see in any video you showing how to do a latch.
edit, i keep trying to use user set or user toggle parameter, and both do the same thing (neither will latch).
I should also mention I am trying to map the controller buttons/faders to the VST parameters. I noticed earlier in this thread someone else having issues with that, which led to you adding the "user toggle parameter".
I guess I should also add these commands to the "normal" parameters and not only the user ones.
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
No. In case a device is detected by multiple extensions simply add one of them and then you can switch between the implementations with the drop down list on the extension.dcarmich wrote: Wed Oct 26, 2022 4:42 am I'm thinking about getting a Launchpad Pro Mk3 myself, but prefer the simpler implementation of Wes Koop's script (https://github.com/weskoop/Launchpad-Pro-Mk3-for-Bitwig).
Would there be any issues with installing DrivenByMoss to use with other controllers along with his script for the Launchpad specifically?
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
I have no plans for it.
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
Plug in power (and stay away from extension cables).function wrote: Thu Oct 27, 2022 5:46 am man - having such a hard time getting this working. updated to new 4.4, with DrivenByMoss 18.1.0. i plugged direct into my comp and everything was working fine. i added an extension cable to the usb, (still powered) and the display works but not the leds. i then tried my original setup, with the one cable, and now the LEDS still don't work! what could it be?
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
You are right, this info is available for the notes on the current page. But this does not cover all the notes which might be selected in the clip. So, I am not sure if this would be more confusing than helpful.minortom wrote: Thu Oct 27, 2022 7:33 amNot even NoteStep.isIsSelected()?moss wrote: Sun Oct 23, 2022 7:18 amSorry, no. The only access to the notes is via the sequencing API and there are no states for selected notes.trevormeier wrote: Fri Oct 21, 2022 2:33 pm Is it possible to have the transpose commands just transpose selected notes (instead of the entire clip)?
- KVRAF
- Topic Starter
- 4869 posts since 13 May, 2004
I can reproduce that (for all my controllers). Will ask support...mastercc wrote: Sun Oct 30, 2022 9:15 pm hi moss! i have a situation with my akai fire, after bitwig's final update (4.4.2) - the controller does not turn off anymore after closing bitwig. anybody else stumbled upon this situation? any ez fix solutions?
Is this Windows?
-
- KVRist
- 316 posts since 18 Sep, 2020
Indeed, though I think what really makes this a no-go is that a step can contain multiple notes, each in its own independent state of selectedness. So my suggestion is moot, API allows access to steps but not to actual notes.moss wrote: Mon Oct 31, 2022 12:07 pmYou are right, this info is available for the notes on the current page. But this does not cover all the notes which might be selected in the clip. So, I am not sure if this would be more confusing than helpful.minortom wrote: Thu Oct 27, 2022 7:33 amNot even NoteStep.isIsSelected()?moss wrote: Sun Oct 23, 2022 7:18 amSorry, no. The only access to the notes is via the sequencing API and there are no states for selected notes.trevormeier wrote: Fri Oct 21, 2022 2:33 pm Is it possible to have the transpose commands just transpose selected notes (instead of the entire clip)?
-
- KVRer
- 2 posts since 7 Mar, 2022
thank you for your support!moss wrote: Mon Oct 31, 2022 12:13 pmI can reproduce that (for all my controllers). Will ask support...mastercc wrote: Sun Oct 30, 2022 9:15 pm hi moss! i have a situation with my akai fire, after bitwig's final update (4.4.2) - the controller does not turn off anymore after closing bitwig. anybody else stumbled upon this situation? any ez fix solutions?
Is this Windows?
