[Justin Daniels]

I’m not planning on doing the proxy creation while editing. The plan was to ingest the full-res footage and create the proxies before anyone started cutting anything.

Also, we’ll be dealing with regular ProRes, not HQ, so the files won’t be quite as intense in terms of bandwidth

[Justin Daniels]

After exchanging emails with Bob and surveying the responses so far – I am leaning towards a 10Gb ethernet setup. My only question about it is in regards to real world performance. Does it actually match up with something like an 8Gb fibre setup when dealing with ProRes422? Furthermore, does the cost vs. what you get for it make it worth it? Or, is Fibre more cost efficient?

I think the move for us is to go with a file-based system (seeing as how we will have multiple users accessing/modifying the same files) so that leaves us with Small Tree, Maxx Digital Final Share, JMR (who can do fibre or 10Gb ethernet) or the Terrablock which has a file based option now.

Also, Bob and I talked about the need for proxy files if dealing with 3 ProRes422 streams at full resolution in multiclips and I’m curious to anyone’s experience with Final Cut Server’s supposed “automatic proxy creation.” Apple’s website says that “Final Cut Server can now create edit proxies automatically. After you ingest your footage in Final Cut Pro, save the project to Final Cut Server. Final Cut Server automatically generates proxy files and links them to the project, so you can either edit with original footage over a high-speed network or choose the smaller proxy files for editing on a notebook or over a slower network.” Does this actually work without glitches?

Thanks for everyone’s help with this.

[Justin Daniels]

From what I’ve experienced with this unexplainable problem is…

The multiclip can be opened, played and then marked in the viewer and those markers will be retained as long as you never switch your camera to something other than the “master” or “default” camera that’s selected when you first open the multiclip.

If you drag that marked multiclip into a sequence and then reopen it in the viewer – the markers seem to stay regardless of what camera you the switch to thereafter. So it appears as the problem is with the original multiclip being opened from the bin into the viewer.

For me, I use the inital multiclip (that I mark in the viewer) as an outline for my footage. I then just select the pieces I want (by clicking my marks that I see in the bin) and drag that section to my timeline.

It’s kind of a tedious workaround, but gets the job done without adding any real time to the edit. You just have to be conscious of where/when you’re clicking.

Put this into the ever-expanding list of “unexplained FCP errors.”