[FFmpeg-trac] #278(undetermined:open): 0.7-rc1: strange colors with x11grab

FFmpeg trac at avcodec.org
Mon Jun 13 02:03:47 CEST 2011


#278: 0.7-rc1: strange colors with x11grab
------------------------+---------------------------
Reporter:  nixscripter  |       Owner:
    Type:  defect       |      Status:  open
Priority:  normal       |   Component:  undetermined
 Version:  0.7-rc1      |  Resolution:
Keywords:               |  Blocked By:
Blocking:               |  Reproduced:  0
Analyzed:  0            |
------------------------+---------------------------

Comment (by nixscripter):

 I think I have it, but I'm not positive. When I tried it at first, I got
 this error:

 $ git bisect start 075933a0687974fca74d6d4ac388d24766d8dc78
 e8876902a9021ec185ca785653067dd34f24c5ce
 Switched to branch 'master'
 Some good revs are not ancestor of the bad rev.
 git bisect cannot work properly in this case.
 Maybe you mistake good and bad revs?

 So, I decided to reverse it: you want to know where the bug was fixed --
 which is the same thing as were the "error regressed", in a sense.

 When I switched them around -- marked the good ones bad, and bad ones good
 -- I got this:

 d85e18e6e342bf58f8e13a95f601082e5d70803a is the first bad commit
 commit d85e18e6e342bf58f8e13a95f601082e5d70803a
 Author: Michael Niedermayer <michaelni at gmx.at>
 Date:   Sat Apr 2 20:26:39 2011 +0200

     yadif: Fix assert() failure

     Signed-off-by: Anton Khirnov <anton at khirnov.net>

 :040000 040000 1aa9b67a74cf716a11fc6d6ba1d1b93e79dddb1c
 d4ba44f572108592e75ef66c050c400da9ff6d5e M      libavfilter

 I don't know if that is right or not.

-- 
Ticket URL: <http://avcodec.org/trac/ffmpeg/ticket/278#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list