[FFmpeg-user] bounty: fix this bug #437 $150

Phil Rhodes phil_rhodes at rocketmail.com
Wed Nov 23 23:04:53 CET 2011

On Wed, 23 Nov 2011 18:42:42 -0000, Roger Pack <rogerdpack2 at gmail.com>  

>> It's not really a bug, it's an unknowable fact about the input and  
>> output
>> video. The only way to fix it is to ask the user what they think the  
>> input
>> is and what the output should be.
> I suppose it just seems odd that, given a "known" full swing RGB
> bitmap, ffplay is unable to display it in full swing (since it has
> control of the conversions from beginning to end).

Yes. Thomas Worth knows more about this than I do, because he spent some  
time characterising ffmpeg's exact behaviour and writing his way around it  
using the source code. The features are in there to solve the problem,  
they're just not exposed to the user. I suspect this is another case of  
some software engineers assuming that anything they don't understand isn't  


More information about the ffmpeg-user mailing list