Publishing to MP4: Layer Trigger working erratically
Feb 07, 2019
Hi
So I've tried every which way of publishing this story to MP4 with the embedded audio and the triggers work when the story is previewed and partially work when publishing to MP4 but all of a sudden they stop advancing. Anyone got any ideas before I through this through the window?!
I've gone so far as to publishing each slide separately (see attached) and I've attached the story so you can see it works.
I just need to pull it out as is so that I can importing into our video editing software.
Help!
6 Replies
Hi Jennifer,
Thanks so much for sharing those files with me! I had a look over your triggers, and everything appears to follow the guidelines we suggest for publishing to a video file.
When I published your course, I found that the video ended on Slide 3, Financial Layer. Is that the place where the video stops for you, as well?
When I publish the individual slides its stops on different layers and freezes (so if you preview slide 2 then watch overview 2 you'll see what I mean), then, as you say, if you publish the whole thing it won't publish and it sticks at different points
Thanks for confirming that, Jennifer! I'd like to enlist the help of our Support Engineers for further troubleshooting. I've opened a case on your behalf, and they'll reach out to you soon with next steps!
Thank Alyssa really appreciate it :-)
Hey Jennifer!
I checked in on your case this morning, and I see that Jose found this issue to be a software bug. He reported it to our team so we can begin looking at next steps.
I really appreciate you giving us a head's up about this issue, and we'll update you as we get more information about it!
Hi, Jennifer.
We appreciate your patience while our team investigated this.
I am happy to share some great news! We fixed the issue you reported where:
Not all layers are being included when project containing slides with multiple layers that have audio is published to video
Be sure to install the latest Storyline 360 update (Build 3.50.24668.0) to take advantage of all the recent features and fixes.
If the problem happens again, please let us know, or you can always work directly with our support engineers here.