On 10/04/2017 22:31, Vittorio Giovara wrote: > On Mon, Apr 10, 2017 at 1:43 PM, James Almer <jamr...@gmail.com> wrote: >>> Even so, what's the user going to do with knowing the fact that >>> the video contains spherical metadata it can't parse correctly/fully >>> support? So, I'm hesitant to add a new type for this uncertain >>> behaviour, wouldn't you agree? >> >> No, because that's the whole point of avprobe, the dump.c code, and >> other tools using the libraries: Informing the user of the contents >> and characteristics of their files. >> avconv and similar tools are what attempt to do something with them, >> and for unknown projections they would do nothing. > > I don't know, I feel like we're discussing about what kind of noise a > tree would do falling in an empty forest :) > I guess we should wait for other people to chime in, and solve this knot >
I'm happy as long the function does return an AVERROR on failure or something easy to match, if I recall correctly Anton seems to be more for not reporting possibly misleading data when it got discussed on IRC. (Anton please confirm :)) I'd go with your initial patch amended to return AVERROR(ENOSYS) at least for now. lu _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
