Depending on the input and/or filters, you sometime have an input or
output pixel format like rgb48le(12 bpc). Unfortunately, most often,
the 12 bpc information is ignored or stripped. This patchset modify
some such cases, at the cost of increasing risks as patches go.
0001 is an actual bugfix to
Hi,
2014-08-20 10:10 GMT+02:00 Christophe Gisquet christophe.gisq...@gmail.com:
One may argue that a proper solution is to reduce as often as possible
references to bits_per_raw_sample and, instead, always use the
colorspace information and to introduce new colorspaces as needed.
I'd prefer
On Wed, Aug 20, 2014 at 10:16:25AM +0200, Christophe Gisquet wrote:
Hi,
2014-08-20 10:10 GMT+02:00 Christophe Gisquet christophe.gisq...@gmail.com:
One may argue that a proper solution is to reduce as often as possible
references to bits_per_raw_sample and, instead, always use the
Hi,
2014-08-20 12:19 GMT+02:00 Michael Niedermayer michae...@gmx.at:
iam happy with either, just please dont do and post both solutions
as then i cannot apply either as i have to expect libav to apply
the other causing conflicts
To summarize without aggravating anyone: I don't think I can
Christophe Gisquet christophe.gisquet at gmail.com writes:
Depending on the input and/or filters, you sometime
have an input or output pixel format like rgb48le(12
bpc). Unfortunately, most often, the 12 bpc
information is ignored or stripped.
Could you explain what command line you are
Hi,
2014-08-20 20:26 GMT+02:00 Carl Eugen Hoyos ceho...@ag.or.at:
Christophe Gisquet christophe.gisquet at gmail.com writes:
Depending on the input and/or filters, you sometime
have an input or output pixel format like rgb48le(12
bpc). Unfortunately, most often, the 12 bpc
information is
