The biggest issue is that as soon as you hit the Custom Export settings box, you are essentially handing the transcode over to Apple Quicktime 7 and its codecs. Some of those codecs (like Apple H264) are notorious for gamma issues, but worse: Apple Quicktime 7 is old 32-bit code, and that makes it slow, as it is unable to use all of the cores and horsepower of your machine.
In practice, you should find that transcode or mixdown, then export same as source will be FASTER. The transcode or mixdown is done inside Media Composer, which does use 64bit code to achieve that, and you can easily tell by looking at system resources monitoring apps while the transcode is happening.
Some tests on the Community Forums have shown that Mixdown is a tad bit faster than transcode, but both will be waaaay faster than 1 minute to 1 minute. After that, the QT Same-As-Source export is simply MC copying the native media into a QT container, which takes as long as any file copy would, so that depends on system speed and drive speeds.
With a gazillion of third party transcoding apps to choose from, free and paid, it makes zero sense to me to keep trying to do those transcodes using old QT7 code (via Custom QT Export). Hence my friends-don't-let-friends remark ;)
J
> On 13 dec. 2016, at 21:51, Terry Barnum <terry@dop.com> wrote:
>
> When did exporting to a "custom QT export" become the wrong way? Doesn't it add time to first Mixdown and then export?
Posted by: "Job ter Burg (L2B)" <Job_L2@terburg.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
No comments:
Post a Comment