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
If I cut a video from 00:39 to 00:49, the trimmed video will start at the proper time but instead of being 10 seconds long it will be 49 seconds long, where the length is seemingly matched to the time stamp of the out point I selected. Similarly, trying to cut a video from 2:30 to 2:50 will result in a 2:50 long trimmed video. When I open the index selector before making the cut, the time stamp it reports is correct.
I'm also having a problem where the export mode is also set to smoothie on start up even though I always set it to ffmpeg. I got around this by commenting out config.export_mode = "smoothie" in the function below:
mp.register_event("file-loaded", function()
local container_fps = mp.get_property('container-fps')
if container_fps == nil then return end
local vid_fps = tonumber(container_fps)
if vid_fps == 0 or switchExportRan then
-- disabled by user / already ran
return
elseif config.switch_above > vid_fps then
print("FPS is above trigger limit, switching export mode to smoothie")
config.export_mode = "smoothie"
end
switchExportRan = true
end)
The text was updated successfully, but these errors were encountered:
If I cut a video from 00:39 to 00:49, the trimmed video will start at the proper time but instead of being 10 seconds long it will be 49 seconds long, where the length is seemingly matched to the time stamp of the out point I selected. Similarly, trying to cut a video from 2:30 to 2:50 will result in a 2:50 long trimmed video. When I open the index selector before making the cut, the time stamp it reports is correct.
I'm also having a problem where the export mode is also set to smoothie on start up even though I always set it to ffmpeg. I got around this by commenting out
config.export_mode = "smoothie"
in the function below:The text was updated successfully, but these errors were encountered: