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

[OdoSendaidokai]

Argh I just released a fix 10.6.4:

• Requires Bitwig 3.2.5+
• Push
  • Fixed: Grid resolution could not be changed in drum modes

The 10.6.4 works great with all Drum* Sequencers on the Push 2.
Thank you very much

[porkloin]

• Launchpad
  • New: Updated documentation images
  • New: Added fixed accent option to the settings
  • New: Fixed accent can be toggled with the yellow pad in the right upper corner of the shift mode

Very nice! @Luis887 this feature should be included now and I updated the Launchpad docs and diagrams to show how to toggle it on and off.

[porkloin]

One thing I've noticed the more that I use the scripts is that the faders in "device mode" work great for anything that is a knob or linear value, but the results are really inconsistent with things that have a finite number of settings. Waveform types on an oscillator in Phase-4/FM-4 is a great example of this. It'd be awesome if we could use the device mode to toggle between those modes in the device/fader view, but I'm not really sure how that would work :\

[SarieDretsBWLinux]

Hi Jurgen! I am the guy who asked if there is a way to map my controller knobs to the instrument layer macros in a "soft controller assignment" way (as its called in the Bitwig users guide), keeping them mapped to the 2x4 while parameters change following the macros of the selected layer. Is this anyway possible by writing some code using the API scripting reference? Thks.

[Luis887]

Thanks @moss and @porkloin!!

[moss]

One thing I've noticed the more that I use the scripts is that the faders in "device mode" work great for anything that is a knob or linear value, but the results are really inconsistent with things that have a finite number of settings. Waveform types on an oscillator in Phase-4/FM-4 is a great example of this. It'd be awesome if we could use the device mode to toggle between those modes in the device/fader view, but I'm not really sure how that would work :\

I am afraid there is no solution for that.

[moss]

Hi Jurgen! I am the guy who asked if there is a way to map my controller knobs to the instrument layer macros in a "soft controller assignment" way (as its called in the Bitwig users guide), keeping them mapped to the 2x4 while parameters change following the macros of the selected layer. Is this anyway possible by writing some code using the API scripting reference? Thks.

If I understand you correctly you want to have 4 user parameters and 4 remote control parameters. Sure you can do that, simply define page sizes of 4.
Post API questions simply in this forum (but not in this thread).

[xtreme sounds]

Thanks Moss

Were you able to look into the Fire issue regarding losing the function of the mute buttons in the drum sequencer when adding new samples to the individual pads in Bitwig?

See my answer above.

Thanks I didnt see it earlier. The workaround I found is to load a drum machine preset and replace the samples in the sampler that is loaded in the pad instead.

[porkloin]

One thing I've noticed the more that I use the scripts is that the faders in "device mode" work great for anything that is a knob or linear value, but the results are really inconsistent with things that have a finite number of settings. Waveform types on an oscillator in Phase-4/FM-4 is a great example of this. It'd be awesome if we could use the device mode to toggle between those modes in the device/fader view, but I'm not really sure how that would work :\

I am afraid there is no solution for that.

I had a feeling you've probably already looked into it. Thanks anyway!

[Luis887]

Hi Moss is posible to Port chord Mode from launchpad pro mk3 yo launchpad x ? Thanks for you hard work

[moss]

Hi Moss is posible to Port chord Mode from launchpad pro mk3 yo launchpad x ? Thanks for you hard work

Possible yes. But not sure if I ever want to tackle this. Never was a fan of preconfigured chords and it involves some head-scratching.

[Luis887]

Ok thanks!

[avoca]

Hi Moss,

On the Launchpad Pro Mk3, if for example I am in Drum64 Note Mode, and I go to Session Mode to start recording on a given pad, and then I go back to Note Mode, I am brought to Scale Mode. (It takes 3 presses of "Note" to get back to Drum64). Is there a way to make it to go straight back to the mode I was in, i.e. Drum64 mode?

Thanks, and many thanks for your great extension.

Windows 7 and Ubuntu 20.04
Bitwig 3.2.7
Driven By Moss 10.6.4

[jmg8]

Hey Moss.

I have an odd behaviour with my Push 2 in Bitwig.
When I have a synth in monophonic mode and I press a pad (keep it held down) then press a second pad all sounds good and as expected. But now when I release that second pad the sound reverts to the first pad (that is still being held down) HOWEVER the velocity is super low. I have tried with accent on/off and the behaviour is the same. But if I go to Ableton and try it, it works correctly. The behaviour I am expecting (and how it works in other DAWs I've tested) when you keep the first note held and press and release a second note, the sounds should revert back to the first note at the same velocity.
So I tested something else to be sure it was the Push 2 that was doing this. I simulated the same keypresses using Bitwig's piano roll and it works normally. So it just seems to be an issue with Push 2 only.
Please could you advise me? Maybe I have some setting wrong?

Thank you

[moss]

Hi Moss,

On the Launchpad Pro Mk3, if for example I am in Drum64 Note Mode, and I go to Session Mode to start recording on a given pad, and then I go back to Note Mode, I am brought to Scale Mode. (It takes 3 presses of "Note" to get back to Drum64). Is there a way to make it to go straight back to the mode I was in, i.e. Drum64 mode?

Thanks, and many thanks for your great extension.

Windows 7 and Ubuntu 20.04
Bitwig 3.2.7
Driven By Moss 10.6.4

Thanks, will be fixed in the next update!