Krita use in VFX

[Moritz Moeller]

Cyrille Berger wrote:

>> Lastly I found that certain very common TIFF flavours (common in my
>> industry) make Krita crash when one tries to open them.
> I guess that is some tiff with the weird colorspaces LogL and LogLuv ? But it 
> shouldn't crash even if it fails.

No, it's a 32bit float single channel tiff (grayscale, if you want) 
containing multiple layers for mip-mapping:

TextureInfo: file "displacement.tif"
Type:   plain texture
Version:       3 (4)
Maxchan:       0 (8)
Channels:      1
Minrpow:       0 (0)
Maxrpow:       0 (14)
Resolutions: [1 x 1] to [2048 x 2048]
Tile size:  4096 (4096)
Total of 5466 tiles.
s mode:    CLAMP
t mode:    CLAMP
Channel datatype: TX_FLOAT

     S:                     1 1
     S: 0 1 2 3 4 5 6 7 8 9 0 1
T  0:  *
T  1:    *
T  2:      *
T  3:        *
T  4:          *
T  5:            *
T  6:              *
T  7:                *
T  8:                  *
T  9:                    *
T 10:                      *
T 11:                        *

No shadow matrices.


The info displayed is partly Pixar TIFF tags that are used to help a 3D
renderer treat such a file correctly for texture filtering etc.
I'll get a list of these tags, if you want to support them.

It would be really awesome if Krita did retain those (like e.g. the 
comment in an EXR).
No other application on the market (including commercial ones)
supports this. Cinepaint e.g. opens all mip-map levels but throws the
tags away on saving. Photoshop opens only the highest mip-map level and
throws all tags away on save too. Tags can also include 4x4 matrices for
shadow depth maps and the like.

If that information would be kept (and be editable, either directly
during working in Krita or even only during save -- the lame Photoshop
way of doing it), that would be a kick arse feature -- as simple as it
sounds.

Metadata that gets lost in applications treating it like 2nd class
citizens (where pixels are the 1st class), usually adds a major layer of
unnecessary complexity to a pipeline as the data as to be re-created
somehow.  I.e. in case of a TIFF texture that is turned into an ordinary
TIFF by stripping its metadata (and likely other stuff like mip-maps 
etc.), another app has to be called every time the image is edited to 
re-create the the metadata (and the mip-map levels etc.).

Worse, the metadata that was in the image in the 1st place must be
stored elsewhere before editing the image, so it can be re-created 
correctly afterwards...


Cheers,

Moritz