![]() There is a long list of things you need to deal with even if you aim for something small and I have utmost respect for Matt for even getting started on this. Support for different hardware, formats, licensing/compliance. With the limited workforce it will also take a long time to catch up technologically while the big players continue to innovate at high speed. It's also hard to justify why someone should invest money into a project to start building something that is readily available from other parties for less. It's impossible to provide the same level of support that higher-end productions require and can get from proprietary vendors to begin with. Realistically, Olive will probably never be a top pick among the high-end tools no matter how narrow the scope may be. ![]() If you can afford it though, then you should use the best tool for each task. I agree that offering a broad feature set in a single app is most useful to individuals and small teams with very limited time. Why would a production team pick Olive just for editorial instead of an industry-standard application that also specializes in cutting? I don't see mid/large scale productions as promising future audience. And I'm not convinced that creating "the best" open-source footage cutting tool would pay out. It would mean to remove features that are already implemented, however. Limiting Olive to cutting only would be a possibility. It's more than just editorial, but something that can go hand in hand (and does in a lot of NLEs). I was thinking low-key compositing as simple as text over video, crossfades, etc., not compositing multiple render passes or anything fancy. 3D and deep compositing might be out of scope but it would be a waste of potential to not make Olive a 2.5D compositor, especially with the node editor and its color-managed pipeline that can actually composite imagery correctly.Įditorial and compositing are very different tasks of course. Every NLE composites frames to some extent. A transition between two videos, a picture-in-picture thing, a text title over a clip. Strictly speaking, anything but a single video at a time is a composition. compositor, I find it hard to draw a line between the two. ![]() Olive shouldn't become a DAW but basic tools for integrated audio editing are very much needed. Following the Unix philosophy, video editing and audio editing would need to happen in different pieces of software, wouldn't they? Not very convenient. NLEs also tend to be a bit like silos, allowing you to do all kinds of things within them, with limited inputs and outputs for interoperability. A headless mode for network rendering, sure, but the complete application is much more than a simple command. I see your point and "do one thing well" isn't a bad philosophy by any means but there are a couple of things I want to say in reply.įirst off, a video editor isn't a command-line utility that you would compose with other commands in a shell or script, at least not primarily. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |