Hi,
Ola Mogstad wrote:
[...]
>> You are probably using an outdated version of ffmpeg (I do not see these
>> warnings when compiling my programs with a recent ffmpeg, and the line
>> numbers you quote do not seem to match the current avcodec.h file).
>
> I have now checked out the latest SVN and compiled my program again and
> I get the same warning. Checking avcodec.h the warnings indeed make
> sense (note that I am compiling with -Wall):
>
> 2316: typedef struct ImgReSampleContext ImgReSampleContext
> attribute_deprecated;
>
> 2337: attribute_deprecated void img_resample(struct
> ImgReSampleContext *s, ...
Note that the line numbers here do not match the ones you previously
posted...
Anyway, I am not seeing those warnings when compiling ffmpeg, nor when
compiling my programs using libavcodec... Maybe they are compiler-dependent?
> Additionally, after checking out the latest svn I get this error when
> compiling my application:
>
> avcodec.h:2933: error: ‘av_malloc_attrib’ does not name a type
This is very strange: av_malloc_attrib is defined in libavutil/mem.h...
I suspect you have some confusion in your include path, and the wrong
headers are included?
[...]
> So, I'm a bit confused. I am using the most recent checkout yet I'm
> getting warnings that you don't see. And again, if I compile with system
> headers (i.e. #include <ffmpeg/avcodec.h> instead of my own #include
> "libav/avcodec.h", etc) my application gets no warnings and output shows
> no wmv2 errors.
See above: maybe your headers and libraries do not match, or there is
some kind of similar problem.
>> This is not surprising: system headers have nothing to do with libavcodec...
>
> What do you mean? By system headers I mean the ffmpeg headers that are
> located in /usr/include/ffmpeg/.
Those are not system headers. Those are ffmpeg headers coming from some
kind of previous installation.
>
>> This surely cannot be related with the ImgReSampleContext warning:
>> you have to
>> 1) Update to current svn
>> 2) Reproduce the problem with the ffmpeg executable
>> 3) Submit a proper bug report.
>
> 1) Done
> 2) How would I do that? ffmpeg seems to compile and run just fine.
So, the problem is not in ffmpeg, or in the library version.
There should be something in your own code (or in your own make
system) which creates the problems.
If the problems cannot be reproduced with ffmpeg, then you can
use it as a comparison for understanding what's wrong in your
code or build system.
>> Setting random values in extradata is never a good idea ;-)
>
> I agree :) I tried removing them and everything fails. As video decodes
> perfectly with the same extradata and system headers, I wouldn't think
> they could be the problem..?
I do not know about wmv2, but extradata generally depend on the
video stream you are playing... So, by hardcoding some fixed extradata
in your code you risk to be able to properly decode only one specific
video stream.
Luca
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
