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
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
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,
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,
