Make Null and Release in Cues-Blind - Undo it, creates unexpected behaviour

Hello,
i had a case where one fixture performed not the way i liked, in some Cues.
So my way to solve this was to hop into Blind and make the Fixture (with all Parameters) Make_Null.
Second showcase, some actors are ill, and the Spots in a couple of scenes needed to be removed.

Performance of the action was as i wished.

Now i decided to undo the Make_Null on an other Day. The show was saved meanwhile, and the desk was shut down a couple of times.

Now the Magic happens.
I thought, while i did:
- [Cue] 2 [Thru] 4 [Enter]
-3 [Thru] 5 {Make Null} [Enter]

I can simply do the same action and everything will be like before.
But i was proven wrong.

Now the int-Values tracking from the Cue 1.
Regardles of me being in CueOnly or Tracking, and regardless of using the Key [CueOnly/Tracking].
Every NIP Value stays as recorded in the Cues.

----

But it will get worse.
If i perform the ON/OFF {Make Null} with some Cells of a Multicell Fixture, the NIP-Values track from Cue1 and Int-Values are fine as in the Cues recorded.
Totaly different behavior.

---

I can get rid of Make_Null if i visit every Cue on there own (still in Blind) and do a {Make Null} for every single Channel.
But that is to much work to do, and i will end up with a ton of Auto-Blocks.

----

And i also noticed, that {Make Null} and {Release} are "tracking" while applying. (that is nothing i expected, nore have i read it in the Manual.)
So i need to use [Cue Only]. (Only if the current user is in Tracking-Mode)

Regardless of using {Make Null} or {Release}, they both show the same behavior. And for me that is kind of confusing.
And the Manual is not helping to solve my thoughts wether this is a bug or i am just to unexperinced.

I attach here a test Showfile, created with v3.2.10.36
In that test File i already have some Channels with Make_Null and Release programmed in.
Make_Null-test 2025-01-09 01-55-09.esf2

Questions:
1. What is the best way to get rid of the Make_Null/Release command in my Case?
2. Is this a Bug?
3. Is there an other way to achieve the same outcome? (for a faulty fixture i could have used [Park], i know...)

Yours
thilda

Related