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

[JayBee-one]

I discoverd the script Console. Its full of this:
(Sorry for the image, posting the errors is not allowed by forumsoftware

2020-06-27 09_38_16-Window.png

Hi,
Bitwig and Script is newest Version. System is Win10

My APCmini does not work. Actually it stucks in the shift Page if i want to select the Drum sequencer.
Yesterday the Srum sequenzer behaves strangly. Could not set steps, setting bar length does not work.
It works very strange. Not like you shoewed in the Video.
If i press Shift the right round Buttons do not lit.
Any Idea.
Thanks.

[dot.solenoid]

Hello Jurgen,

DBM 10 on bitwig 3.2.3 with Icon Qcon Pro X (firmware 2.05)

Using the "toggle faders as editing knobs" does not disable the "select channel on fader touch". So touching any fader results in selecting another track instead of changing the parameter value.

Steps to reproduce:
Activate "toggle faders as editing knobs"
Motorfader adjust to the device parameters
Second display (above motor fader) remains in track mode (should display parameter values/names?)
Touching any knob to change a parameter: this selects a different track instead of changing the parameter value.

[xtreme sounds]

Hi sir

I have another question for you. I see that it appears the fire does not have the same drumpad levels of control as the akai apc40 mk 2 does. Can we get an update wheer if we press a pad with an assigned note we can adjust the following on the fire?

Press the pad of an existing note and keep it pressed to edit the values of a note with the 8 mode knobs. The knobs edit the following parameters:

Gain
Pitch
Velocity (not sure if thats possible on fire)
swing (nudge) - not sure if that possible

I would also be interested if we can assign different samples per step as well without changing the root note. I think this should be possible using layered instrument with drums or something.

I know that a sampler can be placed in a drumpad hit. so the ability to change the position of a sample which has several sounds within in should work.

Hopefully you understand what Im getting at here

[dot.solenoid]

Hello Jurgen,

I'm sorry to report some issues with the DBM 10 on bitwig 3.2.3 with Icon Qcon Pro X (firmware 2.05). It feels like I'm just nagging you instead of rewarding the real value of DBM. Without this driver package, I would not consider bitwig as my next DAW (probably Ableton)

selecting "SEND" enables to cycle trough the FX tracks, on both displays, there is no information on the selected FX channel:

The first display shows the correct FX send values of each track but the second display shows the previously selected (instrument) track & device instead of the currently selected FX track & selected FX device.

Using the cursor keys on the Qcon or mouse to select any FX track the second displays the correct selected device (Sel. device: ......) but the selected track is always named "none" (Sel. Track: None)

[moss]

Hi,
I mapped a Diatonic Transposer Device to a device page and this happens:

Ah, interesting. The SL can only display ASCII characters, I replaced this special character now with the normal ASCII #. Will be fixed in the next update.

The whole mapping thing is a complete mess on the SL MK3, none of any renamed parameter is displayed on its screens. Always the original parameters names of any device are shown up. I really hope this will be fixed some day.

I renamed several parameters of the Diatonic Transposer, also tried with a VST2 and all works well. Also restarted Bitwig several times and the renamed parameters showed up as expected. Could you do a video about that as well?

[moss]

I discoverd the script Console. Its full of this:
(Sorry for the image, posting the errors is not allowed by forumsoftware

Hi,
Bitwig and Script is newest Version. System is Win10

My APCmini does not work. Actually it stucks in the shift Page if i want to select the Drum sequencer.
Yesterday the Srum sequenzer behaves strangly. Could not set steps, setting bar length does not work.
It works very strange. Not like you shoewed in the Video.
If i press Shift the right round Buttons do not lit.
Any Idea.
Thanks.

Thanks for reporting. Will be fixed in the next update.
Until then it should work as a workaround to turn off the Scale button.

[moss]

Hi,
Bitwig and Script is newest Version. System is Win10

My APCmini does not work. Actually it stucks in the shift Page if i want to select the Drum sequencer.
Yesterday the Srum sequenzer behaves strangly. Could not set steps, setting bar length does not work.
It works very strange. Not like you shoewed in the Video.
If i press Shift the right round Buttons do not lit.
Any Idea.
Thanks.

Will both be fixed in the next update!

[moss]

Hello Jurgen,

DBM 10 on bitwig 3.2.3 with Icon Qcon Pro X (firmware 2.05)

Using the "toggle faders as editing knobs" does not disable the "select channel on fader touch". So touching any fader results in selecting another track instead of changing the parameter value.

Good catch! Will be fixed in the next update.

[moss]

I have another question for you. I see that it appears the fire does not have the same drumpad levels of control as the akai apc40 mk 2 does. Can we get an update wheer if we press a pad with an assigned note we can adjust the following on the fire?

That's already possible. I forgot to mention it in the manual but you can see it in the begging of the tutorial video.

I would also be interested if we can assign different samples per step as well without changing the root note. I think this should be possible using layered instrument with drums or something.
I know that a sampler can be placed in a drumpad hit. so the ability to change the position of a sample which has several sounds within in should work.

You can put anything in a drum machine cell incl. device layers but controlling that from a controller is very comlicated and definitvely too much for the small Fire.

[moss]

Hello Jurgen,

I'm sorry to report some issues with the DBM 10 on bitwig 3.2.3 with Icon Qcon Pro X (firmware 2.05). It feels like I'm just nagging you instead of rewarding the real value of DBM. Without this driver package, I would not consider bitwig as my next DAW (probably Ableton)

selecting "SEND" enables to cycle trough the FX tracks, on both displays, there is no information on the selected FX channel:

The first display shows the correct FX send values of each track but the second display shows the previously selected (instrument) track & device instead of the currently selected FX track & selected FX device.

Using the cursor keys on the Qcon or mouse to select any FX track the second displays the correct selected device (Sel. device: ......) but the selected track is always named "none" (Sel. Track: None)

If you select the Send mode you are not editing this Send channel but the volume that is sent to this send channel.

To edit the effect channel you need to switch to the effect track bank. On the QCon it is the button above the "8>>".

If you click on an effect track in Bitwig the current track bank is not toggled on the controller. That's why you saw 'no track selected'.

[esq1]

Hello Jürgen, can it be that the new color support for the drum sequencer is different for Windows and Linux with PUSH 1?
With my Linux installed, the colors are displayed immediately. With Windows 10 only when I change the track and go back again. DrivenByMoss 10.0, Bitwig 3.2.*

Hallo Jürgen, ich habe bei mir Bitwig unter Ubuntu 20.04 aufgespielt und dein Script (Vers.10, Bitwig 3.2.3) natürlich gleich mit dem PUSH1 ausprobiert. Bei Windows 10 musste ich einmal den Track wechseln und zurück zur Drum Sequncer spur gehen damit mir die Farben der Drumpads am Push 1 angezeigt werden. Bei Linux ist das erfreulicher Weise nicht so. Wennn ich in Bitwig die Farben für die Pads einstelle werden sie am Push 1 sofort übernommen. Ich kann es jetzt leider nicht rückwirkend probieren da ich mein Windows ersetzt habe.

[moss]

Hello Jürgen, can it be that the new color support for the drum sequencer is different for Windows and Linux with PUSH 1?
With my Linux installed, the colors are displayed immediately. With Windows 10 only when I change the track and go back again. DrivenByMoss 10.0, Bitwig 3.2.*

Hallo Jürgen, ich habe bei mir Bitwig unter Ubuntu 20.04 aufgespielt und dein Script (Vers.10, Bitwig 3.2.3) natürlich gleich mit dem PUSH1 ausprobiert. Bei Windows 10 musste ich einmal den Track wechseln und zurück zur Drum Sequncer spur gehen damit mir die Farben der Drumpads am Push 1 angezeigt werden. Bei Linux ist das erfreulicher Weise nicht so. Wennn ich in Bitwig die Farben für die Pads einstelle werden sie am Push 1 sofort übernommen. Ich kann es jetzt leider nicht rückwirkend probieren da ich mein Windows ersetzt habe.

There should be no difference. It is also necessary that you have the track selected which contains the drum machine, this can be confusing sometimes.

[dot.solenoid]

selecting "SEND" enables to cycle trough the FX tracks, on both displays, there is no information on the selected FX channel:

The first display shows the correct FX send values of each track but the second display shows the previously selected (instrument) track & device instead of the currently selected FX track & selected FX device.

Using the cursor keys on the Qcon or mouse to select any FX track the second displays the correct selected device (Sel. device: ......) but the selected track is always named "none" (Sel. Track: None)

If you select the Send mode you are not editing this Send channel but the volume that is sent to this send channel.

To edit the effect channel you need to switch to the effect track bank. On the QCon it is the button above the "8>>".

If you click on an effect track in Bitwig the current track bank is not toggled on the controller. That's why you saw 'no track selected'.

Hello Jurgen.

After reseting DBM 10 and selection Pro X setting this issues seems resolved.

[Krooked]

Hi moss, are the user osc parameters still broken? Can't seem to get them to work.

[moss]

Hi moss, are the user osc parameters still broken? Can't seem to get them to work.

Yes, still broken but should be fixed in the next Bitwig update.