[FFmpeg-devel] [PATCH 2/4] lavd: add device capabilities API

Michael Niedermayer michaelni at gmx.at
Sun Feb 16 18:45:14 CET 2014

On Sun, Feb 16, 2014 at 01:28:03PM +0100, Lukasz Marek wrote:
> >>This version still has one open issue: how does it express a limited set of
> >>frame sizes. For example, if a webcam supports exactly 640×480 and 320×240.
> >>Does it return { 320, 640 } for the width and { 240, 480 } for the height?
> >>Is the application supposed to try each width in turn and query the
> >>corresponding range for height? It works, although it is a bit cumbersome,
> >>but it is not intuitive: maybe add a comment, or do it like that in the
> >>examples.
> >
> >maybe AV_OPT_TYPE_IMAGE_SIZE, should be used
> Can AV_OPT_TYPE_IMAGE_SIZE be represented in AVOptionRange?
> I'm asking because I'm willing to change that, but not sure it is
> doable without changing AVOptionRange struct.

it was certainly intended to be representable
see for example opt_list()

and of course things can be done differently if needed


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The greatest way to live with honor in this world is to be what we pretend
to be. -- Socrates
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140216/9f3ea60c/attachment.asc>

More information about the ffmpeg-devel mailing list