![]() I can’t remember the name of that program.įor these reasons, I’m leaning toward staying with Kdenlive or maybe eventually DaVinci Resolve, even though the speed and file size of Losslesscut is tempting. LosslessCut is great for rough processing of large video files taken from a video camera, GoPro, drone, etc. And of course, you can also just drag the ends of a clip to get to the start or end you want.īack in my Windows days, maybe 2005ish, I used another program to cut commercials from TV documentaries, which worked like the razor tool. ![]() Instead it seems you need to mark the portions you want (or don’t want, there’s a toggle), then create a new video file before you can view how well the cut worked, unlike Kdenlive, or other non-linear editor, where you can immediately view it on the timeline and fine tune the cut. I wish it operated more like a non-linear editor where you can use the razor tool to cut a portion you don’t want, then just eliminate the space. They do give warnings that the cuts may not be accurate and might need some trial and error but I haven’t played around with it enough to test that. I’ve seen, for example, that H.265 in CQ mode will cause YouTube to treat HDR video as SDR, but the same exact video rendered in VBR mode will be handled properly by My system is Kubuntu 20.04 LTE and I’m using the appimage, which is available by scrolling down this page. I personally prefer H.265 in “constant quality” mode, but this can sometimes not play nice with certain playback systems. LosslessCut will do the same in seconds without losing quality LosslessCut simply cuts the data stream and directly copies it over. Also, for reference, running mediainfo on your source recordings would be useful. To help you more, it would be useful if you ran mediainfo on whatever kdenlive exported by default to see what codec and codec settings it was using. Kdenlive (and nearly all other FOSS video editors since MANY of them rely on MLT) are an outlier in terms of still being stuck in the int8 world.įor your use cases, that’s probably OK, and you probably just have to tweak the codec settings on export a bit more to get the right bitrate vs. Right-click on the desktop and select Display settings from the context menu. ![]() If you’re not doing color grading/colorspace transforms/anything that requires more than 8 bits per color channel and such, kdenlive will probably do OK for you. I wanted to move to something that had better color management. I’m using the paid version myself - but the main reason I ditched kdenlive was that working with Sony S-Log2/3 video was really problematic in kdenlive - it’s been well known for years to handle full-luma-range video poorly/unpredictably, making it difficult to properly use the lut3d filter to do colorspace conversions. ![]()
0 Comments
Leave a Reply. |