Forum Discussion
Poor image quality when uploading an image with Rise
- 6 years ago
Hi everyone!
Do you have an image that looks blurry in Rise 360? 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.
Hi, I too am facing issues with compression - it's really noticeable in vector/flat style illustrations. I also wanted to let everyone know about what I had observed. When I uploaded my PNG file to be background for the 'Text on Image', my original file size was 56KB (a PNG file with file size 3000x1500 px) but Rise compressed my file to a PNG with a file size of 69KB. Another file, original file size 94KB to 262KB... Which goes against my understanding of... 'compression'... but I took a look at the file dimension and noticed that they changed the width to 1680px. So I resized my PNG accordingly and this seems to do okay sometimes - while I can still see some pixelation, it's something that I can live with... but again, this work around isn't fool-proof either, sadly.
I also wanted to voice my concern also about the 'Best Practices document' - I see that some of the staff are trained to just link it whenever there is a question about image quality, and personally I am wondering if these staff that link to this guide have even read through this - the only information here is that Rise has its own compression technology (which is a complete mystery to us) and the maximum file sizes for each file type. It really needs to provide more guideline to be able to be titled 'Best Practices' since currently it just says 'upload whatever you want under the file size limit and we'll just compress it for you (or in my case make the file size bigger and change the file type without telling you, and render your clean looking vector-style art weirdly).
So Articulate staff, I'm sure you are more aware of how the compression technology behaves in your own product. I think having something like this in the 'Best Practices document' would be really helpful if you cannot fix the bug due to resource restraints - provide us with the dimensions the platform is trying to compress the image to? Thanks!