As much as I now believe that placing an Action on a slide of only .2 seconds is NOT a good idea, moving the Action to the following slide did NOT fully remedy the problem I was experiencing. After extensive Beta testing, I still had reports of slide audio missing the first few words of a sentence or not playing at all. I don’t consider myself a “power user” of Captivate, but have produced nearly 20 programs over the last 3 or so years without this problem. The one difference of this latest program was project size – 13 randomly accessed modules with a total running time of about 40 minutes. Previously I always placed .wav files in my projects and let Captivate do the compression. With this latest project, the .wav files simply made the project too hard to work with, so I compressed them into .mp3 format in Audition before placing into Captivate. I noticed however that if I made any adjustments to audio (timing, etc.) using Captivates internal audio editor, that Captivate saved my changes back as .wav files (in the library). Okay, I understand why, but it seems that’s where my problems began. So… as Rod Ward suggested I reinserted ALL the audio. My workflow was: 1) open the original .wav file in Audition, 2) make any changes found necessary during the programming process in Captivate, 3) save the .wav file as .mp3 in Audition using a new name, and finally 4) reinsert the slide audio in Captivate. Problem solved. Bottom line, for me at least, if I’m going to insert .mp3 audio into Captivate, I won’t mess with it once inserted! One other possibility would be “round-trip” editing of an .mp3 file in Audition directly from Captivate, but have never tried that as recompression of an .mp3 (I believe) would be ill-advised.
Again, thank you for the advice and support!
AdChoices