Forum Discussion
Adding Microsoft Teams Recordings to Storyline
I've been having issues with this. Here's the scenario - I add Microsoft Teams meeting recording to Storyline, publish to my LMS. I have several slides before the video. The video plays perfectly fine, but when the user clicks next, it gives the buffer symbol (spinning wheel), and will not advance to the next slide no matter how long you wait. I've checked every setting and cannot find anything that would prevent it from moving on.
For reference, the slides have the next button hidden until the media completes. The next button works fine, but then won't advance to the next slide.
Has anyone else had this happen or know a fix for this?
Thanks!
Hi JeremySmith-c22,
Thanks for reaching out! I'm sorry to hear you're experiencing buffering when trying to move forward in your course. Happy to help!
I understand you have included an MP4 Microsoft Teams video file in your Storyline 360 project. What is the length/duration of the video?
Are you experiencing this buffering behavior preventing learners from advancing in any other projects you've worked on?
One thing you can try is testing your course in SCORM Cloud. If it plays as expected there, the issue is likely related to your LMS. If the course doesn't play correctly, it'd be helpful for us to test it for further troubleshooting. You can share your file here in this thread or privately in a support case.
- JeremySmith-c22Community Member
Thank you for your response! I have testing it in the SCORM cloud and it works fine. I then published it to the LMS and it is still happening - leading me to believe that it is the LMS.
Question - I published in SCORM 2004. Are there any known issues with 2004 in an LMS? Any chance that publishing it in 1.2 would help?
Thank you!
Hi JeremySmith-c22,
Thanks so much for the update! Glad to hear that things are working as expected in SCORM Cloud.
This issue seems to be isolated to your LMS. What is the current LMS your team is using?
I am not aware of any SCORM 2004 issues. I think it would be beneficial for you to publish in SCORM 1.2 and see if that helps!
If the issue persists, I'd recommend reaching out to your LMS Admin to confirm their system requirements.