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

[LarsDaniel]

Please could you guide if in the DrivenByMoss settings I can change the keys/notes layout to chromatic format?
Thanks

I don't know if this helps, but on Launchpad, pressing the Note button multiple times will cycle through the various play modes.

[andy4trance]

Thank you LarsDaniel, unfortunately cycling through the Note options I have only 3 layouts, none of these is the chormatic scale one, i.e. the isomorphic setting. I asked if there is a setting to add this layout too. The DrivenByMoss is so rich in features and options, its strange this is not in - or it is and I just don't find it.
(below a short description of this. It's pretty common in all matrix controllers)

[Pirapsy]

--------------------------------------------Ableton Push 2 Wish List----------------------------------------------

Hello Juergen i will try from here my luck. I really hope you can help.
Here are some wishes about the Push 2.
--Maybe you could implement an option to the browser settings to permanently disable the preview which when its on the browsing isnt that smooth cause it always trys to load whatever is chosen which makes the user to always wanting to turn the preview off.
Weird things happening with the text's in the browser when navigating to the custom vst folder collection. The names appearing so weird so that its losing sense. An example is since im organizing all the folders with 01. 02. etc. The word 03.Delay is appearing as 03.Di... It would be nice ti give more space to the collums so that everythin makes mores sense.
--If you could also let us know how to customize our "Add Track - Favorite Devices" this would also Help us a lot with the workflow.
--Another weird thing is I got a Hardware Instrument Access Virus Ti2 which i can use with its vst.
In combination with Push 2 in other DAWs than Bitwig works normal.
But in Bitwig what happenes is when pushing Push's 2 Pads they are triggering random parameteres to the Vst. I found out that the problem was the option convert the Pads was selected to Polyaftertouch. By changing it to channel aftertouch the problem doesnt exist anymore. This is maybe also something that you could put as an option to the setup button in the pads section ?!
--If you like i can share a Scale formula which i've already tried in Ableton from here that you could also copy to your script.
I wish i could do most of these things by my own but it seems i cant find a way to open somehow your script and read or edit anything thats written inside.


Thank you for your great work

[LarsDaniel]

Thank you LarsDaniel, unfortunately cycling through the Note options I have only 3 layouts, none of these is the chormatic scale one, i.e. the isomorphic setting. I asked if there is a setting to add this layout too. The DrivenByMoss is so rich in features and options, its strange this is not in - or it is and I just don't find it.
(below a short description of this. It's pretty common in all matrix controllers)

Ok, but I do have an isomorphic Note option, where every line is a fourth apart. (On Launchpad using DrivenByMoss.)

[andy4trance]

Thanks for baring with me Lars, it is the Mutate button on the right side that does the trick, third from below, switches to chromatic from the other default type. (as always, the rtfm problem)

[jekblad]

Today I was able to make some funky music and it was great. Thank you moss.

Question around akai fire: is it possible to change the default velocity of the drum sequencer mode? In the past I have selected the notes after programming and turned the volume up but I think I must be missing something.

[moss]

Ok, I am confused because I thought what I had done was to add the extension manually, and then you talked about adding it manually. So I have to ask: What does "add the extension manually" mean? Also what are you referring to when you say "the stock one"?

You are right. I somehow thought there is also an implementation from Bitwig available but it is only for the old model.
However, here is a screenshot of the Add Controller area where you can check the DrivenByMoss version number:

AddController.png

[moss]

--Maybe you could implement an option to the browser settings to permanently disable the preview which when its on the browsing isnt that smooth cause it always trys to load whatever is chosen which makes the user to always wanting to turn the preview off.

Shouldn't this be remembered if you turn it off in the dialog? If not, please contact Bitwig support.

Weird things happening with the text's in the browser when navigating to the custom vst folder collection. The names appearing so weird so that its losing sense. An example is since im organizing all the folders with 01. 02. etc. The word 03.Delay is appearing as 03.Di... It would be nice ti give more space to the collums so that everythin makes mores sense.

I tried to reproduce this but could not. Can you please post a screenshot of the Bitwig browser as well as a picture of the Push 2 screen?

--If you could also let us know how to customize our "Add Track - Favorite Devices" this would also Help us a lot with the workflow.

That's a bit difficult since it is a file in the bwextension (sadly there is still not API for that in Bitwig).
Instead you can report me the type, name and ID of the plugins you miss. You can learn how to get this information in this video from about 7:20:

--Another weird thing is I got a Hardware Instrument Access Virus Ti2 which i can use with its vst.
In combination with Push 2 in other DAWs than Bitwig works normal.
But in Bitwig what happenes is when pushing Push's 2 Pads they are triggering random parameteres to the Vst. I found out that the problem was the option convert the Pads was selected to Polyaftertouch. By changing it to channel aftertouch the problem doesnt exist anymore. This is maybe also something that you could put as an option to the setup button in the pads section ?!

That setting is already there, called "Convert Poly Aftertouch to".

--If you like i can share a Scale formula which i've already tried in Ableton from here that you could also copy to your script.
I wish i could do most of these things by my own but it seems i cant find a way to open somehow your script and read or edit anything thats written inside.

The source code is here: https://github.com/git-moss/DrivenByMoss
But this is a complex piece of software and in no way a simple script.

[moss]

Today I was able to make some funky music and it was great. Thank you moss.

Question around akai fire: is it possible to change the default velocity of the drum sequencer mode? In the past I have selected the notes after programming and turned the volume up but I think I must be missing something.

Best is to switch it off on the Fire

[AFranke]

Moin Jürgen,
ich habe neuerdings ein Problem mit deinem Script und dem Push 1, oder ich habe etwas übersehen bzw. mache plötzlich was falsch. Ich habe hier das Push und das SLMk3 in Bitwig 4.4.8 und die aktuelle Version deines Scripts (vor 2 Minuten zur Sicherheit von deiner Website herunter geladen und neu installiert) am start. Wenn ich jetzt in BWS mit der Maus zwischen verschiedenen Tracks wechsle/springe, folgt das SLMK3 auch zu dem entsprechenden Track, dass Push allerdings nicht! Es ist auch nicht auf einen Track fixiert, ich habe das mehrfach überprüft. Im Studio I/O Panel sieht man auch, dass dort zwar der aktuelle Track angezeigt wird, der Controller aber selbst nicht folgt. Auch das Rechteck, dass in Bitwig die Gruppe der 8 aktuellen Tracks markiert bleibt einfach dort wo es war und folgt nicht. Wenn ich hingegen die Tracks über die Hardware des SLMK3 in Bitwig wechsle, folgt auch das Push, so wie es sein sollte. Nur mit der Maus funktioniert das nicht mehr.
Alles etwas doof zu beschreiben, deshalb habe ich versucht es mit meinen bescheidenen Mitteln abzufilmen. Das Video findest du in meinem OneDrive:

https://1drv.ms/v/s!AqODDgQzhWl5g5M8jrh ... g?e=EbKQpr

Ich schreibe in Deutsch, weil es mir so etwas leichter fällt das Problem zu beschreiben. Ich hoffe das ist ok.

LG Andreas

I could not reproduce any of this. Does this happen all the time when you start Bitwig? Is this with specific tracks? Does this only happen in combination with the SL?

Sorry for my late reply. I tried this with only Push 1 attached to BWS and it's the same problem as in combination with the SLMK3. I can reproduce it every time.

[moss]

Moin Jürgen,
ich habe neuerdings ein Problem mit deinem Script und dem Push 1, oder ich habe etwas übersehen bzw. mache plötzlich was falsch. Ich habe hier das Push und das SLMk3 in Bitwig 4.4.8 und die aktuelle Version deines Scripts (vor 2 Minuten zur Sicherheit von deiner Website herunter geladen und neu installiert) am start. Wenn ich jetzt in BWS mit der Maus zwischen verschiedenen Tracks wechsle/springe, folgt das SLMK3 auch zu dem entsprechenden Track, dass Push allerdings nicht! Es ist auch nicht auf einen Track fixiert, ich habe das mehrfach überprüft. Im Studio I/O Panel sieht man auch, dass dort zwar der aktuelle Track angezeigt wird, der Controller aber selbst nicht folgt. Auch das Rechteck, dass in Bitwig die Gruppe der 8 aktuellen Tracks markiert bleibt einfach dort wo es war und folgt nicht. Wenn ich hingegen die Tracks über die Hardware des SLMK3 in Bitwig wechsle, folgt auch das Push, so wie es sein sollte. Nur mit der Maus funktioniert das nicht mehr.
Alles etwas doof zu beschreiben, deshalb habe ich versucht es mit meinen bescheidenen Mitteln abzufilmen. Das Video findest du in meinem OneDrive:

https://1drv.ms/v/s!AqODDgQzhWl5g5M8jrh ... g?e=EbKQpr

Ich schreibe in Deutsch, weil es mir so etwas leichter fällt das Problem zu beschreiben. Ich hoffe das ist ok.

LG Andreas

I could not reproduce any of this. Does this happen all the time when you start Bitwig? Is this with specific tracks? Does this only happen in combination with the SL?

Sorry for my late reply. I tried this with only Push 1 attached to BWS and it's the same problem as in combination with the SLMK3. I can reproduce it every time.

Since I cannot reproduce it. Could you give some exact steps of what you are doing? Also your Bitwig startup template might be helpful as well as a screenshot of the DrivenByMoss Push 1 settings.

[RichieHawtin]

Please adapt this script for push 1/2

[LarsDaniel]

(Deleted)

[LarsDaniel]

Ok, I am confused because I thought what I had done was to add the extension manually, and then you talked about adding it manually. So I have to ask: What does "add the extension manually" mean? Also what are you referring to when you say "the stock one"?

You are right. I somehow thought there is also an implementation from Bitwig available but it is only for the old model.
However, here is a screenshot of the Add Controller area where you can check the DrivenByMoss version number:

AddController.png

Ok, back to this issue:
So, my DrivenByMoss version is 19.2.1.
I have a Launchpad Pro Mk3 and if I have a clip selected and press the Custom button, nothing happens. I understand that I should reach a new page for setting clip length, but simply nothing happens.


Furthermore two other issues has come with the new version, but this is in the Flexi script:

1: I have a controller (Faderfox EC4) setup to use "Track: Previous Bank" and "Track: Next Bank".
Before the new version, I had the big red rectangle showing my on screen what bank was active, but I can not get that now. And yes, I am aware of the little button on the top line of the script setup that says "Paints a rectangle around the focused clips ...etc".
When I use the Previous and Next Bank, the focus changes (the tiny coloured triangles move to the next 8 tracks) but the big red rectangle is not there, and, what is worse, the Launchpad does not change page (like it did with earlier version).

2: When I am on the first bank of eight tracks, I have eight knobs controlling the volumes of the eight track. When I move focus to the next eight tracks using the Next Bank command, I now have a very weird situation where knob 1 and 2 does nothing, but knob 3 controls volume on track 9, knob 4 goes to track 10 and so on. (Where knob 1 should have gone to track 9, knob 2 to track 10 and so on.)

I would actually like to go back to v19.1 but it does not seem to be on your site. Can I get it somehow?

[mevla]

Hello. Is the LaunchControl XL able to handle the following ? I tried several combinations with no results. The context is a mix down / mastering and the work to handle in this example is mixing the guitar tracks :

launchControlXL.jpg

Groups are used as (kind of) busses. All effects pertaining to all tracks of a group sit on the group's track inside a FX layer which allows parallel processing (dry/delay/chorus), for instance the Guitar group. The Guitar group and other groups are themselves inside a group. Outside of this group is a track with reference material for mixing.

What would be useful, is being able with the LaunchControl XL to mix within a group the amount of :

dry signal (Dry)
FX 1 - delay (MDelayMB)
FX 2 - chorus (Chorus+)

Along with the volume of the two guitar tracks (Shiraki 1 and 2) themselves.

And being able to move to the next group and do the same with whatever number of FX there are in its FX layer.

In Layer mode pressing Track Select will show the name of the FX Layer that's currently selected, nothing more it seems.

Perhaps on a more general note, to be able to navigate easily within groups.

Is there a way to achieve this functionality with the LaunchControl XL ?

As an aside, it would be useful to be able to see on the LaunchControl XL when a slider/column is actually a group. Not many colours available although one that contrasts with the pale/bright green of the Track focus pads could be used to identify a group. When a slider is identified as a group, then the following sliders could be recognized as part of the group.