For example, If your last line looks like this: This way, InqScribe will know the correct time to stop displaying your last subtitle. At the end of your transcript, simply insert an "out" timecode after the final subtitle. Luckily, this issue is relatively easy to fix.
It then uses as the final "out" timecode, which triggers the "OUT is earlier than IN" error if you have valid timecodes past the 1 hour mark. The issue is that, if InqScribe doesn't have a media file from which to determine the end time of the file, it assumes by default the final frame should be. However, if your timecodes appear to be in order and your transcript meets the following specific set of conditions, you might be encountering an identified bug: The error message "Export Error: OUT is earlier than IN" usually indicates that you have an out-of-order timecode somewhere in your transcript. Bug: timecode error message when exporting > 1 hr transcript without a media file. The solution is to set the start time of your media files to 0:00:00.00 and adjust the timecodes to be relative to 0. : Unable to edit "Text" into "Template_InqScribe".( line 1 )Īnd you might find your transcript text is only 1 frame long. When you import these into FCP, you’ll get errors like this: For example, in InqScribe if your media start time is set to but you’re using timecodes like, the XML generated by InqScribe will have timecodes > 12 hrs. Make sure the timecodes you’re using do not result in a relative time difference greater than 12 hours. 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. If you're using any of the following effects in your FCP Template XML file, please remove them and try exporting again:Īs far as we can tell, FCP will not soft wrap subtitle text. This is because these generators do not store subtitle text in a format that InqScribe can generate. Generators known //not// to work include the BorisFX family as well as Lower Third.
Here’s the list of generators that have been shown to work: The first thing to note is that InqScribe can only generate subtitles for a subset of available text generators. InqScribe’s documentation covers the basic process in brief we’ll try to sketch in some of the details and offer some troubleshooting advice here. Generating subtitles for FCP is a convoluted process. Modified on: Wed, 22 Dec, 2021 at 2:18 PM
0 kommentar(er)
