Forum Discussion
Image compression in Rise
Hi
I'm having an issue with what appears to be an auto compression being applied to images I'm uploading to Rise. It seems to be most obvious in images with text, as the text gets quite badly aliased.
I've attached a screen shot of how it appears in Rise, and the original PNG for comparison. I did wonder if Rise was converting my PNGs to JPG, so I did try re-rendering as a 100% JPG but it ended up looking exactly the same despite the file size being around three times bigger.
Any ideas?
Thanks!
Nic
21 Replies
Thanks for sharing Paul.
I'll be sure to share these examples and feedback with our team.
Having the same problem especially with png files used in the flashcard function. Would like to know when this is fixed. Definitely support the idea of us being able to pick what files are compressed and to what degree!
Hi again, Kashish!
I just responded to your similar discussion – we can keep the conversation going there!
Is there any chance of Articulate changing the image compression algorithm in Rise? My banner looks hideous, even though in my source file it is clean and clear. (I love the clever workarounds posted here, but I cannot use GIF, as my banner has both a photo and icons. I also am not going to replace a banner image over and over in the published output in dozens of Rise courses that will use this banner image.) Whether I upload the image in PNG or JPEG format, too many artifacts are highly evident. Can Articulate please modify the Rise image compression algorithm to ensure better image quality?
Hi Rebecca!
We've designed a workaround to keep your images looking crystal clear.
If you'd like an image to keep its specific file format and not undergo compression, you can opt-out of image optimization on a case-by-case basis. Add _NOPROCESS_ to the name of your image file. It'll upload and display exactly as you saved it. Keep in mind that the 5GB file size limit still applies, and you could see an increase in your output file size.
If this doesn't help please let us know and you can share the file with us privately by opening up a case to investigate further
Oh, that is SO great. My banner image now looks crystal clear. Thanks for the workaround!
Your workaround works great! You should inform your UX team so they can implement controls for it.
Edit: The _NOPROCESS_ solution works even if you crop images, which is amazing! 😃
The work around didn't work for my images.
Hi Karen! To confirm, did you add include the underscore in _NOPROCESS_ to the file name of your image? For example, if your image's file name is Cat.jpg, when you add _NOPROCESS_, it should now read as Cat_NOPROCESS_.jpg. If you have done that and you are still having problems with the image, feel free to open a case here. Our support engineers are ready to help.
Thanks! I was putting it at the beginning of the image name.
Thanks,
Hi Karen, it sounds like you're all sorted out! Let us know if you need any further help with your images.
By the way, replying via email includes your signature with contact information in the public forum. Feel free to edit your reply here!
