Hi community, I created a fairly large course (45 min) in length. All interactions, triggered buttons/text, lightbox animation with triggered icons, specifically synced voiceovers within layers to play only when layer is triggered. However, when I publish the course and play on an iPad, I am seeing issues where the lightbox slides appear but appear blank, voiceover plays on main slide or other layers when I click on a new layer (via an icon, again this works fine on PC when published), and a myriad of other issues. I updated the most recent version of storyline as well. Are these issues common? How should I fix?
- Scott Sweeney, Manager of Instructional Design, the Hershey Co.
Thanks for reaching out here and I'm sorry to hear about the issues you've run into. You mentioned using the latest update of Storyline, and I wanted to confirm if that was Storyline 2 Update 10? Also, what iOS are you using? Do you experience this behavior in the HTML5 output in Mobile Safari or the Articulate Mobile player? I suspect it's something we'd want to take a look at an example of to see what you're describing and then if we're able to replicate on our own devices, by publishing the output again, and taking a look at how it appears in a new file.
Are you able to share a copy of the .story file here with us? If you'd prefer you can also share it privately here.
Hi Ashley, thanks for reaching out. I submitted a case file to have this looked into. Also, one quick thing. I have a lot of slides with layers that have audio. If you want to return and review that layer, the audio doesn't play. I even have triggers set up that say play audio when timeline starts and still the audio doesn't play. Here is an example of a slide I pulled from the course.
Scott, I'd appreciate it if you could post what the outcome is. I've got several courses with various issues related to variables, states, audio, and/or graphics on an iPad, different iOS and running as html5 in Mobile Safari. I'm trying to learn all I can about workarounds so we can decide how to move forward. Thanks very much.
I just took a look at your case and it seems Victor confirmed and shared the following:
Based on our investigation, there is no underlying issue with how your course was configured. However, the issue appears to be specific to iPad's inherent hardware limitation that impact how multimedia operates and the overall performance of HTML5 content. For example, mobile Safari can only play one media file at a time. Since Slide 1.3 contains an Audio on the base layer - and another Audio on its Slide Layers, this creates an issue where the audio jumbles and doesn't work accordingly when viewed on mobile devices. Same goes for Slides with multiple animations - since performance is affected by mobile Safari's limited resource allocation. The responsiveness of content in mobile Safari will generally be slower than desktop browsers. Some courses may not play properly and may even cause mobile Safari to close unexpectedly.
To know more about Safari's limitation and our general recommendation for improving content performance, please read through this article.
Hmm. That's not good LOL. Well that's good to know at least. When I work with clients and they wish to build out large interactive courses and they also want it on iPad compatible i'll have to work with them to scale it back to make sure it's totally compatible. Thanks!
8 Replies
Hi Scott,
Thanks for reaching out here and I'm sorry to hear about the issues you've run into. You mentioned using the latest update of Storyline, and I wanted to confirm if that was Storyline 2 Update 10? Also, what iOS are you using? Do you experience this behavior in the HTML5 output in Mobile Safari or the Articulate Mobile player? I suspect it's something we'd want to take a look at an example of to see what you're describing and then if we're able to replicate on our own devices, by publishing the output again, and taking a look at how it appears in a new file.
Are you able to share a copy of the .story file here with us? If you'd prefer you can also share it privately here.
Hi Ashley, thanks for reaching out. I submitted a case file to have this looked into. Also, one quick thing. I have a lot of slides with layers that have audio. If you want to return and review that layer, the audio doesn't play. I even have triggers set up that say play audio when timeline starts and still the audio doesn't play. Here is an example of a slide I pulled from the course.
Scott, I'd appreciate it if you could post what the outcome is. I've got several courses with various issues related to variables, states, audio, and/or graphics on an iPad, different iOS and running as html5 in Mobile Safari. I'm trying to learn all I can about workarounds so we can decide how to move forward. Thanks very much.
Absolutely! Once I hear back I'll post it out and see if it helps.
Hey Scott,
I just took a look at your case and it seems Victor confirmed and shared the following:
Based on our investigation, there is no underlying issue with how your course was configured. However, the issue appears to be specific to iPad's inherent hardware limitation that impact how multimedia operates and the overall performance of HTML5 content. For example, mobile Safari can only play one media file at a time. Since Slide 1.3 contains an Audio on the base layer - and another Audio on its Slide Layers, this creates an issue where the audio jumbles and doesn't work accordingly when viewed on mobile devices. Same goes for Slides with multiple animations - since performance is affected by mobile Safari's limited resource allocation. The responsiveness of content in mobile Safari will generally be slower than desktop browsers. Some courses may not play properly and may even cause mobile Safari to close unexpectedly.
To know more about Safari's limitation and our general recommendation for improving content performance, please read through this article.
Hmm. That's not good LOL. Well that's good to know at least. When I work with clients and they wish to build out large interactive courses and they also want it on iPad compatible i'll have to work with them to scale it back to make sure it's totally compatible. Thanks!
Did you get the email from our team Scott? It would have come from Support@articulate.com
If not, I hope we can help track that down - I'd hate for you to miss any Support communication!
Yep I got it. Thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.