We Need A Standard Layered Image Format

Re:We Need A Standard Layered Image Format by jjcm on Wednesday May 01, 2013 @03:30AM (#5636907)

Image formats have come a long way. I think the author wants an image format that can replace .psd in a sensible way. TIFF sadly cannot do that. While it can contain layered raster data, it lacks a lot of other capabilities. The author explicitly mentions vector layers, but if you want parity with .PSD you're looking at also having to support adjustment layers (hue/curves/levels/etc), blending modes, opacity/fill, raster masks, clipping masks, vector masks, locks, annotations, guides, grids, gradients, tags, text, comps, channels, and countless other things I can't even think to list (I wont even dive into smart objects). Keep in mind that's just the layer data, there's tons of other metadata in the format as well. It is a behemoth of a file format, and the years of backwards compatibility inside of it have multiplied that complexity to levels of insanity. I have .psd files that if I enable backwards compatibility when saving will increase the file size by half a gig. Granted those are enormous source files to begin with, but with higher def screens on the horizon file sizes are increasing dramatically. Having something more sensible than .PSD is something we're going to have to deal with sooner or later.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by virtualritz on Wednesday May 01, 2013 @08:36AM (#5637511)

Anything that TIFF lacks can be added using custom tags. All people need to do is to agree on names and types for these custom tags that store the new information. This means any old app will still be able to work with such TIFF files and just ignore the information it doesn't understand. So the problem isn't solved but the answer is not coming up with yet-another-file-format.

A good example of extending TIFF with tags is Pixar's PhotoRealistic RenderMan. It uses a TIFF flavor as a base for its mip-mapped textures. Such a TIFF contains a pyramid of layers of the image at different pre-downsampled resolutions and a bunch of custom tags, the renderer interprets when it reads such a file.

However, I can use 'Open As...' in Photoshop and open this as a TIFF. I will simply get the highest resolution layer from the file. That's a simple and battle-proven example of why TIFF is indeed a great answer to the problem.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by twelvechairs on Wednesday May 01, 2013 @07:15AM (#5637304)

To provide a better answer than the GP:

.PDF .SVG .DXF/.DWG

All of these are open standards or basically open standards which are already widely implemented and allow the use cases mentioned (vector and raster combinations and layers) and also many of the ones you have thrown in.

Of course the real problem is that they are far too complex for most people's needs so why bother.

People really don't really often need to share the 'layers' of images combined with vector data (usually you use the layers yourself then just share the final product - a flattened JPG or similar), however if they do the above formats are there for them.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by kruhft on Wednesday May 01, 2013 @04:37AM (#5637029)

.XCF

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by walid on Wednesday May 01, 2013 @07:03AM (#5637285)

Not really that is still as good/bad as .PSD is because of the nature of what the file is used for. They are both primarily containers for unfinished works and are designed to hold a lot of detail without so much regard for size and portability. Of course the .XCF format is open but not good enough for a simple viewer or even a web browser. Some file format based on SQLite will probably be more viable as a cross platform image format that is extensible beyond any one software developer limiting it. Kind of like HTML.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by kruhft on Wednesday May 01, 2013 @07:19AM (#5637314)

It meets all of the requirements of the parent post I replied to, plus it even has a pretty decent open source editor. It's internal structure may not be in SQLite format, but it is an extensible tag based chunk format. You shouldn't dismiss it so easily.

[ Parent | on HN ]