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?
I’m now getting told that a control I haven’t used in the session box is used in the session box. The session box has CC32 on channel 15 (the XoneK2) for one of the track launch buttons. I had the transport stop already assigned to CC32 on channel 13 (the F1). The transport play, stop, etc., set up on the F1, no longer work. When I opened the stop in the editor and simply tried to save it without making changes I got an error stating that I’d already used the setting combination already. It turned out this one is because the app had the midi controller values set to have channel 13, even though the script had 15 as the channel on the session box.
There are other weird clashes going on. The track stop buttons don’t work after changing them back to the XoneK2 in the session box settings (the JSON kept the channel set to 13 even though I’d used midi learn to set channel 15). The track 1 arm button doesn’t work at all (I’ve checked the values). And the LEDs on display don’t match the settings – the arm buttons all light up when I shift to mode 2 and back to mode 1. An LED in the top row randomly turns on or off when I shift to 2 and back to 1 as well.
It took hours to get the initial setup working. With the recent changes, trying to get LEDs to work as expected again and trying to add the F1 has cost most of the last two days and I’m no closer to having working scripts. Is there perhaps some way to determine whether settings will work and, when they don’t, why not?
Sign up
User registration is currently not allowed.