Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-24 Thread Carl Eugen Hoyos
Christophe Gisquet gmail.com> writes: > The sanest thing to do (and that you are hinting at) > is to just drop it. I thought that 2/5 is not correct (but wasn't sure). Patch sent, Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-24 Thread Christophe Gisquet
Hi, 2014-08-24 3:00 GMT+02:00 Carl Eugen Hoyos : > If you believe this is a real-world issue, is > can easily be fixed afaict. Let's summarize this patchset here: opportunities of doing lossless processing are missed. But no user (as in real-world) actually has expressed concern or interest beyon

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-23 Thread Carl Eugen Hoyos
Christophe Gisquet gmail.com> writes: > 2014-08-20 20:26 GMT+02:00 Carl Eugen Hoyos: > > Christophe Gisquet 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 > >> inform

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Christophe Gisquet
Hi, 2014-08-20 20:26 GMT+02:00 Carl Eugen Hoyos : > Christophe Gisquet 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. > > Co

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Carl Eugen Hoyos
Christophe Gisquet 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 trying to fix?

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Christophe Gisquet
Hi, 2014-08-20 12:19 GMT+02:00 Michael Niedermayer : > 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 manage both proje

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Michael Niedermayer
On Wed, Aug 20, 2014 at 10:16:25AM +0200, Christophe Gisquet wrote: > Hi, > > 2014-08-20 10:10 GMT+02:00 Christophe Gisquet : > > 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

Re: [FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Christophe Gisquet
Hi, 2014-08-20 10:10 GMT+02:00 Christophe Gisquet : > 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 this solution although it's

[FFmpeg-devel] [PATCH 0/5] RGB48/64 with bits_per_raw_sample

2014-08-20 Thread Christophe Gisquet
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 t