Well done Wilson.
---In Avid-L2@yahoogroups.com, <avid-l2@yahoogroups.com> wrote:
But that film ends with the surviving (three) samurai watching the now-fearless villagers joyfully planting their rice crop, and Kambei (the wise leader of the ronin) ruefully notes "Again we're defeated. The winners are those farmers. Not us."
On Fri, Oct 4, 2013 at 12:06 PM, <pixcutter@...> wrote:http://wolfcrow.com/blog/the-best-video-editing-software-2013-part-one-the-beginning/
I find his reviews usually in-depth and worth the read, but early in part one this gave me pause:
"Therefore, an NLE can only stand out in these ways:It can import more file formats than its competitor. It can export to more file formats than its competitor. It can work with native file formats (non-destructive editing) if that's what you want. It can handle more frame rates and resolutions than its competitor. It can handle more color information than its competitor. It can handle more audio information than its competitor."
and later:
" It all comes down to which NLE can support the most diverse workflows."
I read his definition of workflow here as what I would consider, well, signal path; the formats or codecs used at various stages through post.
So, is he focusing too much on this aspect, or is he weighting it appropriately?
For me, yes, it's critical to know what formats and codecs to expect, to nail down frame rates and compression, to get deliverables precisely defined, but I consider this more about planning and setting up a project, and just one aspect of workflow.
I find the interface and the NLE's tools ultimately contribute more to an efficient workflow. Or am I giving too much consideration to the day-to-day work of editing?
Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
No comments:
Post a Comment