Tips for Publish to AVI in Adobe Captivate 4
With Adobe Captivate 4, you can publish your Captivate project directly as an AVI file. This enables you to create demos using Captivate and upload them as AVI files on media sharing websites like YouTube etc. There are a few points which you need to keep in mind before proceeding with publishing your projects as AVI.
- Any media encoding process requires a considerable amount of processing power. Publishing to AVI is no different, because it converts the project SWF to AVI using some encoder (more on this in the next point). So, the best result would be seen on a decently powerful machine. I would recommend to close other heavy processes running on the machine before publishing to AVI.
- While the speed of conversion partly depends on the available processing power as well, the quality of output and compression are completely Encoder dependent. Captivate uses DirectShow technology to get encoder from the system. On WinXP, we have a default encoder ‘Indeo Video 5.10 Compression Filter’ works pretty well. On WinVista, we have only one default encoder which works and that is Cinepak Codec by Radius. However, it is not a good option as it takes longer and produces a bigger file. The recommendation would be to use a good encoder, such as XviD. XviD is freely available and can be downloaded and installed easily. Klite Mega Codec pack contains XviD, and some other encoders like DivX which can also be used. We have seen good results with XviD. A point to note here is that a few encoders like ‘Uncompressed’ and ‘MJPEG converter’ are not recommended because they do not do any compression and the resulting file can take up huge amount of disk space(can go up to a few GBs).
- The size of the project in terms of runtime, as well as the size in terms of disk space used also determines how much time will it take to publish a project to AVI. For a normal demo project it roughly takes 1.5 to 2 times the runtime of the project if the above two points are followed. By normal project, I mean a project demo project which contains some audio in the form of narration, fmr slides, mouse etc. A heavy project which contains a lot of animations, text animations etc will convert a bit slower than normal.
- It is not recommended to convert projects which are greater than 800x600 in resolution. As the resolution increases, the conversion process will slow down because it will requires more processing power.
- Most of the encoders do not accept odd numbers as project width or height in terms of resolution. This means that if your project resolution is something like 455x450 or 640x479 or 425x315 etc, you’ll get an error message as ‘Error Occurred’ and the publish will abort. A quick solution would be to resize your project to have even numbers as the project dimensions.
If you keep the above points in mind, publishing your project to AVI can be as easy as publishing to SWF. Just that it takes more time. Hope this helps all who wanted to share their captivate demos on YouTube. Happy publishing!!
Comments
hi!
I am a fulbright scholar from India and presently at the Florida State University, on a research program to develop a training package for teachers to enable them to teach in online environment. As a part of a course i am presently enrolled for, which is related to developing instructional development, we have been trying to export a captivate file (to demonstrate how to develop wiki-pages ) in avi format to a powerpoint slide and failed. Could you suggest us a method to publish the captivate recording in movie format and insert to a powerpoint presentation.
jyoti
Posted by: Jyoti Bawane | March 18, 2009 10:45 PM
Why not talk about publishing to FLV?
Posted by: William Chadwick | April 29, 2009 12:15 AM
Does rendering speed depend on the CPU or the graphics card (GPU)? For example, would it be worth it to upgrade my graphics card or will this make little difference in rendering times?
Posted by: Kevin | July 15, 2009 9:28 PM
I assume you mean encoding time when you say rendering time. If this is the case, all older encoders like Intel Indeo , Cinepack that come by default in windows did not use GPU acceleration. But now there are GPU-accelerated video encoders available in the market. So, If you want a faster AVI publish time 1) Get an encoder that supports GPU accelerated encoding and 2)Get a GPU that goes well with the encoder or vice-versa.
If you are talking about the rendering time of an encoded video then roughly almost all applications use decoders which use GPU accelerated decoding and you will get a wonderful speed improvement if you own a GPU.
Posted by: Ashish Garg | July 16, 2009 2:01 PM
I have imported a PPT into Captivate 4 and want to have the slides move on click, not automatic or timed. How do I set this once the PPT is in Captivate?
Posted by: Sally Grosch | August 13, 2009 1:06 AM
Sally, if you are talking about general PPT Import in Captivate, the PPT Import dialog gives you an option of 'Advance Slide on Click'. For publishing to AVI, this is not possible as Captivate takes an non-interactive view of the project and create the movie out of it.
Posted by: Ashish Garg
|
August 13, 2009 10:06 AM
You wrote that "the best result would be seen on a decently powerful machine." Can you be more specific? I know what the minimum system requirements for Captivate are, and my machine exceeds those. But I'm guessing that the recommended system requirements for converting to AVI are higher, yes?
So what do you recommend in terms of processer speed, memory, and graphics?
Posted by: Jason High | September 13, 2009 1:31 AM
Having RAM as 1 GB or more would help. Other than that, it should be OK.
Posted by: Ashish Garg
|
September 13, 2009 7:24 PM
Hi,
We will be getting large numbers of PPt (e.g. 30 slides) and we will add about 45 mins. of audio to each. We will also want to provide the audio separately as podcast or other mobile. Will Cptvt 4 perform better (inc. compression) than Impatica (java-based). Thanks.
Posted by: michael | October 4, 2009 6:27 AM
I bookmarked this link. Thank you for good job!
Posted by: dilandinga | October 5, 2009 11:26 AM
If you have to do it, you might as well do it right.,
Posted by: Drerimma | October 11, 2009 7:36 AM
Excellent site. It was pleasant to me.,
Posted by: Kedealind | October 12, 2009 12:11 PM
I'm having trouble exporting a Captivate presentation to video. Everything works fine except that in the published file the audio get progressively out of sync. It's ok for the first 30 seconds or so but then the sync issues start to become noticeable and get worse as time goes on. Video is ahead of audio playback. Anybody else have this issue?
Thanks
Posted by: Mark Smithhisler | October 31, 2009 3:46 AM
Captivate just freezes when I try to publish to AVI (a 45 minute clip). It ran all weekend, and when I returned to the machine, Captivate was still using 55% of the (quad core) CPU, and consuming more than half a gig of memory, and the time remaining was just frozen. Publishing to AVI is a non-feature as far as I can see. It should NOT take that long to render a video that length that's lesson 800x600 resolution.
Posted by: Anonymous | November 16, 2009 8:56 PM
Captivate 4's ability to produce AVI files seems to be a crap shoot. Sometimes it works; sometimes it doesn't.
A 6-minute project of plain slides with voiceovers at 1024 x 768 takes under 10 minutes to publish as uncompressed AVI and the file size is 18 mb. On my quad core machine with 4 gb RAM (Vista), this is fine. What isn't fine is that the resulting AVIs are unplayable.
I have to re-compress this movie as H.264, so I don't want to use a codec for the export, but now I have no choice but to try each one to see if any of them work. So far, Main Concept and TechSmith both fail.
I would rather re-record in Camtasia than output this as a SWF.
This is the same computer I use for Premiere Pro and After Effects with much more intensive processes. My only conclusion is that CP4 needs a bug fix.
Posted by: tunghoy | November 17, 2009 6:30 PM
I have 3GB of Ram on my machine and have not gotten it to work. I need to publish to AVI, if not then I will have to publish yet another piece of software...this was one of the reasons for upgrading to 4.
Posted by: Sonia Woolf | November 19, 2009 7:03 PM