Forum Discussion
Audio Cutting Off
I am having a very frustrating audio issue in Storyline 2. I will have a presentation with audio narration (.wav files) on each slide. When I preview or publish the presentation, at least one audio file will cut off in the middle of the slide. If I go into the timeline of that slide, double-click the audio and then click "Save and Close" it fixes that slide. When I preview the presentation again, another slide might be having the same issue...this process will repeat itself over and over again.
I am working with files that are located on my Desktop.
I will really appreciate any help with this issue!!
Hi Tamara!
As far as audio mp3 is a supported format to import into Storyline 2. If you are having difficulty, you could certainly match the recommendations above in case it were a format/codec error.
If you are continuing to have difficulty, I invite you to share with our support engineers here.
- TamaraTarasovaCommunity Member
Thank you, Leslie! Am I getting you right that for the next project it might be worth saving the file in the WAV format rather than MP3?
HI Tamara,
It's worth a try - just based on not knowing what codecs or other elements are a part of your current MP3. Also we'd be happy to take a look at it privately by sharing it with our Support Engineers using the link that Leslie mentioned above.
What Joseph said. :)
But glad to hear you got everything resolved right now - and feel free to keep us posted if you run into it again!
- TamaraTarasovaCommunity Member
Ok, sounds like a plan! thank you so much, Joseph!!!
- ElisiaStewartCommunity Member
Very interesting. Thank you, Matthew! Just to clarify, this has helped your audio from cutting off randomly in the middle of the slide, not just clipping off the very end?
Hi Elisia!
Looks like Matthew has popped in to assist you here and I agree that we would want to be sure that you are utilizing the correct audio format.
There is an Add Attachment button when you reply and you are welcome to share the .story file for someone to take a look at.
- ElisiaStewartCommunity Member
Leslie/Matthew,
I am using the .wav files with the specifications suggested above. I have shared my Story file with Articulate Support a few times and when someone else opens the file, it works fine. Next time the issue occurs, I will post a screencast.
Thanks for the update Elisia and for mentioning that you have been working with support. You are welcome to share a screencast with support as well so that they can further assist.
- RashidKharratCommunity Member
Hello
I am having the exact same problem, I am using .mp3 audio files 48kbps and I made sure that the audio bitrate is also 48kbps in the publish settings, But the problem is still there.
Any help would be much appreciated.
Hi Rashid!
I invite you to take a look at this information:
Although Articulate Storyline and Articulate Studio '13 support a wide range of audio file formats (AAC, AIF, AIFF, M4A, MP3, OGG, WAV, WMA), not all codecs and bitrates are supported. If you encounter either of the issues described above, we recommend converting your audio files to 16 bit 44 KHZ PCM WAV for best results.
- Here’s a video tutorial on how to configure Soundbooth and Audacity to convert to 16 bit 44 KHZ PCM WAV.
- And here’s a video tutorial on how to convert audio files to 16 bit 44 KHZ PCM WAV in iTunes.
It looks like we were unable to re-create the users issue in this thread.
Does this happen with any project or just one? Have you tried to import the audio into a new course to see if you have the same behavior?
- RashidKharratCommunity Member
Hello, the problem has persisted actually. I work with a team of three and i am the only one facing this issue although we all use the same audio files, publishing setting, and articulate version. I have uninstalled and reinstalled articulate and the problem has not been resolved. Please help as I am facing this with every course i publish.
Hi Rashid! I had to read back up on the issue here. With all of your troubleshooting and mention of it working for your colleagues, it may be best to work with our support team directly here.