[FFmpeg-trac] #9702(undetermined:open): Regression of vf_zscale in d0aefc37069e1602aa8cc5568e87f4a5e52fb4f3

[FFmpeg]

#9702: Regression of vf_zscale in d0aefc37069e1602aa8cc5568e87f4a5e52fb4f3
-------------------------------------+-------------------------------------
             Reporter:  Ulrik        |                    Owner:  (none)
  Mikaelsson                         |
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by Balling):

 * status:  new => open

Comment:

 You did not tag the output as full range. Like '''what'''??? That is done
 with -color_range pc and makes a difference in color, rather big one.
 Now... Any normal player (not ffmpeg) will think that untagged hd file is
 bt709. So you forgot to tag it:   -colorspace bt470bg, you also forgot
 -color_primaries smpte170m -color_trc bt709. So the end command is:

 ffmpeg.exe -y -f lavfi -i yuvtestsrc=duration=5:size=1280x720:rate=15 -vf
 'zscale=range=full:primaries=240m:matrix=470bg:transfer=601:rangein=full:primariesin=709:transferin=709'
 -color_range pc  -colorspace bt470bg -color_primaries smpte170m -color_trc
 bt709 -color_range pc -preset veryfast out11212121111.mp4

 Okay, that is nice. Next now that we fixed all "undefined behaviour"...

 Now lets try older build: with the command above it just prints

 >code 3074: no path between colorspaces

 So it cannot be tested.


 '''Now, the bug appears to be that in latest ffmepg matrixin=709 does not
 matter, it is not being accounted for. It is always the same.
 '''
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9702#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker