We’re Tweeting
InqScribe is now on Twitter. We think this will be a great way to share quick tips and information about using InqScribe and related media tools. You can track our tweets on the sidebar of this blog, or follow InqScribe on Twitter.
Author: eric
15 posts
Read more
Dive into Video
If you’re at all interested in where video and audio for the web is going, this chapter by Mark Pilgrim is required reading. Mark does a great job providing background on the core cross-platform codecs that are in use today (with the cross-platform bit ruling out WMV) and talks about how HTML5 will offer native…
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…
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 timecodes…
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.