My team has been experiencing some issues with Published Storyline files. The audio is at the .2 second mark on the timeline and there is no existing cue point. When published, the audio skips over the first couple seconds of the audio file. When you click the replay button, however, the entire audio clip plays.
This is not consistent on all slides - only a handful.
We'd like want to take a look at your .story file and find out a bit more about where and how you're hosting the published output. Are you able to share a copy of your .story file here with us? You can upload it using the "add attachment" button at the bottom of the reply window. If you'd prefer to share privately you can also send it along to our team here.
Ashley, I've shared the module privately with your team.
We publish with the HTML5 output selected (not available offline and not for Articulate Player). We host on Moodle - uploading the entire SCORM package.
Do you have a case number so that I could follow along with your case? You would have received the case number as a part of the confirmation email once the case was submitted.
Thanks Tiffany and it looks like you case has been assigned to my colleague Robert, so he'll be in touch shortly. I'll follow along as well so that I can share any updates here.
I just was checking in on your case and it looks like you and Robert worked through some additional troubleshooting steps and you'll be reaching out to your IT team to assist with:
- Check if clearing your browser cache will help - If the issue persists reinstall Google Chrome - Check the system information if you have recent audio driver
Please feel free to follow up with Robert and let him know the outcome of this situation.
Ashley, just a follow-up. Clearing the browser cache did not work and I have the most recent audio driver. My IT team says it is not a problem with Chrome. I'm at a loss right now and crossing my fingers none of my customers have the same issue that myself and some of my team members are having. I tried to make sure Robert understood it was happening on more than one computer - not an isolated incident, but I don't think that was clearly understood.
8 Replies
Hi Tiffany,
We'd like want to take a look at your .story file and find out a bit more about where and how you're hosting the published output. Are you able to share a copy of your .story file here with us? You can upload it using the "add attachment" button at the bottom of the reply window. If you'd prefer to share privately you can also send it along to our team here.
Ashley, I've shared the module privately with your team.
We publish with the HTML5 output selected (not available offline and not for Articulate Player). We host on Moodle - uploading the entire SCORM package.
Hi Tiffany,
Do you have a case number so that I could follow along with your case? You would have received the case number as a part of the confirmation email once the case was submitted.
Sure! Case: 00793990
Thanks Tiffany and it looks like you case has been assigned to my colleague Robert, so he'll be in touch shortly. I'll follow along as well so that I can share any updates here.
Hi Tiffany,
I just was checking in on your case and it looks like you and Robert worked through some additional troubleshooting steps and you'll be reaching out to your IT team to assist with:
- Check if clearing your browser cache will help
- If the issue persists reinstall Google Chrome
- Check the system information if you have recent audio driver
Please feel free to follow up with Robert and let him know the outcome of this situation.
Ashley, just a follow-up. Clearing the browser cache did not work and I have the most recent audio driver. My IT team says it is not a problem with Chrome. I'm at a loss right now and crossing my fingers none of my customers have the same issue that myself and some of my team members are having. I tried to make sure Robert understood it was happening on more than one computer - not an isolated incident, but I don't think that was clearly understood.
Thanks Tiffany and I'll follow up with Robert as well just to ensure we're all on the same page and any other testing and troubleshooting we can do.
This discussion is closed. You can start a new discussion or contact Articulate Support.