![]() ![]() If TextWrangler doesn't help, or you just prefer to see the actual import error, you can use Apple's Console log viewer application to see the error.Ī. You can then save your transcript, re-export it to XML, and then try importing again into FCP. For example, I would delete the whole word "you're" just to make sure I get the character, and then retype the whole word. Delete the (usually invisible) bad character along with the characters around it (just to make sure). Select Edit -> Find and search for your text (e.g. the bad character is the apostrophe in "you're". For example, if TextWrangler found a gremlin in this line: The character is most likely wrapped in a tag along with other text from your transcript. If you're still having trouble, please try Step #3 below). (If it doesn't find it, you'll get a "Not Found" message - in which case there were no bad characters. If TextWrangler finds the text, it will select it for you. Check the "Wrap around" box to make sure you search the whole document. Click "Zap" - Unfortunately TextWrangler does not give you a message about how many gremlins were zapped. (Leave the "Non-ASCII characters", "Control characters", and "Null (ASCII 0) characters" checked). " radio button - this will mark the zapped item so you can fix it in your transcript.From the menu bar, select Text -> Zap Gremlins.į. If your issue is bad ASCII characters, you can used a text tool like TextWrangler (it's free) to find and replace the bad characters. Fix the timecodes and try saving the subtitled movie again until InqScribe doesn’t report any errors, then do your FCP XML export again. If there are timecodes that are repeated or out of order, the Save Subtitled QuickTime Movie feature will generate a report for you. Use InqScribe’s “Save Subtitled QuickTime Movie…” feature (in the “File” menu) to test your subtitles. If you have timecode errors in your transcript, you may have problems importing into FCP. Here are some suggestions on resolving this problem: 1. Even though some XML validators will ignore them, curly quotes like “ ” ‘ ’ will cause XML errors. FCP chokes on this when it tries to import.Ĭurly quotes in particular can cause problems in FCP. Sometimes as you're typing you might inadvertently hit the Ctrl key while typing a letter, inserting a character that is not valid XML. You have bad ASCII characters in your transcript. If you've been trying to import an XML file generated by InqScribe into Final Cut Pro (FCP), and get this error during the import process, "XML Translation was aborted due to a critical error." there are usually two culprits:Ģ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |