---
title: "Captivate Versus Camtasia Studio"
date: 2010-07-18
description: "$( document ).ready(function() { // Handler for .ready() called. $('#toc').toc({ minimumHeaders: 3, listType: 'ul', showSpeed: 0, headers: '#content h2, #content h3, #content h4, #content h5, #content h6' }); /*..."
canonical_url: https://idratherbewriting.com/2010/07/18/captivate-versus-camtasia-studio/index.html
---

> For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

# Captivate Versus Camtasia Studio

I've been exploring Captivate lately because I wanted to translate some screencasts for a project I'm undertaking. It turns out, Captivate doesn't work so well for screencasting. Slide-based eLearning, sure. But when you have a lengthy software simulation, it fails because you can't edit the audio while watching the video play.

Really? Yes. Really. You know, like if you wanted to ensure the timing of the video is correct as you're listening to the audio, or if you make an adjustment to your video or audio timeline that affects your other actions -- good luck trying to resync the audio with the video.

When you edit the audio, it opens in another window, or even in Soundbooth if you have the Adobe eLearning suite. But the video recording doesn't play, so you can't tell if the small addition or deletion you make on the audio timeline is throwing everything else out of sync with the video recording.