Kdenlive is a little clunky in some ways, but it gets the job done and I was able to figure out the basics after watching a quick tutorial on YouTube. I use kdenlive to cut up screen shares and render them to webm I do occasional light editing work to make tutorials for people. If I were to switch video editors, having the program crash on me constantly is obviously a very big problem.Ģ) I didn't see any obvious language defining why I should switch to Shotcut.
This is a really bad foot to start off on.Ĭan anyone speak to the stability of Shotcut? I see a few comments below mentioning crashes, I just can't tell if we're talking every month or so, or every 5 minutes. I get the impression that this software is extremely unstable across OSes. Here's a bit of feedback, in the event anyone who manages the site reads this comment section:ġ) I checked the FAQ and the 2nd and 3rd question in the FAQ were about crashing on Windows. Very possibly the sweet spot we've been looking for! And has exactly one contributor.īy contrast, Shotcut seems to be built on, and by, with a close correspondence between the runtime API surface and the file system representation of a file, and it's fully open-source. seems to give just read-only access to a lot of things at the TimelineClip level.
Imagine creating a promotional video, then automatically swapping in each client's logo and re-rendering it for each one! The possibilities here are endless.ĭaVinci Resolve can't be beat for #1 and seems to support #3 well, but its API seems designed more for plugins than for automated authoring. be able to run on cloud hardware as a render service
a well-documented timeline-level API for the file format that can replace, timeshift, and add clips and tracks, and a stellar editing UI for "prototyping" a well-edited video This is very cool! I've been looking for some time for a project that has:
0 kommentar(er)
