Did you update the OXI to the latest Firmware? If you did, try to add the extension manually by choosing "Add controller" at the bottom of the port list.Trovarsi wrote: Sat Mar 01, 2025 9:38 pm Hi!When I updated to 24.7.1 and connected the OXI One. I am not seeing any of the settings that you implemented. I do see it as a device giving the option of selecting OXI ONE Port 1 or Port 2. No other information is showing and I'm not able to see/use any of the things you implemented. I must have skipped a step but I don't see it mentioned in any of the videos. Do I need to change some settings on the OXI?
Just for more information - when I connect my Push 3, it showing all the settings you mentioned in my video, and are working well. Please help.
Running it on: Mac M1 Ventura 13.6
DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
The naming might be confusing. This is not about the behaviour of the function but what the button sends.mesamask wrote: Mon Mar 10, 2025 12:32 pm I think for the Generic Flexi the functionality of the buttons is reversed.
The buttons on my controller are doing the exact opposite, toggling when set to "push" and vice-versa.
Push means: you press the button down and it sends 127, you release it, it sends 0
Toggle means: you press the button down and it sends 127, you release it, it sends nothing. You press it again, it sends 0 (and as well nothing on release).
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
"Scroll" functions are for knobs. "Select next/previous" for buttons. Use the later.xtreme sounds wrote: Thu Mar 13, 2025 7:53 pm HI sir. I am programming the Flexi script. It appears the control Device scroll devices/parameters doesnt work when assigning to a button . any way that we can do that so that each push of a button scrolls to a different device or parameter page? the knob works but not a button.
a second isue is I tried applying clip record command and nothing happens. after applying the track record then every time i pressed play it would record. some unexpected behavior here
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Sorry, don't understand your question. Seems you used it successfully in your XL mapping?!xtreme sounds wrote: Fri Mar 14, 2025 12:05 pm a second issue is what does set volume mean? I see a lot of parameters that say set. not familiar with that
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
I am afraid this features is not available. But you can use the edit mode instead. I just did a video about it:illdrik wrote: Fri Mar 14, 2025 2:04 pm hello moss, i'm a freshly new push2 user associated with bitwig thanks to your amazing work. many thanks for this.
i have a sort of request/question concerning the 16 level of velocity in drum mode.
maybe i mess it but didn,'t found the possibility to have the 16 level velocity in live like it is in ableton ? i explain : you can indeed change the velocity in accent mode but only during a recording clip on step sequence, is it possilbe to get this 16 level mpc style mode to actualy live record and listen the selectionned pad ?
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
The problem is that the sysex command for configuring this is not documented and quite complex.mixnar wrote: Wed Mar 19, 2025 8:09 pm Hi there,
I have a problem with the pad sensitivity on my Push3 in Bitwig and in Reaper. Compared to playing a vst instrument in Ableton, the received velocity-curve from thePush3 in Bitwig and Reaper seems really strange. It's much harder to play softer without having notes not played. It also seems harder to play mid-velocity. Changing the pads-settings (sensitivity, gain, dynamics) doesn't make a difference or makes it only worse (notes are still not played or really loud). Is there a pad-setting that mirrors the standard pad-settings from Push3 in Ableton?
Anyone else experiencing this?
Thanks and greetings, M
It might be possible to configure it via Ableton but I did not test if the device keeps the settings.
-
- KVRist
- 35 posts since 4 Aug, 2014
Ah ok I see what I was doing wrong I had the midi channel selected for the motu microlite i am using active in a separate box. When I turned it off I was able to turn the Generic Flexi on and access all the features.moss wrote: Fri Mar 21, 2025 8:06 pmPress the ON button in the left upper / corner. Normally, it should turn on itself as soon as you select the MIDI in-/output.Strangetown wrote: Fri Feb 28, 2025 11:37 am I was hoping to maybe use the Generic Flexi component of the Bitwig extension to obtain more control over a hardware workstation/synth the Gem S3 turbo.However in Bitwig Studio 5.3 this is all you see:
Generic Flexi.jpg
There is no configuration available or load/save etc. I would be grateful for any assistance.
- KVRist
- 143 posts since 20 Nov, 2013
Thanks already for the explanation, Moss. Well I had no intentions to embarrass myself, so I made very sure I knew what I was talking about. It did the opposite. If I had the chance to make a video of it, I would've provided that.moss wrote: Fri Mar 21, 2025 8:18 pm The naming might be confusing. This is not about the behaviour of the function but what the button sends.
Push means: you press the button down and it sends 127, you release it, it sends 0
Toggle means: you press the button down and it sends 127, you release it, it sends nothing. You press it again, it sends 0 (and as well nothing on release).
There was also that strange case where pressing a button on the controller simultaneously (next to the actually assigned target) triggered the "Undo" button on the topbar of Bitwig, for whatever weird reason. Might have been the actual cause why the buttons were functioning in a kind of reversed way.
This was the point when I decided to report it, because it very much looked there must be something wrong.
Meanwhile I got a very different controller setup, but I'll review and try to recreate this once I got time for.
Enjoy your Sunday!
- KVRer
- 1 posts since 24 Mar, 2025 from Berlin, Germany
Hi there! I am not able to dock floating expanded device views into the main window using Generic Flexi (Rel. 29.01.2025).
I thought it was due to the setting: Device ‘Floating window follows current track|, but that doesn't seem to be the cause.
Have I overlooked something? Thanks and greetings in advance.
I thought it was due to the setting: Device ‘Floating window follows current track|, but that doesn't seem to be the cause.
Have I overlooked something? Thanks and greetings in advance.
-
- KVRer
- 25 posts since 28 Mar, 2007
Thanks for you response, too bad then. Unfortunately configuring via ableton is not an option, the push3 doesn't remember the settings.moss wrote: Fri Mar 21, 2025 8:30 pmThe problem is that the sysex command for configuring this is not documented and quite complex.mixnar wrote: Wed Mar 19, 2025 8:09 pm Hi there,
I have a problem with the pad sensitivity on my Push3 in Bitwig and in Reaper. Compared to playing a vst instrument in Ableton, the received velocity-curve from thePush3 in Bitwig and Reaper seems really strange. It's much harder to play softer without having notes not played. It also seems harder to play mid-velocity. Changing the pads-settings (sensitivity, gain, dynamics) doesn't make a difference or makes it only worse (notes are still not played or really loud). Is there a pad-setting that mirrors the standard pad-settings from Push3 in Ableton?
Anyone else experiencing this?
Thanks and greetings, M
It might be possible to configure it via Ableton but I did not test if the device keeps the settings.
-
- KVRer
- 11 posts since 21 Sep, 2022
Any chance that you will take a round and modify the AKAI Fire with a few more options for Reaper ?
For instance - it would be great if we could use the USER 2 mode - at the moment it is bound to Project and Track parameter - but if I am not mistaken, Project and Track and Parameter are not supported in Reaper but Bitwig - so why not use it for sending Midi CC Values for instance.... this way the Fire could be used for some more stuff then now.. for instance controlling "last touched parameter". maybe you could make some configuration window like for USER 1 but more generic...
And another thing would be nice - can we get an option - maybe in the settings - to configure the pads on the "shift view" ?
this way we could add some functions to control reaper on our own for pads that are unused right now...
Cheerz the Heavy
For instance - it would be great if we could use the USER 2 mode - at the moment it is bound to Project and Track parameter - but if I am not mistaken, Project and Track and Parameter are not supported in Reaper but Bitwig - so why not use it for sending Midi CC Values for instance.... this way the Fire could be used for some more stuff then now.. for instance controlling "last touched parameter". maybe you could make some configuration window like for USER 1 but more generic...
And another thing would be nice - can we get an option - maybe in the settings - to configure the pads on the "shift view" ?
this way we could add some functions to control reaper on our own for pads that are unused right now...
Cheerz the Heavy
-
- KVRist
- 33 posts since 8 Sep, 2019
Hello Jürgen, for the Push, seeing the played chords on the screen is an excellent idea, but after the Gb4, the notes are no more recognized on my Push 2 and the other keyboards. Weird. Is it a bug ?
-
wimvandenborre wimvandenborre https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=462766
- KVRer
- 21 posts since 18 Apr, 2020
Hey, does the launchcontrol have an option to show the 16 steps at once in stead of 2 pages of 8 for the sequencer mode?
