Thanks for feedbacks Jeremy
The problems I see with 1 Line compression (ZIPS_COMPRESSION) are:
- when you zoom on a part of the image you are working, you need to load
and uncompress the whole line of every file you use to generate it.
- when you unzoom and should only display 1 pixel for 2 or 2 pixel every
3 (horizontally I mean), it need to load the whole line while only 2
pixels of 3 are needed.
Am I missing something?
Le 03/31/2014 02:50 PM, Jeremy Fernsler a écrit :
I've used EXR w/ ZIPS compression.
Standard ZIP is in blocks, ZIPS compresses scanlines. So your file reads are
faster off the disk and a single decompression falls right into what Nuke is
looking for.
Hope that helps.
-Jeremy
On Mar 31, 2014, at 1:23 PM, Dorian Fevrier
<[email protected]> wrote:
Hi (again for some of you!) Nuke community!
I try to find the faster EXR formats for the exr Nuke reader in a case of a
full CG compositing and it's quite hard to get valid informations.
Could someone confirm me this:
One channel per file (RGBA)
Compression: Imf::NO_COMPRESSION
Order: Imf::INCREASING_Y (I've never been sure about this)
A dataWindow well defined.
Have I miss something?
Big thanks in advance and Hello again!
Regards,
Dorian
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
