• Date
    hacronymus
  • Date
  • Replies 3 replies
  • Subscribers 184 subscribers
  • Views 2545 views
  • Users 0 members are here

1.9.8 Mark error syntax

My apologies if this is fixed in 1.9.9- trying to Mark channels 59 and 64 in a previous cue in which they have no intensity value (have tried @ Enter or giving it a hard 0- cues are at the beginning of the list) and keep getting the error "channels are active in mark range" which is not true.  The reason they can't mark is because the cue they were trying to be marked for they are still at 0 but this error  is claiming they are active (which is not the case).

 

Show file is attached- Cues in question are Cue 3/1 (cue that is being marked for) and Cue 3/0.5 (cue that is being marked in).

 

Thanks!

Parents

  • Hi Matt,

    I don't think this is a change in behavior in 1.9.8.  To mark a light, it has to have an intensity above 0. Since those two channels don't have intensity until cue 2.1, you can't apply the Mark instruction until that cue. You can of course still set it to mark in Q 0.5, but the reference cue has to have an intensity coming from 0.

    Or at least that has always been my understanding. Any time in a show I've wanted to have a light do a live move wile fading up, I give it an intensity of 01 in the initial prep cue.

    HTH,

     

  • in reply to travisres

    Thanks Ben- this actually started out as you describe- which was the board op not understanding why it wouldn't mark- I then came over to look at it and (incorrectly) agreed that it should be able to mark.  When I sat down to initially write the post I realized what was going on.

    My concern is that the error message that we were receiving was telling us the channels couldn't mark because they were active in the mark range which is not true (and hence our confusion).

     

    Matt

Reply
  • in reply to travisres

    Thanks Ben- this actually started out as you describe- which was the board op not understanding why it wouldn't mark- I then came over to look at it and (incorrectly) agreed that it should be able to mark.  When I sat down to initially write the post I realized what was going on.

    My concern is that the error message that we were receiving was telling us the channels couldn't mark because they were active in the mark range which is not true (and hence our confusion).

     

    Matt

Children
Related

www.etcconnect.com