Various session box issues
Hi
I’m trying to add an NI F1 to my setup. I previously had two XoneK2s, but I’m wanting to try out the F1. I’m also updating some settings now that I don’t have to provide scene stop buttons in the session box setup. Or I can provide ones on a different controller if I want. My aim is to use the F1 for transport and device control and the XoneK2 to continue as my track and clip controller.
The first problem I encountered is that when I deleted the values from the scenes and track stop editors, they weren’t all removed from the script. I think the scene stop ones remained. So I couldn’t use those control values for anything else until I manually modified the script and then imported it.
The second problem I encountered is that I can’t set up session boxes in combination. The app complained that I have to set the session boxes in different modes. But when I did that the first box stopped working. My session box navigation controls either had no effect or, those that shared a mode with the second session box moved the first one, but multiple steps rather than the single steps I’d set up.
The third problem is related to the second – after deleting the second session box to try to get the first one working again, the session box was not removed from the script, so it still appeared and the navigation of the first session box still didn’t work.
So how are combination boxes supposed to be set up?
Yes, custom coding in the script can lead to unexpected behaviour :p
FYI, the way code is generated by Remotify, its not possible for 2 session boxes to be loaded at the same time (in the same script).
If you want a session box to persist across multiple modes, set it to mode 0. This is the “global” mode which always remains active alongside another mode (modes 1 through to 16). So you can set controls on different modes to control a single instance of session box, which is what it appears you’re trying to achieve.
Hope this helps.
John
Sign up
User registration is currently not allowed.