[Michael Kammes]

AVCHD is an acquisition format, not really a deliverable. May Ia sk why you want to finish / output in AVCHD?

Are you trying to create a master file (AKA a mezzanine file) to base other encodes later on, from? Or, does this have a specific destination?

You should really look to a more robust codec for archival or a mezzanine format. ProRes 422 or ProRes 422 HQ, DNX 145 or higher, Cineform, etc. These are excellent choices, don’t degrade (as much) if used and edited later.

Another alternate may be h.264. That would give you a smaller file size, but is not the best for editing later on.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Can we get more info? What is the NFS mount on – GigE? 10 GigE? Single or Bonded? Is there a switch – if so, what kind? How many drives is the media sitting on that you are pulling from? Is the NFS mount another CPU or a self contained NAS?

I’ve seen it done dozens, if not a hundred, times. Sustained guaranteed throughput is the issue, and a generic NAS or NFS mount that is not optimized will have no reliability or predictability. Think of it like USB: yes, the bandwidth is technically there, but in burst.

I’d also recommend talking to Bob Zelin about this in the SAN Forum. https://forums.creativecow.net/sanetworks

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Have you downloaded the XDCAM AMA Plugins for 5.5?

With v 5.5.x, you need to download the AMA plugins separately. This allows Avid to make updates to the plugins without the end user having to download a new Media Composer installer.

Go here for info on AMA: https://www.avid.com/US/products/Avid-Media-Access

The third tab over (Plugins) : https://www.avid.com/US/products/Avid-Media-Access/plug-ins

And on that page is the XDCAM plugins.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Lets limit some variables.

Have you verified the codec versions are the same? Are you at MC 5.0.3.8 and does your QT version match what is supported for 5.0.X? (should be 7.6.6)

Export 175 (8bit) NOT 175X. Use Millions of colors, NOT Millions of colors+. Make note of the frame rate (24 vs 23.98, etc)

Now, attempt to import that file into the same project or a brand new one, as long as the project rates are the same, making sure to change your import settings. YCbCr 709, not RGB, Pixel mapping is set to 601 or 709, and select Use Source Files resolution. I hate to say it, but mirror my settings (step 9, 10, and 11).

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Respectfully, you must be missing something. Fast Import is being used by thousands of editors, thus I can only conclude your export settings from Premiere, or Avid import settings are incorrect.

Things to double check:

-Frame Rate mismatches (Premier export vs Avid project)
-Import settings in Avid
-Millions of colors vs millions of color+
-Try NOT doing a fast import (i.e. import a movie file not optimized for fast import) and see if the time is different from the Fast Import – lets make sure there IS a time difference.
-Make sure DNxHD codec versions are the same on both boxes (this should not affect import time, but it doesn’t hurt to make them the same)
-Try MC 5.0.3.8

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Please correct me if I’m wrong, but Supermeet and a User Group: 2 different things…? It was my understanding the user group (lets say, LAFCPUG or CHIFCPUG or BOSFCPUG) had to adhere to community guidelines, but that Apple had pulled sponsorship of the Supermeet, hence the name being changed several years ago.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

I guess I see it as few people on Twitter have: Damned if you do, damned if you don’t.

Not bumping the scheduled presenters would cause a huge backlash. DESPITE Apple pulling sanctioned / support for the Supermeet. DESPITE their withdrawal necessitating expanding the scope of the event for the past several years. That was…well, shitty. DESPITE this, and being a fanboy or not, FCP users would be up in arms for passing on the first whiff of the new product.

And of course, the reverse is true: Having Apple show the new FCP at the Supermeet *should* be one of the biggest things for the post industry in recent history – trumping the importance of those already scheduled (with all due respect to those presenting, I had my tickets prior to the announcement to hear Kevin and Phillip, etc.) This would, as we’ve seen, conceivably cast a bad PR spin on Apple for muscling in, and a potential tarnish on the Supermeet crew.

IM_VERY_HO, for shame on Apple for putting Supermeet in this predicament. Apple doesn’t need the Supermeet crowd to have an event, period. It isn’t needed to have this at NAB to show up the rest of the industry. It’s dirty pool. They’ve backed out from *virtually* every industry event, including Supermeet and NAB. No takebacks, Apple. You should not be able to have it both ways.

Michael and Dan have their plates full, and let’s hope that the backlash from this is the lesser of the 2 evils.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

I wrote up a guide to correctly creating DNxHD files for Fast Import, perhaps it may help:

https://michaelkammes.com/encoding/avid-is-self-aware-fast-import/

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

2 ways to go:

If your storage manufacturer makes or has endorsed an eSATA solution, use it. They’ve tested (or built) the storage on it, so it will yield best performance.

As for 3rd party, Sonnnet’s are pretty darn good (plus Snow Lep compatible): https://sonnettech.com/product/temposataedgeexpress34.html

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .

[Michael Kammes]

Have you tried this locally to see if the problem persists? Can you try copying the footage (or some of it) to a single write volume, relinking, and seeing if that works?

Multi-write volumes with Avid project sharing on Facilis can be a tricky thing.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes

Hear me pontificate: Speaking Schedule .