![]() When the scrub cursor lands, it decodes all P-frames between adjacent I-frames just like that. Now not only is h264 very versatile and your camera will probably insert a lot more I-frames (and less B-frames) than your export will for this exact reason, a modern decent computer is really unbelievably powerful. So if you want to transcode everything before spotting it in your editor, you'll be standing around holding your duck in your hand a lot, as they say in Romania. ![]() Even professionally targeted video cameras from Canon have been using h264 (XF-AVC) for years, and recently switched to the 10 bit h265 (XF-HEVC) in newer Canon cameras. Now unless you're handling professional equipment and are shooting heavy footage like RAW, redcode, AVCHD, ProRes or something similar, pretty much all the amateur and prosumer equipment will write h264 or h265. We had to transcode everything back when we worked on our Avid systems back in 2007. I can see you have some old school experience, perhaps similar to mine. ![]() Personally I think that's a bad idea unless you are working with new media on old hardware. For that, I'll always use Kdenlive over every other Open Source project for quick and simple projects because of its feature set and because I'm running a KDE distro, so it's meant to fit.īut Resolve is still sooooo much better than any Open Source community based project that It's my immediate go to for anything more complicated than just dropping some stuff into a timeline and applying a cross-dissolve. I love Open Source and I try to champion it everywhere I can. It's also the only company that provides full training books with project files for people to work through.įrom my perspective. The power, the features and the refinement that it provides in its free offering is quite simply astounding so much so that you'll end up wanting to buy the (comparatively affordable) Studio version not because you really need it, but because you want to reward a company that treats is free users so damn nice.Īnd I'm sorry if I sound like a schill.I'm really not. So unless Open-Source is critical to you, Resolve is always the right answer. Honestly, the free version of DaVinci Resolve leaves every free open-source editor in its dust. DaVinci Resolve seems to be the hardest to learn but most capable, but I'd settle with any of they can carry out my requirements with ease. Kdenlive has far more documentation & from what I've seen the learning curve doesn't look that steep (for me atleast), but Olive is faster & more stable according to it's users. I've been looking at options & have narrowed it down to these 3.īut I honestly want to know why I should be compelled towards KdenLive. (7) Blend modes - Another important one, need for lens flares & smoke effects and such. (6) Chroma Key - Green Screen stuff, pretty self explanatory. (5) Rotoscoping - Frame by frame Rotoscoping & masking of videos. (4) Good performance - This is where I've heard that Olive beats Kdenlive, but other videos show Kdenlive running on a cheap Chromebook so I'm not sure. (3) Color Grading - The ability to manipulate colors, contrast, brightness, hue, saturation and so on. Also the ability to create ease in/ease out effects (eg by using Bezier curves like in Premiere) when Keyframing. The ability to Keyframe layers & effects with minimal hiccups. ![]() (2) Robust Keyframing - This one is important. (1) Layers - Pretty simple, the ability to add in, crop & animate layers. Here are the things that the video editor needs to be able to do Currently I use Kinemaster which despite being surprisingly good for Android/IOS, is still a VERY limited video editor. I run a small YouTube channel & long story short I need a good video editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |