FCP to Smoke Workflow help

[arythmic]

So we are trying to figure out the best work flow from FCP to SMOKE and here is what I have so far

In FCP we were able to use LOG & TRANSFER to generate the PRORES files in order to offline in FCP.

So is the next step to generate and XML file from FCP, use REDTRIP to make appropriate XMLS, then load the XML into REDCINE ?

Is redtrip the only way to conform a spot and get the appropriate shots for DPX output ?

im lost

thanks

[Joseph Hutson]

Welcome to the forum.

[Alex Carr]

Crimson is a powerful tool that reconnects or Onlines footage to R3d as long as you didnt rename any of the RAW files or Pro res files so they have the same or similar name,

www.crimsonworkflow.com

or

http://www.reduser.net/forum/showthread.php?t=10295&page=14

[Gunleik Groven]

Crimson is a very easy and stable way, but a friend of mine have problems getting the RC dpxs into Smoke.

Ideas?

[Cüneyt Kaya]

Crimson is a very easy and stable way, but a friend of mine have problems getting the RC dpxs into Smoke.

Ideas?

did he export out of RC with redlog or pdlog?

[Gunleik Groven]

I'm not sure, but I'll see into it (we'll meet). I think it may have been naming conventions playing a role, too

[Scott Simmons]

Use Crimson to pull your DPXs and you never have to touch RedCine. Then pull your list from FCP and have Smoke use the list to conform the DPXs. I theory it's relatively simple. This is the workflow for our eQ.

[I Bloom]

There is currently a bug in my Redline Render (curves coming from R3D's are all zero) you need to "Reset to Defaults" before you render to Redline.

Ian

[Gunleik Groven]

Use Crimson to pull your DPXs and you never have to touch RedCine. Then pull your list from FCP and have Smoke use the list to conform the DPXs. I theory it's relatively simple. This is the workflow for our eQ.

But I have seen better results when prep'ing the DPX render a bit in RC prior to output...

Can anyone tell me how to render a RC project in RedLine?

Gunleik

[Scott Simmons]

But I have seen better results when prep'ing the DPX render a bit in RC prior to output...

Gunleik

Gunleik; can you explain what you mean by "prep'ing"? It would seem that you wouldn't want to do any processing in RC to get the absolute cleanest DPX files for color grading if you are doing so on another system....

[Greg M]

We use Crimson to get our footage into to Smoke 2K and render DPX from Red Cine (but only because we havnt had time to play with RedLine yet)

What Gunleik was referring to by "prep'ing" is adjusting white balance, exposure, curves, etc prior to rendering, but from our experience its best to leave it all alone (with the exception of white balance) and do all the corrections inside Smoke.

[Scott Simmons]

We use Crimson to get our footage into to Smoke 2K and render DPX from Red Cine (but only because we havnt had time to play with RedLine yet)

What Gunleik was referring to by "prep'ing" is adjusting white balance, exposure, curves, etc prior to rendering, but from our experience its best to leave it all alone (with the exception of white balance) and do all the corrections inside Smoke.

Yea, that's what I was saying. The less processing on a DPX image the better for color grading in whatever you are using to do it.... at least that's my understanding.

[arythmic]

thanks so much ...
looks like crimson is the way to go

[Gunleik Groven]

What Gunleik was referring to by "prep'ing" is adjusting white balance, exposure, curves, etc prior to rendering, but from our experience its best to leave it all alone (with the exception of white balance) and do all the corrections inside Smoke.


Yes & no... :)

White balance/noise (mostly blue issues...) and checking to that most of the info is in the higher precission area. Sorta...

[Kjetil Haugen]

Crimson is a very easy and stable way, but a friend of mine have problems getting the RC dpxs into Smoke.

Ideas?

We had some problems too getting the dpx's into Flame for finishing (autodesk thing?). If you figure out what the problem is, i'd love to hear it.

[Gunleik Groven]

I'll have a sitdown at fabelaktiv one of the next weeks to try to sort things out. Fredrik probably knows the solution already, if he bothers showing up his smoke chops... :)

[o2madness]

So CineSys (http://www.cinesysinc.com) has come up with a step that allows you to import the DPX files in the right sequence order to your Autodesk Smoke or Flame after your XML from FC Pro....

You create your FCP Pro offline, then export an XML 4, you use either the FXPXMLtoRedcineXML script or Crimson to create the Redcine XML, you use it in Redcine to create your DPX files, then you use that same Redcine XML in a site called redmexican (http://redmexican.com) and that creates a DLEDL which translates it into a batch import EDL and if you use the Soft-Import preference in your EDL menu, the assemble will come up in the right way.

[dimsum]

I cannot seem to get the Smoke workflow down.

Here is what I did:

•offline in FCP 6 using the _M proxies
•export XML
•load XML into Crimson and matched files. Files "Found"
•Export Redcine XML > this sends it to the same folder that my original FCP XML is located.
•Open RedCine> Load Crimson generated XML (following Crimson's Instructions for Redcine) Save XML > Render our of Redcine
•load Redcine XML into redmexican > name path of file > generate DLEDL
•import edl to smoke > soft import

Here is where I'm having problems. Smoke will not link the media. Not sure what I'm doing wrong. Anyone out there have this down?

[o2madness]

OK, everything is perfect, the 2 things you need to check are:
1) make sure that inside RedCine you are choosing the input filename and input file numbers on the output switch so that it actually looks like $F$&.E
2) the path that you should be specifying on REDmexiCAN is the one that your Smoke uses to reach the DPX files you created. if you navigate manually through smoke and can't find that path then you need to ask your Network Admin. to mount that drive/path in your Smoke.

[o2madness]

BTW REDmexiCAN has a video now so you can see the process of importing the files using Smoke.