fbpx
Welcome, Guest
Username: Password: Remember me
{JFBCLogin}
25 Jan 2021
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Read More...
  • Page:
  • 1

TOPIC:

Need 608 Captioning 19 Apr 2017 21:56 #87347

  • JoeEditor
  • JoeEditor's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Seems Compressor embeds 708 closed captioning, and a station we're being asked to send a show to requires 608 captioning. What solutions would you guys suggest for embedding 608 captioning (USA broadcast)?

Please Log in to join the conversation.

Need 608 Captioning 19 Apr 2017 23:53 #87351

Very surprised about that, I am running Compressor 4.3.2 and i'm getting EIA 608 cc Using Mpeg 2 transport stream setting...

Please Log in to join the conversation.

Need 608 Captioning 20 Apr 2017 00:17 #87352

  • JoeEditor
  • JoeEditor's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
After more research I can document that Compressor is doing 608. Not sure why this particular station is claiming I'm delivering 708. Odd...

Please Log in to join the conversation.

Need 608 Captioning 20 Apr 2017 08:32 #87360

Compressor relies on the source .scc.
That might be the problem.

Please Log in to join the conversation.

Need 608 Captioning 20 Apr 2017 10:58 #87368

  • JoeEditor
  • JoeEditor's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Our .scc carries both 708 and 608 protocol metadata.
Compressor outputs 608 when using a Transport Stream mpeg2 preset.
support.apple.com/en-us/HT204625

So, I'm using a Transport Stream preset, and not sure why this one station claims we're delivering 708.

For something that is the law, you'd think we'd have more control and options in the Apple pro video apps.

Please Log in to join the conversation.

Need 608 Captioning 20 Apr 2017 11:39 #87374

Our .scc carries both 708 and 608 protocol metadata.
Compressor outputs 608 when using a Transport Stream mpeg2 preset.
support.apple.com/en-us/HT204625

So, I'm using a Transport Stream preset, and not sure why this one station claims we're delivering 708.

For something that is the law, you'd think we'd have more control and options in the Apple pro video apps.

The problem is complicated, And it is a North America problem only.
One problem is that "Apple Transport Streams" only cover AV interleaved - no metadata into it.
Adobe's implementation does, but has a lot of other problems.
Telestream's way is the only one which is reliable.

SCC and it's 608 type is an ancient format for analog stuff.
Maybe Apple doesn't care for "ancient" things.
And the rest of the world (not NA) doesn't care about SCC. Even Japan has it's own definition.

Talk to the station if there is an alternative - bigger stations accept TTML as additional file.

Please Log in to join the conversation.

Need 608 Captioning 20 Apr 2017 11:42 #87375

  • JoeEditor
  • JoeEditor's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Yep, it's a mess...
So much for "industry standards"...

Please Log in to join the conversation.

Need 608 Captioning 21 Apr 2017 13:13 #87408

  • JoeEditor
  • JoeEditor's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
UPDATE: So I documented that Rev.com is in fact sending me 608 .scc files. I documented that Compressor is in fact only outputting 608 captioning. Suddenly this TV station backtracks and admits the file I delivered is just fine. Broadcast, the most messed up, confusing industry I've ever been involved with...

Please Log in to join the conversation.

  • Page:
  • 1