Any update on this issue?  I recently upgraded from Captivate 4 to 5 and am having the same frustrating experience.  I can only record 4-5 slides at a time before this happens to me and with a large project ahead of me I am considering returning to Captivate 4.

On a separate but related note, I have also had several situations where using the record audio option crashes my entire computer, forcing me to reboot.  Anyone else have this problem?

Thanks!

More input...

Recalibrating doesn't seem to prevent the error for me.

Captivate seems to lose its place with the counter that is tracking the audio recordings.

When the error occurs, the  message is "unnamed audio clip", whereas when things are working well, the clips are numbered sequentially.

I thought maybe saving might be triggering the audio crashes, but apparently that has nothing to do with the problem.  Even if I don't save, the issue comes up every 6 or 7 recordings.

I figure I'm losing almost 5 minutes every time I have to save, exit, re-launch and re-calibrate the mic.   What a disappointment!

I am using an older Andrea headset, non-USB, and it worked fine with Captivate 4; no audio "crashes".

--Linda

I applied a recent Captivate patch a few weeks ago, but experienced no changes in the sound issues we've been reporting here.

I have sent the Captivate 5 development team a sample of a file where two things have been occurring:

• Captivate "loses" the audio device every few slides.
• On long files, more than a couple of my sound clips have been dropping audio, mostly at the end.

Upon analysis, the team did see the issue, and think that the problem was occurring with very large files.   Is that perhaps the case with those of you who are experiencing sound problems?

They also suggested a workaround for the dropped audio, but it did not correct my issue.  It only caused drops at the beginning of the affected clips instead.

To fix the problem for the current deadline-driven project,, I re-created around affected 20 slides and then, hoping to avoid re-recording the audio,  imported the audio from the problem slide.  That corrected the clipping issue, suggesting that perhaps the cause of the problem is somehow in the code and/or the slide -- and not directly in the MP3 file.

I have a large project coming up, and regrettably, I'm going to use Captivate 4 so I don't risk adding uncompensated troubleshooting time to my work.

The developers are aware of all the sound issues.  I encourage you to continue to report bug issues at their site, and to post any insights here.

I'm very impressed with some of the new UI features and efficiencies in CA 5, but feel that it is critical that the audio be corrected and thoroughly tested on all user hardware platforms.

--Linda

Having same problem on Window 7, 32 bit, with Captivate 5....But WORSE.... sometimes the program totally freezes right after it loses the mic, and then Captivate forces a shut down losing all of my unsaved work... I'm NOT a happy camper right now. My headset mic is not usb either.

I worked some months back with the developers.

They had me try a workaround in some test files and also took a look at a file I sent them in which I was experiencing the lockup and clipping problem.

Their suggestions for workarounds did not address enough of the audio issues.

Especially with large files, I was still getting clipped endings on some audio, and was also experiencing the lockups and need to re-boot.

Sadly, I've reverted to V4 for my production work because I was losing too many hours to workarounds for a software problem.

Then I noticed that even in V4, I experienced some similiar issues with clipped audio, although not as much as in v5.  The lockups do not exist for me in v4.

I did learn over time that if I add silent time at the end of a recording in order to compensate for Captivate potentially clipping the end of a sound recording, I set focus earlier in the track by clicking.  That seems to eliminate much of the clipping issues.  Sometimes I just record a few seconds or two without speaking, and then of course make that section silent.

I'm not a developer, but my sense is that if any of the code from v4 was used as part of the v5 audio code development, the problem was potentially migrated over.

I know the developers are aware of and workingn on these issues, but I'm not privvy to any specific patch schedule that addresses this further.

It's a fairly new laptop, and everything is up to date. The laptop is usually very quick to process things when using other programs. I have run updates, done disk cleans, defrags, etc... and it doesn't stop the problems with Captivate.

I just got Captivate about 1 month ago, and have loaded all updates, and I check for new ones every day.  I have used it quite a bit since that time, and have noticed that the larger my file gets (over 100 slides) the worse the performance gets. Like taking forever just to update a change on one slide.

I am resorting to doing the audio recording outside of captivate, as I can't afford to lose anymore time on my projects.

I totally agree... Captivate is not stable at all!  I have resorted to recording audio on a Blank Project, with just one slide. Then I save it as a podcast, instead of adding it right to a slide. Later I'll go back and import the audio to the proper slides.

I thought this might help, however, it does not! Even on a blank project, with NOTHING saved to the project, Captivate CRASHES after 3 or 4 recordings... This is ridiculous... How can Adobe even pretend to say this is ready for Market, and actually charge money for it!  It doesn't do what it is supposed to do! Don't they have a Quality Assurance Department??

Captivate could be an Awesome Product, IF it actually worked correctly... but it doesn't. I would not recommend Captivate to anyone until they get it repaired... too much time is wasted dealing with these errors.

I have also found, closing down Captivate, and reopening the project, "resets" the software to again recognize the M-Audio interface we are using with our condenser microphone and to accept the channel and pre-amp values that we originally preset. Thanks for sharing and continue luck on your project. Work arounds rock!

Jim Richmond

e-Learning/Career Management Services

Right Management

4000 Piedmont Parkway

High Point NC 27265

United States

Phone +1 919 403 5615

Mobile +1 336 259 9524

jim.richmond@right.com

www.right.com

Not sure if this will help or not, but I actually received a call from Adobe the other day, regarding my download of the trial version of Captivate 5. My boss purchased it for work, and I downloaded the trial version at home to practice. So I was happy to explain all of my problems with the program to the girl on the other end. I also told her that myself and many others had been posting on the forums about these problems. She told me that she would pass along my comments to their "engineers" and that they had seen the postings on the forum, so they were aware of the problems and were working on it.  I halfway believe that is just what she says to anyone with concerns. I do believe that if enough our our complaints are on here, Adobe has to realize it will hurt their sales of Captivate. As much time as Captivate has cost me in production, we would have been better off to buy a more expensive program to start with! We'll see if they actually do something about it now.