Brad Hards

You can also use the `--benchmark` option.

> For me color related just implementing avifenc-like `-d` and `-y` is enough. > ``` > -d,--depth D : Output depth [8,10,12]. (JPEG/PNG only; For y4m or stdin, depth is...

> Would like to add something like `-p depth=10` if possible, thanks. We already have `--bit-depth` / `-b`. So what (exactly) do you need that those do not do? I...

Possibly you could propose the changes you think are appropriate (either in place of, or along side, the existing instructions) as a Pull Request. That would ensure your needs are...

Another option would be to put the version into the spec. So if you want to update to ISO BMFF v8, the spec name would be isobmff_v8. The reason for...

Concur. However there are cases where it does reference a dated version (e.g. ISO/IEC 15444-16:2021 references ISO/IEC 23008-12:2017, not 2022; and 23008-12:2017 references 14496-12:2015).

> Also, multiband rasters in OGCAPI maps/tiles/coverages (by "multiband" I mean non-RGB and non-RGBA; either single-band elevation, or two-band slope, or 12-band Sentinel multispectral, etc etc). Including the questions: does...

Possibly we could just do something like: ``` diff --git a/src/specs/heif/heif.cpp b/src/specs/heif/heif.cpp index 4ccda2f..9471f43 100644 --- a/src/specs/heif/heif.cpp +++ b/src/specs/heif/heif.cpp @@ -1093,14 +1093,14 @@ static const SpecDesc specHeif = { if(!strcmp(sym.name,...

I agree E does not mention heif at all (and I have the final ed 2, 2022 version). It was the "any coding format" that made me think `.heif` was...

My suggestion is at #87.