It would be nice if the remote controls of the first device in the selected chain were automatically mapped to the encoders on the OT

When the extension boots up, it doesn't know what scenes are selection on slots A and B, nor does there seem to be a way of asking (I had thought that the CC61 with a value of 0 trick was working, but closer testing suggests otherwise.

It's not a huge deal, as the situation would no doubt resolve itself quickly as the user starts selecting scenes. In any case, there should be a way to have this persist across sessions

Currently, when in device remote control mode, navigation between devices is quite limited. In particular, you can only access devices at the same 'level', which means you can't get into device chains or anything like that.

The underlying issue here is likely something similar to #22

Produce a prototype of bringing OT scenes into the Bitwig modulation system

OT has a 'command' to send all of its current CC values (at least on the audio side; less sure about MIDI). That might be handy.

It might also be nice to push to the OT the current values of all things it currently controls, if that thing exists.

• hit a button and pull in the current state of the software world -- ideally without having the hardware echo the message back.
• and conversely, hit a button and push the current state of the hardware world (a good candidate for being hidden behind a shift function

There are currently unused:

• encoders (PB and AT)
• a few trig keys
• the page key
• the yes and no buttons, but they probably can't be used without impacting functionality on the audio side
• the crossfader
• the scene keys

Look into sending MIDI data out from Bitwig to control the OT's crossfader. The source should of the data to send out should be configurable (e.g. mod wheel (CC 1)).

So far, I haven't done anything at all with the Clip Launcher. It's not really part of my workflow, but it might be nice at least to have a quick way create and record a clip on the current track. Something along those lines.

The purpose of this ticket is to look into what might make sense and then create some other tickets to implement whatever ideas emerge.

Complete current path of 'linear' or single-parameter banks per track (track 1 is volumes, 2 is pans, etc.)

Look into something a little more track oriented:

• CCs of each track mapped to a bank of 8 (or maybe 7, plus one for master/project) tracks
• page 1 has vol, pan, send1, send2
• page 2 has remote controls (?)

Currently, when you navigate the main track bank forward or backward, there are a few potential issues.

1. Page crosses group boundaries

• if you have, say, 2 normal tracks, a group with 2 tracks, and then 5 more normal tracks after it, then the bank would include the first two, the group plus its two members, and then 2 of the remaining tracks for a total of 7 (instead of what you might expect, that the internal tracks of the group would be skipped)
• it is definitely possible to include tracks in the bank only if they are at the same level, as DrivenByMoss works this way
• I think it might be a nice thing to have as an option

2. Moving the track bank back and forth does not change the track selection

• mostly, I kind of like this because it doesn't force all controllers to focus on the same track
• but it would be nice to have as an option

In Bitwig, remote control banks / pages really want to be of size 8. FX2 page on the OT has only 6 controls. Even when defined as having a size of 6, navigation of the pages still proceeds in 8s; hence the last two are inaccessible.

Can we scroll these 6 controls within the larger 8-control page in a sub-page of some kind? Failing that, can we get the PB and AT knobs of FX1 to work?

Lots of small things could be cleaned up:

• make sure static values are in constants and those constants centralized
• to many variables are protected
• do we really need everything to be final or is that just some weird convention?
• JavaDoc or at the very least the occasional explanatory comment
• and the like

I looked into this briefly early on, but it would be nice if the transport controls (at least play and stop) on the OT could control BW's transport.

Currently, the master track only supports the project remotes, but not remotes on devices on the master track.

I think it might also be impossible to navigate pages of the project remotes, but not completely sure Page nav for project remotes works. Just device remotes needs to be added