[FFmpeg-trac] #10431(avfilter:new): Bug in lut3d.c

FFmpeg trac at avcodec.org
Fri Jun 23 09:58:41 EEST 2023


#10431: Bug in lut3d.c
--------------------------------------+------------------------------------
             Reporter:  Michael Koch  |                    Owner:  (none)
                 Type:  defect        |                   Status:  new
             Priority:  normal        |                Component:  avfilter
              Version:  git-master    |               Resolution:
             Keywords:                |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+------------------------------------
Comment (by Michael Koch):

 Replying to [comment:1 Elon Musk]:
 > Please cite specifications to make this valid ticket.

 I had a link to the specification, but it's dead now.
 Here are a few examples where the min and max values are set to 0 and 1,
 which are the default values:
 https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=40284

 By the way, in the above link is also described that 1D- and 3D-LUTs can
 be specified in the same *.cube file, and in this case the 1D LUT is
 applied before the 3D LUT. Is this feature implemented in FFmpeg?

 It seems logical to me that min and max can also be set to other values
 than 0 and 1. Otherwise the LUT_1D_INPUT_RANGE option is useless.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10431#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list