The aim is not to expand the grid, rather to just keep one controller operating the grid (officially supported), and the generic script to just operate on whatever the grid the officially supported controller have set.moss wrote: ↑Fri Oct 29, 2021 4:34 amYou cannot combine them to create a larger grid if that is what you asking. But sure you can use both to e.g. edit on one the plugin, control volumes on a second and play on a third.Mantras wrote: ↑Fri Oct 29, 2021 3:33 amI have a question about the generic controller script.
If I have 2 controllers, one officially supported where I can navigate the "session box" with up-down-left-right buttons, to basically steer what tracks and clips are in focus by 8x8, and another controller with the generic script - is it possible to have the generic controller script to chain on to whatever the "session box" is set at by the official controller?
I hope you understand. For instance, by the generic script controlling pan, send or volume on whatever tracks is in the "focus" from the other controller.
From my days with Ableton using two different controllers would result in two different "focus groups", two different colored squares, where I would have to move the square on both controller to keep it at sync.
So my aim is using Bitwig with two controller but just have one controller as the master, deciding where the focus on the clips and tracks is, and the slave controller (generic midi script) to just modulate whatever the focus is set on by the other controller...
It's difficult to explain!