![]()
Can you then import this file into FCP? Are the subtitles appearing at the right times? Try using our FCP XML Templateįirst see if you can export a FCP XML using the default template that comes with InqScribe. Export the file, and open it in your browser. Make sure that “Export OUT points” is checked, since this mimics how FCP XML exports are parsed. This can be useful if you're able to load an XML file into FCP, but the subtitles aren't showing up where you thought they would.Īn HTML export is a quick way to verify that InqScribe is breaking your transcript up in the way that you expect. INQSCRIBE SUBTITLE SCC NOT WORKING PREMIERE PRO PROMake sure you're using Final Cut Pro 7įinal Cut Pro X uses a different XML format that is not currently supported by InqScribe. Here are our FCP troubleshooting strategies, in roughly escalating order. INQSCRIBE SUBTITLE SCC NOT WORKING PREMIERE PRO GENERATORIf your generator also uses a single parameter named Text, it should be fine. InqScribe looks for a parameter named "Text" in that location. These should be located down the following nested path: sequence/media/video/track/generatoritem/effect/. You're looking for the parameters associated with the generator. The other is to create the XML template from FCP, and then inspect it with a text editor. One is to simply try it and see whether InqScribe can handle it. ![]() If you want to verify whether a generator not on this list will work, you have two options. Here's a current list of text generators that we know work. It also rules out some default generators, like Lower Third, that store subtitle text using multiple XML nodes. This rules out some generators, like the BorisFX family, that store subtitle text as binary data. InqScribe currently only works with text generators that represent the text of the subtitle as plain text in XML format. That will give you a rough approximation of where you'll need hard line breaks. Then set the width of the transcript window to the width of the subtitle region you plan to use in your video. (At least, not with the text generators listed above.) That means that you need to ensure that hard line breaks are in the right place within InqScribe before you export to FCP.Ī tip here is to set the font and size of your transcript to what you'll use within FCP for your subtitles. Watch Your Line BreaksĪs far as we can tell, FCP will not soft wrap subtitle text. ![]() For best results, we recommend exporting your own custom template from FCP and using that instead. Note that the default option may or may not work for you because it makes a lot of assumptions about your project settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |