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

[moss]

Changing the speed of the relative encoders does not work either unfortunately. I have looked at the issue again, and it really comes down to the fact that 7-bit CCs range from 0 to 127: once a control in the device panel is attributed to an encoder, its steps are 1/127 of the total range of the parameter.

No. Relative knobs send only +1 or -1 (or larger values if it is capable to detect turn-speed).

But I just noticed why it is not working for you. I use the setter method instead of the increase one due to harmonize the handling of different knob types. So, it is actually 128 values. Will see if I can change that...

[moscom_electronics]

Changing the speed of the relative encoders does not work either unfortunately. I have looked at the issue again, and it really comes down to the fact that 7-bit CCs range from 0 to 127: once a control in the device panel is attributed to an encoder, its steps are 1/127 of the total range of the parameter.

No. Relative knobs send only +1 or -1 (or larger values if it is capable to detect turn-speed).

But I just noticed why it is not working for you. I use the setter method instead of the increase one due to harmonize the handling of different knob types. So, it is actually 128 values. Will see if I can change that...

Great! Thanks again!

[xtreme sounds]

Hey sir would you be willing to fix the livid base script for Bitwig or make a better version? Its mostly done but has a few issues? If so only 2 files from the download pack are actually needed. I can tell you which ones and which 2 simple things need fixing.

http://wiki.lividinstruments.com/wiki/B ... stallation

If not I understand

[moss]

Hey sir would you be willing to fix the livid base script for Bitwig or make a better version? Its mostly done but has a few issues? If so only 2 files from the download pack are actually needed. I can tell you which ones and which 2 simple things need fixing.

http://wiki.lividinstruments.com/wiki/B ... stallation

If not I understand

I have no plans to support that device.

[tarjiband]

Hi guys,
I wonder if someone here can explain again how to make work push 2 with Bitwig, as there's almost no information left on that and the install for new comers is also impossible. non of the recent updates got a push extension and I can find no information on what and how to install. My push used to work with Bitwig up until now that my extension file is suddenly gone and who knows what else since a a few hours ago after installing Big Sur.
Please help!
Best

[moss]

Hi guys,
I wonder if someone here can explain again how to make work push 2 with Bitwig, as there's almost no information left on that and the install for new comers is also impossible. non of the recent updates got a push extension and I can find no information on what and how to install. My push used to work with Bitwig up until now that my extension file is suddenly gone and who knows what else since a a few hours ago after installing Big Sur.
Please help!
Best

Nothing has changed here and the information is really easy to find.
Download DrivenByMoss from http://www.mossgrabers.de and read the included manual for installation notes.

[tarjiband]

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 guys,
I wonder if someone here can explain again how to make work push 2 with Bitwig, as there's almost no information left on that and the install for new comers is also impossible. non of the recent updates got a push extension and I can find no information on what and how to install. My push used to work with Bitwig up until now that my extension file is suddenly gone and who knows what else since a a few hours ago after installing Big Sur.
Please help!
Best

Nothing has changed here and the information is really easy to find.
Download DrivenByMoss from http://www.mossgrabers.de (http://www.mossgrabers.de) and read the included manual for installation notes.

Hi,
Thanks for the quick reply. Really appreciated.
I'm downloading DrivenbyMoss 9.89 and there's no Bitwig extension file in it for push 2. What am I supposed to copy and paste in extensions folder then?
Would you be so kind to send me the link to the instruction you're mentioning? the only instruction I find just plainly tells me to copy the extension file which does not exist. the only DrivenbyMoss version I find which includes the extension file is way old with that push2display folder which again there's no instruction what to do with it.
your help is greatly appreciated man. Thank u in advance.

[moss]

Hi guys,
I wonder if someone here can explain again how to make work push 2 with Bitwig, as there's almost no information left on that and the install for new comers is also impossible. non of the recent updates got a push extension and I can find no information on what and how to install. My push used to work with Bitwig up until now that my extension file is suddenly gone and who knows what else since a a few hours ago after installing Big Sur.
Please help!
Best

Nothing has changed here and the information is really easy to find.
Download DrivenByMoss from http://www.mossgrabers.de and read the included manual for installation notes.

Hi,
Thanks for the quick reply. Really appreciated.
I'm downloading DrivenbyMoss 9.89 and there's no Bitwig extension file in it for push 2. What am I supposed to copy and paste in extensions folder then?
Would you be so kind to send me the link to the instruction you're mentioning? the only instruction I find just plainly tells me to copy the extension file which does not exist. the only DrivenbyMoss version I find which includes the extension file is way old with that push2display folder which again there's no instruction what to do with it.
your help is greatly appreciated man. Thank u in advance.

If you are still on Bitwig 3.1.x, you need to download DrivenByMoss-8.98-Bitwig.zip which I guess you did.
Then unzip the files. Take a look at the file DrivenByMoss-Manual.pdf. This is the manual which contains all you need to know about the installation.
The file which needs to be copied is DrivenByMoss.extension. This file contains all extensions, there is no specific file for the Push.

[xtreme sounds]

Hi on the latest fire script. Are you sure the Drum machine pitch (selector knob) is working on the steps? I have the knob speed set to 15. Is that causing the issue?

Is there a way to add a midi clip with recording?

[moss]

Hi on the latest fire script. Are you sure the Drum machine pitch (selector knob) is working on the steps? I have the knob speed set to 15. Is that causing the issue?

Yes, this can be an issue.

Is there a way to add a midi clip with recording?

You can press a clip on the grid (depending on the action you have selected in the settings).

[xtreme sounds]

Hi on the latest fire script. Are you sure the Drum machine pitch (selector knob) is working on the steps? I have the knob speed set to 15. Is that causing the issue?

Yes, this can be an issue.

The pitch selector knob on a drum step is not working automatically. The reason I forgot about is that in Bitwig we have to turn the samplers key tracking "ON" for each part of the drum kit. Which then lowers the sample down by 2 octaves.

[dplduffy]

Hey Moss,

Loving the SL MKIII script, thanks so much for the work you do on these. I have a couple requests

1. The ability to drill into FX inside devices. Currently in Device - Devices Mode I can only see devices that are in the top level of the track. For example if I have Polysynth followed by a Blur effect I can see both of them on the display, but if I put the Blur device inside the Polysynth FX container the only way to get to it is clicking Blur on my screen.
2. The light guide to follow the octave transposition of the keybed. Currently if I am on Octave 0 and play a key the corresponding key lights up as I would expect, however if I go to any other Octave (ex Octave 1) and press the same key, the light that turns on is one octave above the key I am pressing. I'm guessing this is because the light you are displaying is the note being sent to bitwig and there is no way for you to know what octave the keybed is on (since Novation doesn't expose that information to you, I just checked the programmers reference guide)... Is this correct? I guess I would need to send a request to novation for that one lol.

Thanks again!

[moss]

The ability to drill into FX inside devices.

Yes, this means also to support layers, which I so far did only on the Push. This is horribly complicated but I simplified some things internally not too long ago, so might be worth to give it a shot.

The light guide to follow the octave transposition of the keybed. Currently if I am on Octave 0 and play a key the corresponding key lights up as I would expect, however if I go to any other Octave (ex Octave 1) and press the same key, the light that turns on is one octave above the key I am pressing. I'm guessing this is because the light you are displaying is the note being sent to bitwig and there is no way for you to know what octave the keybed is on (since Novation doesn't expose that information to you, I just checked the programmers reference guide)... Is this correct? I guess I would need to send a request to novation for that one lol.

Sadly, your assumption is right. I asked Novation about it and they are busy with lots of new stuff. So, not sure if they will revist this again and you should definitively make your voice heard

[dplduffy]

The ability to drill into FX inside devices.

Yes, this means also to support layers, which I so far did only on the Push. This is horribly complicated but I simplified some things internally not too long ago, so might be worth to give it a shot.

The light guide to follow the octave transposition of the keybed. Currently if I am on Octave 0 and play a key the corresponding key lights up as I would expect, however if I go to any other Octave (ex Octave 1) and press the same key, the light that turns on is one octave above the key I am pressing. I'm guessing this is because the light you are displaying is the note being sent to bitwig and there is no way for you to know what octave the keybed is on (since Novation doesn't expose that information to you, I just checked the programmers reference guide)... Is this correct? I guess I would need to send a request to novation for that one lol.

Sadly, your assumption is right. I asked Novation about it and they are busy with lots of new stuff. So, not sure if they will revist this again and you should definitively make your voice heard

Sounds good! I’ll send a email to novation support asking for it

[maciej86]

Hello fellow users,

I am currently using Komplete Kontrol S25 mk1 and Launchpad X to control Bitwig. All working nicely with the drivenByMoss script but I am having some problems when mapping parameters to external vsts. Take Arturia's Mini V for example:
1. mapping plugin buttons
the VST button is OFF when the knob is "0" and ON when the knob is ">0". This works but being not symetrical (only 1 value for OFF and many values for ON) makes it somewhat less immediate. Now, this can be fixed by first mapping the VST button to Bitwig's modulator button and then mapping the modulator button to the controller in the Preset Page. It has to be Preset Page and not Device Page, even though built in instruments like Polysynth support buttons in the Device Pages. Does anybody know why is this? Or is there an alternative way to map VST buttons? Or perhaps a controller with both knobs and buttons can work better? (Like Push 2, KK mk2 or Maschine)

2. mapping plugin multi-select switches
They are encoders but with finite number of positions. On Mini V this is the waveform select switch for example. When I mapp the multi-select switch in the Device Page (or the Preset Page) the selection is very "choppy". Turning a knob on S25 doesn't change anything until I turn it fast, but then it might skip a few selections because of this. I was experimenting with the "knob sensitivity" setting in the KK script by Moss, however I can't seem to find a good setting.
A workaround I found is again to use Bitwig modulator. Mapp multi-select switch to Macro and then the macro to Device page. This restores the smoothness but makes the knob on the KK display % value of the Macro as opposed to the multi-select value (in this example the waveform name: square, sawtooth etc.) Is there alternative way? Perhaps toggle different states with a button press instead of rotary encoder?


I'm on Bitwig 3.2.8, the controller settings for KK display "BETA" in case this is important
Using DrivenByMoss 11.5.2

Sorry for lengthy post, I hope it makes sense and someone can point me in the right direction. And thanks for the awesome work with the scripts!

Best Regards,
Maciej