Podcasting and Edit Timing

During my recent tour with Adobe UK demonstrating Adobe Captivate and Adobe Acrobat Connect Professional, I was asked whether I ever used the Captivate audio feature Edit Timing. Well I have to be honest and say that until now this one of those features that I have hardly used. However, like many Captivate users I am always looking for ways to cut down on my workload and any opportunity I get to re-purpose content I welcome with open arms. Which brings me nicely to the topic of podcasting.

As recently appointed training manager for WebAssist I'm always on the look out for new and creative ways to offer informal learning to our users; and one way of doing this is to use podcasting.

Now when it came to creating the podcasts I naturally turned to Adobe Captivate and looked for a way to take the voice-over from the existing feature tours (demonstrations) and use this in my podcasts.

Now if you are sitting there thinking well surely that is simple enough, you just export the audio you recording when you first captured your screen action! Then let me explain how I create my voice-over.

Firstly, I don't use Adobe Captivate, whilst the recording and editing tools present in the applications are fine for many users; they just don't offer the power that I need. Instead I use Sony Sound Forge to record and edit my voice-over. Oh and in case you are wondering I don't use a headset either. I currently use a Sure SM 58 microphone - yes I am one of those Captivate users. Once I have recorded my audio I then import this on to each of the appropriate slides.

Anyway back to podcasting. So here I am with maybe 30 audio files scattered through my entire project. So how do I get them all back into one single file? The answer is to use Captivates Edit Timing audio feature.

Here are the steps....

1. Start by opening the Adobe Captivate project file you wish to extract the audio from
2. Insert a new blank slide (Shift + Ctrl + J)
   
3. Move the new slide to the very start of your project.
4. Double-click on the slide background and set the duration to say 120 secs
   Note: If you don't set the duration to a high value you won't be able to move all the audio segments to just a single slide.
5. Choose Edit > Edit Timing > Project
6. Select the first of the slide markers and drag it to the first slide - your new blank slide.
7. Now do the same for the rest of the slide markers
   Note: If you find that you cannot move a marker, go back to the blank slide and extend its duration.
   
8. Once all the markers are all located on the first slide click OK.

Now using the Thumbnail view you should find that only one slide has audio attached to it.

The final task is to export the audio. To do this:

1. Choose Audio > Advanced Audio...
2. In the Advanced Audio dialog box select slide that has the audio
   
3. Select the option - Include MP3 files in export
4. Click Export
5. Click OK
6. Specify where the audio file should be created

Then it is simply a case of creating the project file you want to use for the podcast and importing the just exported audio.

WebAssist Success Story

Earlier this year Adobe Systems Inc wrote a success story based upon the tremendous impact Adobe Captivate has had upon our business. This study is also featured in the e-Learning Guilds new ebook "The eLearning Guild's Handbook of e-Learning Strategy."

Announcing Adobe Captivate 3

The wait is over, Adobe have today announced the latest version of Captivate, Adobe Captivate 3. Over the next few weeks I will be blogging about many of the new cool features (and some extra little bits) but for now here is the list of new features:

• Multiple recording modes
• Automatic rerecording of web applications (MS IE 6 only)
  
• Random Quizzing and Question Pooling
• Cut, copy and paste slides
• New Questions Slides
• Hot-spot
• Sequence
• Zooming in and out in Branching view
• Slide groups
  
• Answer Shuffle
• Rollover Slidelets
• New Slides transitions
  
• Microsoft PowerPoint Import - Now Adobe Captivate can convert PowerPoint slides into SWF files whilst retaining the animation effects
• XML file export and import for easy localization
• Preview project while recording audio
• Find and Replace
  

You can ready about all of these features in more details from the Adobe Captivate 3 features page at Adobe.com

Adding XML data in Adobe Captivate Projects

I am always looking for ways that I can extend my Adobe Captivate projects but not only so that I can include cool features but also to save myself some time. One of the time saving features I have been looking at recently is integrating XML (Extensible Markup Language) into my project files. Let me start by painting my requirements picture. WebAssist has a number of product suites (Super Suite, Web Developer Suite and Web Designer Suite) which currently are on special offer, now imagine that I have created a product feature tour that describes each of the suites and I want to include the current pricing for each of the product suites.

View the Adding XML Data into Adobe Captivate projects sample.

Whilst I could just add the prices using transparent text captions what would be a lot more efficient would be to store the prices somewhere else so that once the special offer has ended I can adjust the prices without having to republish my Adobe Captivate project file. XML is an idea format for storing the suite prices but, since you cannot link XML data directly into Adobe Captivate you have do have to be prepared to spend a little time in Adobe Flash the end results are worth the extra effort.

The first step is to create the XML document which is something that you can very easily do in Adobe Dreamweaver CS3 or even Notepad if you don’t to use an HTML Editor.

<?xml version="1.0" encoding= "UTF-8" ?>
<!-- xml document created by Mark Fletcher -->
<products>
<product product_name="Super Suite" price="449.99"></product>
<product product_name="Web Developer Suite" price="249.99"></product>
<product product_name="Web Designer Suite" price="149.99"></product>
</products>

The next step was to fire up Adobe Flash and insert all the graphics and insert the graphics I wanted to include in the document. In this case I inserted the WebAssist logo and suite box shots.

Because I wanted to load text from a file instead of adding just static text, I inserted some text boxes and then using the Properties inspector text type drop down menu I selected Dynamic Text and gave each of the text fields a title.

Now for the ActionScript code which is used to display the data. I should point out that there are other ways of working with XML in Flash which I might come back to at some point in the future, but, for now here my AS logic.

// create an XML object called "my_xml"

my_xml = new XML();

// load data from an external XML file into "my_xml" object

my_xml.load("wa_offers.xml");

// When the data has been loaded... Call a function ("my_function" in this case)

my_xml.onLoad = my_function;

// ignore "white spaces", text nodes that only contain white space are discarded

my_xml.ignoreWhite = 1;

// function contents

function my_function() {

// take the data from the XML lines (line 0,1,2) and place that data inside text fields

text_field_1.text = my_xml.firstChild.childNodes[0].attributes.product_name;

text_field_2.text = my_xml.firstChild.childNodes[1].attributes.product_name;

text_field_3.text = my_xml.firstChild.childNodes[2].attributes.product_name;

//

text_field_a.text = my_xml.firstChild.childNodes[0].attributes.price;

text_field_b.text = my_xml.firstChild.childNodes[1].attributes.price;

text_field_c.text = my_xml.firstChild.childNodes[2].attributes.price;

Having tested the ActionScript code actually works, I then published the Flash document and turned my attention to Adobe Captivate

To add the published Flash file, I simply inserted the exported SWF file as an animation

At first when I did this I honestly thought that this wasn't going to work since in Captivate the XML data is represented as "undefined" both in Edit view but more alarmingly when I previewed.

However, I decided to press on and see what would happen once I have published the Captivate file.

In order to get XML to work correctly I did find that I had to publish the project using Flash version 8 but once I had done this and made sure that my XML file (wa_offer.xml) was in the same folder as my published Flash files the data did show through correctly.

I have included the sample files below in case you want to experiment with this

Published SWF files and XML
Sample Flash File with ActionScript code

Disposable or re-usable content

In a traditional e-learning environment the general consensus is that when creating learning content you should ensure that your e-learning objects are reusable. However, with rapid training tools such as Adobe Captivate is this still valid?

According to William Ward the keynote speaker on the Adobe e-learning tour I have just finished; in many situations the cost of creating new content is so low that you can just throw the outdated content away and start again and in many cases William (Billy to his friends) is absolutely right!

This is something that I have done many times with the Captivate content I have created. In many cases amount of time and the cost of trying to integrate new content into existing projects just isn't worth it. This is especially true when the narrative needs to be recreated from scratch as trying to ensure the tone and the color of voice-over is exactly the same just isn't worth the time and effort involved.

Yet there are also many instances when, Adobe Captivates flexible work flow has enabled me to literally drop a few new images and voice-over into an existing project and save myself a ton of work.

For example, last week as part of a marketing campaign I had to update an existing product feature tour. In total these updates took no more than approximately 45minutes whereas, creating the project again from scratch would have probably taken me a whole day and this is what I probably love the most about Adobe Captivate. As you may have heard me state before, because Adobe Captivate is so flexible, I can mold my content around my work flow rather than being forced down a single path.

The upshot of this is that whether you always ensure your e-learning content is reusable or you because of a short product life cycle you are happy to throw existing content away and start again from scratch with a rapid e-learning tool such as Adobe Captivate it really doesn't matter.

So over you to. Wherever possible when creating your Adobe Captivate projects do you re-purpose existing content or do you always start with a blank canvas?

Announcing Nutshell

Last week the company I work for (WebAssist.com) announced the release of Nutshell - Enhanced Reporting for Adobe Acrobat Connect Professional.

So why I am talking about this in a blog that is supposed to be dedicated to Adobe Captivate and e-learning? Well, because Adobe Captivate works seamlessly with Adobe Acrobat Connect Professional. Integrate Adobe Acrobat Connect Professional with Adobe Captivate and you can track your learner's progress and ensure they meet their learning objectives and what Nutshell does is offer multi-tiered reporting on all Adobe Acrobat Connect Professional trainings as well as meetings and events. With Nutshell you can not only generate reports on your Acrobat Connect activity you can also do the same for all groups, departments or your entire organization!

Want to learn more about Nutshell? View the feature tours I created for this new product, which of course were created in Adobe Captivate!

Upgrading from Captivate 1 to Adobe Captivate 2: Fudging Text Entry Boxes:

Today I am going to share some of my experience of working with Text Entry Boxes when upgrading from Adobe Captivate 1 to Adobe Captivate 2.

Back in Adobe Captivate 1 WebAssist (the company I now work for) asked me if I would create a series of interactive simulations for an eCommerce extension to Dreamweaver – eCart. This was a very detailed project and involved me creating over 60 interactive project files, many of which included TEBs (Text Entry boxes.)

Recently due a number of corporate branding updates I had to upgrade the original Captivate project files from Adobe Captivate version 1 to version 2.

Naturally I started the lengthy process of testing the upgraded files to make sure that during the conversion process no issues had been introduced.

Imagine my horror when I found that any text I inserted into the Text Entry boxes (during preview / run-time) was rendered at a different font size in Adobe Captivate 2.

Here is the reason why this happens.

After upgrading a Captivate 1 project to Adobe Captivate 2, font in text entry boxes appears large in Adobe Captivate 2. This is because of a bug in Captivate 1 and Flash Player. The font used while editing and publishing the SWF file was not the same as the original font. This bug has been fixed in Adobe Captivate 2. However, Captivate 1 projects will continue to have large font in Text Entry Boxes when the projects are upgraded to Adobe Captivate 2.

The Adobe Captivate team offers two workarounds to address this issue.

1. After upgrading a Captivate 1 project to Adobe Captivate 2, open the upgraded project.
2. Edit the font in a text entry box.


3. Use the Apply all option to apply the change to all text entry boxes in the project.

Now in theory this all sounds fine and certainly much easier that the second workaround which I will introduce in a moment.

The problem is that whilst you can change the font size in the TEBs in many cases when testing the TEBs at run-time having entered the correct text and moved to the next slide or whatever On Success action you have specified the text on the next slide of the project jumps slightly.

Now when you’re working with a single project file that has maybe one or two TEBs repositioning the Text Entry boxes isn’t a huge deal; especially since you can use the Advanced Interaction dialog box to locate all these controls. However, when you are working with multiple files all of which have many TEBs then this approach is simply a non-starter.

The second workaround might be a lot more complicated but at least it saves you from having to manually reposition your TEBs.

Here are the steps:

1. Upgrade all the Captivate 1 projects to Adobe Captivate 2.
2. From the Start menu, click Run, type REGEDIT, and click OK. The Registry editor appears.
3. Browse to HKEY_LOCAL_MACHINE > SOFTWARE > Adobe > Adobe Captivate > 2 > FudgeFactor.
4. Change the value of the FudgeFactor key to 1. The default value of the key is 1.4.
5. Close the Registry editor. The changes are applied after you restart Adobe Captivate.
6. Preview or publish the Adobe Captivate 2 projects.

What I do is create a folder on my Windows desktop and Label this “Fudge Factor is set to 1”