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

[moss]

Uuuh! This bug was corrected some time ago, but it is here again. The SL MK3 does not display renamed parameters correct anymore. It displays only the original parameter names. In DrivenByMoss 10.7.4 all works fine! All newer ones do not.

Hmm, I see. Last time it was accidental, now it is intentional. Need to talk to Bitwig if they can fix this or I need to think about a workaround.

[AFranke]

Uuuh! This bug was corrected some time ago, but it is here again. The SL MK3 does not display renamed parameters correct anymore. It displays only the original parameter names. In DrivenByMoss 10.7.4 all works fine! All newer ones do not.

Hmm, I see. Last time it was accidental, now it is intentional. Need to talk to Bitwig if they can fix this or I need to think about a workaround.

If it's intentional, why 10.7.4 still works just fine until today in 3.2.8 & 3.3 beta? Hmmmm....

[moss]

Uuuh! This bug was corrected some time ago, but it is here again. The SL MK3 does not display renamed parameters correct anymore. It displays only the original parameter names. In DrivenByMoss 10.7.4 all works fine! All newer ones do not.

Hmm, I see. Last time it was accidental, now it is intentional. Need to talk to Bitwig if they can fix this or I need to think about a workaround.

If it's intentional, why 10.7.4 still works just fine until today in 3.2.8 & 3.3 beta? Hmmmm....

Because I switched to the new hardware API which has a specific function to get the label. This function seems currently not to respect the change. As I wrote above I am not sure if this can be fixed on Bitwigs side since a parameter could be assigned to multiple pages with a different name.

[AFranke]

Uuuh! This bug was corrected some time ago, but it is here again. The SL MK3 does not display renamed parameters correct anymore. It displays only the original parameter names. In DrivenByMoss 10.7.4 all works fine! All newer ones do not.

Hmm, I see. Last time it was accidental, now it is intentional. Need to talk to Bitwig if they can fix this or I need to think about a workaround.

If it's intentional, why 10.7.4 still works just fine until today in 3.2.8 & 3.3 beta? Hmmmm....

Because I switched to the new hardware API which has a specific function to get the label. This function seems currently not to respect the change. As I wrote above I am not sure if this can be fixed on Bitwigs side since a parameter could be assigned to multiple pages with a different name.

Ah, that makes sense! Thank you. For me, the ability to add, edit and display those pages on the dis plays was the main reason to get and use and SL MK3. I use it a lot and have made many configs for my plugins.

[babyblue]

Hi Jürgen,

i am just (again) configuring my PCR 500 knobs & faders to control the mixer in Bitwig 3.2.8 with 10.9.0.
When i select the next free "Slot", the "Selected Slot-Midi-trigger" > "Type": value always jumps to the default "Off" entry.
It would be fine, if Flexi could "remember" the last used Type: e.g. CC.
Thanks for your Flexi!
Best regards
Bernd

[babyblue]

Hi,

is it possible to control Instrument parameters with the 8 (9) knobs and faders of a PCR 500, although i have already assigned them with Flexi to control the volume and pan of Bitwigs mixer?

Studio One differentiate between Focus:Global (Mixer) and Focus:Instrument. Is there sth. similar in Bitwig?

[moss]

Hi,

is it possible to control Instrument parameters with the 8 (9) knobs and faders of a PCR 500, although i have already assigned them with Flexi to control the volume and pan of Bitwigs mixer?

Studio One differentiate between Focus:Global (Mixer) and Focus:Instrument. Is there sth. similar in Bitwig?

Yes, use the Modes feature. See

[babyblue]

thanks

[superscalar]

hi everybody,

i have an issue with my beatstep. dont know if it is my hardware, setup or a bug.
in play mode i cannot move the base note upwards.
if i select the base note to Gb in bitwigs "studio io" section i can bring the base note down to C. but i cannot move the base note in the opposite direction.

running bitwig on arch linux.

best regards. ingo

[babyblue]

i forgot the procedure how to save a Flexi Setting...
i get an alert "Error writing file: PCR(Zugriff verweigert"

i got it, hope so. I created an empty document txt file and renamed it PCR-500.properties file.
Now i can load and save the settings....

[babyblue]

Hi,

is it possible to control Instrument parameters with the 8 (9) knobs and faders of a PCR 500, although i have already assigned them with Flexi to control the volume and pan of Bitwigs mixer?

Studio One differentiate between Focus:Global (Mixer) and Focus:Instrument. Is there sth. similar in Bitwig?

Yes, use the Modes feature.

sorry, i don't understand how to use the Modes feature. I have configured the R1 Knob of my PCR, Selected Mode: Panorama, to move the Panorama of track 1. Now, when i change Selected Mode: Send 1, my R1 Knob is controlling Send 1 (Track 1) and looses the Pan control of track 1, what am i doing wrong?

[moss]

Hi,

is it possible to control Instrument parameters with the 8 (9) knobs and faders of a PCR 500, although i have already assigned them with Flexi to control the volume and pan of Bitwigs mixer?

Studio One differentiate between Focus:Global (Mixer) and Focus:Instrument. Is there sth. similar in Bitwig?

Yes, use the Modes feature.

sorry, i don't understand how to use the Modes feature. I have configured the R1 Knob of my PCR, Selected Mode: Panorama, to move the Panorama of track 1. Now, when i change Selected Mode: Send 1, my R1 Knob is controlling Send 1 (Track 1) and looses the Pan control of track 1, what am i doing wrong?

Nothing, that's how it works. A mode has 8 parameter knobs for one page of X. Where X is Volume, Pan, Send 1, Parameter, etc. The page can be navigated up / down with the respective functions. What you might be looking for is the Track mode. This gives you the controls of the selected track with: Volume (Knob 1), Pan (Knob 2), Send 1 (Knob 3), Send 2 (Knob 4), ...

[moss]

hi everybody,

i have an issue with my beatstep. dont know if it is my hardware, setup or a bug.
in play mode i cannot move the base note upwards.
if i select the base note to Gb in bitwigs "studio io" section i can bring the base note down to C. but i cannot move the base note in the opposite direction.

running bitwig on arch linux.

best regards. ingo

Thanks, will be fixed in the next update.

[superscalar]

hi everybody,

i have an issue with my beatstep. dont know if it is my hardware, setup or a bug.
in play mode i cannot move the base note upwards.
if i select the base note to Gb in bitwigs "studio io" section i can bring the base note down to C. but i cannot move the base note in the opposite direction.

running bitwig on arch linux.

best regards. ingo

Thanks, will be fixed in the next update.

great! thank you

[neijlu]

Using the latest DrivenByMoss script 10.8.0 on linux (Linux Mint 20 == ubuntu 20.04) , I can't get BWS 3.28 or 3.3 beta to work reliably with my APCMini. It s more than feasible that I am doing something wrong i.e. using BWS incorrectly and I wondered if someone could offer me some advice please.

I am afraid it is the device that is a bit wonky. I had similar issues since the beginning, like lights going of for no particular reason. Only solution is then to unplug and replug it.

Hello, using BTW on linux with novation LPmk3 and akai APCMini

I know there already was some bugs with APCMini and moss extension, but I only use the APC to control launching clip, in session mode, and it was working well with DBMoss 7.6, ruining BTW 3.2.8

But the session mode doesn't work anymore with the two new versions 8.98 and 10.9 ,(if we select the session mode we see the note mode)

It is a way to see what change in the script between version 7.6 and 3.2.8 make the session mode doesn't work anymore ? (and may be made it work in next release

(Hope to be understandable with my bad english )