cros-codecs
cros-codecs copied to clipboard
chromeos
Hi, it would be very useful to have access to codec parsers separately from the main crate. I'm wondering if splitting the crate in two would be worth considering?
Fixes #44 Partially address #49 Relies on chromeos/cros-libva#10
The only decoder interface that we support at the moment is the stateless one. For ease of use, clients should rather use a stateful API, close to the one proposed...
Right now using cros-codecs requires to know which decoding hardware is available and how to access it. More generic software however would benefit from the ability to discover the accelerated...
This issue is to track the development of the V4L2 stateless decoder support. Since we have all the codec parsers already in place, it should just consist of extending and...
Currently the H.264 parser will return a `Stream contain unsupported/unimplemented NALs` anyhow error if `num_slice_groups_minus1 > 0`. This prevents the `FM1_BT_B`, `FM1_FT_E` and `FM2_SVA_C` test vectors of Fluster's `JVT-AVC_V1` test...
We can expand the `CodedBitstreamBuffer` to accept another generic from the backend, a segment, which would require `AsRef` . In the case of the vaapi it would be mapped to...
This is a regression introduced by 39e3d000: ``` thread 'decoder::stateless::h264::vaapi::tests::test_25fps_block' panicked at 'called `Result::unwrap()` on an `Err` value: decoder error: decoder error: while syncing picture ``` The `sync()` call on...
