Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Native FCP Support for Build 17?

Jordan Livingston

Well-known member
Joined
Feb 9, 2009
Messages
349
Reaction score
0
Points
0
Age
44
Website
www.jlpmovies.com
Does anyone know (or have an educated guess) when we can expect native REDCODE support of Build 17 footage within Final Cut Studio? The FCS plugin download seems to have been neglected for a while...

I have a short film (~12 mins) that wishes to use the following workflow:

- FCP Native 'offline' edit (REDCODE in QT wrappers)
- Export Native footage to Color for grade
- Render Color output to DPX
- 'Online' (titles, dissolves, crop to 1.85:1, etc.) DPX files in After Effects
- Downconvert to HD 1080p 10-bit using either After Effects or Compressor (haven't decided which yet)

In my view, this is by far the best workflow for maintaining maximum quality throughout post - especially for a short form project without any real storage space issues. I'd really rather not add the extra step of generating offline ProRes files for FCP, only to later manually conform back to REDCODE prior to grading in Color.

That being said, I do need to start cutting soon, so if FCP support for Build 17 isn't on its way, I will have no choice... Is anybody in the loop on this?

- Jordan

P.S. As an editor, post supervisor, and DIT - I LOVE the RED... I can't wait for Scarlet and Epic cameras!
 
There is a minor bug currently, but it has a workaround.

Bring one of your clips into REDAlert, click on "Defaults" and add a first-light (if needed). This makes the black files from build 17 visible. Save the preset or a few of them for different first lights and use them in FCP for ingest.

Hope this helps.
 
There is a minor bug currently, but it has a workaround.

Bring one of your clips into REDAlert, click on "Defaults" and add a first-light (if needed). This makes the black files from build 17 visible. Save the preset or a few of them for different first lights and use them in FCP for ingest.

Hope this helps.
Hi Uli,

I tried this and I still receive an error message when trying to import Build 17 media via "Log And Transfer." Is there something obvious that I'm missing?

- Jordan
 
What does the message say?
 
What does the message say?

My apologies for the long delay in getting back to you... I don't recall what the message said verbatim, but it was something about an 'unsupported format.' After clicking "ok" the Log and Transfer window just hangs indefinitely.

I think I'm going to have to move forward with the ProRes HQ files rather than the native R3D. I know I can always go back to online R3D later, but we had an amazing workflow ready to go that saved a lot of storage space and time by not having to convert all of our rushes. Oh well. :-(

- Jordan
 
Are you pointing L&T directly to the .RDM folder? L&T doesn't seem to look very deep into the folder structure, I got that "unsupported format" too, when pointing to a higher folder.
 
Are you pointing L&T directly to the .RDM folder? L&T doesn't seem to look very deep into the folder structure, I got that "unsupported format" too, when pointing to a higher folder.

Okay, I just tried this again, drilling down all the way to the ".RDC" folder. The message I receive is as follows:

"A001_C001_0129B2.RDC" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media."​

When I select the ".RDM" folder, I suddenly see my clips! But not all of my RDM folders, only some of them! This is further than I've gotten before... any idea why some folders show up and others do not?

- Jordan
 
Any fancy symbols in your paths? Try to stick to ASCII, I even use underline instead of spaces – it's UNIX under the hood…
 
I might be missing something but... I just offline/onlined a music video with Hans' Clipfinder workflow (Transcoded Offline files back to> Native L&T > Color >FCP) without any issues.....

Build 17 footy. 2 cameras, very long takes. No issues....

:huh:
 
FWIW, you might want to try the latest Clipfinder release, as described in this post
http://www.reduser.net/forum/showthread.php?t=26302
The new release allows you to collect all .RDC folders for selected clips into a single directory to ingest from. It also allows you to clean up the mess afterwards.
If your material is distributed across multiple drives you need to repeat the procedure described in the post for each drive.

Cheers,
Hans
 
Hi All,

So, I got the clips to work, finally! I had to do it one .RDC folder at a time for some reason. Perhaps I'm not organizing my folder structure correctly? Here's how I do it (comments welcome):

PROJECT FOLDER ("Name_Of_Movie")

DAY OF SHOOT ("day01_02-20-09")

CAMERA ROLL ("A001_01281B.RDM")

RDC FOLDERS ("A001_C001_0129B2.RDC")

I'm also disappointed to learn that FCP generates an entirely new set of "native" files. My hope was that by editing native, I could avoid the long 'ingest' time, and ALSO - could continue to one-light correct in RED Alert (using the original camera files) and would see those changes reflected in Final Cut Pro and in Color... Too much to ask, I suppose.

- Jordan
 
Back
Top