Forum Discussion
Poor image quality when uploading an image with Rise
Hello,
I created and saved-for-web a .png image in Photoshop. When I uploaded it with Rise (as a centered image in my blocks-lesson), it converted it with poor quality. Is it possible to avoid those artifacts? Looks not so good when a course is viewed on PC screen.
Thank you!
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 Nova!
If you need to add more white space around the edges of your image, you can easily do that by inserting the image on a blank PowerPoint slide. Align the image to the center of the slide, then save the PPT file as a PNG image.
Finally, insert the PNG image into the Rise 360 image block.
Let us know if that helps you!
Sorry, but I have to get this off my chest,
Don't we have here one of the most discussed threads and is it possible, that it's one of the oldest, still ongoing threats/problems? Maybe in the whole world? it's been around for a good three years not. C'mon guys!?
I'm adding a screenshot that shows the fair quality PNG I shot with snagit on the right side and on the left, the just terrible result of how it looks in my latest RISE project.
I really don't know why I am burning a hefty CHF 1300 a year for that. This is highly unprofessional and as soon as I learn of another tool, that can do about the same, I'll be outa here.
best Roland
If it's a PNG file, you should append _NOPROCESS_ to the file name so it won't get compressed when you upload it to Rise. For example: instead of "image.png", name your file "image_NOPROCESS_.png.
Hi JC
Thx a lot for the hint, which actually helped! Nevertheless, I'm a sort of power user in my company and one of the very few who speak English (I know, there's a German community, but it's not more than a shadow of what this community is). Therefore I can relate to hints like yours. But the reason why we selected articulate/rise was, that it's so front-end-oriented easy-to-use and does not require any IT know-how.
I still try to explain this to my rise users but I also believe, that the pic import should work naturally and look good.
But again, thanks for the tip and have a good week
RolandHI Roland,
This workaround has been implemented 7 months ago. (you can see Alyssa Gomez's comment on page 7 of this post). It works very well for me. To save myself the extra work of renaming the files by hand, I use the automatic renaming feature in Adobe Bridge to add _NOPROCESS_ to the filenames of the images I need to keep uncompressed. Other software or utilities could be used to do the same.
Glad to help!
Hello, has there been any improvements on this? I have created 4 image heavy modules and now that I'm on the last two I am having problems with my images showing a blur even though they're hi-res.
Edith, are you using the above naming toggle to turn off the compression for an image?
TestImage.pngwould become TestImage_NOPROCESS_.png
_NOPROCESS_ does not accept special characters in the file name
By the way, is there something like _NOPROCESS_ for videos?
Every video asset I upload gets reencoded and ends up being 2-3x the original size. For example my original file (8.3MB):
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '01 - IVRv3 - final_NOPROCESS_.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.29.100
Duration: 00:07:00.76, start: 0.000000, bitrate: 157 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1728x1080 [SAR 1:1 DAR 8:5], 96 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
Metadata:
handler_name : Core Media Video
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 52 kb/s (default)
Metadata:
handler_name : Core Media AudioSame file when exported by Rise (23.5MB):
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'dTOkrwFfZ5Gnb1xZ_transcoded-Hz-bDN6U0jmxEOFU-01 - IVRv3 - final_NOPROCESS_.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf57.71.100
Duration: 00:07:00.77, start: 0.000000, bitrate: 447 kb/s
Stream #0:0(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 160 kb/s (default)
Metadata:
handler_name : SoundHandler
Stream #0:1(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1152x720 [SAR 1:1 DAR 8:5], 278 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
Metadata:
handler_name : VideoHandlerSo lower resolution and yet almost 3x times larger file.
Jan, I opened a case with my team so we can look into what's happening here. You should get a confirmation email soon!
Crystal Horn
Jan, I opened a case with my team so we can look into what's happening here. You should get a confirmation email soon!
Thanks for ignoring me...
3 years later....has anyone got a workaround?
HR, does the solution not work for you for images? It has been working nicely for awhile, using _NOPROCESS_ at the end of the image name as stated in this thread.
Hello,
Are there any updates on this? I added "_NOPROCESS_" into the file name, and am still experiencing the issue when adding an image into the "labeled graphic" interaction.
Thanks!
Hello, just to double-check, did you name it xxx_NOPROCESS_.jpg or xxx_NOPROCESS_.png? You have to make sure it is exactly like that, the placement of the _NOPROCESS_ before the .jpg or .png otherwise it won't work. It can't just be in the filename.
Hi Jeff,
Thank you for the response! My file name is Zoe_NOPROCESS_.jpg
Seems like it's correct, but am I missing anything? Thanks again.
Thanks for opening a support case, Anna! If we can help clarify anything Robert shared with you in your case, please let us know!
