| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Those functions are only useful inside filters. It is better to not
support user filters until the API is more stable.
|
| | |
|
| |
|
|
| |
Signed-off-by: Mans Rullgard <mans@mansr.com>
|
| |
|
|
| |
Signed-off-by: Mans Rullgard <mans@mansr.com>
|
| |
|
|
|
|
|
|
|
|
| |
the evaluated value converted to int.
That's required because -1 is evaluated as NAN, which converted back
to int looks like a random number, this is especially annoying when
debugging sources with undefined pos (as the video4linux2 device).
Signed-off-by: Janne Grunau <janne-ffmpeg@jannau.net>
|
| |
|
|
|
|
|
|
|
| |
eval API.
More grep-friendly and more consistent with the rest of the FFmpeg
API.
Originally committed as revision 25708 to svn://svn.ffmpeg.org/ffmpeg/trunk
|
|
|
Originally committed as revision 25655 to svn://svn.ffmpeg.org/ffmpeg/trunk
|
