Forum Discussion
New BUG: Audio files are encoding even when compression is set to 'None'
New BUG: Audio files are encoding even when compression is set to 'None'.
This is super annoying when you have already made the perfect settings in your external program. My team and I are heavy power-users and have hundreds of courses with thousands of audio and video files where we push Storyline to its limits.
Also a feature to set compression to None as default for audio and video files would be awesome.
Also please fix the Bug, where if you 'Replace' a video file, you can't change compression from 'Automatic' to 'None' - the field is greyed out.
Thanks for fixing the trigger condition crash bug in the latest update.
Hello Asbjørn!
Sorry for the trouble! I'd like our Support Engineers to work with you directly so we can log your findings.
It sounds like you've come across two issues:
- Audio files are encoding even when the compression is set to "None."
- Compression settings are greyed out when replacing a video file.
Are these issues happening just in the latest version of Storyline 360 (Build 3.57.26476.0)? Also, are you finding this behavior occurs in all projects or just the specific file you are working on?
It would be helpful for us to test your project on our end. Can you share the .story file with us privately in a support case? After testing, our Support Engineers will work with you directly via email.
You'd also like to see a feature for the option to set a default for the compression setting for audio and video files. I'll share this with my team too.
Hello,
Here is a sample video of the compression issue. Every audio file in this .story (except for an error audio clip) is set to 'Do not compress' - but it still compresses upon export, as demonstrated in the video.
This .story file is 64MB, so here is a Wetransfer link to it: https://we.tl/t-s1k6yaloyx
Med venlig hilsen
Asbjørn Reinhold Ravn
Digital læringskonsulent
Kommunikation og Digital LæringHello Asbjørn!
Thank you for sharing the link to download your file! I've opened a support case on your behalf and linked this discussion to your support case. We'll reach out with an update soon after reviewing your file!
Hey,
This happens with identical video files. I have made a screen recording showcasing the issue, and demonstrating that both files can be set to Automatic OR no compression and that both files can have the option greyed out, after using the Replace feature. After using the Replace feature, the entire Slide gets 'tainted' and even after deleting the video and reinserting it, the problem persists with the compression method being greyed out.
The screen recording is attached to this e-mail.
Med venlig hilsen
Asbjørn Reinhold Ravn
Digital læringskonsulent
Kommunikation og Digital LæringHaving same issue...was this resolved?
there is no known problem with mp3 audio and set audio compression 'None'
just tested with SL 3.86
please upload a example .story file with your problem here as attachment
Appreciate the reply. I can't post my client's file or video in this case, but I did some further digging & tests and it turns out that for my specific instance, it was just a setting issue:
Even though I had compression set to "none", it was being overwritten by the "adaptive video" setting, since that requires re-encoding."adaptive video" means the video will published in 3 different sizes* - so a recompress is unavoidable
* side effect: the scorm package will is significantly enlarged
We are having the same issue, still right now. Even when setting audio to compression "none" for each audio track in the specific settings, it will encode when publishing, taking lot of time for courses with lot of audio tracks.
I confirm we have the same bug when replacing video tracks, You will not be able to change compression settings because it will be greyed out. I think this happens because SL thinks you are trying do customize the video track inside SL (like when you need to cut or change audio volume) so It creates sort of new custom audio/video track.
How come no other developers experienced the same issues?
thanks
Hi Zio,
Sorry to hear that you ran into this issue.
There was a bug described in this thread that caused the compression field to get disabled when a video was replaced, but it was fixed in a previous release of Storyline 360 (Update 75). Can I ask which version of Storyline are you currently using? I checked the email you used to post here but it doesn't appear to be associated with an active subscription.
Additionally, would you be willing to share a copy of your project file here or in private by opening a support case so we can check if the same behavior can be replicated in Storyline 360's most recent version? We'll delete it when we're done testing!
