Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Broadcasting CC not displaying but detected. Can Scope/rasterizer find problem?

  • CC not displaying but detected. Can Scope/rasterizer find problem?

     Mark Spano updated 7 years, 8 months ago 2 Members · 4 Posts
  • jay agoglia

    January 15, 2013 at 2:46 pm

    Hey Cow comm,

    I would like to get some insight as to why a QT cosed captioning track is present and the captions do not display or play out.

    QT7 sees the QT CC track
    AJA CTR xchange see the CC

    Neither will them play out.

    During the process of working with the file: (EV encoding)
    I saw and QC’d captions viewing the out put of all gear. From APR source file, to HD cam SR and back to APR again. I ran tests and am pretty confident that it has something to do with the source file (or possibly pipeline though tests would suggest otherwise)

    Any thoughts on what to look into to help trouble shoot this. I have an evertz cc encoder and a tektronix web 7200 rasterizer to obtain specific caption/aux data info.

    I am wondering what exactly on our tektronix unit could I look for
    HD source file 1920×1080 29.97, APR

    Thank you

    Jason Agoglia
    QC Manager
    On The Spot Media

  • Mark Spano

    January 15, 2013 at 3:02 pm

    Assuming you are using an AJA device to output the video, it’s probably just that the VANC is not turned on for output. Go to the AJA Control Panel under Format and make sure VANC is checked. You can see it here (I have an IO Express):

  • jay agoglia

    January 15, 2013 at 3:19 pm

    Hi Mark,

    Thank you for the response. The VANC checkbox is checked and just checked to verify. I don’t think I would have been able to see the captions play from the SR otherwise. Something is funky about the QT closed cap track in this file. I have a work around but would love to get to the bottom of this. Any other thoughts?

    going) APR-AJA-HD teletrax-SR
    back) SR- pipeline log and capture

    FCP log and capture is the work around so either FCP is handling this specific error in the captions track better than pipeline, pipeline is corrupting the captions (again tests say otherwise), something is inherently corrupt on the source QT CC track.

    I need more thoughts!

    thank you

    Jason Agoglia
    QC Manager
    On The Spot Media

  • Mark Spano

    January 15, 2013 at 3:30 pm

    I’m just throwing darts here, but the only other thing I can think of is that somewhere along the way the caption data is moving to a different line in VANC than what the decoder is looking for. Then you might have a situation where the device detects caption data (some flag is ON) but won’t display it because it doesn’t know where to look for the essence of the data.

Viewing 1 - 4 of 4 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can. Our Privacy policy | GDPR Policy