A CPU intensive ending of publishing a course is the "optimizing images" section. Is there any documentation on how Optimizing Images / Publish Quality handles image optimization for png vs jpg images as far as HTML5 output?
Hi there, Sam. Tell me about what's happening on your end. It sounds like you might be making decisions about your image file types based on how that part of the publishing process works. Is that accurate?
I'd like to make our courses optimal for HTML5 playback for both desktop and portable devices. I've observed that the final phase of publishing will utilize all the cpu cores to "optimize images". There's no information as to whether this optimization is for Flash output or HTML5 output. (Enquiring minds want to know.)
If there is some optimization of images at publish time for HTML5, I'd like to know more about it so we can make better decisions. Are images resized for mobile? Are both jpg and png compressed further? What optimization is Storyline doing?
Hi Sam. The HTML5-only publishing option might generally take a bit longer than the Flash-only option during the image optimization. That process is designed to automatically compress images and preserve image quality to make your course look good and launch smoothly without a lot of image file maintenance on your end. It might take a few minutes and pull from your computer’s resources during that time.
If it’s becoming problematic for you, would you be able to open a case with our support team?They’ll probably explore some specifics to your system and to the types of projects you're publishing to see if they can give you more insight into what’s happening with your files.
The HTML5-only publishing option might generally take a bit longer than the Flash-only option during the image optimization. That process is designed to automatically compress images and preserve image quality to make your course look good and launch smoothly without a lot of image file maintenance on your end.
I would wouldn't say this is problematic. The time a learner spends loading HTML5 content is higher than the time it takes Flash to load. Are there any insights that would keep up image quality for the learner while keeping the learner's load time down?
Does the automatic compression of HTML5 images downsize large images to a more optimal size for portable device viewing? Does it do this for both png and jpg? Are jpg's compressed to a lower quality? Are png images compressed? When publishing a course, what does the HTML5 image compression phase do exactly?
Did you ever get an answer to this? images are loading very slowly for me, despite choosing the lowest image quality at publish (jpeg images). I tested it in my LMS and in SCORM Cloud with he same slow result in both leading me to believe it's an issue within storyline and the way it renders images
Hey Jason - Looks like you've reached out to our support team as well, so I encourage you to continue the conversation there for the best service.
Sam is a regular contributor in the forums, so I'm sure he'll get back to you. You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.
9 Replies
Hi there, Sam. Tell me about what's happening on your end. It sounds like you might be making decisions about your image file types based on how that part of the publishing process works. Is that accurate?
I'd like to make our courses optimal for HTML5 playback for both desktop and portable devices. I've observed that the final phase of publishing will utilize all the cpu cores to "optimize images". There's no information as to whether this optimization is for Flash output or HTML5 output. (Enquiring minds want to know.)
If there is some optimization of images at publish time for HTML5, I'd like to know more about it so we can make better decisions. Are images resized for mobile? Are both jpg and png compressed further? What optimization is Storyline doing?
Things like that.
Hi Sam. The HTML5-only publishing option might generally take a bit longer than the Flash-only option during the image optimization. That process is designed to automatically compress images and preserve image quality to make your course look good and launch smoothly without a lot of image file maintenance on your end. It might take a few minutes and pull from your computer’s resources during that time.
If it’s becoming problematic for you, would you be able to open a case with our support team? They’ll probably explore some specifics to your system and to the types of projects you're publishing to see if they can give you more insight into what’s happening with your files.
I would wouldn't say this is problematic. The time a learner spends loading HTML5 content is higher than the time it takes Flash to load. Are there any insights that would keep up image quality for the learner while keeping the learner's load time down?
Does the automatic compression of HTML5 images downsize large images to a more optimal size for portable device viewing? Does it do this for both png and jpg? Are jpg's compressed to a lower quality? Are png images compressed? When publishing a course, what does the HTML5 image compression phase do exactly?
Did you ever get an answer to this? images are loading very slowly for me, despite choosing the lowest image quality at publish (jpeg images). I tested it in my LMS and in SCORM Cloud with he same slow result in both leading me to believe it's an issue within storyline and the way it renders images
Hey Jason - Looks like you've reached out to our support team as well, so I encourage you to continue the conversation there for the best service.
Sam is a regular contributor in the forums, so I'm sure he'll get back to you. You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.
I haven't had any feedback about this. Storyline image compression remains a mystery.
I see these questions were from 2 years ago. Is there any documentation available now about how Storyline handles images?
Hi there, Vicki!
I'm happy to lend a hand! There are quality settings in Storyline's Publish window that allows you to set the compression rates:
✏️Note: Image compression only applies to JPG files.
Let us know if you have any specific questions or concerns. Happy to continue the conversation!
This discussion is closed. You can start a new discussion or contact Articulate Support.