I received an email from a Captivate developer who was publishing a Captivate project as an MP4 video so that it could be used in Adobe Premiere. She was required to deliver an MP4 that was published at a frame rate of 30 frames per second (fps). She checked her Captivate publishing settings (via File > Publish Settings) and verified that Captivate was set to publish at 30 fps.
After publishing the MP4 video, she learned that the Frames Per Second setting in the Publish dialog box controls published SWFs, not MP4s. In fact, the MP4 she published was actually set to 15fps, which was unacceptable for her needs. Unfortunately, there is no Captivate setting that controls the fps of MP4 videos... she was stuck.
I sent a quick email to the Adobe Captivate team on her behalf inquiring if there was a workaround. It turns out that there is. Adobe has received multiple emails from Captivate developers requesting a way to output MP4 videos at 30fps instead of 15fps. The Adobe team responded by creating a small text file (MP4Settings.ini) that simply sets the fps for published MP4 videos to 30fps during the Publish process. I've included both a link to the MP4Settings.ini file and quick instructions on its use below
- Download the MP4Settings.ini file to your computer.
- If necessary, close Captivate.
- Copy the downloaded MP4Settings.ini file to the Captivate install directory (this is typicallyC:\Program Files\Adobe\Adobe Captivate 6 (32 Bit or 64 Bit).
- Start Captivate and re-publish the project again as an MP4.
Note: If you've never published a Captivate project as a video (MP4), you'll find the process painless. Simply choose File > Publish. From the Select Type drop-down menu, choose MP4 Video and then click the Publish button.
While videos will work nicely on sites such as YouTube and play on mobile devices such as the Apple iPad, the video is, well, simply a video. Any interactivity that you might have added to the lesson won't work at all. If you want to publish content that will remain interactive while accessed with a mobile device, you should consider publishing as HTML5 instead.