Search options (Page 142 of 363)

I'm afraid nobody here knows the answer It's a dark ffmpeg magic behind the reencoding process.
Probably it's just a question of one missing ffmpeg option... and I have no idea which one is missing.

if you send the report via SVP probably it could reveal something

you can override settings from mpv64/mpv.conf from the standard mpv's conf location(s)

run it with --log-file=<some-writeable-path> and search for "ipc" in the log

[   0.019][v][ipc] Starting IPC master
[   0.020][v][ipc] Listening to IPC pipe.
...
[   0.092][v][ipc_0] Client connected

you'd better copy error text from the Events log

It changes only the "threads" option in ffmpeg.
I have no idea why it affects the file size

SVPcode (also SVPcast, mpv, VLC) can't handle correctly variable frame rate videos or videos with incorrect frame rate defined (e.g. when MediaInfo reports 23.810 fps while the video is actually 23.976 fps)

surprisingly, this is THE ffdshow - the one that everyone use
and it's dead for years

"animation" are those settings ported to SVP 4

let's check mpv's log

try an older mpv-1.dll build: link

> Can you explain "force exact value"

when it's "off" SVP selects the minimum possible denominator value (<target rate> = <source rate> * num / den)

"off", "uniform" => 23.976 * 5/2 = 59.94, every 5th frame is original one
"on, 60 Hz", "uniform" => 23.976 -> 60.000, every frame is interpolated, more artifacts