I don't understand why the quality of images I upload is so bad in Rise. They look fine in browser, but when I upload (and Rise compresses/crunches them) they get fuzzy, pixly and unprofessional.
I upload i png, have also tried jpg - with much worse results. Any ideas? Attached an image showing what I see in Rise v. local browser.
Hello! I noticed that there's no issue when using Chrome, but some of my graphics are washed out using IE and Edge. This is problematic if I have a quote against an image. Anyone else is experiencing this? I tried adding _NOPROCESS_ to the filename, but it didn't work.
I used the "noprocess" workaround but it's not helping. I'm looking at this multi-year old thread and wondered if there were any developments. No process has had no impact on my images.
The image you provided is quite small — the dimensions are 94 × 199 pixels. The image quality is degraded because Rise 360 has to stretch the image to fit inside the container.
Do you have another version of this image with larger dimensions?
I'd love to lend a hand. Are you having trouble with a particular image losing quality when you upload it to Rise 360? If you don't mind sharing the image, I can make recommendations for how to improve the image quality after import.
It is a range of issues and we never know which one will or won't be degraded in quality.
I was told _NOPROCESS_ is the only workaround, I was hoping there would be a more permanent solution (maybe even a toggle that allows no process to be applied to all images in a course) rather than needing to manually select and rename the images that were poor quality.
Thanks, Buck. If your original image file has small dimensions, the image may look blurry after upload it to Rise 360 because Rise stretches the image to fill the container.
I would recommend increasing the size of your image before importing it into Rise 360, and you should see a significant improvement!
I would also like to be added to any emails about fixes. I'm having this same problem, particularly using Rise in Chrome. When I use Firefox, the images don't look as bad/unprofessional.
Thanks, Julie. We'll post here if we build anything in Rise to help. For now, the workaround is to add _NOPROCESS_ to the file name of the image to prevent compression. You'll only do this for images that appear blurry.
To follow-up on Alyssa's question above. I get blurry images (images of system screen shots) in Storyline 360. They look fine as originals, but compress when publish for review. The same happens if I copy images from power-point. Is the _NOPROCESS_ implemented in Storyline 360 as well?
Hi Charlotte! Thanks for your question. The _NOPROCESS_ workaround is for Rise 360 only, so it won't work in Storyline 360.
Would you mind sharing your .story file and the Review 360 link with our team? We'd like to compare how the images appear in the file to how they appear in Review 360. You can share those assets privately by opening a case here.
The _NOPROCESS_ workaround worked once and then stopped. I've tried re-uploading the image, but I'm not having any luck. I've tried Chrome & Safari - any idea how I can sort it out?
if you're using a labeled graphic with a small image, in which case, Rise will scale the image up to at least 760 px wide so it will blur. If you try to use _noprocess_ for that, it won’t work.
I can suggest clearing your browser cache, then save the file as a different name + the _noprocess_
Is there an update to this problem, because the _NOPROCESS_ trick still works, but there's still some weird anti-aliasing going on without the workaround of my PNGs. Find attached a screen grab of one with the _NOPROCESS_ tag and one without side-by-side literally in the same editor.
Adding _NOPROCESS_ to the file name of your images will keep the image exactly as you saved it. What you're seeing on the right in your screenshot is your image file after Rise 360 compression. When you run into an image that loses quality as a result of that compression, using _NOPROCESS_ in the file name is the fix.
I don't have an update about other ways to opt out of image compression for your images at this time. We'll let you know if that changes.
116 Replies
The _NOPROCESS_ option is a good one for me, thank you!
Hello! I noticed that there's no issue when using Chrome, but some of my graphics are washed out using IE and Edge. This is problematic if I have a quote against an image. Anyone else is experiencing this? I tried adding _NOPROCESS_ to the filename, but it didn't work.
Hi Annilee!
Does the image appear washed out while authoring the course, or while viewing it as a learner?
Since Internet Explorer isn't a supported browser for authoring courses, you'll want to stick with using Edge, Chrome, or Firefox.
Can you share a screenshot of what you're seeing in Edge compared to other browsers?
I used the "noprocess" workaround but it's not helping. I'm looking at this multi-year old thread and wondered if there were any developments. No process has had no impact on my images.
Hi Micah!
The image you provided is quite small — the dimensions are 94 × 199 pixels. The image quality is degraded because Rise 360 has to stretch the image to fit inside the container.
Do you have another version of this image with larger dimensions?
I just tried this and it has not made a difference. I don't understand why this happens.
Any updates on a fix for this rather than a workaround?
Hi Carol and Samantha!
I'd love to lend a hand. Are you having trouble with a particular image losing quality when you upload it to Rise 360? If you don't mind sharing the image, I can make recommendations for how to improve the image quality after import.
Thanks Alyssa, I contacted support.
It is a range of issues and we never know which one will or won't be degraded in quality.
I was told _NOPROCESS_ is the only workaround, I was hoping there would be a more permanent solution (maybe even a toggle that allows no process to be applied to all images in a course) rather than needing to manually select and rename the images that were poor quality.
I would love some recommendations how to improve an image AFTER upload, as I can see no ways to alter anything except opacity in some cases.
Hi Buck,
Can you tell me more about how you'd like to improve an image after upload? Is your image blurry or degraded after you add it to an image block?
Yes, blurry / degraded. I ask because I cannot see a way to adjust anything after uploading an image.
Thanks, Buck. If your original image file has small dimensions, the image may look blurry after upload it to Rise 360 because Rise stretches the image to fill the container.
I would recommend increasing the size of your image before importing it into Rise 360, and you should see a significant improvement!
I would also like to be added to any emails about fixes. I'm having this same problem, particularly using Rise in Chrome. When I use Firefox, the images don't look as bad/unprofessional.
Thanks, Julie. We'll post here if we build anything in Rise to help. For now, the workaround is to add _NOPROCESS_ to the file name of the image to prevent compression. You'll only do this for images that appear blurry.
Hi Crystal... just to make sure if my image name is Blue.jpg then I would name it Blue_NOPROCESS_.jpg. Correct?
Yes, exactly, Ivana! You could put it in the beginning or the end of the file name. As long as it's in there, it will work.
Thanks!
To follow-up on Alyssa's question above. I get blurry images (images of system screen shots) in Storyline 360. They look fine as originals, but compress when publish for review. The same happens if I copy images from power-point. Is the _NOPROCESS_ implemented in Storyline 360 as well?
Hi Charlotte! Thanks for your question. The _NOPROCESS_ workaround is for Rise 360 only, so it won't work in Storyline 360.
Would you mind sharing your .story file and the Review 360 link with our team? We'd like to compare how the images appear in the file to how they appear in Review 360. You can share those assets privately by opening a case here.
Hi Alyssa & Crystal,
The _NOPROCESS_ workaround worked once and then stopped. I've tried re-uploading the image, but I'm not having any luck. I've tried Chrome & Safari - any idea how I can sort it out?
Hi D du Bois,
if you're using a labeled graphic with a small image, in which case, Rise will scale the image up to at least 760 px wide so it will blur. If you try to use
_noprocess_
for that, it won’t work.I can suggest clearing your browser cache, then save the file as a different name + the
_
noprocess_
Please let me know if that worked for you!Hi there Renz,
Thank you - after I sent this I discovered the live chat feature on the support page and Hazel managed to get me sorted.
Looks like the _NOPROCESS_ tag needs to be duplicated at times for it to work, in case anyone else is struggling with this:
ImageName_NOPROCESS_NOPROCESS_.png
I really hope the dev team can get this sorted out soon.
Is there an update to this problem, because the _NOPROCESS_ trick still works, but there's still some weird anti-aliasing going on without the workaround of my PNGs. Find attached a screen grab of one with the _NOPROCESS_ tag and one without side-by-side literally in the same editor.
Hello, Windesheim Flevoland.
Adding _NOPROCESS_ to the file name of your images will keep the image exactly as you saved it. What you're seeing on the right in your screenshot is your image file after Rise 360 compression. When you run into an image that loses quality as a result of that compression, using _NOPROCESS_ in the file name is the fix.
I don't have an update about other ways to opt out of image compression for your images at this time. We'll let you know if that changes.