2019-03-08 23:48 GMT+01:00, Ulf Zibis :
> I do some experiences with 16 bit input and I discover a colour problem
> (see attached screenshot).
> The input image is from https://samples.ffmpeg.org/image-samples/
>
> Here is what I did:
> $ ./ffmpeg -i debug/flower-separated-contig-16.tif
This
Am 12.03.19 um 05:45 schrieb Gyan:
>
> No, in here:
>
> static const AVFilterPad fillborders_inputs[] = {
> {
> .name = "default",
> .type = AVMEDIA_TYPE_VIDEO,
> .config_props = config_input,
> .filter_frame = filter_frame,
>
On 12-03-2019 01:04 AM, Ulf Zibis wrote:
Am 11.03.19 um 20:27 schrieb Paul B Mahol:
On 3/11/19, Ulf Zibis wrote:
Am 09.03.19 um 09:39 schrieb Paul B Mahol:
On 3/9/19, Ulf Zibis wrote:
Another question is, why the fillborders doesn't check if the input is
writable, as suggested in
Am 11.03.19 um 20:43 schrieb Carl Eugen Hoyos:
> Our jpeg encoder only supports 8-bit yuv
Ok, that's the reason, thanks.
> No need to post Mediainfo output, all necessary information
> is in the FFmpeg console output.
Maybe for you. ;-)
For me it is not obvious. I guess you mean the info could
2019-03-11 20:31 GMT+01:00, Ulf Zibis :
>
> Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos:
>> 2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>>> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
2019-03-09 10:44 GMT+01:00, Ulf Zibis :
> Which format should I use with option -f ?
You should
Am 11.03.19 um 20:27 schrieb Paul B Mahol:
> On 3/11/19, Ulf Zibis wrote:
>> Am 09.03.19 um 09:39 schrieb Paul B Mahol:
>>> On 3/9/19, Ulf Zibis wrote:
Another question is, why the fillborders doesn't check if the input is
writable, as suggested in doc/writing_filters.txt.
>>>
Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos:
> 2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
>>> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
Which format should I use with option -f ?
>>> You should never need the option -f (except when reading
>>>
On 3/11/19, Ulf Zibis wrote:
>
> Am 09.03.19 um 09:39 schrieb Paul B Mahol:
>> On 3/9/19, Ulf Zibis wrote:
>>> Another question is, why the fillborders doesn't check if the input is
>>> writable, as suggested in doc/writing_filters.txt.
>>>
>> Because it request writtable frames.
>
> Hey Paul,
Am 09.03.19 um 09:39 schrieb Paul B Mahol:
> On 3/9/19, Ulf Zibis wrote:
>> Another question is, why the fillborders doesn't check if the input is
>> writable, as suggested in doc/writing_filters.txt.
>>
> Because it request writtable frames.
Hey Paul, how is this managed?
I don't see something
2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>
> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
>> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
>>> Which format should I use with option -f ?
>> You should never need the option -f (except when reading
>> raw g.729 and similar rare raw formats), what did you
Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
>> Which format should I use with option -f ?
> You should never need the option -f (except when reading
> raw g.729 and similar rare raw formats), what did you try?
When I use
$ ffmpeg -i 16.jpg -vf
2019-03-09 10:50 GMT+01:00, Ulf Zibis :
>
> Am 09.03.19 um 10:23 schrieb Michael Koch:
>>
>> Doesn't FFmpeg automatically convert 16-bit RGB to 16-bit YUV, if this
>> is required?
>
> -vf fillborders doesn't require YUV, so no automatic conversion happens.
You asked for yuv, 16 bit rgb is nothing
2019-03-09 10:44 GMT+01:00, Ulf Zibis :
>
> Am 09.03.19 um 10:10 schrieb Carl Eugen Hoyos:
>>
>> You can make such files with FFmpeg
> Which format should I use with option -f ?
You should never need the option -f (except when reading
raw g.729 and similar rare raw formats), what did you try?
>>
Am 09.03.19 um 10:23 schrieb Michael Koch:
>
> Doesn't FFmpeg automatically convert 16-bit RGB to 16-bit YUV, if this
> is required?
-vf fillborders doesn't require YUV, so no automatic conversion happens.
-Ulf
___
ffmpeg-user mailing list
Am 09.03.19 um 10:10 schrieb Carl Eugen Hoyos:
>
> You can make such files with FFmpeg
Which format should I use with option -f ?
> and links to two such files were provided in this thread.
The files from ticket #503 are only gray, and the JPEG's from ticket
#855 seem corrupted or at least not
Does gimp allow to create 16bit yuv files as requested?
No, it can create 16-bit PNG files with pixel formats RGB, GRAY, RGBA
and GRAYA.
Doesn't FFmpeg automatically convert 16-bit RGB to 16-bit YUV, if this
is required?
Michael
--
**
ASTRO
2019-03-09 9:26 GMT+01:00, Michael Koch :
>
>> It like to try some tweaks with fillborders filter, so I need some
>> 16-bit per plane images for testing. Can you help me with that?
>
> You can make 16-bit images with the latest version of GIMP.
You can make such files with FFmpeg and links to two
On 3/9/19, Ulf Zibis wrote:
>
> Am 09.03.19 um 00:18 schrieb Paul B Mahol:
>> On 3/8/19, Ulf Zibis wrote:
>>
>>
>> tiff is encoded with alpha, which is not initially available. Filter
>> is working fine.
> I do not really understand this argumentation, but this is not my main
> interest.
>
> It
It like to try some tweaks with fillborders filter, so I need some
16-bit per plane images for testing. Can you help me with that?
You can make 16-bit images with the latest version of GIMP. Use "export
as", then use *.png as filename, then select "16bpc RGB" as pixel
format, then click on
Am 09.03.19 um 00:18 schrieb Paul B Mahol:
> On 3/8/19, Ulf Zibis wrote:
>
>
> tiff is encoded with alpha, which is not initially available. Filter
> is working fine.
I do not really understand this argumentation, but this is not my main
interest.
It like to try some tweaks with fillborders
On 3/8/19, Ulf Zibis wrote:
> Hi,
>
> I do some experiences with 16 bit input and I discover a colour problem
> (see attached screenshot).
> The input image is from https://samples.ffmpeg.org/image-samples/
>
> Here is what I did:
> $ ./ffmpeg -i debug/flower-separated-contig-16.tif -vf
>
21 matches
Mail list logo
