3 ms·
Where this might get tricky is if you seriously want to support non-destructive editing as well, because in that case any filter that can be applied in non-dest
by iggldiggl 6y ago
Where this might get tricky is if you seriously want to support non-destructive editing as well, because in that case any filter that can be applied in non-destructive mode effectively needs to become part of the file format specification, too.
- wongarsu 6y agoYou could store filters generic enough that any software can skip over filters it doesn't recognize (e.g. you store filter type uuid, filter data length, then arbitrary filter parameters), have some open registry where you can get official filter uuids in return for an example implementation. Of course not everyone will register every filter, so the format should probably store the image once unfiltered and once with all filter applied, that way if a program doesn't recognize or implement some filter it can still fall back to the destructively filtered version. But of course that increases file size, which may or may not be a concern.