Welcome to InqScribe News

Welcome to the new InqScribe News! We’ve tidied up a bit and moved over to a shiny new blogging engine.

The older InqScribe News site is still available, but we’ll be posting new information here, including notes on development, bug reports and workarounds, and tips for getting the most out of InqScribe. We hope you’ll follow along.

Exporting NTSC DF to Final Cut Pro

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.

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 time codes will drift farther and farther from where they should be, the later in the movie you go.

There is a workaround that you can use until we fix the problem.

Update: 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 can be found here.

Read the rest of this entry »

InqScribe and LTC

We’ve added a knowledge base entry discussing the challenges inherent in decoding linear timecode (LTC). In short: InqScribe can’t do it, we’d like to support it, but it’s really hard to do the analog-to-digital conversion. We’ll track alternative solutions on the KB page as we find them.