| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Deprecate AVFilterBuffer/AVFilterBufferRef and everything related to it
and use AVFrame instead.
|
|
|
|
|
| |
Any alleged performance benefits gained from the split are purely
mythological and do not justify added code complexity.
|
| |
|
|
|
|
|
|
|
| |
A number of compilers, for example those from TI and IBM, choke on
these initialisers. The current style is also quite ugly.
Signed-off-by: Mans Rullgard <mans@mansr.com>
|
| |
|
|
|
|
| |
Signed-off-by: Martin Storsjö <martin@martin.st>
|
| |
|
| |
|
|
|
|
|
|
| |
It is not used in any filters currently and is inherently evil. If
passing binary data to filters is required in the future, it should be
done with some AVOptions-based system.
|
|
|
|
| |
It will allow adding new fields to it without ABI breaks.
|
|
|
|
|
| |
They are only useful inside filters and we don't allow user filters for
now.
|
|
|
|
|
| |
It is only useful inside filters and we don't allow user filters for
now.
|
| |
|
|
With the following additions:
* support to gray format
* support to yuva420p format
* parametric luma/chroma/alpha radius
* consistency check on the radius values, avoid crashes with invalid values
Signed-off-by: Anton Khirnov <anton@khirnov.net>
|