[Tim Vaughan]

There’s a lot of variables to your question, but what it sounds like is it can be done in Ps. I’d create an automated action (google how to do if you’re not aware) which resizes the images, adds any effects (gaussian blur, etc) and exports a single completed image. Then run the automation on the folder(s). Import the effected images and you should be good to go.

[Tim Vaughan]

As I don’t have access to your system nor know your settings, I can only use my experiences as reference.

The mcc caption file will come in a 704×480. It is dependent on who you get the file from, but our cc files have the option to receive from our captioner as drop/non-drop frames. It sounds like you may need to modify direct from Mac Caption.

We receive both 608/708 in the mcc file, but you have to make sure your display is set to show 708’s/608’s in the program monitor (click the wrench, enable CC and change preview settings to 608 or 708)
Also make sure v1 and v2 on the timeline are enabled to receive both captions. (If only one is enabled, only 1 will show)

Hope this helps

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

I see this whenever I export a sequence with captions to mxf op1a. 99% of the time, it’s just a single movie on track 1 with captioning on tracks 2, 3. There isn’t any media to be offline, nor have their been any errors in the render save the yellow checkmark at the end of render. Absolutely no idea, and if you don’t see anything wrong with your completed export, chalk it up to Adobe being Adobe…

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

Thanks. Both 608 & 708 do show in the report. This is great to hear, thanks!

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

Michael, how about the 608’s? Do they come in as well? When we export the mcc (608+708) file embedded in the video (mxf-OP1a), when I import the completed video to check, only the 708’s come in. However, when I send to broadcast, the 608’s and 708’s both show. In v2015, an exported movie came in with both. In v2017, only the 708’s. It’d be friggin great news if this is finally resolved!

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

I’d recommend making sure “import captions with media” is on (Premiere Pro Prefs–>Media), and import the captioned footage into Pr. That’s how we check… You’ll need to make sure captions are enabled and displayed in the viewer window. When they come in, it should take a minute or so to “scan closed captions”. Boom!

Tim

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

In that case, Tyler says stay away from Avid. Use Adobe. ????

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

I, too, work at a PBS station. The editors pretty much use Avid; however, their version does not support 708 cc. It’d be nice to come in to money… ☺ All that being said, we export their projects and use Adobe Pr Pro to embed 608/708 captions and export mxf op1a. Adobe’s Media encoder far exceeds their version of Avid for web exports both in time and quality as well. Not to mention, with Adobe, you pretty much get the suite vs just the editor.

Hope this helps….

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

Wait a minute–I believe I may of stumbled upon it. 🙂

function toTitleCase(str)
{
return text.sourceText.replace(/\w\S*/g, function(txt){return txt.charAt(0).toUpperCase() + txt.substr(1).toLowerCase();});
}
toTitleCase()

Thanks Dan!

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC

[Tim Vaughan]

Thanks Dan. I’m not great (heck, I barely know js but I’m starting…)… I’ve not had any luck when running the functions from stack overflow. I’m ending up with errors all over. When I try

function toTitleCase(str)
{
return str.replace(/\w\S*/g, function(txt){return txt.charAt(0).toUpperCase() + txt.substr(1).toLowerCase();});
}

I end up with [object layer]. (Not what I’m looking for…) To my limited knowledge, after declaring the function and adding in

text.sourceText.toTitleCase()

at the end (or toTitleCase() or variations of that, it’s not working. I certainly hate to take up your time on this. I was hoping it would be rather easy….

—
Tim Vaughan
Production Editor and Motion Graphics, PBS Charlotte
Charlotte, NC