| commit | b5aaec5d3e9ce2c44525e1653817aaf7f34706b2 | [log] [tgz] |
|---|---|---|
| author | Alexandre Courbot <acourbot@chromium.org> | Mon Jul 31 21:49:50 2023 +0900 |
| committer | Alexandre Courbot <acourbot@chromium.org> | Tue Aug 01 15:17:48 2023 +0900 |
| tree | 2eef43c51b6253676d0432911287cb8a835d5f0b | |
| parent | 62ea24e8c90564694af2e226c79a100d6694ec71 [diff] |
codec/h264: reference SPS from PPS Add a direct reference to the SPS from the PPS. This removes the need to run a lookup that can theoretically fail in the decoder.
A lightweight, simple, low-dependency, and hopefully safe crate for hardware-accelerated video decoding and encoding on Linux.
It is developed for use in ChromeOS (particularly crosvm), but has no dependency to ChromeOS and should be usable anywhere.
This crate is still under heavy development and is not recommended for use yet.
The ccdec example program can decode an encoded stream and write the decoded frames to a file. As such it can be used for testing purposes.
$ cargo build --examples
$ ./target/debug/examples/ccdec --help
Usage: ccdec <input> [--output <output>] --input-format <input-format> [--output-format <output-format>] [--synchronous] [--compute-md5 <compute-md5>]
Simple player using cros-codecs
Positional Arguments:
input input file
Options:
--output output file to write the decoded frames to
--input-format input format to decode from.
--output-format pixel format to decode into. Default: i420
--synchronous whether to decode frames synchronously
--compute-md5 whether to display the MD5 of the decoded stream, and at
which granularity (stream or frame)
--help display usage information
Fluster can be used for testing, using the ccdec example program described above. This branch contains support for cros-codecs testing. Just make sure the ccdec binary is in your PATH, and run Fluster using one of the ccdec decoders, e.g.
$ python fluster.py run -d ccdec-H.264 -ts JVT-AVC_V1