{"id":11,"date":"2009-04-29T03:23:32","date_gmt":"2009-04-29T07:23:32","guid":{"rendered":"http:\/\/blogs.inquirium.net\/inqscribe\/?p=11"},"modified":"2009-04-29T03:23:32","modified_gmt":"2009-04-29T07:23:32","slug":"exporting-ntsc-df-to-final-cut-pro","status":"publish","type":"post","link":"https:\/\/blogs.inquirium.net\/inqscribe\/2009\/04\/29\/exporting-ntsc-df-to-final-cut-pro\/","title":{"rendered":"Exporting NTSC DF to Final Cut Pro"},"content":{"rendered":"

There’s a bug in InqScribe 2.0.5 that affects FCP XML exporting. Currently the bug only affects exports that use XML templates that are based on NTSC DF.<\/p>\n

The bug is that InqScribe is counting the dropped frames when it converts from the timecode to a single frame count number. As a result, the converted timecodes will drift farther and farther from where they should be, the later in the movie you go.<\/p>\n

There is a workaround that you can use until we fix the problem<\/span>.<\/p>\n

Update<\/strong>: turns out the workaround didn’t work. Drat. But the good news is that we’ve fixed the underlying problem in InqScribe 2.1. A public beta<\/a> can be found here.<\/p>\n

<\/p>\n

This fix takes advantage of the fact that the conversion from non-DF timecode to a frame number works fine in InqScribe, and actually lines up with what the DF value should be. The tricky part is getting FCP to recognize the imported XML as DF.<\/p>\n

It goes like this:<\/p>\n

1. Export from FCP a non-DF XML template for InqScribe.<\/p>\n

2. Export FCP XML from InqScribe using the template.<\/p>\n

Since InqScribe notices that the template is non-DF, it’ll convert based on that timecode format, which we know will actually line up with what you want.<\/p>\n

3. Open the exported XML file in a text editor and do a global search and replace as follows.<\/p>\n

FCP XML notes timecode format like this:<\/p>\n

<rate>
\n<ntsc>FALSE<\/ntsc>
\n<timebase>30<\/timebase>
\n<\/rate><\/code><\/p>\n

If the value for <ntsc> is TRUE, it uses DF. If it’s FALSE, it uses non-DF.<\/p>\n

So, if you replace “<ntsc>FALSE” with “<ntsc>TRUE”, you’re essentially converting the XML file to DF, which what you want. Remember to do a replace all — there will be tons of <rate> bundles throughout the XML file.<\/p>\n

4. Import the modified XML into your project.<\/p>\n

If all goes well, FCP will decide this is a proper DF import, and<\/em> you’ll see all the timecodes line up.<\/p>\n","protected":false},"excerpt":{"rendered":"There’s a bug in InqScribe 2.0.5 that affects FCP XML exporting. Currently the bug only affects exports that…\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,9],"tags":[87],"_links":{"self":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/11"}],"collection":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/comments?post=11"}],"version-history":[{"count":0,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/11\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/media?parent=11"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/categories?post=11"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/tags?post=11"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}