On 05/19/2020 05:50 PM, Carl Eugen Hoyos wrote:
Am Di., 19. Mai 2020 um 21:22 Uhr schrieb Mark Filipak
:
while "progressive" can theoretically be interlaced (or hard
telecined) it is very unlikely.
That statement seems contrary to the MPEG standard.
I have already explained to you that when
On 05/19/2020 05:50 PM, Carl Eugen Hoyos wrote:
Am Di., 19. Mai 2020 um 21:22 Uhr schrieb Mark Filipak
:
while "progressive" can theoretically be interlaced (or hard
telecined) it is very unlikely.
That statement seems contrary to the MPEG standard.
I have already explained to you that when
Am Di., 19. Mai 2020 um 21:22 Uhr schrieb Mark Filipak
:
> > while "progressive" can theoretically be interlaced (or hard
> > telecined) it is very unlikely.
>
> That statement seems contrary to the MPEG standard.
I have already explained to you that when we use term "interlaced",
this is not rel
On 05/19/2020 12:30 PM, Carl Eugen Hoyos wrote:
Am Di., 19. Mai 2020 um 17:51 Uhr schrieb Mark Filipak
:
Regarding why "smpte170m" & "progressive" & "top field first" and other
notations appear to be arguments to a supposed yuv420p() function,
well, you'll have to ask the developers.
There is
Am Di., 19. Mai 2020 um 17:51 Uhr schrieb Mark Filipak
:
> Regarding why "smpte170m" & "progressive" & "top field first" and other
> notations appear to be arguments to a supposed yuv420p() function,
> well, you'll have to ask the developers.
There is no such function, the encoding properties tha
On 05/19/2020 10:43 AM, Moritz Barsnick wrote:
On Tue, May 19, 2020 at 09:56:51 -0400, Mark Filipak wrote:
If ffmpeg uses "smpte170m" with "progressive" to denote hard
telecine, then I want to detelecine first.
I thought it was understood that "smpte170m" is a notation for a
colorspace or colo
On Tue, May 19, 2020 at 09:56:51 -0400, Mark Filipak wrote:
> If ffmpeg uses "smpte170m" with "progressive" to denote hard
> telecine, then I want to detelecine first.
I thought it was understood that "smpte170m" is a notation for a
colorspace or color encoding (in the widest sense), while "progre
On 05/19/2020 02:18 AM, Carl Eugen Hoyos wrote:
Am 19.05.2020 um 06:18 schrieb Mark Filipak
:
relying on 'progressive' versus 'smpte170m'
I don’t think this distinction makes any sense.
Carl Eugen
Why do you say that, Carl Eugen?
If ffmpeg defines "progressive" as a video that contains pi
> Am 19.05.2020 um 06:18 schrieb Mark Filipak
> :
>
> relying on 'progressive' versus 'smpte170m'
I don’t think this distinction makes any sense.
Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmp
On 05/18/2020 07:04 PM, Carl Eugen Hoyos wrote:
Am Di., 19. Mai 2020 um 00:29 Uhr schrieb Mark Filipak
:
... yuv420p(tv, progressive) ... 29.97 fps ...
... yuv420p(tv, smpte170m, top first) ... 29.97 fps ...
... yuv420p(tv, smpte170m, progressive) ... 29.97 fps ...
https://www.google.com/sear
On 05/18/2020 07:04 PM, Carl Eugen Hoyos wrote:
Am Di., 19. Mai 2020 um 00:29 Uhr schrieb Mark Filipak
:
... yuv420p(tv, progressive) ... 29.97 fps ...
... yuv420p(tv, smpte170m, top first) ... 29.97 fps ...
... yuv420p(tv, smpte170m, progressive) ... 29.97 fps ...
https://www.google.com/sear
Am Di., 19. Mai 2020 um 00:29 Uhr schrieb Mark Filipak
:
>
> ... yuv420p(tv, progressive) ... 29.97 fps ...
> ... yuv420p(tv, smpte170m, top first) ... 29.97 fps ...
> ... yuv420p(tv, smpte170m, progressive) ... 29.97 fps ...
https://www.google.com/search?q=SMPTE+170M
You did a lot to make me beli
... yuv420p(tv, progressive) ... 29.97 fps ...
... yuv420p(tv, smpte170m, top first) ... 29.97 fps ...
... yuv420p(tv, smpte170m, progressive) ... 29.97 fps ...
The top one appears to be soft telecined.
The middle on appears to be hard telecined.
What's the bottom one?
Thanks,
Mark.
--
COVID-19
13 matches
Mail list logo