August 28, 2019
E-learning reacts slowly on action buttons
Comments
(2)
August 28, 2019
E-learning reacts slowly on action buttons
(2)

Dear all,

I have some problems with many of my e-learning projects:

Everything works fine in preview, but after publishing to html the e-learning seems to react only slowly on action buttons (especially “go to next slide” or “jump to slide”). I’ve  created my own navigation bar at the bottom and every button is displayed right at the beginning.  When I play the e-learning in explorer or chrome (both the same issue) I click the “next” button and only after some seconds I get to the next slide.  It works, but veeeery slowly.

No matter which content is displayed, this issue seems to destroy the e-learning because colleagues have to wait and it gets boring…

I’m using CP 9, 22 slides in this project, slide audio on every slide, advanced actions for CC and play/pause.

Does anyone have the same problem or a solution to improve the performance?

Best regards,
Christine

2 Comments
2019-08-29 17:15:13
2019-08-29 17:15:13

This is only a guess, but it could be possible that you are not optimizing your resources before importing them into your project. For example, an image downloaded from a stock photography site might be thousands of pixels wide and tall. It can also be such a high resolution that the file size is equally significant. One indication would be the project file size (CPTX file). For example, if you had a 60 slide eLearning course and the project file size is 20 – 40 megabytes this probably isn’t the case. If on the other hand, the project file is 500 megabytes or more your resources are probably much larger than they need to be.

When I process an image, I tend to choose a resolution no larger than the largest that image would get enlarged to in my eLearning. For example, If my elearning project is 1024 x 627, I would resize an image that initially was, say, 6144 pixels wide down to 1024 pixels wide. If the image was also 300 pixels per inch, I might reduce the pixels per inch down to 72 pixels per inch. When preparing images for print 300 is often used, but 72 pixels per inch is suitable for the web.

Like
(2)
2019-08-28 09:28:24
2019-08-28 09:28:24

Captivate 9 is ‘old’, hope you have the most recent version (9.0.3).

Audio  and video files have to be loaded On Enter for each slide, contrary to other objects. I always recommend to keep the audio clips as short as possible, maybe distribute over more slides. And leave a small gap before and after the audio clip timeline, to avoid that Captivate sees them as a continuous clip and tries to load all at once.

Like
(2)
Add Comment