[John Heagy]

[Oliver Peters] “It’s not exactly “conjured”. This exists because Avid licensed it from Apple.”

The codec yes, but creating an mxf wrapper for ProRes was all Avid.

[John Heagy]

[Michael Gissing] “John, it is worth playing with DNxHD.”

We have and found if far harder to encode. This is why Arri didn’t offer 120fps initially in DNxHDx on the Alexa.

We get 10bit quality at 140Mb with ProRes(SQ) but would need to go up to DNxHDx 220 for 10bit.

It’s cross platform but mainly via Avid’s QT codec so were back to relying on the QT 32bit API.

The fact that DNxHD is an open standard is appealing, but encode and storage efficiencies for the same quality go to ProRes.

It’s not that we can’t use DNxHD, tho I think that’s essentially the case in FCPX, we really don’t want to.

What I’d really like is ProRes.mxf which Avid conjured up but that’s under lock and key unless Apple embraces it.

I see ProRes and FCPX being linked so that’s another reason I’d like to see FCPX flourish.

[John Heagy]

[Michael Gissing] “Most of my jobs come from FCP 6 or 7 or AVID. So they open in FCP7 (via Automatic Duck for AVID). They are sent to Color for grading and when I then add back in text it is correct. “

Thanks for detailing your reasons for not using FCPX. I’ll always be quick to ask for details when the word “can’t” is used. I find in most cases “won’t” is more accurate. Not to knock your reasons, I’m just eager to learn from others any potential deal breakers that might apply to our workflow.

For us ProRes QT is a big reason to hope FCPX will meet our needs. There will never be a better NLE for editing ProRes QT than FCPX unless Adobe embraces AV Foundation. That will never happen unless Apple releases AV Foundation for Windows. Right now Adobe and AVID are suck with 32bit QT APIs.

We are communicating our desires for both FCPX and AV Foundation to Apple. We are happy with the improvements so far. Much work is still required and seeing our requests included in future updates is what we are looking for next.

John

[John Heagy]

Oh I see now. There is no such thing as ndtc 23.98 so it will be impossible for it to match your dftc 60i master.

[John Heagy]

[Michael Gissing] “I can’t use it as a finishing tool the way I did with FCS3…”

Is weak audio mixing and lack of tape I/O keeping you from using FCPX as a finishing tool?

[John Heagy]

If you start the conversion on an even second the two should match. Otherwise it will be offset but should not drift.

[John Heagy]

“2 million Pr seats in 5 years”

Wasn’t it about 5 years ago Adobe finally created a Mac bundle with PS and AE, and oh by the way you get Pr as well. I can tell you that’s why we have 40 seats of Pr we don’t use. We used to have to buy AE separate from the Design Bundle and that didn’t include Pr.

John

[John Heagy]

[Jeremy Garchow] “- More reliable/user controlled Project/Event backup system.
– “Show matte” on Color Mask selections
– Color Coded Roles
– Expand Audio shows all audio tracks, not a mix down
– Range based Project Export
“

Interesting list Jeremy. It points out how different people’s needs are when it comes to FCPX.

I’m looking for foundational items before we start asking for edit features. My 5 are:

-Read embedded Reel/Tape ID in QT and export user defined reel in exported movies.
-Include an “xml export” metadata tab where whatever is selected is exported in the xml.
-Read only Xsan locations so other users can add the same location owned by another user.
-Include all ProRes codecs in the Project Render setting.
-Direct Renders where we want. Having renders be part of the Project location will blow up our Project volume and drastically impact our project backup policies.

I have one request for AV Foundation:

-Reference movie support so it can be added to FCPX.

John Heagy

[John Heagy]

[Bret Williams] “Oh come on…”

Thanks for the list Bret, that’s far better then letting websites communicate your wishes.

My question was for Rainier, maybe he agrees with your answer or maybe he has other wishes.

Don’t expect Apple to “make it pro” if you don’t list what you want. We are communicating specifics to Apple and, while we’re not changing to FCPX or any other NLE for at least another year, we are happy with the progress so far.

Apple adds 4 to 5 features per update, so I’d be interested in your top 5. Believe me, Apple likes requests in short prioritized lists. Based on how they’ve responded so far… they are listening.

John Heagy

[John Heagy]

[Rainer Wirth] “To us, it hasn’t met a professional editors standard.”

Can you be more specific? I’m interested in understanding the difference between what doesn’t work and what you simply don’t like.

John Heagy