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

[digidennis]

DrivenByMoss 21.0.0 is online!
...
Enjoy!

Hi moss - Thank you very much. I 100% will enjoy it.

Got some questions regarding push3 on bitwig (beta 5.0.4). I have push3 firmware 1.0 Build 71 (live beta)

I cant trigger scenes, edit/select notes unless I turn MPE off. I can play the drumpads in drum layout though.

Any thoughts ?

[questionaire]

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!

I think i found another bug with the launchpad pro mk3 script. When you switch over from session to note the way the keyboard/pads are represented shift from drumpad to keyboard etc. with every move from note to session and back it shifts everytime to another view representation.
I would expect that it would remember the representation when you left note and return from session to note.

I dont think this is intended?

[moss]

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

I see. This is a bit tricky but I implemented just something similar for the Push 3. Will be in the next update.

[moss]

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

Thanks, this makes it clear and now I see what you mean.

The cursor key behaviour is correct since it moves by 8 pages.
The direct selection is broken and will be fixed in the next update!

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

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!

There are some issues with Bitwig releasing devices. But always when I want to test this, everything works fine.

[moss]

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?

Currently, not. But I was thinking about it as well. Will take note.

[moss]

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?

Yeah, might make sense for some commands. Will take note.

[moss]

DrivenByMoss 21.0.0 is online!
...
Enjoy!

Hi moss - Thank you very much. I 100% will enjoy it.

Got some questions regarding push3 on bitwig (beta 5.0.4). I have push3 firmware 1.0 Build 71 (live beta)

I cant trigger scenes, edit/select notes unless I turn MPE off. I can play the drumpads in drum layout though.

Any thoughts ?

Yes, I just realised I need to turn off MPE on most of the other modes
Already working on it!

[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!

I think i found another bug with the launchpad pro mk3 script. When you switch over from session to note the way the keyboard/pads are represented shift from drumpad to keyboard etc. with every move from note to session and back it shifts everytime to another view representation.
I would expect that it would remember the representation when you left note and return from session to note.

I dont think this is intended?

No, it should be remembered but seems to work fine for me. Can you give some exact steps to reproduce it?

[questionaire]

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!

I think i found another bug with the launchpad pro mk3 script. When you switch over from session to note the way the keyboard/pads are represented shift from drumpad to keyboard etc. with every move from note to session and back it shifts everytime to another view representation.
I would expect that it would remember the representation when you left note and return from session to note.

I dont think this is intended?

No, it should be remembered but seems to work fine for me. Can you give some exact steps to reproduce it?

Simply push session button then note and then back session and then again note makes the view change from full keys to keyboard view to yellow drumpads to full keys to keyboard view etc. etc.

I'm on linux but that shouldnot matter i think. Is it maybe because i did not update to latest firmware 1.2.2 ? I'm still on 1.2.1

I have updated to 1.2.2 now and still the same behaviour

[Kaz62]

I posted this on another thread, but wanted to post here for visibility to Moss...

Would it make sense to have the Project Remotes and Track Remotes be driven by modes (like the Track/Volume/Pan/Device Modes) instead of their own entry in the Generic Flexi controller?

This way, the same buttons/controls could be applied to the Project and Track remotes instead of requiring their own configuration.

Strangely, if I switch focus on the Project Remotes in the UI by clicking on the remote panel, I can control the remote values with the same 8 control currently assigned to something else (Mode Set Values 1-8). However, I cannot return to the device panel unless I click on it in the UI.

Thanks again for all the hard work.

[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?

Currently, not. But I was thinking about it as well. Will take note.

Ok, I really hope you can add that like Ableton did. I've often found that I want to trigger scenes or clips at the same time as trigger one shots from a drum racks for example, or just play an instrument in real time while switching scenes. You either have to stop playing the instrument, switch over to clips view, trigger the scene ahead of time (quantized) and quickly switch back over to the track with the one shots or instrument, which is annoying, or you need two controllers. This ability to fire off a scene while you are in a play mode is really useful.

[phelios2063]

I noticed that the scales are not working as expected. Some notes that are not part of the selected scale will be triggered by the pads.

Also in MPE mode the notes are off sometimes. For instance in chromatic mode when I slide five pads to the right I sometimes get a fourth and sometimes a third interval.

[yomguy]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hi Moss,

First, thank you so much for the wonderful work you provide for the whole Bitwig community. On my side, I can run the Push 1 smoothly during live sessions and the Icon Platform M+ in the studio which is really, really great! I also appreciate the extensive documentation as well as the regular new feature integration. It always goes in the right directions without braking the workflow.

I have a request about the write mode on the Icon Platform M+. As it does not have any Touch mode button, it is currently impossible to enable this mode from the controller. Indeed, the write button enables the write mode for all tracks that have record mode engaged. This is pretty problematic when you want to overwrite an automation only for the tracks from which you touch the faders and not the others.

In order to set the touch mode by default, I have produced this hack (https://github.com/yomguy/DrivenByMoss/commit/639b4f8b4f7a0f83a092a5eec52c6784539e8969).

To avoid this hack, it would be nice to have an option in the settings to choose the default behavior of the write button, "write" or "touch" for example. I have tried to implement it but I am afraid my Java knowledge and my understanding of the architecture of the extension are too limited so far. So, do you think this feature could me implemented in a way it doesn't have conflicts with other controller settings? Or maybe you have a better idea?

BTW, I have just sent you this PR (https://github.com/git-moss/DrivenByMoss/pull/363) to allow the use of the general Java environment on Debian based systems - including Ubuntu - coming from the official JRE package.

Cheers,
Guillaume

[zpawn1]

Hi Moss
thank you for you work
Everything is working great so far except for clip selection, even at the lowest pad velocity the clips are always triggered to play instead of selection, I'm using a Launchpad X and and a Launchkey mini mk3, both have the same issue.

I'm using Windows 10, Bitwig 5.0.4, DrivenByMoss 21.0.0, the latest Novation USB drivers and also tried its three previous versions