| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Guard AVIF decoding with enable_dav1d_decoderI think the code would be clearer if we add `enable_avif_decoder` and `ENABLE_AVIF_DECODER` and use them (instead of `enable_dav1d_decoder` and `ENABLE_DAV1D_DECODER`) with AVIF.
Would that work?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Guard AVIF decoding with enable_dav1d_decoderI think the code would be clearer if we add `enable_avif_decoder` and `ENABLE_AVIF_DECODER` and use them (instead of `enable_dav1d_decoder` and `ENABLE_DAV1D_DECODER`) with AVIF.
Would that work?
technically, yes. but we will still need the enable_dav1d_decoder flag to control whether or not dav1d is being built. so if we are to add a `enable_avif_decoder` flag, it will simply be an alias to `enable_dav1d_decoder`.
so it is simpler to just gate AVIF decoding on dav1d availability since there is no reason to disable avif when dav1d is available.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Guard AVIF decoding with enable_dav1d_decoder
The existing guards use enable_av1_decoder which may or may not
be dav1d depending on hardware AV1 support. Whereas AVIF decoding
is always done via dav1d and thus guarding it with enable_av1_decoder
is incorrect.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |