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

[EEGsynth]

Hi there! First of all, amazing work MOSS!

I've set up a simple patch to send OSC commands (e.g. from Pure Data and a Python library I am making) to Bitwig, using vkb MIDI note messages and convert them in Poly Grid into a modulation signal. However, this limits me severely to 128 MIDI notes, and 1 channel per Poly Grid patch. Is there away around this using OSC with Bitwig somehow? Is there any way using more than 7 bits? I've been able to use double that on a MIDI2CV convertor using pitchbend, but I don't see a way to do that with DrivenByMoss/Bitwig, and I rather not use MIDI at all.

Thanks!
Steve

[moss]

Hi Moss, thanks for everything

My English is not very good, I meant this view isn't working, I can change the selected pad but I can't change the volume, pan or sends.

Hope that clears my question
THanks!!

Sorry, I cannot see a problem. Changing the drum slot settings works fine here in all modes. Could you please check if the drum device is selected and a clip on that track is selected as well? If you are still stuck, maybe you could do a video, so I could see what you are doing and the issue.

[moss]

Hi Moss.
Thank you for fixing the issue of only 8 user controls being available in your OSC script. I've come across an issue that happens on all controllers and I'm curious if you know what's causing it.
If a parameter has written automation and a physical knob (be it MIDI knob, MIDI encoder or OSC control) that I can move I'll come across a weird bug. The first MIDI/OSC message sent doesn't move the software control. So if a knob is at 0% and I send a MIDI/OSC message that should move it to 50% it doesn't do anything (it activates the green automation override dot and momentarily flashes the control as if it was moved to 50% for 1ms and the back to 0%) until I send a message that would move it to 51%. Then it's back to business.
I've tried this on 3 different controllers with different control scripts, one with knobs, one with encoders and OSCPilot.
Have you ever come across something like this, is this an old issue?
Thanks.

Edit: happens with the mouse as well. This is an internal Bitwig problem

Set the take over mode to "Immidiate" and see if this fixes your issue.

[moss]

Hi,
i'm having issue with flexi for selecting action, the list is huge and everything doesn't fit on my screen.
i can still select with arrows keys outside the screen but i can't see what i'm selecting.
https://imgur.com/a/U6QUy01
i'm on Bitwig 3.3 with DrivenByMoss 10.9.2
i'm on OSX 10.13.6

Thanks for you help.

Yeah, I see what you mean. The possibilities you have regarding UI is a bit limited, not sure what to do about it. Will think about it.

[moss]

Hi there! First of all, amazing work MOSS!

I've set up a simple patch to send OSC commands (e.g. from Pure Data and a Python library I am making) to Bitwig, using vkb MIDI note messages and convert them in Poly Grid into a modulation signal. However, this limits me severely to 128 MIDI notes, and 1 channel per Poly Grid patch. Is there away around this using OSC with Bitwig somehow? Is there any way using more than 7 bits? I've been able to use double that on a MIDI2CV convertor using pitchbend, but I don't see a way to do that with DrivenByMoss/Bitwig, and I rather not use MIDI at all.

Thanks!
Steve

You could also add poly aftertouch to the game but maybe it is easier if you do your own OSC implementation.

[EEGsynth]

Hi there! First of all, amazing work MOSS!

I've set up a simple patch to send OSC commands (e.g. from Pure Data and a Python library I am making) to Bitwig, using vkb MIDI note messages and convert them in Poly Grid into a modulation signal. However, this limits me severely to 128 MIDI notes, and 1 channel per Poly Grid patch. Is there away around this using OSC with Bitwig somehow? Is there any way using more than 7 bits? I've been able to use double that on a MIDI2CV convertor using pitchbend, but I don't see a way to do that with DrivenByMoss/Bitwig, and I rather not use MIDI at all.

Thanks!
Steve

You could also add poly aftertouch to the game but maybe it is easier if you do your own OSC implementation.

I would be interested in making my own OSC implementation. I wouldn't know where to start, however, or how to easiest create modules for BitWig. I will see if I can find something on that, but any pointers to resources or people would be greatly appreciated!

[moss]

Hi there! First of all, amazing work MOSS!

I've set up a simple patch to send OSC commands (e.g. from Pure Data and a Python library I am making) to Bitwig, using vkb MIDI note messages and convert them in Poly Grid into a modulation signal. However, this limits me severely to 128 MIDI notes, and 1 channel per Poly Grid patch. Is there away around this using OSC with Bitwig somehow? Is there any way using more than 7 bits? I've been able to use double that on a MIDI2CV convertor using pitchbend, but I don't see a way to do that with DrivenByMoss/Bitwig, and I rather not use MIDI at all.

Thanks!
Steve

You could also add poly aftertouch to the game but maybe it is easier if you do your own OSC implementation.

I would be interested in making my own OSC implementation. I wouldn't know where to start, however, or how to easiest create modules for BitWig. I will see if I can find something on that, but any pointers to resources or people would be greatly appreciated!

There is an in-depth Bitwig programming tutorial series on my Youtube channel:

Part XI looks into OSC.

[NKirn93]

Set the take over mode to "Immidiate" and see if this fixes your issue.

It was on immediate. That was the first thing I tried.

[moss]

Set the take over mode to "Immidiate" and see if this fixes your issue.

It was on immediate. That was the first thing I tried.

Then I have no idea because what you described sounds like that.

[moss]

DrivenByMoss 10.9.3 is online!

• Requires Bitwig 3.2.5+
• All devices
  • New: The cursor clip can now be pinned in the studio pane (below the cursor track). By using this you can edit different launcher clips on multiple controllers.
• Novation SLMkIII
  • New: Press Stop + Clip in Session mode to stop the playback of the clip.
  • New: Shift + Play toggles write arranger automation.
  • New: Shift + Loop toggles write clip launcher automation.
• OSC
  • New: Added new command /track/{1-8}/remove
  • New: Added new command /device/remove
• Push 1/2
  • New: First button in the clip mode toggles if the clip is pinned.
  • New: Improved the layout of the Groove mode.

Enjoy!

[EEGsynth]

Hi there! First of all, amazing work MOSS!

I've set up a simple patch to send OSC commands (e.g. from Pure Data and a Python library I am making) to Bitwig, using vkb MIDI note messages and convert them in Poly Grid into a modulation signal. However, this limits me severely to 128 MIDI notes, and 1 channel per Poly Grid patch. Is there away around this using OSC with Bitwig somehow? Is there any way using more than 7 bits? I've been able to use double that on a MIDI2CV convertor using pitchbend, but I don't see a way to do that with DrivenByMoss/Bitwig, and I rather not use MIDI at all.

Thanks!
Steve

You could also add poly aftertouch to the game but maybe it is easier if you do your own OSC implementation.

I would be interested in making my own OSC implementation. I wouldn't know where to start, however, or how to easiest create modules for BitWig. I will see if I can find something on that, but any pointers to resources or people would be greatly appreciated!

There is an in-depth Bitwig programming tutorial series on my Youtube channel:

Part XI looks into OSC.

Oh, that's wonderful, thanks!

[anttumad]

Very nice work, thanks a lot.
I'm on Komplete A49 and when I press the octave down and up buttons I get a voice notification.
How can I disable it?
I've searched for this problem in the threat with no luck.

Thanks a lot!

[moss]

Very nice work, thanks a lot.
I'm on Komplete A49 and when I press the octave down and up buttons I get a voice notification.
How can I disable it?
I've searched for this problem in the threat with no luck.

Thanks a lot!

I guess you mean the Accessibility Mode? You can turn it on/off with Shift+Mixer.

[anttumad]

Thats it! Shift+Ideas (button) deactivates it.
Thank you again for the good job and the quick answer!

[artsense]

DrivenByMoss 10.9.3 is online!

first of all big thanks for your job!
found 2 litle bugs with Push2 on Bitwig:
1. Brightess of the LEDs is always on max after first start of Push. It show right numbers in Setup menu, but always on max untill i touch the LEDs knob
2. Everytime i start Ableton after Bitwig my Push2 going crazy with colors of pads and etc until Push2 restart

was the same behaviour on previous versions...