News and Notes related to Digital Media Transcription, Analysis, and Captioning.
RSS icon Home icon
  • Windows QuickTime Vulnerabilities

    Posted on April 21st, 2016 Alex No comments

    By now, you may have heard about the security vulnerabilities posed by QuickTime for Windows.  Given the security vulnerabilities, if you’re a Windows user, we highly recommend uninstalling QuickTime.

    What does this mean for Windows InqScribe users?

    1. You will still be able to play and transcribe most media that Windows Media Player supports.  For more about the types of files supported by Windows Media Player, head over to our media format guide here.
    2. Unfortunately, you will not be able to export a subtitled QuickTime movie using the QuickTime 7-exclusive “Save Subtitled QuickTime Movie” feature.

    Currently, InqScribe requires either QuickTime or Windows Media Player to play back audio and video files. You do not need QuickTime to run InqScribe on Windows–you can still use Windows Media Player for most files.  If you choose to uninstall QuickTime, InqScribe will automatically switch over to Windows Media Player. As long as your media files are supported by Windows Media Player, InqScribe will be able to play them as it normally does, and you may not notice any difference.

    How Do I Make Subtitled Videos Without QuickTime?

    Since you won’t be able to use InqScribe’s built-in subtitled QuickTime movie feature without QuickTime, you may need to find a new method of creating movies from your transcript. Luckily, there are a number of different subtitling options available to InqScribe users via Windows Media Player, VLC Player, YouTube, Final Cut Pro, etc. For more about these options, check out our “What are the different ways to create a subtitled video?” article.

    Why Does InqScribe Still Use QuickTime?

    When InqScribe debuted 10 years ago, QuickTime was arguably in its prime. QuickTime supports a range of media files, and through subtitle track support, giving our users a straightforward way to produce standalone subtitled movies. We’ve been very happy with the relationship between InqScribe and QuickTime, but the writing is on the wall: QuickTime is now over 20 years old, an eternity in software terms. With these vulnerabilities public, and Apple no longer supporting the software, it’s clear that QuickTime is no longer the way moving forward.

    Taking all of this into account, we’ve decided that future versions of InqScribe will no longer use QuickTime.

    What’s Next for InqScribe?

    We are currently working on a major overhaul of InqScribe.

    For OS X, InqScribe will use AV Foundation for media playback. AV Foundation is Apple’s official replacement for QuickTime and offers decent subtitle support. AV Foundation has the additional feature that it is also used for media playback on iPhones and iPads, so moving to AVFoundation should simplify the process of producing subtitled content for Apple’s mobile devices.

    For Windows, InqScribe could probably get by continuing to rely on Windows Media Player, but we want to look closely at moving to either DirectShow or its modern successor, Media Foundation. Of these options we’d prefer to use DirectShow, because Media Foundation doesn’t yet have strong support for subtitles. (Unlike Apple and QuickTime, Microsoft continues to support DirectShow).

    Beyond the native media engines for OS X and Windows, we are also looking at whether InqScribe can support alternative media engines that would enable playback of additional media formats or provide additional functionality that the native engines lack. Examples of engines in this class include VLC, GStreamer, and web-based solutions to play back online content like YouTube or Vimeo.

    InqScribe will continue to export a wide range of subtitling formats, and we will make sure that it will continue to be easy to generate subtitled content that can be viewed with standard apps on OS X and Windows. It’s worth noting that moving to more modern media playback engines will mean that future versions of InqScribe will not run on some older systems. You can read more about future system requirements here.

    We hope this helps to clarify our direction moving forward. In the meantime, InqScribe will continue to rely on QuickTime and Windows Media Player. If you have any questions InqScribe, feel free to contact us at support@inqscribe.com.

  • How to Convert an Audio File

    Posted on October 16th, 2015 Alex No comments

    Have you ever come across an audio file that won’t play in InqScribe? Although InqScribe supports a wide variety of formats (generally anything that will play in QuickTime 7 or Windows Media player 11), one day you may run into an audio file that won’t play correctly. If this happens, don’t panic, you can usually resolve the problem by converting or transcoding the file.

    There are a few possible reasons why the file won’t play correctly. For example, it may be in an unsupported container or contain unsupported codecs. Converting the file will rewrite its data into a new, hopefully more legible format for InqScribe. In this article, I’ll explain how to convert/transcode an audio file using the free, open source software Audacity.

    Remember, converting or transcoding involves decoding the original file, and then encoding the file into a new format. It’s not quite as simple as renaming a file “Example.wma” to “Example.mp3.” If you’re totally confused, check out our blog post “What is a Codec Anyway?” for an explanation of codecs, containers, transcoding, and more. If you have a video file you need to convert, head over to our “Video Conversion Tools” article.

    Audacity screenshot

    Converting with Audacity
    http://audacityteam.org/ 

    Audacity is something of a standard in the audio world. Although many use it to record and edit audio, you can also use it to convert or transcode files.

    The first step will be downloading and installing Audacity (available here: audacityteam.org). Audacity is a free, open source software available for Mac and PC. It is unaffiliated with InqScribe. Once you have it ready, here’s what to do:

    1. Launch Audacity and select “File > Import > Audio”. Choose the file you’d like to convert and click Open.
    2. Audacity will begin loading the file. Once loaded, you should see at least one blue waveform appear on screen
    3. Select “File > Export Audio.” Here, you’ll be given some options. You’ll want to first choose a name and save location for your converted file. Then, select the format for the new file. To maximize compatibility, we generally recommend the MP3 format.
    4. If you want more control over the quality (the default is 128 kbps) and bit rate, you can customize your settings by selecting the “Options” button.
    5. Once you have the settings to your liking, select “Save.”
    6. Audacity will then prompt you to “Edit Metadata”. Here, you can enter artist name, track title, album title, etc. This is primarily useful for music files. Feel free to leave these columns blank– they are not necessary.
    7. Click “OK” and Audacity will convert the file.

    That’s it! Now load the new file into InqScribe (either by dragging it into the media window or by clicking “Select Media Source”) and transcribe away.

    If you still can’t get the file to play correctly, or if you have any questions for us, feel free to send an email to support@inqscribe.com.

  • Hard Coding Your Subtitles: Actually Not Hard

    Posted on April 1st, 2015 Alex No comments

    There are quite a few ways to creates subtitles in InqScribe (check out a list of them here). Using the built-in “Save Subtitled QuickTime Movie” option is probably the quickest and easiest, but if you or your colleagues don’t have access to QuickTime 7, sharing the exported video file can be a problem. If you’d like to ensure your subtitled movie plays the same across all devices, hard coding your subtitles may be the answer for you.

    “Hard coding” or “burning-in” subtitles means taking the subtitle track and writing it into the video itself. If a video file has burned-in subtitles, it ensures the video will look the same no matter how it’s played. Note that you won’t be able to toggle subtitles on or off; if they’re burned-in, they’re there for good. To be clear, you cannot use InqScribe to burn-in subtitles. You can, however, export your InqScribe transcript to a Subrip .srt file and use free online tools to create a video file with hard coded subtitles. In this post, I’ll explain how to use InqScribe with VidCoder and Submerge.

    First, you’ll need to create and prepare your InqScribe transcript. Once it’s ready, export as a Subrip .srt file by selecting “File > Export > Subrip Format…” Note the save location of the file- you’ll need to access it soon. Now that you have a subtitle file, it’s time to burn it into a copy of your source video. To do this, we’ll use the free VidCoder (Windows-only) and Submerge (Mac-only).

    VidCoder (Windows-only)

    VidCoder is a free, open source software that uses Handbrake as it’s encoding engine. Designed for DVD/Blu-Ray and video encoding, VidCoder also allows you to hard code your subtitles. Here’s how:

    1. Download VidCoder from their CodePlex website: https://vidcoder.codeplex.com.
    2. Install VidCoder by opening the executable file. It should be called something like “VidCoder-1.5.3.1-x64.exe.”
    3. Launch VidCoder. From the startup menu, select “Video File…” Locate your original source video and select “Open.” Note that you’ll want to load the source video, NOT a subtitled QuickTime movie created in InqScribe.
    4. Once the video loads into VidCoder, you’ll have a few more options. Under the “Subtitles” heading, select “Edit…” Then, select “Import .srt File” Locate your .srt file and click “Open.”
    5. You’ll see your subtitle file loaded into “External subtitles.” Make sure to check “Burn in” and then click “OK.”
    6. Now that you have your video and subtitle file loaded into VidCoder, select “Encode” in the bottom right of the menu. Once it’s finished, you should see the new encoded video file appear in your specified folder.

    Submerge (Mac-only)

    Submerge is a tool designed specifically for hard coding subtitles on Mac. You’ll find it comes with more options to adjust subtitle position and appearance than freeware like VidCoder, although Submerge has a price tag of $19. Fortunately, Submerge offers a free timed demo for new users to try out.

    Note that we are in no way affiliated with Submerge or its creator, but are simply offering it as a possible subtitle burn-in solution to InqScribe users.

    You can find more information about Submerge, including directions on how to get started at their website: http://www.bitfield.se/submerge.

    Do you use a different tool to hard code subtitles? If you have any recommendations, we’d love to hear from you. Likewise, if you have any questions about creating subtitles with InqScribe, just shoot us an email at support@inqscribe.

  • What is a Codec Anyway?

    Posted on November 13th, 2014 Alex No comments

    If you work at all with digital video, you’re bound to run into issues of media compatibility. What makes a video incompatible? Will it work in InqScribe? It’s a complicated subject. In this post, we’ll explain a few key terms that should help you understand how digital video works (and sometimes, how it doesn’t work).

    Codec

    Codec stands for coder/decoder, and it does just that. Raw video tends to take up large amounts of storage, and codecs allow us to shrink down the file size, usually without losing too much quality. Codecs achieve this by taking the raw video data and encoding it into a shorthand. Once encoded, codecs also play a role in decoding this shorthand.

    Note that codecs are independent of a video’s file extension. So, .mp4, .avi, .mov, etc. are not codecs. A .mp4 file could use a H.264/AVC or MPEG-4 Part 2 codec, for example. You can see which codecs are supported by QuickTime via Apple’s support page here. To check which codecs you have available in Windows Media Player, follow Microsoft’s directions here (use drop-down bar on right to select your version of Windows).

    Although some are more popular than others, there are dozens of different codecs out there. Since each uses a unique coding language, it’s important to use codecs that are compatible with your workflow (and that you have access to- some codecs are proprietary). What should you do if you come across an incompatible codec? Transcode! More on that in a bit…

    Container

    QuickTime "movie could not be opened" message

    Look familiar?

    As its name suggests, a container file packages compressed video data. Containers identify and sort out codecs, which are the ones doing the actual compressing. Most common video containers are compatible with multiple codecs, so don’t assume one container is always going to have the same codec.

    Chances are, you’re more familiar with containers than you are with codecs. They’re more visible because the file extension is often associated with the container. A file with the name “Sample.mp4” has a file extension of “.mp4”, which indicates the MP4 container. Other examples of containers include AVI, MPEG-2, FLV, and RM to name a few.

    In addition to a file’s codec, programs such as QuickTime and Windows Media Player will have their own specs for which containers they support. So, to drive this home: just because you have a compatible container for your video file, it doesn’t mean you have a compatible codec. And vise-versa.

    Transcode

    To transcode is to convert from one encoding to another. When you transcode a file, you are essentially changing a video’s codec or its container, perhaps both. The terms “transcoding” and “converting” are generally used interchangeably.

    It’s worth noting that transcoding a file will result in some loss of quality. The extent of this may or may not be noticeable.

    If you’re interested in transcoding, check out our blog post on Media Conversion Tools for more information.

    Mux

    To “mux” a file is to combine multiple channels into one. When referring to video files, these channels are typically audio, video, and/or subtitle tracks. Muxing is useful when compiling several of these tracks into one output, such as when you’re creating a DVD or Blu-ray disk.

    Since not all media player can process muxed files, you might not always want a file to be muxed. This is when demuxing comes into play.

    Demux

    To demux a file is to extract the individual tracks back into their separate channels. Demuxing is useful when you come across an unsupported muxed file.

    Since transcoding will rewrite a file’s video and audio data, it can actually be used to demux a file. So, when in doubt, transcoding can solve several different problems associated with incompatibility.


    Understanding these terms and concepts should equip you to deal with incompatible media. And remember, if you’re ever having trouble getting InqScribe to recognize your media files, just send an email to support@inqscribe.com.

  • Video Conversion Tools

    Posted on October 2nd, 2014 Alex No comments

    Sometimes you go to transcribe your video in InqScribe only to find that InqScribe won’t play that video type. InqScribe relies on the QuickTime 7 or Windows Media Player 11 specs for media playback, and is able to play most anything that can be played in those players. But if your media is not supported by either of those two players, you’ll need to convert it to a format that is.

    Converting, or transcoding, involves decoding the original file, and then encoding the file into a new format. It’s not quite as simple as renaming a file “Example.avi” to Example.mp4.” If you’re totally confused, check out our blog post “What is a Codec Anyway?” for an explanation of codecs, containers, transcoding, and more.

    After a quick Google search for “media conversion tool,” you’ll soon realize that there are a lot of options out there. Some of these tools will be more useful to you than others, and some might even install unwanted malware on your computer. Which one should you use? While we don’t endorse any single media converter, here are a few that have worked for us (and our users) in the past:

    HandBrake

    https://handbrake.fr/
    HandBrake is a well-known, trusted, and free conversion software available for Mac, PC, and Linux. Since it’s a software, you won’t need to upload or download your video to a website (unlike Online-Convert below). Everything is done locally on your machine and you don’t need an internet connect to convert files. HandBrake supports batch file processing, which comes in handy if you’re planning on converting multiple media files. The drawback is that video conversion is limited to MP4 and MKV outputs. However, if your goal is to convert a video into an InqScribe-compatible format, the MP4 container will work just fine. Here’s a simple step-by-step guide to HandBrake:

    1. Download and install HandBrake from their website.
    2. Open HandBrake and click “Source” in the upper left portion of the window. Select the video or audio file you wish to convert. For example, “Desktop > Documents > My Videos > SampleVideo.mov.”
    3. Select where you’d like to save the new transcoded file by clicking “Browse” in the Destination section. By leaving it blank, it will save automatically to your desktop.
    4. Select the Container of the transcoded file. For video, you’ll have two options, MP4 and MKV. MP4 will work best with InqScribe.
    5. Next, in the bottom half of the HandBrake window, you’ll be able to edit various settings such as the frame rate, bit rate, and codecs of your media file. Adjust them to your liking.
    6. Click “Start” and your file will begin converting. HandBrake will notify you when the converted file is finished. It will then appear in the location of your choosing.

    Online-Convert

    http://www.online-convert.com/
    Online-Convert is a relatively new conversion tool that is gaining some traction. This website supports a wide variety of formats and, best of all, using the website doesn’t require you to install any software. The only thing you’ll download from Online-Convert is your converted media file. Note that, as a web-based converter, this option requires you to upload your video to the Online-Convert server. If you have a very large file and/or a poor internet connection, this option may not be the best for you. As per their terms of service, all uploaded files are deleted from the Online-Convert database within 24 hours, though even this policy may be an issue if your files are confidential.  Here’s how the site works:

    1. From the homepage, select your converter and file type. For example, “Video converter > Convert to AVI.”
    2. You will then be taken to a new page where you can adjust your  media settings. First, upload your original media file by selecting “Choose files…” You can also convert files from a URL or directly from a DropBox account. Going along with our example, you might select “Desktop > My Documents > Videos > SampleVideo.mov.”
    3. Adjust the settings to your liking. These settings will vary depending on whether you’re converting audio or video, but know that you’ll have the option to specify the audio/video quality, bit rate, frame rate, and length of your media file.
    4. Once you’ve chosen your settings, select “Convert file” to proceed. You should see a green bar appear indicating the progress of your upload.
    5. When the upload is complete, you will be taken to a new page with the text “Your file has been successfully converted.” Your converted file will automatically begin downloading. Soon you will have your converted media file ready to go! In my case, I received “SampleVideo.avi” in my Downloads folder.

    Do you use a different media conversion tool? We’d be happy to hear your thoughts and suggestions. Email us at support@inqscribe.com.

  • Comparison: InqScribe vs. Express Scribe

    Posted on July 31st, 2014 Alex No comments

    At InqScribe, we strive to create the best, most reliable transcription software. But, as some of you are aware, we aren’t the only ones on the market. You may even use a combination of other transcription tools alongside InqScribe in your line of work. To help clarify and distinguish InqScribe from the competition, we thought a simple, honest comparison might be helpful. In this post we’ll be looking at Express Scribe, one of our popular competitors.
    InqScribe vs. Express Scribe

    First, let’s start with the basics. Both Express Scribe and InqScribe are designed to make transcription a faster, easier, and more user-friendly experience. Combing an audio/video player with a text editor, they both employ features such as adjustable play speed, foot pedal support, and custom keyboard shortcuts. Currently, InqScribe is built around Windows Media Player 11 and QuickTime 7 (though change is around the corner). This means InqScribe will play pretty much anything supported by these media players. Express Scribe has its own set of supported formats.

    InqScribe and Express Scribe offer a free limited version of the software, in addition to a more fully-featured 14-day trial. The biggest difference here is that the free version of Express Scribe limits you to only a few audio file formats (specifically, AIFF, MP3, WAV, and WMA), while InqScribe’s free version grants you full format support but limits your ability to save and export. It costs $40 to upgrade to the full version of Express Scribe, while a license of InqScribe sells for $99 with free updates and significant discounts for students, schools, and nonprofits.

    Although Express Scribe and InqScribe are designed to fill a similar niche, they were built with different features in mind. Taken from NCH Software’s website, Express Scribe is a “professional audio player software for PC or Mac designed to assist the transcription of audio recordings.” Express Scribe takes more of a focus on audio transcription, and some of its features reflect this, including the ability to “dock” dictation devices. Many Express Scribe users work with a separate text editor such as Word, controlling their media in the “mini” view or using system-wide shortcuts.

    In contrast, InqScribe was built from the ground up with professional video transcription in mind.  We focus on the ability to type a transcript in the same window that’s controlling a media file. Aside from allowing you to visualize what you’re typing, same-window transcription prevents juggling between programs and frees you from trying to locate which media file is associated with which text document. InqScribe does it all in one compact place.

    If you’re transcribing audio recordings and prefer working in a separate text editor, then Express Scribe could be right for you. It does boasts a native spell-check and word counter, which are admittedly absent in InqScribe (for now, that is…).

    That said, InqScribe offers a few unique features of its own. Working in the same window allows you to take advantage of clickable timecodes. As soon as you click on a recognized timecode, InqScribe will take you directly to that spot in the video or audio file. Some of our users employ this feature to annotate their videos, using InqScribe to take notes on specific moments in their media file.

    One of my favorite features in InqScribe are snippets. The ability to quickly insert custom bits of text can considerably speed up a workflow. For example, I like to assign the “Enter” key to insert a line of blank space, a timecode, and the main speaker’s name. Snippets can make typing faster and help ensure consistency in the transcript.

    Once you have your transcript proofed and ready to go, InqScribe allows you to export into a variety of file formats– such as plain text, XML, Subrip SRT, etc. You can even save your transcript directly into a subtitled QuickTime Movie. No matter if you’re creating high-quality professional videos or a quick draft, InqScribe will accommodate your needs. In fact, we encourage users to find the workflow that best suits them, whether it’s with Word, Excel, Final Cut Pro, or YouTube.

    Lastly, we welcome feedback from our users. Be it a support question, a feature request, or an honest opinion, we’re a small team that reads and responds to all inquiries. We hope you’ve found this a useful comparison. If you have any questions about whether InqScribe is right for you, feel free to email us at support@inqscribe.net

  • Guest Blog: Using InqScribe to Record the Wabanaki Experience

    Posted on July 17th, 2014 Alex No comments

    Many nonprofits use InqScribe to help transcribe interviews and spread their message. In this guest blog, Rachel George explains how she came across InqScribe through her work with the Maine Wabanaki-State Child Welfare TRC.

    By: Rachel George, Research Coordinator

    Maine Wabanaki-State Child Welfare TRC ChildrenThe Maine Wabanaki-State Child Welfare Truth and Reconciliation Commission is charged with clarifying the experiences of Wabanaki Native American children and families involved with state child welfare. Historically there has been an incredibly high rate of removal of native children who were placed into non-native homes, resulting in continued intergenerational trauma and loss of culture. The 1978 Indian Child Welfare Act implemented new placement priorities recognizing the ties that native children have to their tribes, as well as the tribe’s interest in their children. This made it harder for native children to be placed in non-Native homes, yet the State of Maine continued to have high rates of removal.

    The TRC is investigating these removals by hearing the experiences of native children and families, and also from state officials, case workers, service providers and adoptive and foster families. From these investigations we’ve gathered a number of video and audio recordings from private statements, interviews, and focus groups. With the help of a few volunteers, we are currently working on transcribing an increasing pool of interviews and statements which are all approximately an hour long.

    Prior to coming across InqScribe, we were simply running the video through QuickTime and having a word document open simultaneously. I am sure I don’t need to tell you that this was a lot less effective than using InqScribe. Having the video and text in a single window streamlined our process. Since we’re working with long videos and multiple transcribers, it’s great to have a program that helps us stay organized and consistent. And, unlike some other transcribing software, InqScribe allows us to transcribe video as well as audio recordings.

    Overall, InqScribe has been a really valuable resource for us and has sped up the process of transcribing statements and interviews. It’s a system I am very happy to support and was very keen to push to my staff and colleagues.


    Research Coordinator Rachel GeorgeAbout the Author

    Rachel is a young indigenous scholar from Vancouver, British Columbia. As a member of the Ahousaht First Nation, she has grown into an advocate for indigenous rights. She has a genuine and enthusiastic commitment to strengthening the voices of indigenous peoples, and seeking methods of redress that are complementary to indigenous needs and rights.

    Thanks Rachel! Interested in learning more? Check out the Maine Wabanaki-State Child Welfare TRC website and read Rachel’s generous endorsement of InqScribe.

  • Guest blog: A Filmmaker Uses InqScribe for Translations and Subtitles

    Posted on May 22nd, 2014 christina No comments

    InqScribe is popular among filmmakers for a variety of reasons. In our latest guest blog, Scott Squire shares his workflow to translate and create subtitles for his documentary.

    by Scott Squire, Independent Producer & InqScribe user

    Our movie, The Girl Who Knew Too Much is a feature documentary about women’s empowerment, the complexities of globalization and the crisis of mental health support in Nepal. We shot our movie over seven years on six different cameras, with varying degrees of asset management rigor. We ended up with nearly 200 hours of footage to be logged and/or translated and subtitled. This project taught us the value of having solid workflows—from managing footage in the field through the process of translation. We cannot stress the importance of having a process (that works with every camera!) before you shoot a single frame.

    Our translators at work

    Our workflow includes the use of InqScribe and Final Cut Pro to produce translations and final subtitles for our movie. Critical to our process is having a clear folder/file structure that essentially depicts our workflow. I will refer to the folder/filenames used on our project, but obviously these would change based on your own project details.

    Folder structure to organize our workflow

    Set up

    We make sure that the top-level directory is accessible from all of our workstations. Our workflow begins with our editor placing callouts for the media that needs translating in the folder called In1. Fiona Highlighted Documents. Sometimes these are snippets from a clip, sometimes a whole reel. She reads our transcripts and highlights them, and then sends us scans of the highlighted pages as PDFs. (Unfortunately, on this project, we didn’t have InqScribe at the start, which means our original transcripts were in a variety of formats.)

    Review the translation and verify timecode in InqScribe

    We assemble all of the relevant translated files and then create an InqScribe document for each clip. Our workflow involves moving the InqScribe transcripts through a series of reviews by native speakers who verify the accuracy of the translation and the placement of timecodes. Timecode references should be at least at 10-second intervals (we recommend every 4-5 seconds). Be careful with InqScribe’s sensitive timecode selection so that you don’t timecodes out of order. And be sure to have opening AND closing timecodes in InqScribe or else your subtitles will run too long.

    Export XML file from InqScribe to Final Cut Pro

    Once the translation is complete and the timecodes are reviewed, we use InqScribe to export an XML file to be used in Final Cut Pro. It’s good to keep your XML template easy to access because you’ll be using it a lot. We keep ours at the top-level folder of our shared directory: /Master Wrapping Subtitle Template v1.3 (use this one).xml.

    Instructions for creating a custom FCP 7 XML export template can be found in InqScribe’s Knowledge Base.

    Very important is the naming of files. InqScribe will show the default name as “export.xml.” Click the “Choose” button to select a destination to save the file. Navigate to /Out2. Subtitle XMLs for Final Cut Pro > Interview XMLs from InqScribe. The name of the XML needs to match the file it came from. The best way to do this is to navigate to the original InqScribe file, select and copy the name (all but the “.inqscr” extension) and paste this into the pane of the export dialog. Double check your naming and destination—this is a big pain if you get it wrong. CONSISTENCY and ACCURACY in naming and filing are CRITICAL.

    If you’re lucky, when you click “Export,” the export window will just close and your shiny new XML file will turn up in the proper place. If InqScribe alerts you to a non-consecutive timecode you will need to go back and correct where needed. The error will only tell you approximately where to start fixing first. Cancel out and go back to check all of the timecodes where the error message is indicated.

    Import XML files to Final Cut Pro (FCP)

    In Final Cut Pro, you will create a project (Subtitle_Master_Project) and import the first InqScribe XML file in the scene you just created. When you import the InqScribe XML, it will come into FCP as a sequence with the generic name that matches your text generator template (Master Wrapping Subtitle Template…). You must change this back to the name of the original file. As before, navigate back to the file and copy and paste the name in the FCP browser to replace the template name.

    Drag the newly imported sequence into the timeline. It will contain only a subtitle track. Next, import the associated master footage or locate the clip and drag it into the FCP browser window. When the media clip has been imported, be sure it’s in the right folder inside the browser. Drag the clip into the timeline so that you have both footage (video and audio) AND a subtitle track above the video. These should be the same length, but there may be gaps in the transcription file. If the closing timecode was correctly input in the InqScribe file, the endpoint will match the end point of the media.

    If you’ve done your job in InqScribe, the clip lengths should all match up and you’ll have a subtitled sequence! You can now export the sequence from Final Cut Pro as a XML to send to your editor.


    About the author

    Scott Squire is a filmmaker who, along with his wife Amy Benson, is the producer of The Girl Who Knew Too Much.

  • Modernizing InqScribe

    Posted on March 7th, 2014 eric No comments

    InqScribe is closing in on ten years old. It’s been a point of pride that InqScribe still runs on older systems — with InqScribe 2.2, as far back as OS X 10.4 and Windows 2000.

    Now, however, the media playback engine changes we discussed earlier are forcing us to reconsider that approach for future versions of InqScribe.

    To recap, InqScribe’s media playback engines will be moving from QuickTime to AVFoundation on OS X, and from Windows Media Player to DirectShow (or possibly Media Foundation) on Windows. The new engines come with their own system requirements (for AVFoundation, OS X 10.7) that force us to abandon some older systems.

    Another important consideration for us is whether Apple and Microsoft support the system versions that InqScribe supports. Here, too, change is coming. Apple is no longer releasing security patches for OS X 10.6, which effectively means they no longer support it. Similarly, Microsoft has announced that they are discontinuing support for Windows XP next month.

    We are hesitant to recommend that our users continue to use an unsupported system, primarily because of security issues. With XP in particular, once Microsoft stops issuing security updates, XP systems will be at greater risk for malware.

    A benefit of moving to more modern OS versions is that InqScribe will be able to take advantage of some of the features that these systems provide (native spell checking!), without having to worry that users of older systems will be left out.

    We think it will be in our users’ best interests to upgrade to a supported system. Combined with the higher system requirements of the media engines, we are planning to update InqScribe’s minimum requirements to the following.

    • OS X 10.7. AVFoundation requires OS X 10.7 or newer, which makes this an easy decision.
    • Windows 7. Dropping Windows XP support is a given, since Microsoft is doing the same. We could support Windows Vista, but our internal use data suggests that the number of current Vista users using InqScribe is vanishingly small. So we’re planning to jump directly to Windows 7.

    If you have an older system, InqScribe 2.2 will continue to work for you. The new system requirements only apply to future versions of InqScribe.

    We’re excited for the next release of InqScribe. Talking about system requirements isn’t as exciting, but it’s necessary. We’re announcing these changes now so that users who will be impacted by the system requirements change will have to time to explore their options for upgrading their system before the next version of InqScribe is released.

    If you have questions or concerns about these changes, feel free to get in touch and we’ll be happy to clarify. We’ll be continually updating this support article with frequently asked questions and answers. And you can always contact us via our support page.

  • Retiring QuickTime

    Posted on March 7th, 2014 matt No comments

    When Apple released QuickTime in 1991, it was revolutionary. QuickTime provided a straightforward means to open and play a wide variety of audio and video formats. Over the years, Apple enhanced QuickTime, adding support for additional formats, subtitles, Windows support, and even a handful of interactive features.

    When InqScribe debuted (nearly 10 years ago!), QuickTime was arguably in its prime. InqScribe has always relied on QuickTime to handle media playback: for a long time our support slogan was “if QuickTime can play it, so can InqScribe.” InqScribe also relied on QuickTime’s subtitle track support to give our users a straightforward way to produce standalone subtitled movies.

    We’ve been very happy with the relationship between InqScribe and QuickTime. But the writing is on the wall: QuickTime is now over 20 years old, an eternity in software terms. And Apple has been very clear that QuickTime is no longer the way forward. Apple has officially deprecated QuickTime, to the point of warning developers that apps submitted to the App Store will be rejected if they continue to use QuickTime.

    (InqScribe is not sold through the App Store, so this warning doesn’t impact us directly. But we get the point.)

    So we’ve made the decision that future versions of InqScribe will no longer use QuickTime. Which raises two key questions: how will InqScribe manage media playback, and how will our users be able to quickly produce subtitled videos?

    For OS X, InqScribe will use AVFoundation for media playback. AVFoundation is Apple’s official replacement for QuickTime and offers decent subtitle support. AVFoundation has the additional feature that it is also used for media playback on iPhones and iPads, so moving to AVFoundation should simplify the process of producing subtitled content for Apple’s mobile devices.

    For Windows, InqScribe could probably get by continuing to rely on Windows Media Player, but we want to look closely at moving to either DirectShow or its modern successor, Media Foundation. Of these options we’d prefer to use DirectShow, because Media Foundation doesn’t yet have strong support for subtitles. (Unlike Apple and QuickTime, Microsoft continues to support DirectShow).

    Beyond the native media engines for OS X and Windows, we are also looking at whether InqScribe can support alternative media engines that would enable playback of additional media formats or provide additional functionality that the native engines lack. Examples of engines in this class include VLCGStreamer, and web-based solutions to play back online content like YouTube or Vimeo.

    InqScribe will continue to export a wide range of subtitling formats, and we will make sure that it will continue to be easy to generate subtitled content that can be viewed with standard apps on OS X and Windows.

    It’s worth noting that moving to more modern media playback engines will mean that future versions of InqScribe will not run on some older systems. We’ll have a separate post soon talking about the next release and InqScribe’s minimum system requirements.

    If you have questions or concerns about these changes, feel free to get in touch and we’ll be happy to clarify. We’ll be continually updating this support article with frequently asked questions and answers. And you can always contact us via our support page.