I found other threads discussing the buffering of videos, but what I would like to know is, why isn't there an option to set a buffer for your video like there is in Flash or HTML5?
Video playback is affected by so many variables, but at least some of those variables can be managed by setting a good buffer size in milliseconds for your video. That way, the video doesn't start playing until the user's system has downloaded enough of it to actually play.
Storyline progressively downloads videos (except SWF movies) in published courses. This means learners won't have to wait for each video to fully download before it begins to play.
Here's how Storyline handles different video formats:
MP4 and FLV videos are natively supported in Storyline and will progressively download by default.
SWF movies are natively supported in Storyline. However, they won't progressively download.
Storyline converts all other video file formats to MP4 and progressively downloads them in published courses.
In some cases, you may have an MP4 file that isn't properly formatted. As a result, learners may experience a long delay while the entire video downloads. If you have an MP4 file that takes a long time to play, you may be able to correct it with the method described here.
We're always interested in hearing about other features you'd like to see, so I'd love to have some more detail on your learners and their environments, and how this would help as a feature request!
I completely understand how Storyline delivers video; I was a Flash developer looooonnnggg before I started using Storyline.
To be clear, this is NOT an issue with Storyline; it's an issue with the bandwidth and hardware the client is using to deliver the training.
That is why, if I were still developing in Flash, I would set a reasonably sized buffer in milliseconds for the video player to make sure that a good portion of the video had already loaded into memory before it started playing. Sure, they get to watch a spinning circle for the amount of time it takes their system to load the buffer.
BUT for systems and networks that are faster, the buffer is overrun so quickly they don't even notice it and for slower systems / networks, they get the video with fewer stutters and stoppages as their systems try to catch up.
2 Replies
Hi Rodney,
Storyline progressively downloads videos (except SWF movies) in published courses. This means learners won't have to wait for each video to fully download before it begins to play.
Here's how Storyline handles different video formats:
In some cases, you may have an MP4 file that isn't properly formatted. As a result, learners may experience a long delay while the entire video downloads. If you have an MP4 file that takes a long time to play, you may be able to correct it with the method described here.
We're always interested in hearing about other features you'd like to see, so I'd love to have some more detail on your learners and their environments, and how this would help as a feature request!
I completely understand how Storyline delivers video; I was a Flash developer looooonnnggg before I started using Storyline.
To be clear, this is NOT an issue with Storyline; it's an issue with the bandwidth and hardware the client is using to deliver the training.
That is why, if I were still developing in Flash, I would set a reasonably sized buffer in milliseconds for the video player to make sure that a good portion of the video had already loaded into memory before it started playing. Sure, they get to watch a spinning circle for the amount of time it takes their system to load the buffer.
BUT for systems and networks that are faster, the buffer is overrun so quickly they don't even notice it and for slower systems / networks, they get the video with fewer stutters and stoppages as their systems try to catch up.
I will definitely submit a feature request.
This discussion is closed. You can start a new discussion or contact Articulate Support.