[FFmpeg-devel] [PATCH] mpeg4videodec: silence "Invalid and inefficient vfw-avi packed B frames detected" warning

Don Moir donmoir at comcast.net
Mon Sep 9 00:11:20 CEST 2013


----- Original Message ----- 
From: "Reimar Döffinger" <Reimar.Doeffinger at gmx.de>
To: "FFmpeg development discussions and patches" <ffmpeg-devel at ffmpeg.org>
Sent: Sunday, September 08, 2013 1:48 PM
Subject: Re: [FFmpeg-devel] [PATCH] mpeg4videodec: silence "Invalid and inefficient vfw-avi packed B frames detected" warning


> On Tue, Sep 03, 2013 at 04:35:35PM -0400, Don Moir wrote:
>> >Though for some reason this yet again seems to have degenerated into
>> >an IMO fairly pointless back and forth, with no attention
>> >or comments that would allow me to understand the issue and where I
>> >might have misunderstood the problem on the two suggestions I had
>>
>> Yes exactly. All I said was I would compile out the warnings if
>> good... just a switch mind you.. just a comment and not to generate
>> endless BS
>>
>> I expect the name calling to happen next :)

> Yes, because you don't give any useful explanation.
> It sounds like "me hate warnings, me crush warnings".
> Why would you want to _compile_ them out?

It should be enough to say that I have no need for the warnings... For me just wasteful calls even I don't do anything with them. 
There are some cases where I might have 10 videos playing at same time. Sometime you get alot of calls for warnings for even one 
video and the more videos the more calls. I don't like to waste even if somewhat trivial.

My original comment about this was passive, but if there was an easy way to flag them out I would.

At least some if not most of you, dwell on the details that may be useful for a developer and thats fine. I focus on the 
entertainment business where details like warnings are not important. Clearly most people watch video and listen to music for 
entertainment reasons. Maybe you forget. I don't know.

> But since it's not something that could be done trivially with a
> macro or so I'm not sure it's worth it, but it's interesting to
> consider.

Possibly not to trivial not sure. One thing is the fatals would have to be separated.


> I would imagine they add some size to the binary, so it would
> be interesting in some resource-constrained cases.
> But since it's not something that could be done trivially with a
> macro or so I'm not sure it's worth it, but it's interesting to
> consider. We do already have the NULL_IF_CONFIG_SMALL macro for
> example, but the av_log needs to handle NULL arguments.

Size is not much of an issue but size would be reduced.


>> >1) Making the message less technical and more helpful (for the users that
>> >care, why should users not caring about messages be relevant there?)
>> >2) Possibly adjusting the level, which also makes it easier for users
>> >to filter depending on what they care about, though at some level it's
>> >always going to be just a matter of opinion.
>>
>> Nobody I deal with cares about the warnings, would complain if I
>> offered, and they would not even be paying attention to it. They are
>> busy doing other things beside sitting on there ass... Normally
>> standing and keeping the show running without even looking at the
>> computer.. They control with a controller like Numark etc
>>
>> If they need to do it so bad they would do it offline with any tool they choose
>>
>> You have your opinion, I have mine
>
> WTF does this have to do with opinions? I am asking for what the
> actual _problems_ are and offering possible solutions.
> If your users don't care about warnings, then just don't show
> it to them, that's absolutely trivial to do (as far as I can tell,
> it seems to work fine in MPlayer at least), whether ffmpeg command-line
> or library or whatever is used. In what way would these users have any
> relevance whatsoever to how we word message and at what level we print
> them?

Yes correct and I do not display the warnings. If a there was a trivial way to compile them out I would do that.

> You tell me over and over your users don't care about warnings.
> I understood that the first time. On the other hand I _still_
> have no clue what you are trying to tell me or otherwise accomplish
> by repeating that over and over again, while not actually responding
> to the questions I do ask.

Not trying to tell you anything Reimar. Have a nice day.






More information about the ffmpeg-devel mailing list