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

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

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.

It's simple, what I'm doing. I just select different tracks with the mouse, by clicking the header of the track that I want to select. While the SLMK3 (and also my APC40) follow those selections, Push 1 doesn't. It just stays where it was.

Here are my Push settings:

Bitwig_Studio_TbMeptzGHc.png

Here is another video that shows up my problem:
https://1drv.ms/v/s!AqODDgQzhWl5g5N1yoM ... A?e=7oqyUq

The red "selection" is the Push, yellow is the SLMK3 and green is the APC40. You can see the red one does not follow my track selections, while both other controllers do, they jump to the next group of 8 tracks. Btw, I found another problem while I made the screencast. Watch what happens if I was on the third "group of eight" (Global Transposer, Control Room) and then jump direct to track 1 (Inst 1), now the SLMK3 and APC do not select the first "group of eight" (Inst 1 to Hive), they select the "second group of eight" (Inst 9 to Inst 16) instead!

Here is the link to the project:
https://1drv.ms/u/s!AqODDgQzhWl5g5N_sFI ... A?e=bSu8m4

Best regards
Andreas

[moss]

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.

As, I wrote before, it works fine for me. Do you see the notification "Clip Length" in Bitwig when you select Custom?

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

I did not activate it so far. Will add it in the next update.

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

Are you using it via Volume Mode or a direct mapping of the Volume function? Maybe test again with the next update when you can see where the focus actually is.

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?

Simply change the version number in the download link. But I do not expect that this will change anything.

[moss]

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 :

No, it is not supported. The Layer Mode always focuses on the 1st device.

[moss]

It's simple, what I'm doing. I just select different tracks with the mouse, by clicking the header of the track that I want to select.

Ah, I see. That is actually a bug in Bitwig (I reported it already some time ago). It works if you click the tracks on the left instead.

[AFranke]

It's simple, what I'm doing. I just select different tracks with the mouse, by clicking the header of the track that I want to select.

Ah, I see. That is actually a bug in Bitwig (I reported it already some time ago). It works if you click the tracks on the left instead.

Do you mean selecting them in the Arranger view? Hmm, that's shite, because I work in the Mixer view 99% of the time. Maybe I should also report this. I hope they will fix this soon, but in my experience, they will declare this bug as a feature.

[LarsDaniel]

As, I wrote before, it works fine for me. Do you see the notification "Clip Length" in Bitwig when you select Custom?

As I wrote, nothing happens. Absolutely nothing, nor here, nor there.
It is not a big issue, I just thought it was odd. (And it might be rather nice to use the clip length controls.)

Are you using it via Volume Mode or a direct mapping of the Volume function? Maybe test again with the next update when you can see where the focus actually is.

I am using Volume mode, but anyway, I just found my way back to the way where all volume controls work as expected AND I can change track banks WITH the big red rectangle via the Flexi script on my Faderfox. The setting that fixed both issues was "Exclude Deactivated Items" ON. When it is OFF I lose the big red rectangle and apparently screws with the track number sequence. (And this is on 19.2.1 btw.)

Anyway, I am SO relieved that my setup is working again. Thanks.

[bluelife]

Servus Jürgen,

I have bitiwig 4.4.8 and an mpc live 2 on Windows 10.
Everything is up to date. I downloaded the newest version of your script today too and copied it to the correct place.
The script is installed and configured in bitwig. Live shows up as expected.
The network connection is established using the akai tool. It shows up as connected in the mpc live 2 as well.

When I click on connect, it just stops at the waiting for ableton. I've waited too.
I've reset the mpc live after updating.
I've tried rebooting the computer and the mpc.
I've tried different orders, bitwig before the network connection and vice versa.

I did have it running once in bitwig 4.4.3 or 6. But then it also didn't always connect.

Any help would be great,

Danke, Richard

[moss]

Servus Jürgen,

I have bitiwig 4.4.8 and an mpc live 2 on Windows 10.
Everything is up to date. I downloaded the newest version of your script today too and copied it to the correct place.
The script is installed and configured in bitwig. Live shows up as expected.
The network connection is established using the akai tool. It shows up as connected in the mpc live 2 as well.

When I click on connect, it just stops at the waiting for ableton. I've waited too.
I've reset the mpc live after updating.
I've tried rebooting the computer and the mpc.
I've tried different orders, bitwig before the network connection and vice versa.

I did have it running once in bitwig 4.4.3 or 6. But then it also didn't always connect.

Any help would be great,

Danke, Richard

Hmm, seems like you already checked the obvious things.
Are you using the ethernet connection or WiFi? If it is WiFi try ethernet.
When it is waiting for the connection, start again the Akai tool and see if it is selected.
Check the JavaScript console in Bitwig, which shows the connection info/attempts.

[bluelife]

Thanks, I'm using an ethernet cable. My WiFi is not very stable. I'm connected directly to the computer without a hub. I'll take a look at that console, not sure where it is, but sure I'll find it, thank

[bluelife]

This is what the console says:
Added MIDI IN: UC Midi Port 1
Added MIDI IN: UC Midi Port 2
Added MIDI IN: Akai Network - MIDI
Added MIDI IN: Akai Network - DAW Control
Added MIDI IN: Arturia KeyLab Essential 49
Added MIDI IN: MIDIIN2 (Arturia KeyLab Essenti
Added MIDI IN: Seaboard Block
Added MIDI IN: RME ARC
Added MIDI OUT: Microsoft GS Wavetable Synth
Added MIDI OUT: UC Midi Port 1
Added MIDI OUT: UC Midi Port 2
Added MIDI OUT: Akai Network - MIDI
Added MIDI OUT: Akai Network - DAW Control
Added MIDI OUT: Arturia KeyLab Essential 49
Added MIDI OUT: MIDIOUT2 (Arturia KeyLab Essent
Added MIDI OUT: Seaboard Block
Added MIDI OUT: RME ARC

[bluelife]

I also treid restarting the akai tool, same problem. Thx

[bluelife]

Ok, I have it working now.
For anyone else: uninstall network tool, restart.
Reinstall network tool, restart
Starting order was then mpc, turn on ethernet, then network tool until it finds it, and then bitwig.

Thanks

[chamania]

in the OSC Documentation there are note colors for scale, root etc
the script is sending notes and some colors via the vkb-midi osc messages.

i managed to make an isomorphic keyboard that works well but
how can i change scales etc or is this something that works only in reaper or is it a work in progress?
there is some kind of arpeggio included with options for note length and speed but no patterns.

would be awesome if we could have the push type scales portet over to OSC like you did for the launchpad if im not mistaken.

[xtreme sounds]

Hi i dont think the select knob on the akai fire to control a steps pitch is working on the drum machine at this time.

[AFranke]

It's simple, what I'm doing. I just select different tracks with the mouse, by clicking the header of the track that I want to select.

Ah, I see. That is actually a bug in Bitwig (I reported it already some time ago). It works if you click the tracks on the left instead.

Moin Jürgen,
I also reported this to Bitwig support last weekend. They wonder, as I also do, that it only happens with Push and they would get in contact with you.

Andreas