Latest News: Bitwig Updates Bitwig Studio to 5.2
DrivenByMoss: Bitwig extension for many hardware controllers (version 23.2.1)
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
Version 8.94 is online!
Get it from http://mossgrabers.de
Get it from http://mossgrabers.de
- Generic Flexi
- New: The MIDI channel for the keyboard (or pads if it is a pad controller) can be explicitly set (previously it was fixed to channel 1). It can also be turned off or set to all. If a MIDI note is mapped to a function on this MIDI channel, the note is blocked from being played. Note: If you have selected All for the channel the note is blocked on all channels!
- New: Modulation Wheel (CC 01), Sustain Pedal (CC 64) and Pitchbend were previously automatically routed to Bitwig. You can now turn them off individually if you want to map them to something else.
- Launchpad
- New: Option to remove the master and group-master tracks from the track bank (requires restart of extension).
- New: Pro: Disabled Delete button if used without button combination to prevent accidential deletions.
- OSC
- Fixed: Changing output server/port did still not work.
- KVRian
- 512 posts since 22 Aug, 2014
-
- KVRer
- 14 posts since 19 Nov, 2015
No Problem.moss wrote: ↑Thu Mar 26, 2020 8:08 amSorry, you totally lost me. Could you please describe step by step what you are doing and what is going wrong? Thanks.bronko83 wrote: ↑Wed Mar 25, 2020 5:20 pm so the user mappings are completely empty. I tried to find it in the extension code but its hard to follow the references just reading on github. The modwheel seem to trigger the ToggleTrackBanksCommand in Track and Volume Mode. In Parameter Mode it is toggeling the window of a device when selected. But I cannot find where the wiring goes wrong.
Edit: Ok I guess its the BUTTON_MAIN_ENCODER funtionality that the modwheel is asigned to. I assume in the buttonChange method you get the modwheel cc value = 1 which equals to that encoder button value in the button map and executes the actions?
System:
Native Instruments S61 mk1
Bitwig 3.1.3
DrivenByMoss 8.94
1. Start Bitwig, Keyboard is correctly setup with the extension in Controller Settings
2. Create new Project, Keyboard shows "Please select a device"
3. Touch or move ModWheel-Strip
4. Everytime the modwheel sends a command Bitwig is performing the same action that the big main button would do on pressing it down. (Depending on the current selected mode of the keyboard, open/close device window or jump between effect tracks and instrument track)
So I think I narrowed it down to the Kontrol1ControlSurface.
Here you assign the BUTTON_MAIN_ENCODER to the Value 1
Code: Select all
/** Clicking the main encoder. */
public static final int BUTTON_MAIN_ENCODER = 1;
Code: Select all
public void buttonChange (final int usbControlNumber, final boolean isPressed)
{
final ButtonID buttonID = BUTTON_MAP.get (Integer.valueOf (usbControlNumber));
Hope that makes it clearer
-
- KVRian
- 909 posts since 7 Nov, 2017
Just stabbing around in the dark: What other controllers do you have hooked up to Bitwig? I wonder if something might be "stealing focus" from the remap function in Bitwig, in some way that's preventing the Push knob turns from being "seen" by Bitwig?
I have only two other controllers in my system: one is a MidiFighter Twister (from DJ TechTools), running one of the extension scripts posted here in this forum. The other is a Touche expression controller (by Expressive E) that's being driven by the "Generic MIDI Keyboard" controller that comes with Bitwig.
-
- KVRist
- 76 posts since 10 Mar, 2014
Thnx Yokai. As I arrived at that thought too I deleted all other controllers from Bitwig, including the one for Push 2. Re-added the Push 2 as only controller, but: no difference (also tried with the new 8.94 extension) Except user mode, all other functionality works perfectly.
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
-
- KVRist
- 76 posts since 10 Mar, 2014
@Yokai: already PM'd Moss, I found the solution, my prefs file (...\AppData\Local\Bitwig Studio\prefs) was apparently corrupt!
As soon as I deleted it, Moss' latest extension / user mode works as expected.. I should have thought of that earlier, as I experienced something similar in the past with a certain DAW of a company with a name that starts with an A....
Phew, glad this is sorted now, thanks again for your interest
As soon as I deleted it, Moss' latest extension / user mode works as expected.. I should have thought of that earlier, as I experienced something similar in the past with a certain DAW of a company with a name that starts with an A....
Phew, glad this is sorted now, thanks again for your interest
-
- KVRer
- 3 posts since 28 Feb, 2018
Hi Moss,
I was wondering if the SL MK3 controller extension has a feature for stopping a single clip or a particular scene?
I looked at the Wiki and couldn't find those features, but perhaps they are there. Thank you for the awesome controller extensions!
Dan
I was wondering if the SL MK3 controller extension has a feature for stopping a single clip or a particular scene?
I looked at the Wiki and couldn't find those features, but perhaps they are there. Thank you for the awesome controller extensions!
Dan
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
Sorry, no.dannynyc wrote: ↑Sat Mar 28, 2020 3:18 am Hi Moss,
I was wondering if the SL MK3 controller extension has a feature for stopping a single clip or a particular scene?
I looked at the Wiki and couldn't find those features, but perhaps they are there. Thank you for the awesome controller extensions!
Dan
- KVRist
- 317 posts since 20 Nov, 2006
Any news on Akai Force support?
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
No, don't think that this will happen.
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
Here is the video documentation for 8.94:
https://youtu.be/vwM0qyVeDWE
https://youtu.be/vwM0qyVeDWE