When publishing, the MP3-file is used (compressed, you know). But to make editing audio possible in CP the WAV-file is needed. Compare it with a CP-file, which can be edited (like WAV) to the SWF-file (like MP3).
If you try to edit audio in Captivate, it will happen in raw audio file. We can say .wav file.
When Captivate project is published you will always get a .mp3 file. in the published output.
This has nothing to do with the audio being imported.
- If you import a .mp3 audio file, Captivate keeps the original .mp3 file with itself and also converts the mp3 file to wav file internally.
- If you import a .wav file, Captivate does not do any modifications. It uses the same file for editing (if needed) and publishes a .mp3 file.
Again, all this is nothing to do with the scenario you are mentioning (audio export)
- While you export your audio file, Captivate purposely allows you to export both formats of audio as it might be useful to the user.
Hope this clears your doubt.
Thanks for that answer! Can we take it one step further and clarify something please?
Imagine that one has a MP3 file they successfully import into Captivate. It gets converted to WAV upon import. If the user does not modify it in any way during the edit process, is the same MP3 used when publishing? Or is it modified in any way going back out?
Helpful and Handy Links
This can happen (original file being used to publish) but not always.
There are many ways in which audio can be placed in the project. Depending on the way audio is distributed in project, Captivate decides whether to use the original audio file or generate its own audio.
Mukul, Lilybiri & Rick,
Thanks for your help.