Audio quality degrading in Captivate

Forum|Forum|5 years ago
July 7, 2020
3 replies
760 views

So I have recorded audio for my e-learning course in Adobe audition. It sounds good in Audition and when played independently, but when I import it into Captivate it is sounding scratchy (best term I can describe). Any idea of how to fix this? This isn't my first time importing a .wav file from audition to Captivate, just the first time I've noticed a degredation in quality. Thoughts?

Audio and video

This topic has been closed for replies.

P

paperthreads

Participant

I am having the same issue. We haven't developed new eLearns with audio for a few months, and are back at creating our next batch of courses - and the audio is coming out horrible through captivate. I created in Audition, it sounds great. Bring it into Captivate, and it's terrible sounding.

Really terrible sounding in the Audio edit screen when adding the closed captioning, it's robotic sounding.

When I preview the slides/course in HTML or Slide preview, it's not as bad, but terrible.

So I published, just to see how it sounds, and it is still very crackly.

This is not a new process for me, have been doing course with audio for some time now - it worked before, but is not working now.

Did you report this to Adobe? Did you find a solution?

J

Jacob Hokland

Inspiring

Not a bug. Just Captivates way to compress the audio so it is tagged to match 30 FPS in the time line. But the task is outdated and unnecessary now-a-days.

Export the project and replace/overwr ite the audio files with the source files (remeber to rename your files so the are matching.)

Lilybiri

Legend

It is a WAV file, correct? What are the settings? How did you test in Captivate (Preview or after publishing)? I mostly use your workflow, creating the audio clips in Audition and then import them to the Captivate library from which I drag them on the appropriate slides.

C

catherine.johnsonAuthor

Participant

It is a WAV file. So it's currently 48000 Hz and 32 bit (float). I'm listening to it in the production side and previewing it in HTML5. I'm hearing it in both. I honestly haven't tried putting it into my LMS yet to see if it is there. I've never had this issue before and I didn't change my overall process at all.