On 6/19/2016 4:52 PM, Thomas Mundt wrote:
> James Almer schrieb am So, 19.6.2016:
>> On 2/7/2016 8:39 PM, Thomas Mundt wrote:
>>> + at item deint
>>> +Specify which frames to deinterlace. Accept one of the following
>>> +values:
>>> +
>>> + at table @option
>>> + at item 0, all
>>> +Deinterlace
James Almer schrieb am So, 19.6.2016:
>On 2/7/2016 8:39 PM, Thomas Mundt wrote:
>> + at item deint
>> +Specify which frames to deinterlace. Accept one of the following
>> +values:
>> +
>> + at table @option
>> + at item 0, all
>> +Deinterlace all frames.
>> + at item 1, interlaced
>> +Only
On 2/7/2016 8:39 PM, Thomas Mundt wrote:
> +@item deint
> +Specify which frames to deinterlace. Accept one of the following
> +values:
> +
> +@table @option
> +@item 0, all
> +Deinterlace all frames.
> +@item 1, interlaced
> +Only deinterlace frames marked as interlaced.
> +@end table
> +
> +The
>>> Paul B Mahol schrieb am Mi, 17.2.2016:
> If nobody plans to comment on code I will apply this soon.
I´ve seen you applied it. Thanks.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On 2/16/16, Thomas Mundt wrote:
Paul B Mahol schrieb am Di, 16.2.2016:
> On 2/8/16, Thomas Mundt wrote:
>> Hendrik Leppkes schrieb am Mo, 8.2.2016:
How does the speed
>>> Paul B Mahol schrieb am Di, 16.2.2016:
On 2/8/16, Thomas Mundt wrote:
> Hendrik Leppkes schrieb am Mo, 8.2.2016:
>>> How does the speed compare to YADIF?
>>> Or in other words, is it usable in real-time, or
>>> Paul B Mahol schrieb am Di, 16.2.2016:On 2/8/16, Thomas
>>> Mundt wrote:
> Hendrik Leppkes schrieb am Mo, 8.2.2016:
>>> How does the speed compare to YADIF?
>>> Or in other words, is it usable in real-time, or
On 2/8/16, Thomas Mundt wrote:
Hendrik Leppkes schrieb am Mo, 8.2.2016:
>> How does the speed compare to YADIF?
>> Or in other words, is it usable in real-time, or rather designed for
>> offline processing?
>>
> YADIF is quicker, because
I forgot one information:
With yadif and w3fdif the temporal interpolation of the first and last field of
a source file tend to result in heavy artefacts at fast motions. Therefore
BobWeaver uses spatial cubic interpolation at first and last field.
That´s the filter_intra function.
I attached
On Mon, Feb 8, 2016 at 12:24 PM, Thomas Mundt
wrote:
> I forgot one information:
> With yadif and w3fdif the temporal interpolation of the first and last field
> of a source file tend to result in heavy artefacts at fast motions. Therefore
> BobWeaver uses
>>> Hendrik Leppkes schrieb am Mo, 8.2.2016:
> How does the speed compare to YADIF?
> Or in other words, is it usable in real-time, or rather designed for
> offline processing?
>
YADIF is quicker, because of its CPU optimizations. Without CPU optimizations
BobWeaver is
Hi,
last years I did many quality tests with commercial broadcast transcoder
software for SD/HD conversions.
Aside from few exeptions the weak point always was the deinterlacer. This was
even more visible with new OLED monitors.
Here artefacts from edge directed interpolation are much more
12 matches
Mail list logo