[Michael Gibrall]

The following is what is stated on Sony’s web page devoted to Vegas:

Vegas Pro supports CEA608 captions and CEA708 containers containing CEA608 captions.

When rendering to XDCAM HD/HD422, CEA608 data is uplifted to CEA708 format so that CEA608 and CEA708 captions are available when playing via HD SDI. CEA608 CC1 is uplifted to CEA708 Service 1, and CEA608 CC3 is uplifted to CEA708 Service 2. Please note that caption positions can be slightly different after uplifting to CEA708.

When you render to a format that does not support embedded captioning markers, an .SCC file is created using the base name of the rendered media file.

When I went to render, I found XDCAM HD but no reference to HD422.

Am I missing something?

[Michael Gibrall]

I did some research, and found that Sony Vegas Pro supports closed captioning in the CEA608 and CEA708 standard.

https://www.sonycreativesoftware.com/webhelp/vegaspro/12/enu/content/Adding_Closed_Captioning_to_Video_Files.htm

When doing a search on what the standards are, I found that CEA608 was the older, analog format, that supports English, Spanish, French, Portuguese, Italian, German, & Dutch only.

CEA708, the digital form of closed captioning, will accept characters from all languages.

https://www.3playmedia.com/2015/08/11/whats-the-difference-between-cea-608-line-21-captions-cea-708-captions/

I’m not in front of my editing computer right now, but when I am, I am going to see if i can toggle to cea708 closed captioning in the command drop-down menu when entering in the text.

[Michael Gibrall]

Thanks for trying to help.

The link is about how to actually create closed captioning, with instructions written in Japanese.

Cutting and pasting Japanese characters will physically go in, but when rendering the .scc file, there is no Japanese language to be found.

[Michael Gibrall]

My workplace’s IT manager is going to go around and uninstall all Quicktime players on all PC’s at work. He sent out an email saying that he recommends everyone do so at home on their personal computers.

I asked him if I don’t run the application, how would it still matter?

His response was it may be possible for someone to access it through your web browser if you have the Quicktime plugin active.

So, since I can’t uninstall Quicktime for my copy of Sony Vegas Pro, I went and disabled the plugins on IE and Firefox browsers.

Just an FYI.

[Michael Gibrall]

Two recommendations outside of Sony Vegas…

1.) Audacity (free). But note that while it works, it can really strip down the music/singing/talking.

2.) Izotope RX, current version is 4 (around $300 if I remember correctly.) I used RX version 2 via suggestions here, because that’s what was available at the time. It will get rid of the pops without sacrificing the quality of whatever is playing back on the record.

[Michael Gibrall]

John:

I went ahead and spent the $30 to purchase Quicktime Pro 7 on my PC.

I demuxed and remixed the ProRes 422 HQ file and it worked. It did not recompress (couldn’t, anyway, since ProRes is Mac native) and it was a straight copy of the given audio and video streams. Sony Vegas Pro 12 and Quicktime Pro 7 both state the video file is ProRes 422 HQ and the file size is the same.

So for your future reference, Quicktime Pro 7 on a PC will demux/remux a ProRes 422 HQ file on a PC.

[Michael Gibrall]

Can you use Windows Restore and go back a few months?

[Michael Gibrall]

Yeah, I don’t want to re-render. I can’t have that.
Shucks.

[Michael Gibrall]

John, I did the ffmpeg trial to see if I could demux and remux without spending any money.

But I’d have no problem spending the $30 to purchase Quicktime Pro.

If I demux and remux with Quicktime Pro, I’m assuming I won’t get that prompt again in FCP?

[Michael Gibrall]

Thanks, John. Lots of things to consider.