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 tho...
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.
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 Audio
Same 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 : VideoHandler
So 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!
Thanks for ignoring me...
Hello, Sergio. We're happy to help you, too! It looks like you indicated that you weren't able to use special characters in the image file name with the _NOPROCESS_ tip.
Can you tell me a bit more about what characters you're using? What happens? Can you share an example image file here with a file name that doesn't work?
Thanks!
