[FFmpeg-trac] #7163(avcodec:closed): 12-bit ProRes not supported

[FFmpeg]

#7163: 12-bit ProRes not supported
---------------------------------------+-----------------------------------
             Reporter:  spookybathtub  |                    Owner:
                 Type:  enhancement    |                   Status:  closed
             Priority:  wish           |                Component:  avcodec
              Version:  git-master     |               Resolution:  fixed
             Keywords:  prores         |               Blocked By:
             Blocking:                 |  Reproduced by developer:  0
Analyzed by developer:  0              |
---------------------------------------+-----------------------------------

Comment (by pdr0):

 Replying to [comment:22 spookybathtub]:
 > I'm not disputing that this file is 422.  I'm just saying it is
 theoretically possible for the 422 codec to contain 12-bit precision.
 From the [https://www.apple.com/final-cut-
 pro/docs/Apple_ProRes_White_Paper.pdf whitepaper]:
 > >Like Apple ProRes 4444 XQ and Apple ProRes 4444, all Apple ProRes 422
 codecs can in fact accept image samples even greater than 10 bits,
 although such high bit depths are rarely found among 4:2:2 or 4:2:0 video
 sources.



 Good point, but it's pretty ambiguous about "containing" -


 {{{
 Apple ProRes 422 codecs support up to 10-bit image sources...

 Like Apple ProRes 4444 XQ and Apple ProRes 4444, all
 Apple ProRes 422 codecs can in fact accept image samples even greater
 than 10 bits, although such high bit depths are rarely found among 4:2:2
 or 4:2:0 video sources.
 }}}


 Does "can accept" indicate "supported" at that bit depth ? Or does that
 mean if you feed it 16bit YUV, it decodes from the native prores decoder
 at 16bits or 10bit ?  eg. 8bit mpeg2 "can accept" 10bit data too, it just
 gets truncated to 8bits. To me, "support up to 10-bit" is critical
 phrasing. "up to" defines an upper limit

 Have you ever seen authentic 12bit Prores 422 HQ?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7163#comment:23>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker