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

[akeia]

Firmware is also up to date?

Just tried an older Beatstep with Version 1.1.0.0 and it WORKS. There must have been changes on Arturia side that broke it.

SOLUTION:

Beatstep has a global transpose (SHIFT+Big Knob) that messed up the pad notes. This setting seems to live through flashing the OS version and the template. The script now works also on 1.2. Lesson learned: Check the MIDI monitor first.

[aMUSEd]

NI Kontrol S series is a bit broken in the 5.3 beta

[drsyncenstein]

question for those using Icon p1 Nano, or maybe for Moss?

With controllers, like the Arturia minilab or NI controllers with DBM, the controller focus follows the tracks i select in Bitwig with my mouse. So as long as i select what i want to edit with the mouse, it's the correct device on the controller.

Because the Icon controllers are based on HUI or Mackie UC and have dedicated buttons to select a track bank or a track, i wonder if they can do the same.
Because if i need to select a track or a device from the controller, while i already have it in focus from the mouse, it would not be very usable for me.
Anyone experience with that?

[drsyncenstein]

And any extension for the controller for the remote zero Sl for bitwig in the near future than? I just dont want to throw this device away..Danke!

Never had one for testing but in theory it should already work with the Remote Mk2 implementation.

It works partly, see a previous post from me:
viewtopic.php?p=8710530&hilit=drsyncenstein#p8710530

[moss]

Firmware is also up to date?

Just tried an older Beatstep with Version 1.1.0.0 and it WORKS. There must have been changes on Arturia side that broke it.

Hmm, strange. I just tested it to be sure and it works fine for me with 1.2.0.3.

EDIT: Ah, just saw you later post...

[moss]

NI Kontrol S series is a bit broken in the 5.3 beta

Which one, Mk1 or Mk2?

[aMUSEd]

MkIII

The ability to switch keyboard display modes is broken

[tamasj]

Hi guys,

I'm a new user, Novation SL49 Mk3 on Mac, Bitwig 5.2.

Spent a couple of hours trying to find out something, but probably it's better to find answer here.

So, everything works, apart from plugin parameters don't show up on the SL screens.
I can add VSTs from the controller, but only their name show up on the screen in the mint blue square and I can't see any assigned parameters to the knobs above the displays.

Although here I can assign parameter controls to the knobs and they work, but it only shows the CC number, not the name of the parameter.

With built-in Bitwig devices it works perfectly, set of parameters are displayed on on the screens with names.

Any idea?

Thanks in advance!

[tamasj]

Any idea?

Thanks in advance!

There is a .txt file with the list of the 3rd party dependecies with github links, it's not mentioned in the manual, but do I need to install them?

[moss]

MkIII

The ability to switch keyboard display modes is broken

Which button did you configure?

[moss]

Any idea?

Thanks in advance!

There is a .txt file with the list of the 3rd party dependecies with github links, it's not mentioned in the manual, but do I need to install them?

You need to create parameter pages for each VST plugin. Watch this:

[aMUSEd]

MkIII

The ability to switch keyboard display modes is broken

Which button did you configure?

METRO but I have tried reverting to the default STOP and the others but none work, the view stays on mixer

[moss]

MkIII

The ability to switch keyboard display modes is broken

Which button did you configure?

METRO but I have tried reverting to the default STOP and the others but none work, the view stays on mixer

Just checked and it works fine for me on Windows 11.

[vrobot]

Hi Moss,

I just purchased Bitwig and after seeing your videos the Akai Fire.
Amazing work on the integration, thank you for your time and effort.

I think I found a bug.
DrivenByMoss 24.5.1
Akai Fire
Bitwig 5.2.7

In drum4 mode when scrolling through the drum cells in Bitwig's Drum Machine device with the select knob, an empty cell in a row stops the scrolling.
The empty cell cannot be scrolled to and hence past to reach further populated cells.
The behaviour is different if the empty cell is first in a row, the left most cell.
Empty rows with no cells can be scrolled through and past.
The problem happens in both directions, scrolling forward and backwards.

To reproduce load a Drum Machine with a factory preset.
Delete a single cell's content.
Attempt to scroll past the empty cell.

Let Me know if you need more info or a video.
Apologies if this has been reported before, this thread is too long to read. I did search.


Cheers
Rob

[moss]

Hi Moss,

I just purchased Bitwig and after seeing your videos the Akai Fire.
Amazing work on the integration, thank you for your time and effort.

I think I found a bug.
DrivenByMoss 24.5.1
Akai Fire
Bitwig 5.2.7

In drum4 mode when scrolling through the drum cells in Bitwig's Drum Machine device with the select knob, an empty cell in a row stops the scrolling.
The empty cell cannot be scrolled to and hence past to reach further populated cells.
The behaviour is different if the empty cell is first in a row, the left most cell.
Empty rows with no cells can be scrolled through and past.
The problem happens in both directions, scrolling forward and backwards.

To reproduce load a Drum Machine with a factory preset.
Delete a single cell's content.
Attempt to scroll past the empty cell.

Let Me know if you need more info or a video.
Apologies if this has been reported before, this thread is too long to read. I did search.


Cheers
Rob

That's a known Bitwig issue. Reported it already quite some time ago...