Jason Livingston
Forum Replies Created
-
Hi Daniel,
As with anything related to captioning, it depends on what you need to deliver.If you’re delivering tape, then you can use VTR Xchange (AJA) or Ventura (Matrox) to output a HD/SD file with closed captions to tape. The closed captions track is created in MacCaption.
If you’re delivering some kind of file, then FCP7 didn’t really handle this either, so nothing has changed. You export your (uncaptioned) movie to the required file format, then embed captions into it using MacCaption.
Shawn mentioned Manzanita, which is a plugin for MacCaption if you need to deliver CableLabs-spec MPEG-2 transport streams. For other file types, including program streams, QuickTime, MXF, etc. you can caption them natively in MacCaption without needing any other software or hardware.
So, other than the lack of tape output, FCPX hasn’t changed much on the captioning side of things.
Best regards,
Jason Livingston
CPC Closed Captioning -
Jason Livingston
April 28, 2011 at 4:33 am in reply to: Blackmagic Ultrastudio has 1 Thunderbolt portHi Luke,
Is that a confirmation that the shipping version of the Ultrastudio 3D will have only one Thunderbolt port, unlike the two port version demoed at NAB? -
Jason Livingston
April 21, 2011 at 9:25 pm in reply to: AJA Express lo can’t pass captions via SDI ?Hi John,
This is the latest info I have:https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=389915#a4
https://cdn.pinnaclesys.com/SupportFiles/attach/HW-Capabilities_1.2.pdf
(on the last page, under Ancillary Data)Jason Livingston
CPC Closed Captioning -
Jason Livingston
April 21, 2011 at 9:14 pm in reply to: Blackmagic Ultrastudio has 1 Thunderbolt portSorry I’m confused… in this picture from NAB it looks like it has two Thunderbolt ports, but this thread (and the pics on Blackmagic’s website) describe it as having only one port.
One port would seem to be very limiting as it would prevent the use of an external monitor (the monitor must be the last device in the chain and won’t have any passthrough ports).
-
Hi Alex,
This is a bit late reply to your post but I thought I could help.HD-SDI supports closed captions because it includes VANC (vertical ancillary) data support. It is the only HD interface which does.
DVI, HDMI, and DisplayPort do not support closed captions as they only carry the active picture area without VANC data. So you won’t find any monitors that can decode closed captions from these inputs.
The only way this could work is to go HD-SDI into a device with a closed captions decoder, and then take the open captioned (captions in the image) output of that device into a converter. (This is how HD set-top boxes work; they render the closed captions into the image and then send the image via HDMI or component.)
Best regards,
Jason Livingston
CPC Closed Captioning -
It may have something to do with it working on the SDI input but not on the analog inputs.
And sure, you can try this on the MacCaption demo. If your captured file is 720×486 and you can see the “morse code” dots & dashes at the top of the frame, simply drag-and-drop the video into the right side (text area) of MacCaption and it will decode the line 21 CC into text & time codes.
Best regards,
Jason Livingston
CPC Closed Captioning -
Hi Jeff,
I’ve been told by the other techs here that this did work. But I just tried it using the latest drivers 7.9.5 or something like that, and I couldn’t get it to work for me. I’m not sure if Blackmagic changed something in the driver or if something else is going on.Our MacCaption software can extract the line 21 and convert it to QuickTime CC track even if the capture card is not doing it automatically during capture, so that is another option.
Best regards,
Jason Livingston
CPC Closed Captioning -
What ties it together is a little piece of JavaScript code that checks the user agent string (which tells you what browser/device is visiting the page), and then embeds the HTML5 version for Apple iOS devices, and Flash for everything else. (You can get more fancy if you want… default to HTML5 and fallback to Flash, etc.)
There are even some Flash player skins that do this automatically, like JW Player can default to Flash but fall back to HTML5 or vice versa.
Again, the main points are:
1) You use the exact same video file for both: A QuickTime H.264 .mov file. This works in Flash too. No need to upload the video twice or change any file extensions.2) You don’t need separate HTML pages either, just a bit of code to change the embedded player type.
-
Yep, flash can use a H.264 QuickTime .mov file with AAC audio, just like Apple iOS devices use.
If you rename it to .f4v I don’t think Apple iOS devices will even try to play it, so stick with .mov.
Here’s an example. On this page, the English QuickTime and Flash players point to the exact same movie file (cpcdemo.mov). That way you only have to transcode & upload the video once.
https://cpcweb.com/webcasts/webcast_samples.htm
Jason Livingston
CPC Closed Captioning -
Actually, yes you can.
F4V is no different from QuickTime-wrapped H.264.
That is, you can transcode once to QuickTime H.264, and both the HTML5 version or QuickTime version, plus the Flash player, can point to the same video source file.
You still need to code the web page so that the video is presented using HTML5/QuickTime embed for the iOS devices, and HTML5 or Flash for others. But the point is that both embedding methods can link to the same H.264 video file.
