Forum Discussion

SarahSexton's avatar
SarahSexton
Community Member
7 months ago

Thank you so much for your response. I am quite anxious as I was hoping to have this new updated version of our course live as of 04.01.2025. 

I have a couple of follow-up questions/statements.

  1. When you wrote, "There are some errors generated in the process of loading the baby feeding video clip on 2.3." How did you know there were errors generated?  What alerted you?
  2. I started with your suggestion of disabling all of the images/text boxes/etc. on slide 2.3, republishing it and loaded onto our LMS (Learning Point).  I clicked the next button on slide 2.2 and slide 2.3 became active as it should. (Yay!)
  3. I then tested the other suggestion of reloading the video again onto the slide, republishing the course and uploaded the new version to test this version on our LMS.  It did not work.  Please find the screen shot of slide 2.3 Test 2 below.

What you recommend next?  

  • Nathan_Hilliard's avatar
    Nathan_Hilliard
    Community Member
    7 months ago

    You'll need to narrow down exactly what is causing the problem. If you can remove only the video and have it work, then its probably the video. Otherwise, try removing everything and adding it back in small groups until it stops working, and then back up and add things one by one until you identify the culprit.

    If it is the video I would redownload the video (maybe at a lower resolution) and try replacing with that one. If not working, replace the video with some other short clip (maybe one you've used already) as a test to make sure the slide works with the different clip. If that works, use some utility like Premiere or some online tool to reprocess the clip you want to use and try that. I would suggest shooting for a lower resolution/smaller file size.

    If none of that works, or you can't really figure out what is causing the issue, consider rebuilding the slide and deleting the original.

    Of course, make a backup of your project before you start making big changes.

    The error was noted in the developer panel (Chrome, F12). It indicated that there was an issue loading or preloading that particular clip, but it still worked so it loaded at some point.