This command, for example, would extract a 1.5-second clip starting at 5.3 seconds into 'longfile.avi' and save it to 'shortfile.avi':įfmpeg -ss 00:00:05.30 longfile.avi -t 1.5 shortfile.avi To extract video from a certain time, use the -ss and -t flags to specify start time and duration, respectively:įfmpeg -ss HH:MM:SS INFILE -t DURATION OUTFILE 4 Changing the video resolution (scaling).I use that once in a while, but I'm usually after what kdenlive does by default, scaled to fit. If you drop a 640 clip and use an affine transition, there is an adjust to original size underneath the X Y W H bit. not sure about, maybe? I can't think why that wouldn't work, inefficient for sure, but that might not matter. Those are also very good ideas, especially the composite one which I may try if ffmpeg sws-flags doesn't work. Qubodup wrote:I did a quick comparison of two scaling methods and one effect: Is it possible to have a clip retain its resolution when getting placed in a project of a different resolution? (This was the second-biggest confusion for me when I first started using Kdenlive, right after why transparent images weren't transparent. Speaking of scaling manually, I have a related question: when I put a 640x480 clip in a 1920x1080 project, it gets scaled and letterboxed automatically (unless blue icon composite is on, then there's no letterboxing). If you simply want the visual effect, the Pixelize effect might be a compromise.
The Crop, Scale and Position effect appears to be using interpolation.ģ.
Didn't matter whether the blue icons were set to opaque or composite.Ģ.
Warning! Using Composite causes some serious memory abuse on my system just by previewing. The Composite transition appears to not use interpolation. You can get the full-size images by right-clicking and selecting "open image in new tab"ġ. I did a quick comparison of two scaling methods and one effect:
0 kommentar(er)
