This IS the Avid L2: [Avid-L2] RE: FCP rendering to Avid ISIS 4.2+

Thursday, November 14, 2013

[Avid-L2] RE: FCP rendering to Avid ISIS 4.2+

Owen,

As I understand it, import uses the Quicktime engine which is still 32 bit and not multithreaded. Avid Transcode via AMA is not limited by Quicktime and is much faster.

Consolidate, which just means copy, should be the same as fast import assuming the same length clip.

Any difference, real or perceived by Media Composer, between what the file and the native Avid resolution will cause the dreaded slowdowns on import.

---In avid-l2@yahoogroups.com, <owen@...> wrote:

thanks job!!

Owen's iphone

On Nov 14, 2013, at 4:53 PM, "Job ter Burg (L2B)" <Job_L2@...> wrote:

Also, if you AMA, then TRANSCODE from DNxHD175 to DNxHD175 you are losing a generation. If you AMA, then CONSOLIDATE the DNxHD175 source, it stays in the same generation.
If you Fast Import, you also stay in the same generation. Fast Import should be just as fast as a consolidate, AFAIK.

On 14 nov. 2013, at 21:04, Mark Spano <cutandcover@...> wrote:

Link AMA and transcode always burns importing. Importing is slow and old.

On Thu, Nov 14, 2013 at 2:44 PM, owen <owen@...> wrote:

Hi,
I tested importing a dnxhd 175x yc 709 quicktime mov to dnxhd same colorspace vs
transcode of a dnxhd 175x 709 quicktime mov to 175x same colorspace as mov and the transcode seems faster.
What is your experience with this?
thanks,
owen