You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simply changing the FPS of media (and adding pitch) manually is more complex than it needs to be.
Problem:
Change 23.976 to 24 and normalize audio
Solution:
[23.976 to 24]
profile-cond=container-fps=23.976
speed=1.001001
pitch=1.001001
audio-pitch-correction=no
af-add=rubberband=pitch-scale=0.999,engine=finer
sub-speed=24/23.976 (this value will work with speed/pitch too ?)
sub-fps=24
Proposed solution:
If mpv can handle conditions, how about the following:
Additionally it would be nice to hold one frame longer instead of repeating it. hold-cond = 24 = 2 for example would output 24 frames in 2 seconds instead of bobbing the output to 48 frames (reduces CPU/GPU usage)
Also I want to mention that the manual is very confusing on this topic, see image attached:
Expected Behavior
Simple and straightforward
Actual Behavior
Not simple and straightforward
The text was updated successfully, but these errors were encountered:
mpv Information
No response
Important Information
Reproduction Steps
Simply changing the FPS of media (and adding pitch) manually is more complex than it needs to be.
Problem:
Change 23.976 to 24 and normalize audio
Solution:
Proposed solution:
If mpv can handle conditions, how about the following:
Additionally it would be nice to hold one frame longer instead of repeating it.
hold-cond = 24 = 2
for example would output 24 frames in 2 seconds instead of bobbing the output to 48 frames (reduces CPU/GPU usage)Also I want to mention that the manual is very confusing on this topic, see image attached:
Expected Behavior
Simple and straightforward
Actual Behavior
Not simple and straightforward
The text was updated successfully, but these errors were encountered: