Forum Discussion

AsbjrnReinholdR's avatar
AsbjrnReinholdR
Community Member
3 years ago

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 p...
storyline 360
ZioFonta's avatar
ZioFonta
Community Member
5 months ago
Asbjørn Reinhold Ravn

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.

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

  • JoseTansengco's avatar
    JoseTansengco
    Staff
    5 months ago

    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!

Related Content