Generating subtitles for FCP is a convoluted process. 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.
The first thing to note is that InqScribe can only generate subtitles for a subset of available text generators. Here's the list of generators that have been shown to work:
Generators known not to work include the BorisFX family as well as Lower Third. This is because these generators do not store subtitle text in a format that InqScribe can generate.
As far as we can tell, FCP will not soft wrap subtitle text. (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.
A tip here is to set the font and size of your transcript to what you'll use within FCP for your subtitles. Then set the width of the transcript window to the width of the subtitle region you plan to use in your video. That will give you a rough approximation of where you'll need hard line breaks.
Here are our FCP troubleshooting strategies, in roughly escalating order.
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.
An HTML export is a quick way to verify that InqScribe is breaking your transcript up in the way that you expect. Make sure that “Export OUT points” is checked, since this mimics how FCP XML exports are parsed. Export the file, and open it in your browser.
First see if you can export a FCP XML using the default template that comes with InqScribe. Can you then import this file into FCP? Are the subtitles appearing at the right times?
If you're not seeing individual subtitles with our template, the problem may have to do with how InqScribe is breaking your transcript into separate entries.
If you're having trouble with a text/subtitle generator not on the generator list shown above, try creating a custom template using the default Text video generator. If you can get this to work, and your preferred generator isn't working, there may be a fundamental compatibility problem. Send us sample files (see the next step) and we'll let you know if there's a solution.
Finally, if you're still stumped, send us some sample files and we'll see what we can do. Here's what we need to see:
It would also help if you could describe what happens when you try to import the file into FCP and where the process is breaking down.