Ok, I don't think at this point it's a secret that I'm struggling to get VC to do what I want with a BCF2000 and an APC Mini. For example, I would love the cue list to run the functions (scenes mostly) that are created without being modified by what's going on with the sliders controlling individual lights. I have tried setting all fixture channels to LTP rather than HTP, I have tried unsuccessfully to get loopback to work to reset all the sliders before running functions in the cue list. Right now it's honestly very hit or miss as to what will happen whenever I do anything. I'm attaching my current qxw file, in hopes that someone will take a look at it and give me some pointers to adjust.
My main goal is to streamline setting scenes with the physical sliders, dump them to a scene, then create a cue list with those scenes, and have the cue list be able to run without interference. Looking at the dmx monitor, It's hard to really see what's going on. I tried creating a ZERO level function to run before running the cue list, but that doesn't seem to work. Help! Help! and yes I've been through all the forums and documentation.
For more clarification... When I run the cue list with existing scenes something is keeping control and the DMX Monitor shows that it's not getting the DMX values that the function should be sending. They are currently remaining zero most of the time. The BCF Sliders are getting the input from the scene but it's not getting passed on. Not at all sure why?
I suggest to keep HTP and LTP like the fixture definition editor originally put them by default, and try the following instead:
Use the lower (empty) frame in your workspace as a container for the 50+ page frame, and add a submaster to this "parent" frame.
To do that, select the multipage frame in design mode and press ctrl-c, then enlarge the lower frame, hover the mouse over it's inner area and ctrl-v. Then delete the original multipage frame, add the new fader next to it and in properties set it to submaster mode.
Now you can put the submaster to zero, and all lights should dim down, while Pan/Tilt (and whatever other LTP channels there are, Gobo, Prism, Beam shape etc.) should keep their values. they will always follow the "last" value received. It doesn't matter what your panel has set them to. Last received value Takes Precedence. On the contrary, HTP channels that are not defined in a cue, will just go dark in case they were on before, because there is no "Highest" level from this cue taking over at that moment. It's maybe a bit confusing at first, but makes much sense.
I tried that in your workspace with the desired result for MOVING 2 (set to HTP), but for most of your fixtures I miss the custom definitions (they are all converted to generic dimmers, so I cannot tell a colour from a tilt channel), and anyways wouln't go through that many channels to put them all back to HTP, so uplading my modified version doesn't make much sense.
PROGRAM MODE with zero.qxw