For example, let’s say you’re shooting an interview, and it begins at 1:00pm. While you’re doing the interview, you can take notes in InqScribe, noting when a particularly interesting conversation happens by inserting the current time. For instance, if the interviewee says something interesting 12 minutes and 3 seconds into the interview, you can insert a time stamp next to your note about that with one keystroke, e.g.:

“[01:12:03.00] T didn’t know it at the time.”

Alternatively, instead of using time of day, you can also use a stopwatch.

How do you do this? Just set the Media Source to an Offline Media type and select “Use time of day” or “Use stopwatch timer”.

Here are detailed instructions:

1. Create a new transcript “FIle->New Document…”
2. Click on the “Select Media Source…” button
3. In the “Source Type” popup menu, select “Offline Media”
4. Under “Time Code:” select the “Use time of day” radio button.

(Or you can select “Use stopwatch timer” and select a start time and end time.)

Then just type away as you normally would, using Command-; or (Ctrl-; in Windows) to insert the current time. Instead of using the media time, InqScribe will now insert the current time of day, or the stopwatch time.

Can I type from my stenotype machine into InqScribe?

Yes. In most cases, you’re going to be using CAT software that converts stenotype chording into individual key events. (Basically, the CAT software pretends its a keyboard sending keystrokes to the computer.) This approach works well with a lot of applications, including Word, TextPad, and others. InqScribe should have no problem receiving text input in this way. (A point of comparison: we know that InqScribe works well with AutoHotKey and other utilities that send artificial key events.)

Can I trigger shortcuts and snippets in InqScribe via my stenotype machine?

Currently, we doubt this will work. That’s because the stenotype machine is not normally listed as an available input device. The way that InqScribe tracks shortcut triggers is by checking all known input devices (keyboards, foot pedals, gamepads, etc.) for known shortcut combinations.

With a stenotype machine that is interfaced via CAT, the machine doesn’t show up as an available device. The key events just magically appear. And since key events by themselves don’t serve as triggers for InqScribe, we recommend instead a workaround like using a foot pedal with the stenotype machine, where the foot pedal provides the triggers.

We’re looking into ways that we might support snippet insertion (or shortcut triggering) via normally text entry. There are a couple of ways to do this. MS Word has one model for its auto-complete tool, where common abbreviations and misspellings are corrected or expanded after you type them. Another approach relies on an explicit triggering keystroke which follows the snippet abbreviation, so you’d type something like “tc`” and the ` character is the trigger to look up the “tc” snippet and insert it into the transcript. Since our goal is to let you transcribe more efficiently, we want to play around with these approaches to see what feels most comfortable. But if you’re got an opinion, let us know.

• You don’t have to assign a trigger/keyboard shortcut to snippet
• You can activate the trigger window with <cmd-1> (Mac) or <ctrl-1> (Windows)
• When the trigger window is activated, you can select snippets by typing the first few letters, or using the arrow keys to select the snippet
• Hit <return> or <enter> to insert the snippet

If you’re using Final Cut Pro 7 and importing InqScribe-generated FCP XML files, you’re probably pulling your hair out. As of FCP7, any imported subtitles beyond the two minute mark show up with a duration of only one frame.

The problem is twofold. First, InqScribe is setting incorrect values for the in and out points for each generated subtitle. In prior versions of FCP, these values were essentially ignored on import, because in and out points for a static subtitle don’t really mean that much. (The start and end points for the subtitle, which determine where the subtitle goes in the sequence, were and are correct.)

Unfortunately, FCP7 is interpreting those values differently, and any subtitle with an in point greater than the subtitle’s stated duration ends up with a frame length of 1. Since InqScribe was setting every subtitle’s duration to 3600 frames (because this value shouldn’t really matter: effective duration of the subtitle is based on the start and end values), most users will find that subtitles that start at the two minute mark or later are affected.

We’re working on a fix for the next beta release. In the meantime, there is a workaround.

Here’s an excerpt from an InqScribe-generated FCP XML file:

<generatoritem id="Text">
    <name>Text</name>
    <duration>3600</duration>
    <rate>
        <ntsc>TRUE</ntsc>
        <timebase>30</timebase>
    </rate>
    <in>7540</in>
    <out>7610</out>
    <start>7540</start>
    <end>7610</end>

Note that InqScribe sets the duration to 3600 (regardless of the actual duration, which is based on the start and end values). InqScribe also sets the in and out points to the start and end values. The problem is that in and out values should technically never be greater than the duration.

So the fix is to change every instance of in and out to this:

<in>100</in>
<out>3600</out>

With this change, in and out stay within duration’s range, and FCP7 won’t clip the resulting subtitle.

To make this change easily, use a tool that supports regular expressions to find all instances of the in and out tags. Here’s a solution that uses sed, which comes installed on OS X.

1. Export the FCP XML file from InqScribe as usual (let’s say it’s called export.xml).
2. In the Terminal, navigate to the directory containing export.xml, and issue this command (which is one long line, make sure to copy the whole thing):

sed -e 's_\(<in>\)[0-9]*\(</in>\)_\1100\2_g' -e 's_\(<out>\)[0-9]*\(</out>\)_\13600\2_g' < export.xml > export_fixed.xml

3. Import the resulting export_fixed.xml into FCP7.

If you want to dig into sed so you understand what that command is doing, here’s a solid sed tutorial. It’s a very powerful tool.

His focus is primarily on h.264 and Ogg video, since offering video in those two formats will cover all modern browsers. He also describes methods and tools you can use to encode your videos in those formats (including Firefogg, which was new to me, and FFMPEG2Theora for Ogg, and Handbrake for h.264).

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 information to help us more quickly troubleshoot the problem.

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 Time Code Format:” select “00:01:23.29″ from the popup menu.

4. Check the “Recognize Unbracketed Time Codes” checkbox.

5. Click “OK” to close the window.

6. Select “Transcript->Adjust Time Codes…” from the menu bar.

7. Leave the “Adjustment:” field blank, and click “Adjust.”  This will reformat all of your time codes to the unbracketed format.

—

To change ALL of your future transcripts to use the unbracketed time codes…

…On a Mac:

1. Select “InqScribe->Preferences…” from the menu bar.

2. Click on the “New Document” tab at the top of the “InqScribe Preferences” window.

3. Under the “Inserted Time Code Format:” select “00:01:23.29″ from the popup menu.

4. Check the “Recognize Unbracketed Time Codes” checkbox.

…On Windows:

1. Select “Edit->Options…” from the menu bar.

2. Click on the “New Document” tab at the top of the “InqScribe Preferences” window.

3. Under the “Inserted Time Code Format:” select “00:01:23.29″ from the popup menu.

4. Check the “Recognize Unbracketed Time Codes” checkbox.

By the way, there are a number of other formats that you can use as well.