This fixes an accidental transmute (found by @projectgus) from an &Input to a &Context,
which was only working accidentally by type layout coincidence.
Co-Authored-By: Angus Gratton <gus@projectgus.com>
Instead of silently passing possibly unset `time_base`s back into ffmpeg,
force users to explicitly handle (even if just by early panic) their absence.
BREAKING CHANGE: `time_base` and `set_time_base` functions now
return/accept Option<Rational> (±Into). `unwrap`/`expect` is a valid way
to surface this unwanted state early in user code.
For symmetry, `set_time_base` also allows unsetting by passing a `None`,
so all existing calls (with non-zero timebases) need to wrap the
argument in `Some`.
error[E0428]: the name `AV_PIX_FMT_YUV420P9` is defined multiple times
--> /wrkdirs/usr/ports/multimedia/av1an/work/Av1an-0.2.0/cargo-crates/ffmpeg-sys-next-4.4.0/src/avutil/pixfmt.rs:155:1
|
38 | pub const AV_PIX_FMT_YUV420P9: AVPixelFormat = AV_PIX_FMT_YUV420P9LE;
| --------------------------------------------------------------------- previous definition of the value `AV_PIX_FMT_YUV420P9` here
...
155 | pub const AV_PIX_FMT_YUV420P9: AVPixelFormat = AV_PIX_FMT_YUV420P9BE;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `AV_PIX_FMT_YUV420P9` redefined here
|
= note: `AV_PIX_FMT_YUV420P9` must be defined only once in the value namespace of this module
tilpner
Kornel
pkubaj
chrox
meh
Vivien Venuti
Christopher Brown