Automark Bug

Hi there

 I'm currently running version 1.3 of the Eos software and think I have discovered a bug with AutoMark.

During the show, what happens is....

I run Q 75.  This cue runs for ~10 secs.  In this cue, Ch 4 > 10 fade out (these ch's are Studio Spot CMY units).  There is a follow time of ~3secs which triggers Q75.2  The S/Spot restore in Q81 (which is the cue after Q75.2)  Since Q's 75 & 75.2 overlap, the S/Spots are still fading out during Q75.2. Once Q75.2 is complete, the S/Spots start to AutoMark (Gobo and Colour values change) even though these channels have not yet reached zero.

I have worked around this problem by plotting a Q 75.5 which is a follow from Q75.2 and places the S/Spots in the correct state before fading up in Q81.  Q75.5 doesn't start until after Q75.2 is complete.

I'm assuming this is a bug.  Please let me know if this is not a bug and I'm just being special.

 Cheers

Parents
  • Someone please correct me if I am wrong, but I do not think that this is a bug-per say.

    The logic for Automark, as I understand it, is that it looks one cue ahead (and only one cue ahead.)  It then executes an if..then statement.  IF,in the next cue the Non intensity parameters for this channel <>(do not equal) what they are now, and IF the intensity parameter is 0 in this cue, then make the non-intensity parameters match the ones in the next cue.

    That is exactly what they are doing.  Automark looks at cue 75.2 and says hey channels 4 thru 10 have different NIP values in cue 81 then where they are at now, so I am going to look at their intensity.  And since their intensity in cue 75.2 is at 0, they go ahead and move.

     I understand that it is not doing what you think it should, but I would disagree - It is doing exactly what it should.

    Your workaround is exactly what needs to happen to make this work.  

    But, Please someone do correct me if I am wrong in any of my thoughts above....

    Derek.....  Anne.... Bueller? 

     

     

  • Actually, Eos is suppossed to take this situation into account and should wait to do the mark until the intensity reaches 0. This also also allows you to have an intensity move to 0, and mark for the next cue, all in the same cue.

    However, there does appear to be a defect in 1.3 that is allowing Eos to start the mark before the intensity reaches 0 when you have this case of overlapping cues. This is fixed in 1.3.1 though, which releases very soon.

    Thanks for asking about it.

Reply
  • Actually, Eos is suppossed to take this situation into account and should wait to do the mark until the intensity reaches 0. This also also allows you to have an intensity move to 0, and mark for the next cue, all in the same cue.

    However, there does appear to be a defect in 1.3 that is allowing Eos to start the mark before the intensity reaches 0 when you have this case of overlapping cues. This is fixed in 1.3.1 though, which releases very soon.

    Thanks for asking about it.

Children
Related