Software updates, tips, and user stories
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…
While we do have a new version of InqScribe expected soon, the current version, 2.0.5, works fine with the new Snow Leopard Mac OS (10.6). In general, if you do have problems with InqScribe, please report it to us using the InqScribe Help menu’s “Report a Bug…” feature. This provides us with a little more…
I have an existing InqScribe transcript that uses bracketed timecodes: [00:01:23.29] I want to use unbracketed timecodes: 00:01:23.29 — Here’s how you can do the conversion: 1. Open the existing transcript in InqScribe. 2. Select “Transcript->Transcript Settings…” from the menu bar. 3. Under the “Inserted Timecode Format:” select “00:01:23.29” from the popup menu. 4. Check…
InqScribe currently does not support bold text. However, you can use Microsoft Word’s “Find and Replace” feature to bold text. Here’s how you can do that: 1. Export your transcript to Microsoft Word. (You can just cut and paste.) 2. Select “Edit->Replace…”. 3. Click on the triangle next to the “Replace All” button to reveal…
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…
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…
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.