Audio Compression and Bitrate Options

Nov 08, 2018

Hello!

We've run into an issue where all audio files are being compressed significantly. This is a problem because we are attempting to demonstrate various levels of audio compression, but the files are all being compressed further than intended. Some files are original, full bandwidth and bitrate, while others are intended to be compressed and low bitrate in order to demonstrate how audio quality can vary. However, they all end up being highly compressed so the demonstration is not effective at showcasing how compression reduces audio quality.

Is there a way to prevent the uploaded files from being compressed at all? 

11 Replies
Michael Anderson

I can't answer your question, but one alternative would be to replace the audio files manually after you have published your course. This is not optimal. Another option might be to host the original audio files on a web site and play them directly from there, so that Storyline cannot recompress them at all.

Michael Anderson

Your best solution may be to pre-compress the files that you want to sound bad to whatever bitrate you want to demostrate, using a different program outside of Storyline, then insert all files into Storyline, and when publishing choose the highest quality audio setting. The quality of your worst files will not improve, demonstrating what low bitrate sounds like, and your high bitrate files will still sound pretty good.

Basheer Bazoun

Thanks Ashley, The files are of the same type, but different bitrate levels. They are all being reduced equally to 24 kbps, even though they were uploaded at 320, 192, 168, 128, 64, 32, 16 and 8 kbps. I understand the functionality may not support this much variation.

Ashley Terwilliger-Pollard

Ah, good to know, Basheer. 

Storyline will only allow for you to customize the bitrate upon publishing between 16 kbps and 160 kbps, so it sounds like even if they were importing as needed you'd still be stuck at publishing. I think your best method is to look at finding those files in the published output and replacing them there.