• Date
    BrentFJ
  • Date
  • Replies 15 replies
  • Subscribers 184 subscribers
  • Views 19309 views
  • Users 0 members are here

Capture not working?

Hi again

I tried using the "capture" function the other day but it didn't seem to work as I expected.  I entered  [601 thru 602 @ 6 capture enter].  This changed the values and put a "c" next to the channel numbers to indicate they were captured.  However, once the channels were de-selected (but still captured) they would still respond to move instructions from cues.

My understanding was capture works like a hold function, and channels will not respond to instructions from cues until released from the captured state.  Is this a misunderstanding on my part or a glitch?

Cheers 

Parents Reply Children
  • in reply to BSmith

    Hi Anne

    Currently working with v1.3.1.  I'll have to double check, but from memory, I get the "c" so long as the channels aren't manual and displaying the "r".

    This problem is 100% repeatable.  I'll double check again when I go in tonight and try and get some more accurate answers about when the "c" is displayed.

     
    This show also originated from a Strand Showfile, but the transfer was done back in v1.1 or 1.2.  Let me know if you need anymore info

     Cheers


     

  • in reply to BrentFJ

    Ok, this is frustration, but I think I've figured some of it out.

    Today, I went to all of our different consoles (EOS, ION, and RPU.)  I would: 1.select channels  2.Capture them  3.observe the "c" placed in the tombstone and the channel number changing to Amber  4. Deselect the channel  5. Give the channel a move instruction.  Every time, the channel moved, while the "c"  remained.

    Finally, I happened to notice that the LED on the Capture button was not lit.  Out of curiosity, I double-tapped the button, wondering if I would see a Capture screen (like Park).  Instead, I got "Capture Enable" on the command line.  Once I executed it, Capture worked exactly how I expected.  Wierd thing is, channels Captured before the Enable move while those Captured after don't.  But they look the same.

    I am willing to believe that this is at least partly by design, but I don't get it yet.  Could someone please (patiently) explain it to me.  Why would you need to Enable the feature to use it?  Why not have it the same as Park?  Would someone want the feature disabled at certain times?  Why is there no distinction between Captured channels (Enabled) and Captured channels (Disabled)?  Is there a purpose for Captured channels (disabled) that when Capture becomes Enabled, do not change to immovable channels?

    Eagerly awaiting enlightenment,

    Brent Smith

    Tennessee Performing Arts Center

     

Related

www.etcconnect.com