Re: [FFmpeg-user] For discussion: A better video notation.

On 02/04/2021 06:50 PM, Mark Filipak (ffmpeg) wrote: For discussion: A better video notation. 24PPS@23.9FPS (aka "24p") Cinema (i.e. 24PPS) mastered at 23.9FPS, 0.1% slow. 24PPS@23.9FPS (aka "30i") Soft-telecined: cinema with 29.9FPS metadata, 0.1% slow. 24PPS@25FPS  

Re: [FFmpeg-user] For discussion: A better video notation.

On 02/05/2021 12:10 AM, Carl Zwanzig wrote: On 2/4/2021 7:54 PM, Jim DeLaHunt wrote: I'll point out that that this notation seems to have an obfuscation of its own, when it says "23.9". Yes, that should be 23.97 (or .98?) if not the fraction; same for 29.97 or the fraction. Well, if the

Re: [FFmpeg-user] For discussion: A better video notation.

On 02/04/2021 10:54 PM, Jim DeLaHunt wrote: Thanks, Jim, On 2021-02-04 15:50, Mark Filipak (ffmpeg) wrote: For discussion: A better video notation. 24PPS@23.9FPS (aka "24p") Cinema (i.e. 24PPS) mastered at 23.9FPS, 0.1% slow. 24PPS@23.9FPS (aka "30i") Soft-telecined: cinema

Re: [FFmpeg-user] For discussion: A better video notation.

On 2/4/2021 7:54 PM, Jim DeLaHunt wrote: I'll point out that that this notation seems to have an obfuscation of its own, when it says "23.9". Yes, that should be 23.97 (or .98?) if not the fraction; same for 29.97 or the fraction. Later, z! ___

Re: [FFmpeg-user] For discussion: A better video notation.

On 2021-02-04 15:50, Mark Filipak (ffmpeg) wrote: For discussion: A better video notation. 24PPS@23.9FPS (aka "24p") Cinema (i.e. 24PPS) mastered at 23.9FPS, 0.1% slow. 24PPS@23.9FPS (aka "30i") Soft-telecined: cinema with 29.9FPS metadata, 0.1% slow. The notation codes for

Re: [FFmpeg-user] For discussion: A better video notation.

On 02/04/2021 07:20 PM, Carl Zwanzig wrote: On 2/4/2021 3:50 PM, Mark Filipak (ffmpeg) wrote: For discussion: A better video notation. Well, none of them go with the industry standards like 1920p30 or 480i29.97... Those, more standard notations are where I began. But in order to

Re: [FFmpeg-user] For discussion: A better video notation.

On 2/4/2021 3:50 PM, Mark Filipak (ffmpeg) wrote: For discussion: A better video notation. Well, none of them go with the industry standards like 1920p30 or 480i29.97. Consider that the main notation expresses resolution and frame/field rate of the encoded video itself and isn't concerned

[FFmpeg-user] For discussion: A better video notation.

For discussion: A better video notation. 24PPS@23.9FPS (aka "24p") Cinema (i.e. 24PPS) mastered at 23.9FPS, 0.1% slow. 24PPS@23.9FPS (aka "30i") Soft-telecined: cinema with 29.9FPS metadata, 0.1% slow. 24PPS@25FPS (aka "25i") Cinema with 25FPS metadata, 4% fast.

Re: [FFmpeg-user] Out of virtual memory (swap, I assume) = telecine+setpts combination

On Thu, Feb 4, 2021 at 11:02 PM Mark Filipak (ffmpeg) wrote: > On 02/04/2021 04:50 PM, Paul B Mahol wrote: > > Well, perhaps your command queues too much frame and that is bad. > > Perhaps? > > Perhaps not. I just checked telecine+setpts with your arguments and it leaks 0 bytes. > ffmpeg -i

Re: [FFmpeg-user] Out of virtual memory (swap, I assume) = telecine+setpts combination

On 02/04/2021 04:50 PM, Paul B Mahol wrote: Well, perhaps your command queues too much frame and that is bad. Perhaps? ffmpeg -i source.mkv -map 0 -filter_complex "telecine, setpts=N*1001/3/TB" -codec:v libx265 -x265-params crf=20:qcomp=0.60 -codec:a copy -codec:s copy "with both

Re: [FFmpeg-user] Out of virtual memory (swap, I assume) = telecine+setpts combination

Well, perhaps your command queues too much frame and that is bad. On Thu, Feb 4, 2021 at 10:34 PM Mark Filipak (ffmpeg) wrote: > On 02/03/2021 12:23 AM, Carl Zwanzig wrote: > > On 2/2/2021 2:52 PM, Mark Filipak (ffmpeg) wrote: > >> If that's true, what's eating the swap? Transcoding parts 1, 2,

Re: [FFmpeg-user] Out of virtual memory (swap, I assume) = telecine+setpts combination

On 02/03/2021 12:23 AM, Carl Zwanzig wrote: On 2/2/2021 2:52 PM, Mark Filipak (ffmpeg) wrote: If that's true, what's eating the swap? Transcoding parts 1, 2, 3, & 4 all succeeded when running concurrently. Transcoding part 5 fails, even when ffmpeg is the only app running. Out of curiosity,

[FFmpeg-user] OT, Noise, am I'm loosing it? (rant)

Recently watched ‘Win it all’ on Netflix. (Ok, you can flame me for bad taste, but that would be beside the point.) Now, in this flick, a ‘Netflix original’, noise on close to every interior shot is beyond reasonable. Now, Netflix has very high demands on delivery. How could this happen? Why did

Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]

Am 04.02.21 um 09:12 schrieb Korn Moffle: unsubscribe me idiot - how dumb are you when you believe writing that into a random answer with a random subject could work? > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org >

Re: [FFmpeg-user] concat a/v desync (only in MPC-HC)

I was wrong. `cat` and "concat:" help to solve the problem with real world videos. Looks like ffmpeg can detect sudden resets of the PTS. I mean, if we concatenate two .ts files and both have STARTPTS=0 then ffmpeg will begin adding a certain number to the PTS in the remaining frames. This

Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]

unsubscribe me Sent from Outlook From: ffmpeg-user on behalf of Phil Rhodes via ffmpeg-user Sent: Tuesday, February 2, 2021 12:12 AM To: ffmpeg-user@ffmpeg.org Cc: Phil Rhodes Subject: Re: [FFmpeg-user] "instead of complaining,