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

[johanhov]

Hi! I have not read all the posts, so I'm sorry if I have missed something. Bitwig supports launching clips in two alternative ways; main and ALT (holding the ALT/OPTION (on MAC)-key while launching a clip). I haven't found a way to do this from my Novation LaunchKey MK3. Could it be possible to make holding the Scene 1 (>) key on the LaunchKey act as an ALT-key, in the same way the Stop/Solo/Mute-button right below it can be held without launching a scene in order to switch modes? It would be awesome!

PS. There are some functions missing from the manual: Undo + clip deletes clip. Play + clip stops the clip immediately.

[johanhov]

Hi! I have not read all the posts, so I'm sorry if I have missed something. Bitwig supports launching clips in two alternative ways; main and ALT (holding the ALT/OPTION (on MAC)-key while launching a clip). I haven't found a way to do this from my Novation LaunchKey MK3. Could it be possible to make holding the Scene 1 (>) key on the LaunchKey act as an ALT-key, in the same way the Stop/Solo/Mute-button right below it can be held without launching a scene in order to switch modes? It would be awesome!

PS. There are some functions missing from the manual: Undo + clip deletes clip. Play + clip stops the clip immediately.

Actually I think the ...-button would be better, as someone might want to ALT-launch Scene 1.

[moss]

Hi! I have not read all the posts, so I'm sorry if I have missed something. Bitwig supports launching clips in two alternative ways; main and ALT (holding the ALT/OPTION (on MAC)-key while launching a clip). I haven't found a way to do this from my Novation LaunchKey MK3. Could it be possible to make holding the Scene 1 (>) key on the LaunchKey act as an ALT-key, in the same way the Stop/Solo/Mute-button right below it can be held without launching a scene in order to switch modes? It would be awesome!

PS. There are some functions missing from the manual: Undo + clip deletes clip. Play + clip stops the clip immediately.

Actually I think the ...-button would be better, as someone might want to ALT-launch Scene 1.

The "..." cannot be used since this immediately activates the PC keyboard emulation. Scene 1 is also problematic as you wrote yourself. Maybe the PLAY button would be the best choice. Will add it to the wishlist.

[johanhov]

Thank you!

I would love to keep the "stop immediately" functionality from play+clip though, or maybe play+stop+clip could do that if the ALT launch q is set to Off?

[moss]

This hopefully answers some questions:

[hyeena]

Thanks for nice script for Bitwig!

I was wondering if there is any workaround / solution for the gamepad use as a XY controller?

At the moment X+, X- (and Y+, Y-) does same thing, the idea of the joystick is lacking.

If I have understood the mechanism behind joystick, the rest/zero position is at 50% value of the both 2 potentiometers that joystick is made of. I dont know how gamepads provide that information to system in digital domain thought. The far left down position is value 0 in both of the potentiometers and the far right up position is value 127 on both of the potentiometers.

Should I look for the solution with analog values with the Arduino or circuit bend one of the true midi controllers?

br. Jukka

[nowiamone]

Hi Jürgen,
here my "OSC Script Bug Report" (Track Navigation set to Flat, Bitwig 5.0, Drivenbymoss 20.3.0, OSC/PILOT interface), updated 6th of july

1. /track/selected/name does not give out Group-Track-Names. Instead, the last selected Non-Group-Track is shown.

2. /track/1-x/selected seems to have malfunctioning feedback, as soon as a group-track is existing in the project.

Example:
8 Audiotracks exist. Each AudioTrack is represented by
/track/selected/name and /track/1-8/selected on the OSC Interface.
When selecting Audiotracks, this properly shows in the OSC Interface.
But, when a grouptrack of any size is created, this newly created Grouptrack continues to be “selected” on the OSC Interface, even when switching focus to other Audiotracks within Bitwig.
And vice versa: when the Grouptrack isn’t selected in Bitwig/OSC, and i switch the selection from a Audiotrack to the Grouptrack, the Audiotrack continues to be “selected” on the OSC Interface.
I’m not sure, but this behavior might have something to do with /track/x/selected being able to Fold/Unfold the Grouptrack by pressing a Togglebutton (OSC OFF 0 and ON 1) twice. This is a really awesome function!, but maybe it’s “swallowing” the OSC OFF/ON message for showing on/off of the track-selection somehow. But that's just a guess.

3. Same Problem exists, when switching between selecting Audio and Miditracks. The last selected Audiotrack keeps showing as selected in the OSC interface, even when actually the Miditrack is now selected, and vice versa.
For Audio and Midi Clip-Slots (/track/x/clip/x/isSelected) the behavior is sometimes similar, but sometimes slightly different: instead of "is Selected" to change to the midi track, it stays with the Audiotrack - and the miditrack is falsely shown as not selected. It can also lead to several audio or midi clips being falsely shown as selected at the same time.

For the first three points above, i used a Bank page size equal to the number of my Tracks.

4. There is a buggy behavior when using a number for "Bank page size" which is higher than the number of existing Tracks. Result: Some Tracks never get fully loaded into the /track/x/name Textbox, when loading the Bitwig Liveset. They keep being empty, even when /refresh is used. Only when manually renaming the Track in Bitwig, the Textbox gets refreshed and shows the actual Trackname again - or when Restarting the OSC Script. Could be nice to have a /restart OSC script button!
But there are also problems which persist, even after restarting the OSC Script with OSC adresses like /selected. The problem gets worse the higher the difference between actual amount of Tracks and "Bank page size".
I know it says "must match your client template", but my client template has 24 Tracks and over 100 Scenes. Because i have a big Liveperformance Liveset (actually it has 300 Scenes the last time i put my songs into Ableton). I also encountered everything getting really slow (reaction speed of VU meters, selections, etc.) in both the Interface and bitwig with banksizes above 100 - and once OSC even crashed with a Java heap space error. (+ Bitwig crashed).
On my interface, i often times use dummy clips or support-samples which are in scenes far away from the first 30+ scenes - and i want to be able to press them immediately, without having to switch banks.

5. This is not a bug i think, but would love to know a solution: When using OSC Script to “select Clip”, for example /track/1/clip/20/select, Bitwigs Cliplauncher View (vertical and horizontal) doesn’t follow the selection! Is there any chance this might be changed to following the selection? Searching through the OSC commands, I haven't found any fast ways to scroll through Scenes or select specific scenes or clips, with Bitwigs view following.

Thank you for helping!

[milosh_]

Hi. I installed DrivenByMoss 20.3.0
Ableton Push 2 does show up in settings but the on/off buton is greyed out and it does not allow to turn it on.
On Push 2 itself I can see only Push logo.
I am on Windows 7, Bitwig 5.0
What can be wrong?
cheers

If it is grayed out, it means that the MIDI and/or USB ports are not set. Can you select them? If not, something is wrong with your hardware connection.

Thank you! I had to install ableton to make push 2 work on my system. I suppose ableton installs the drivers for the controller. Is it how it works?
Never the less it works with bitwig at this moment

[moss]

Thanks for nice script for Bitwig!

I was wondering if there is any workaround / solution for the gamepad use as a XY controller?

At the moment X+, X- (and Y+, Y-) does same thing, the idea of the joystick is lacking.

If I have understood the mechanism behind joystick, the rest/zero position is at 50% value of the both 2 potentiometers that joystick is made of. I dont know how gamepads provide that information to system in digital domain thought. The far left down position is value 0 in both of the potentiometers and the far right up position is value 127 on both of the potentiometers.

Should I look for the solution with analog values with the Arduino or circuit bend one of the true midi controllers?

br. Jukka

It is on my todo list but no idea when I find some time to look into this.

[milosh_]

Script for Push 2 is awesome! A lot of features and more fun to play with Bitwig now.
I noticed some small issues.
Tempo knob lags a lot. It feels like there is some latency between twisting the knob and tempo change.
Also it is very difficult to use the browser with push 2. For example when i twist "tags" knobs it jumps between tags like crazy

[mevla]

Hello. Is it possible with the Launchpad to assign pads on a per-pad basis and not as faders ? Like the keyboard and drum modes are doing, but user defined ?

[joris.roling]

Hi Jürgen,

In Bitwig 5 the Project and Track Remotes are currently not accessable with the original Akai APC40, am I right?
Is this because there is nu clear UI button for this? I think the Akai APC40 mkII uses a User button the OG Akai APC40 does not have?

Wouldn't it be an idea to user the Shift + <- & Shift + -> in the "Device Control" section so that once the most left device in a track is reached, the next Shift + <- press would go into Track Remote parameters, and one press more would go into Project Remote parameters, thus following what's happening on screen? Wouldn't that be a logical UX?

I would very much like to have access to these new Bitwig 5 features (Track & Project Remotes) with my beloved APC40 OG.

Would that be possible?

Cheers,
Joris

[xtreme sounds]

hi sir on the akai fire is there a way to add a 4x4 drum square colored pads set for use with any drum machine plugin? I know the pads only light up when using with the Bitwig Drum Machine (the loaded samples load up in a 4x4 grid).

You can use the Drum 64 mode. Make sure that "Turn off empty drum pads" in is disabled in the settings.

Hi I did those things and the pads containing samples are still not lit up using XO. its ok no biggie

I forgot to mention: simply put an empty drum machine before XO.

Hi I did that but the only pad that lights up is the one I play.

Did you disable "Turn off empty drum pads"?

I did and i see all yellow squares filling up the fire. Im looking for lights to represent just the pads that have loaded sounds in XO. its ok no biggie

[moss]

You can use the Drum 64 mode. Make sure that "Turn off empty drum pads" in is disabled in the settings.

Hi I did those things and the pads containing samples are still not lit up using XO. its ok no biggie

I forgot to mention: simply put an empty drum machine before XO.

Hi I did that but the only pad that lights up is the one I play.

Did you disable "Turn off empty drum pads"?

I did and i see all yellow squares filling up the fire. Im looking for lights to represent just the pads that have loaded sounds in XO. its ok no biggie

That's not possible since there is no protocol via a plugin could send such information.

[pervyinthepark]

Hey, I'm trying to add some scales... well, a lot of scales, maybe... heh.

I've found where in the git to put the scales but, uh, not really sure what to do from here to compile to a bwextension? im a scrub... I'm trying to add the missing 7 note scales (not all modes) and then the bebop scales.

i have no idea what to do with maven or git haha...