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
  • Oh - forgot to mention... The channels didn't respond to move instructions if they were still selected after a manual adjustment, but I think channels do that regardless if they are captured or not

    Thanks 

  • Brent, I just tried this.  Are you working with 1.3.1?  Because it appears to be working properly in the currently released software.   You are seeing the yellow 'c', but they are still responding to playback instructions?   Can you go into about and confirm exactly which build you are working with?

    And yes, you are correct, selected channels are withheld from playback instructions.

  • Anne,

    I experienced the exact same thing two weeks ago, but refrained from chiming in.  I have 1.3.1, and had not used capture much.  My thought was that it would be the same as park, but on the live screen, thus succeptible to recording.  However, the levels changed with the first cue I took, requiring apologies to my LD.  Yes, there was a 'c' in the tombstone.  Is my understanding of capture flawed?

    Brent Smith

    Tennessee Performing Arts Center

  • Oh yeah, (and this might be relevant to the other Brent).  My show was originated from a Strand board.
  • Hmm... I'd be really surprised to find that the origin of the data makes any difference (but, I've said THOSE words before.....).  Is this 100% repeatable?  

    a  

  • At the time, I gave up and moved on.  I'll try some replication this week and let you know.

  • 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


     

  • 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

     

  • I have found this thread: http://community.etcconnect.com/forums/thread/3991.aspx , But it still doesn't explain why single channels can't be Captured.
  • One thing that has not been mentioned here is that capture only preserves manual (displayed in red) levels. When you first capture a channel, it will also make the channel manual and will be preserved when you fire the next cue. If you then record it to a cue, or sneak it out, then it is no longer manual (displayed in blue/green) and is not preserved when you fire the next cue. The 'c' is displayed even when it is no longer manual, so that further manual changes you make are captured. 
  • Dan,

    Since my last post, I have come to understand (I think) the difference between regular Capture and Global Capture.  I now can see the benefit enabling and disabling Global Capture. 

    However it is now even more apparent that regular Capture is not working.  Have you tried this yet?  On each of four discrete consoles, a de-selected captured channel with manual levels (that is, no yellow border, levels in red, channel # in amber, and displaying a small "c") would move with cue instructions, levels changing color to reflect up or down, and finally, the "c" remaining.  Really, that can't be right, can it?

     

  • Hi all

    Just to add to Brent (smith)'s post - after having a toy around last night with the console, I'm experiencing the exact same problem with regular capture as Brent (smith) is.  Haven't played with global capture, but it would seem that regular capture is misbehaving.

    Cheers 

  • I have tried this a few times on 1.3.1 and am not seeing what you two are describing. Could you send me your showfile and a step by step reproducer, starting with [GoTo Cue Out]. Or see if the problem occurs after a [file new].

     Ex: (cue 1 contains chan 1 at 50)

    [Goto Cue Out]

    [Chan 1 at full]

    [Chan 1 Capture]

    [Goto Cue 1].  When I try this, chan 1 stays red at full, I am guessing that if you do this, it fades to 50.

     I don't think it would be showfile specific, but I'd really like to reproduce it here so it can be fixed.

  • Thanks Brent for sending in your show file, it was very helpful. It looks like if you have an RFR attached, capture is not working. If you remove the RFR, you would still need to restart Eos for capture to work again. the capture latch feature [Capture Capture Enter], where all manual levels are automatically captured, does not have this defect and works fine. This will be fixed ASAP.
  • Dan,

    Well I'll be Durned!  I just tested it and you are exactly right.

    I was afraid it would turn out to be me being dumb somehow.

    I appreciate your powers of detection!  Thanks.

Reply Children
No Data
Related