[FFmpeg-trac] #2653(undetermined:new): problem with libopenjpeg with some option
FFmpeg
trac at avcodec.org
Sat Jun 8 22:44:15 CEST 2013
#2653: problem with libopenjpeg with some option
-------------------------------------+-------------------------------------
Reporter: sulio | Owner:
Type: enhancement | Status: new
Priority: wish | Component:
Version: git-master | undetermined
Keywords: libopenjpeg | Resolution:
j2k xyz | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Old description:
> Summary of the bug:
> How to reproduce:
> {{{
> % ffmpeg" -i sample.h264 -vf
> crop=iw:ih-2*138,scale=2048:858,lutrgb=gammaval(2.6) -pix_fmt yuv444p12le
> -vcodec libopenjpeg -profile 1 -cinema_mode 1 "decoded/test_%6d.j2c
>
> ffmpeg version N-53885-gf97e28e
> built on gcc windows 7 64 bit by Zeranoe
>
> The problem is:
> 1. I have no see any gamma change in picture. 26 is high value for gamma
> and thisd can be very visible.
> 2. libopenjpeg do not receive or do not execute the follow option
> "-profile 1" with above command line should be expected converting of
> h264 video to sequence of JPEG2000 images with digital cinema standard.
> testing jpeg2000 images after, show that they are NOT digital cinema
> compliant. My testing tools cannot say why but absolutely sure say that
> they are not digital cinema compliant. libopenjpeg itself used with
> another programs (for example image_to_j2c or OpenDCP do well conversion
> exactly on DCI specifications for jpeg2000 for digital cinema. I guess
> that avoptions are not sent corectly to openjpeg. For example "-profile"
> command are not specific for libopenjpeg, its not "private" command only
> for libopenjpeg and may be ffmpeg do not pass this option to libopenjpeg.
> Also explanation of AVoptions generally is ambiguous and is hard to
> understand how exactly are used such options. ffmpeg -h
> codecs=libopenjpeg do not do big thing due to lack of details. Also I do
> not understand who decide which pix_fmt should understand libopenjpeg,
> but original openjpeg understand xyz12le and in ffmpeg do not understand
> it,instead understand yuv444p12le this may be not so important because
> anyway xyz transformations is done before libopenjpeg encoding.
> 3. I cannot understand why xyz12le is only input format , its make more
> sense to be more output format.
> I attach an report file and you will see what I'm talking about. IF what
> is written in wiki is true then with this command we should have from
> some video file source,XYZ encoded,gammacorected jpeg2000 DCI compressed
> sequence of images, but for some reason its not happened.
New description:
Summary of the bug:
How to reproduce:
{{{
% ffmpeg" -i sample.h264 -vf
crop=iw:ih-2*138,scale=2048:858,lutrgb=gammaval(2.6) -pix_fmt yuv444p12le
-vcodec libopenjpeg -profile 1 -cinema_mode 1 "decoded/test_%6d.j2c
}}}
ffmpeg version N-53885-gf97e28e
built on gcc windows 7 64 bit by Zeranoe
The problem is:
1. I have no see any gamma change in picture. 26 is high value for gamma
and thisd can be very visible.
2. libopenjpeg do not receive or do not execute the follow option
"-profile 1" with above command line should be expected converting of h264
video to sequence of JPEG2000 images with digital cinema standard. testing
jpeg2000 images after, show that they are NOT digital cinema compliant. My
testing tools cannot say why but absolutely sure say that they are not
digital cinema compliant. libopenjpeg itself used with another programs
(for example image_to_j2c or OpenDCP do well conversion exactly on DCI
specifications for jpeg2000 for digital cinema. I guess that avoptions are
not sent corectly to openjpeg. For example "-profile" command are not
specific for libopenjpeg, its not "private" command only for libopenjpeg
and may be ffmpeg do not pass this option to libopenjpeg. Also explanation
of AVoptions generally is ambiguous and is hard to understand how exactly
are used such options. ffmpeg -h codecs=libopenjpeg do not do big thing
due to lack of details. Also I do not understand who decide which pix_fmt
should understand libopenjpeg, but original openjpeg understand xyz12le
and in ffmpeg do not understand it,instead understand yuv444p12le this may
be not so important because anyway xyz transformations is done before
libopenjpeg encoding.
3. I cannot understand why xyz12le is only input format , its make more
sense to be more output format.
I attach an report file and you will see what I'm talking about. IF what
is written in wiki is true then with this command we should have from some
video file source,XYZ encoded,gammacorected jpeg2000 DCI compressed
sequence of images, but for some reason its not happened.
--
Comment (by cehoyos):
Could you test if reencoding the sample rgb-bary-12bpc.preview.jpg from
ticket #1279 works?
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2653#comment:3>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list