FINAL CUT PRO X now supports native R3D

[Eric Santiago]

Constraint on scaling the clip "is the default behavior" - When you press the shift key it disables the constraint.

Yep sorry I was talking position constraint.
Ill check soon if it does work now.

 

[Ben Jackson]

Not picking on you personally, Ben, but I think this kind of thing has been one of the main problems since FCPX was introduced. People didn't take time to learn the nuances and so there was a lot of claims and complaints about all the things it "couldn't do." Trouble is, it COULD do these things if you only took the time to learn how! Thankfully, with Apple finally getting around to doing the R3D thing, maybe folks will put in the effort to learn the application. The Ripple training is a pretty good way to start.

Totally agree. I'm well into my project and FCPX has been a DREAM to work with. Everything I could do in FCP7 I can do in FCPX AND wayyyyyyyyyyyy more. If I need things not to jump around for some sort of syncing to music reason (for example, a music video) I can lift from the main storyline, keep the main storyline blank and create separate storylines for all my main sections. They then act magnetically - which I love - and I don't lose any of the features of FCPX. The magnetic time line DOES save a TON of time.

Again - changing raw settings as I go thru - is a dream.

For VFX, rather than exporting whole clips, I've taken to creating a compound clip of any clip I want to do some Mocha or Motion on...then I simply export Prores 4444 from FCPX's export option, and I have JUSt the clip I need, rather than the whole R3D. FCPX transcode seems to be fast too, again, using all of the CPU as opposed to Redcine-x (this app needs a serious makeover behind the scenes).

My previous post was incorrect, I believe I'm running at 1/4 res, not 1/2. It looks perfect on my 2nd monitor though, as opposed to what I see when I go to a 2nd monitor in redcine-x..

BTW, I'm not having problems with redcine-x anymore, as I discovered a bad memory module. So everything works nicely now - but I still say FCPX is the perfect workflow for me now.

Only time FCPX is slow is when dealing with 3rd party plugins - so somewhere there that needs work, but it might just be the code of the plugin. Tried reFine - slow as a dog, and Beauty Box isn't much better but not too bad. Magic Bullet seems fine.

But my usage of these things is now purely in the realm of creativity/artistry - NOT fixing weird colours etc, as I can do that in the raw settings as I go thru. For a single editor who has to do all my own VFX and grading myself, this is just great. And if you're sending stuff off to a 3rd party grader, then I can't see why using Roles to export stems and the rest of it wouldn't be just about perfect. You can easily set everything to Redlog Film before you export, but have it in redgamma3 whilst editing and people watching over your shoulder...

Solves so many things that Michael Cioni talked about as issues.

 

[Ben Garvey]

Here is a possible fix for the green footage issue -

I ran into this with some old footage too (also on a 5770) - I believe it is just an RMD file issue with the color science on older firmware footage.

What I did to work around it was change from Red Color 2 to Red Color 3 in the FCP X popup. You can do this for multiple clips in the event library by selecting a group.

Once I did this, I could toggle it back to other color science and gamma settings.

Matthew,
I have just starting diving into FCP X on my first project with Scarlet footage from the latest firmware update, and I am having the same issues you are. And switching RED gamma hasn't cured it. It seems once I start transcoding a certain clip in FCP X to a proxy, it turns green. And so far it is only happening with a couple of select clips. Any other methods to fix this?!

 

[Matthew B]

Hi Ben - I sent you a PM. First thing to check would be the denoise settings in the RMD. Also note that Switching the color science not gamma is what I needed to do -

 

[Jerrod Cordell]

There are some impressive things and then some things that just seem too un-pro, so for a simple web edit i'm finding FCPX to work well....but when i need to get into motion control and keyframing and some just advanced features, i go back to PrPro....i see that i also need to put in more time with FCPX, but for those advanced functions i seem to be always using and mixed media, i think i'm so used to controls in PrPro and FCP7....just seems FCPX is far to i-movie...and to get to advanced functions i have to put a clip into my timeline to manipulate it instead of working form the preview monitor....maybe i have not figured it out correctly, but that's how it goes for me....

The preview monitor is back by the way. And you can toggle it on and off, which is nice. I haven't messed around with motion control on clips not in a timeline yet but I imagine you can work with them. But don't quote me. I'm weird and always do that stuff in the timeline anyway, even in FCP6.

 

[Ben Garvey]

Matthew, you're right, switching the color science solved the footage turning green issue, for now. How strange. Thanks! Hopefully FCP will fix this in the next update.

Hi Ben - I sent you a PM. First thing to check would be the denoise settings in the RMD. Also note that Switching the color science not gamma is what I needed to do -

 

[Eric Santiago]

Matthew, you're right, switching the color science solved the footage turning green issue, for now. How strange. Thanks! Hopefully FCP will fix this in the next update.

Or RED

 

[Ben Garvey]

I am having an issue of FCP X not updating the saved changes to the RMD file in CINE-X. Is anyone else having this issue? And what import settings are people using for FCP X? Should I just have it import the R3D file as optimized?

The steps I have done are:

1. Open R3D in CINE-X
2. Select and save RMD of all clips in CINE-X that will be imported in FCP X
3. Import clips in FCP X
4. Adjust clip color/settings in CINE-X
5. Save RMD in CINE-X
6. Go back to FCP X... and nothing changed.

I was working on another project where I had 'optimized media' selected for the import option in FCP X and seem to have better luck in the RMD being updated, but I had to fiddle around the 'Modify RED RAW Settings' in FCP X to make it update, and it didn't work all the time.

But it seems to me, working with the R3D natively in FCP, and not creating optimized or proxy media will be the best route for FCP X to recognize the updates to the RMD, but this is not the case. Am I doing something wrong or missed a step?

 

[AndreasOberg]

I really like Final Cut Pro X so far after using Premiere on PC. Refreshing.

A few weird thing with the Apple update
- the proxies are half the resolution of the original. This means your 5k clips will be 2.6k and our 2k slow motion shots will be 2k. Myself I would have prefered to just have all the proxies in 1080p resolution. Now I got blurry slow motion and the 2.6k takes a lot of space.

Also what debayer does Final Cut use for proxies? Its taking a long time to do them so I'm thinking 1/2 or maybe full resolution.

Anyone else that would like to have a few more settings like this for Red workflow.
Also I really miss an easy workflow with HDRx. So far the only solid way I have found working with HDRx is to use After Effects or Davinci. Anyone else have any better workflows?

Cheers!! Having too much fun to go to sleep
/Andreas

 

[Stephen Brock]

Heh, too bad many of us already made the exodus to PPro CS6 and probably won't look back for a while... ;-)

 

[Sulekh Suman]

unabble to install Red Apple plug in for FCPX

unabble to install Red Apple plug in for FCPX

Why is Mac 10.8.2 not letting me install Red Apple Workflow Installer V2.1?