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

[moss]

Hello Moss,

With using Launchpad Pro mk3 and Launchkey mk3 simultaneously and launching a scene makes the clips belonging to that scene light up green slowly flashing on the launchkey. The clips on the Launchpad Pro mk3 will flash but keep their original clip colour. This is when i use the Drivenbymoss scripts for both devices.

When i use the Launchpad Pro mk3 Bitwig script instead of the drivenbymoss script the clips work as expected on the both devices and they turn out green flashing when launched, can this somehow be corrected in the drivenbymoss script?

It is not a deal breaker i will use the bitwig script meanwhile for the Launchpad Pro mk3. But it would be cool to use the both devices with the drivenbymoss script.

I feel somehow being an ass by pointing bugs to you, it is in no way intended for complaining about this awesome piece of work!

Danke schön,

Questionaire.

Thanks for reporting! Will be fixed in the next update!

[moss]

Hello and thankyou for making all these amazing scripts available.

I use the Maschine MK3 script in Bitwig.

In device parameter control I can navigate device pages with the large encoder up/down move. However, it seems to me that they work in the opposite order to how I would expect.

Down moves up the list
Up moves down the list

ie: To get to the first page I have to press the encoder to the down position. To get to the last page I press the encoder to the up position.

Is this intentional? Is there a way to flip it?

Thanks!

It does work the other way round for me. Could it be that you flipped the MIDI CCs in the template? Try to reinstall the latest template from DBM 21.0.0.

[moss]

Maybe pile on to Ticket 174664 with your experience.


 

If someone can give some reproducible steps, this would be very helpful!


 

Apparently my first report got lost, just reported again and received this:

Re: Navigating Remote Pages is broken on Push 1 and 2
Hi Chris​,
​
thanks for the info! If this is something Moss can narrow down in his code, he is in direct contact with our dev team and can report what he thinks is the issue with the API there.

Best regards,
Bitwig Technical Support Team

Is this still happening to you in 5.0.5?

[moss]

DrivenByMoss 21.0.0 is online!

Big feature is Ableton Push 3 support! But there are also many other goodies!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Fixed an exception with controllers not having user parameters.
  • Fixed: Improved feedback of automation modes.
• Generic Flexi
  • Fixed: Switching project/track remote pages was triggered twice.
• HUI
  • New: RecRdyAll toggles rec arm state on all tracks.
  • New: Option+Jog Wheel - Change tempo (press Shift for fine adjustment).
  • New: Control+Jog Wheel - Change loop start (press Shift for fine adjustment).
  • New: Alt+Jog Wheel - Change loop length (press Shift for fine adjustment).
  • Fixed: Clip related function did not work when assigned to F1-F8 buttons.
• MCU
  • New: Shift+RecArm toggles rec arm state on all tracks.
• OSC
  • Fixed: /track/param did trigger project parameters.
• Push
  • New: Added support for Ableton Push 3.
  • New: Push 2: Removed unecessary Rec Arm, Solo and Mute from Cue channel.
  • New: Metronome volume has been moved into the metronome settings mode (long press metronome button).
  • New: Improved session configuration mode. Easier selection of what to show on the display.
  • New: 'Add Track' mode has now 7 favorites for each track type as well as 7 device favorites.
  • Fixed: Push 1: Master volume graphical representation was not missing line if VU mode was active.
  • Fixed: Do not notify tempo value when tempo knob is used in browser mode to scroll results.

Enjoy!

Nice
I am actually quite tempeted by Push3, but the price...

Ìt is a good time to get a cheap Push 2

[guitarfrenzi]

Maybe pile on to Ticket 174664 with your experience.


 

If someone can give some reproducible steps, this would be very helpful!


 

Apparently my first report got lost, just reported again and received this:

Re: Navigating Remote Pages is broken on Push 1 and 2
Hi Chris​,
​
thanks for the info! If this is something Moss can narrow down in his code, he is in direct contact with our dev team and can report what he thinks is the issue with the API there.

Best regards,
Bitwig Technical Support Team

Is this still happening to you in 5.0.5?

Yes> Push 1, Bitwig 5.05, DBM 21.0.0

Behaviour:

Using 'Remote Controls Editor', selecting a page, reflects perfectly on the Push and turning a knob on Push reflects perfectly back to the editor for the page in focus.

Turning a knob in editor does not focus the push to the page that contains that parameter

Selecting any page on push (bottom row) almost always switches focus to the very last page, both in push and editor.

*The only way to get to the parameters of a 'remote control page', is to select within bitwig

Thanks

[Spin Boyz]

Hi Jurgen,

Absolutely love you Bitwig extension. SO useful, thank you for doing it.

I'm curious if you're considering adding support for the MPC Studio to the list of supported MPCs?

I got rid of my MPC One to focus more specifically on learning Bitwig more deeply, but REALLY miss the MPC pads. I've tried a bunch of other pad controllers, but for some reason the MPC pads just feel better to me (I like the added resistance over something like SL MkIII) and would love to get great integration with the MPC Studio.

Best.

No, I have no plans. It works completely different and I am not sure if it is even possible to support it.

I have the MPC Studio too. It would great if it was supported.

[ekkomouse]

Would push three switch back-and-forth between the Standalone mode and controller mode for bitwig?

[aehaem]

Hi,

First I wanna thank you for your wonderful work, doing so many Midi Controller scripts, with so much time and dedication.
But I have a problem I get not used to, so I wanted to kindly ask you for help (also anyone here in this Threat, maybe someone can help me)
My English is not so good, so I hope you understand my problem...

I am trying to use the the DrivenByMoss Flexi Controller with a footswitch, since I am a guitarPlayer and want to use Bitwig as a Looper (I am also playing LinnStrument, but controlling Bitwig with the Footswitch). So I am recording only Audio Clips and evrey clip by it´s own (not more clips than one), one after one...

I have enabled select Tracks when selecting Clips in Clip Launcher, but what I want to be able to be able to select the clips (or also empty clip slots, since audio clips can not be prepared). But with the Flexi controller I can only start clips (or record clips, when slot is empty) without highlighting the slot.

My Background for that issue is, I want to be able to delete a recording clip (when I am doing mistakes, bad timing etc.).
I can delete a highlighted clip since I have BomeMidiTranslater, where I can use Bitwigs Shortcuts with Midi, so that is no problem, the only thing I cannot do is highlight the clipslot I want to record in.

The best way around would be to have the slot highlighted by selecting a Track and start the scene. The "Split" of scene + the "Row" of tracks is pointing to a cell and this way Bitwig is already recording clips (when autoArm audio tracks and record on scene launch is enabled), but not highlighting it. The only way in Bitwig is vice versa, highlighting a Track when selecting clips.

So I would need the Flexi to Highlight the clip slots one to eight of a scene to be able to record one of my eight "looper Tracks" (since I have different FX on any Track, between I want to choose when recording).

Is there a way I don´t see or would it be able to implement this behaviour ?

Thank you

[moss]

Yes> Push 1, Bitwig 5.05, DBM 21.0.0

Behaviour:

Using 'Remote Controls Editor', selecting a page, reflects perfectly on the Push and turning a knob on Push reflects perfectly back to the editor for the page in focus.

Turning a knob in editor does not focus the push to the page that contains that parameter

I was surprised that it follow at all since this is not necessarily expected. But I agree that it should be consistent. This is clearly something Bitwig needs to address.

Selecting any page on push (bottom row) almost always switches focus to the very last page, both in push and editor.
*The only way to get to the parameters of a 'remote control page', is to select within bitwig

I cannot reproduce this. I am not sure if this is user error. You select the pages with the buttons which are directly below the display.

[moss]

Hi Jurgen,

Absolutely love you Bitwig extension. SO useful, thank you for doing it.

I'm curious if you're considering adding support for the MPC Studio to the list of supported MPCs?

I got rid of my MPC One to focus more specifically on learning Bitwig more deeply, but REALLY miss the MPC pads. I've tried a bunch of other pad controllers, but for some reason the MPC pads just feel better to me (I like the added resistance over something like SL MkIII) and would love to get great integration with the MPC Studio.

Best.

No, I have no plans. It works completely different and I am not sure if it is even possible to support it.

I have the MPC Studio too. It would great if it was supported.

Still no plans for this.

[moss]

Would push three switch back-and-forth between the Standalone mode and controller mode for bitwig?

Ah, now I understand the question. I am not sure to be honest since I only have the controller version but I guess it works the same as with Ableton.

[guitarfrenzi]

Yes> Push 1, Bitwig 5.05, DBM 21.0.0

Selecting any page on push (bottom row) almost always switches focus to the very last page, both in push and editor.
*The only way to get to the parameters of a 'remote control page', is to select within bitwig

I cannot reproduce this. I am not sure if this is user error. You select the pages with the buttons which are directly below the display.

Not user error - To reproduce:

Start a new default project

Add 3 remote pages to the instrument track: Perform; Page 2; Page 3

Perform is active....push right arrow on Push 1 ->Page 3 is selected

Push the left arrow->Perform is active

Push the Page 2 button ->Page 3 is selected

Page 2 cannot be selected on the Push, but when selected in the Editor it then becomes active.

*If you cannot reproduce, maybe it's a firmware differential on the hardware?

Thanks

[ekkomouse]

Would push three switch back-and-forth between the Standalone mode and controller mode for bitwig?

Ah, now I understand the question. I am not sure to be honest since I only have the controller version but I guess it works the same as with Ableton.

I just lightly tested, it seems that it doesn’t release the push Three completely when you press the power button on the script in settings controllers, you have to switch all three midi drop downs to none, then you can switch into standalone mode on push three. Would be a little better if it let go of push 3, then could use it as an instrument for lives devices and record into bitwig. Probably wishful thinking, very cool it works regardless, thanks!

[Echoes in the Attic]

Is it possible to have the clip view in the screen (and trigger scenes with the wheel) while keeping note view on the pads? So you can play notes and also trigger a scene with the wheel using the display?

[LarsDaniel]

Hi Jürgen,
Using LP3mk2 and newest software versions.
I am in Session view and I want to double the content of a clip. On the Launchpad, I press Shift + Duplicate and this carries out the action. Unfortunately, after the action it leaves me on the Shift Page, where my expectation off course is to be back on the Session page. This then requires an extra click on the Shift button to get back to Session.
Is this something that could be fixed?