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

[Trovarsi]

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

[mesamask]

I think for the Generic Flexi the functionality of the buttons is reversed.

ButtonToggleOrPush.png

The buttons on my controller are doing the exact opposite, toggling when set to "push" and vice-versa.
(Bitwig v5.3.2, DrivenByMoss v24.7.1, Windows)

[xtreme sounds]

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

[mesamask]

... 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. ...

That's quite ironic lol. Was testing this because I thought what you're saying might be related to what I was posting just before you (toggle/push behavior of buttons).
Turns out it's the exact opposite for me, using buttons to step through parameter pages works fine for me (if what is shown below is what you want to do):

testings.gif

I was using "Device: Select Next Parameter Page" for that, maybe you were using a different one? But the Parameter Pages are a one way street, in order to go back a second button is required (with "... Previous ... Page").

The irony is that in contrast to you it's not working for me when I'm trying to use knobs for that

[xtreme sounds]

BUttons work for previous and next paramaters but not 'scroll'. Any way to get it to work with scroll commands? and I gues the previous poster would like previous and next to work with knobs.

[xtreme sounds]

a second issue is what does set volume mean? I see a lot of parameters that say set. not familiar with that

[xtreme sounds]

I made a pretty good flexi script for the launch control XL for device management that I feel fits my workflow in Bitwig. If anyone wants it. I have attached it.

1-8 upper right 8 device knobs
9-12 lower right 4 knobs volume send fx 1-4
13-20 8 faders 1-8 tracks levels
21-28 top buttons select track
29-36 bottom buttons scenes
37-38 send select buttons (track page change)
39-40 device select buttons (prev next device)
41. Device button (open browser)
42. Mute button selected
43 Solo button selected
44 Arm button selected
45 bottom 8 right knob (switch devices)
46 bottom 7 knob (Mastercrossfader)


other right knobs are free to use

[illdrik]

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 ?

[pc999]

Nevermind

[mixnar]

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

[moss]

Hi Moss, I just found myself in a situation that happens frequently when recording where the clip section in bitwig is closed on screen, and I want to open it but i'm playing chords and the pc mouse focus is in a vst gui. This happens a lot and I usually tap on my touchscreen and then press ctrl and tab to show the clips and then back to the push to add a clip before recording.
Not very fluid. My question is isn't there a way to show the clip launcher on screen from the push? If not maybe holding "shift" + "session" buttons on the push could show it on the arranger page?

You can press Device and then toggle "Window" to close the plugin GUI.

Lastly would it be possible to add the project time in seconds just above the "Audio Engine" readout of the display when you press "master" on the push?

Noted.

[moss]

Is it possible to make the Flexi extension work dynamically with CCs? As in, I want to assign CCs from a controller to device parameters, but I only want the CCs to control device parameters on the selected track. So when I switch tracks, the same CCs can control parameters on the current selected track and not the previously selected track.

Yes, by using track remote controls. In Generic Flexi look at the functions found in the "Track Remotes" list.

Thanks, but I was hoping to avoid using remotes so I can have more than 8 CCs available simultaneously, and I’m using the MIDI fighter twister so I have the knobs setup as dual function (for pitch and velocity on a sequencer, for instance.). To make this work with remotes I have to scroll through many pages and can only utilize 8 knobs at a time.

I am afraid there is currently no solution for this (except mapping each and every control directly in a project).

[moss]

Well hello again. Since last update there are 3 things I need to write here about.
- When Push 2 On/Off button is pressed to turn it on: random midi or audio channels including also the master their faders are being repositioned to a negative level.

I cannot reproduce that. Any more hints? What are you doing exactly. Which OS?

-The Add device button in previous update was not working as intended by the Manual description,
which by the last 2 updates is fixed but: when adding the device instead of the browser being closed it still reopens itself. A momentary fix is pressing add device button multiple times or for a longer period.

Please note the exact steps you take (which buttons you press and which devices are on the track).

-The new implementation of giving as the opportunity to use the arrows to scroll through tracks by page or one at a time would be much more meaningful to: when pressing the arrow buttons it also chooses the track.

That was not what "people" were asking for. To select a track simply press the button below it.

[moss]

Hello, I'm having a major frustration using the Push 1 with Bitwig with live clip recording.

I want to be able to record a clip from the Push and have it automatically stop recording the clip at the end.

Right now, if I press New Clip, during playback, it makes the new clip and starts recording it, but continues to record, so if I am recording live it can be very easy to record overlapping notes on accident which then break the entire process, as they can't be undone without undoing the entire clip recording.

Am I missing something? It seems pretty much impossible to use the push in a live loop recording process with bitwig as is, which is odd, since that is supposedly a major strength of both Bitwig and the Push. But not together at all it seems.

Yes, one of my frustrations as well. I talked to Bitwig several times about this but so far no solution.

[moss]

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.

Press the ON button in the left upper / corner. Normally, it should turn on itself as soon as you select the MIDI in-/output.