[Cris Daniels]

Who exactly asked Apple to re-write how we edit? We asked for 64-bit, better tools, an update to the interface was due for certain.

The problem is as simple as it looks, it is Imovie Pro. Plain and simple. How anyone could deny that is ridiculous.

If Apple thinks this is how people edit, especially in production environments, boy are they out of touch…

If Apple thinks adding a few functions into FCP X adequately replaced Color, or Final Cut Server, that is delusional as well.

It is also becoming clear there is a certain segment of Apple cheerleaders, non-Apple employees and Industry gurus”, who are either getting the marching orders, or paid to put lipstick on this pig. No worries, we simply note their credibility hit and move on.

Nobody that insists that I need to “see how brilliant Apple was” in their “re-invention” of “professional editing” is relevant.

This same kind of reaction would occur if Adobe revamped Photoshop into some kind of node based application, or told us Photoshop Elements was actually an upgrade…

And if the answer is “wait and see what we do with the updates to FCP X”, then why the hell is it out now? Are they admitting is isn’t ready for prime time? That is a damage control statement if I every heard one. You WILL NOT see the most important features missing added back in, that is what WE KNOW and is the crux of the problem.

As far as Apple holding some kind of crystal ball, and laughing at the way everyone emulates this software in the end. Uhh….. wishful thinking.

[Cris Daniels]

You need to run the software (5DtoRGB), once you select a video file, you can go to the dropdown and select the decoding matrix. It specifies that Canon DSLRs shoot 601, but it does give you the choice to pick 709. The software is written by a post house and I have had quite a few back and forth emails with the guy so this is absolutely verified behavior. I always use this software for Canon transcodes, and I hope that full DNxHD support isn’t far off.

MC5 bringing in all HD footage via AMA as 601, that needs to be fixed by AVID.

[Cris Daniels]

This is the app I have been using to transcode DSLR footage for Final Cut and they have verified that Canon uses the 601 matrix with the DSLR’s, of course nobody quite knows why…..

https://rarevision.com/5dtorgb/

I have don’t know if all QT files are acting this way, most are correctly tagged Rec709 internally. This Canon footage is an aberration,most HD footage should come in as 709. If its all coming in 601, AMA is the culprit.

[Cris Daniels]

Right, I understand that the RGB full range option would be perfect for importing motion graphics and such. That having been said, there are full range video files exist, the Canon 5D MKII which shoots full range HD in the 601 colorspace for example ,although it is obviously not RGB footage. My original question was “how does MC handle footage that is not specifically shot 16-235”, glad to know that the 709 option won’t bungle the footage.

So far as I can tell there are only two ways to import footage, through the import command, and the AMA. Is there some other way I am missing?

And thanks a million on the “Add Edit” tip, that is exactly the tool I was looking for.

I am liking the program so far, I am trying to learn it in case the next version of FCP is a turkey. I think that the real problem for me is the lack of Blackmagic/AJA support.

[Cris Daniels]

Great, thanks for the quick reply,

I am coming from FCP and using the MC5 demo so this is why I have some of these basic questions.

So basically it looks like you are designating whether your are importing RGB or YCbCr footage from that dialog box. Just wanted to make sure that it would properly honor my video signals as shot and not clip upon import.

Does working with the AMA media interpret the video files any differently (in terms of those overbrights)

P.S. – I miss the razor blade tool from FCP