Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

Crimson Workflow is available for download.

iBloom? How are things coming with avid xml support? And will crimson by end of May be able to load r3d files without the FCP xml step? I'm actually more exited about crimson now than build 16 and new versions of redcine...
 
Okay, so I'm making my first attempt at a Crimson workflow with a short I shot two weekends ago. I rendered all the _M.mov as ProRes proxies into a new directory and pulled them all into FCP. Problem! All the 3k _M.mov are a different resolution and now FCP isn't happy on the timeline and redlines them all for re-rendering. Do I just bite it and render them or is there a better thing to do?
 
Kjetil Haugen said:
iBloom? How are things coming with avid xml support? And will crimson by end of May be able to load r3d files without the FCP xml step? I'm actually more exited about crimson now than build 16 and new versions of redcine...
Click to expand...

Hmmm, build 16 is gonna be pretty great, I'm pretty damned excited about that :)

Avid doesn't support Avid XML so what's your rush ;) EDL support is in the works. I'm rebuilding the internals right now to be alot smarter and more flexible. In programming terms this is called adding a "layer of abstraction". I decided this was a smart thing to do as I was implementing EDL's. You will like the results, Crimson 1.0 has a little bit of 2.0 deep inside. "When" is a good question though? End of May is my personal deadline to reach and feature lock Crimson 1.0

Shawn Nelson said:
Okay, so I'm making my first attempt at a Crimson workflow with a short I shot two weekends ago. I rendered all the _M.mov as ProRes proxies into a new directory and pulled them all into FCP. Problem! All the 3k _M.mov are a different resolution and now FCP isn't happy on the timeline and redlines them all for re-rendering. Do I just bite it and render them or is there a better thing to do?
Click to expand...

You could go back and rerender the 3K prores using geometry parameters in compressor to rescale the footage to 1K or 2K instead of .75K or 1.5K. Thus matching everything on your FCP timeline. This won't effect your Crimson stuff later. (Tip: Learn to make compressor droplets. They are the sh!t.)

IBloom
 
ibloom said:
You could go back and rerender the 3K prores using geometry parameters in compressor to rescale the footage to 1K or 2K instead of .75K or 1.5K. Thus matching everything on your FCP timeline. This won't effect your Crimson stuff later.
Click to expand...
Sweet! Thanks man. That was my hunch, but didnt know for sure. I already separated out my footage into 4k and 3k bins. Btw, it'd be awesome for others to show how their directory structure goes. Here's mine:
[Proj]
---->[Day_01]
----------->[4k]
--------------->[A007_901228.RDM]
----------->[3k]
--------------->[A008_901228.RDM]
----------->[1k_proxies] (these are the generated 1k ProRes files I will be editing from)
---->[Day_02]
----------->[4k]
--------------->[A009_901228.RDM]
----------->[1k_proxies] (these are the generated 1k ProRes files I will be editing from)

See any potential problems? Or is this dir structure good?

Now I must learn what a compressor droplet is...
 
Okay, so my 1kProxies directory now holds a ton of 1k ProRes files that look like this for 4k origination
A002_C002_901228_M-Apple ProRes 422 LQ.mov

and this for 3k origination
A002_C005_901228_H-Apple ProRes 422 LQ 3K.mov

After I chop away Crimson will do fine with this? Is there anything else I could be doing now to make things easier at the back end?
 
Shawn Nelson said:
Okay, so my 1kProxies directory now holds a ton of 1k ProRes files that look like this for 4k origination
A002_C002_901228_M-Apple ProRes 422 LQ.mov

and this for 3k origination
A002_C005_901228_H-Apple ProRes 422 LQ 3K.mov

After I chop away Crimson will do fine with this? Is there anything else I could be doing now to make things easier at the back end?
Click to expand...

You can just tell Crimson what drive your stuff is on and set the search depth to unlimited. And your done. Directory structure is not important.

Try the attached droplet with one _H or _M proxie from a 3K file. I think it will force it to 1K.

http://www.reduser.net/forum/uploaded/582_1209539403.zip

IBloom
 
Hi Ian,
does crimson work with color yet? in other words, can i cut offline in the fcp, go to redcine to export dpx files, then roundtrip to color (do the cc) then send to fcp?
thanks!
 
ricbrazil said:
Hi Ian,
does crimson work with color yet? in other words, can i cut offline in the fcp, go to redcine to export dpx files, then roundtrip to color (do the cc) then send to fcp?
thanks!
Click to expand...

It can be done using the AJA wrappers. But it's not automated. Not a priority form me, considering Apple is clearly working on a better solution, R3D directly in color.
 
Ian, is it possible to conform in Crimson from a timeline which was cut with material imported into FCP with the new Log & Transfer plugin ?

thanks
Manuel
 
manuelwenger said:
Ian, is it possible to conform in Crimson from a timeline which was cut with material imported into FCP with the new Log & Transfer plugin ?

thanks
Manuel
Click to expand...

Apparently there is a bug their currently. If you want to send me an XML from that kind of timeline, I'll see if there is a quick fix for it.

Ian
 
Ian, I tried to do my first roundtrip and got buggered up. It was simple, three straight files, only cuts. In theory, the damned simplest thing I could have done. I got these errors.

Fri, May 9, 2008, 7:34 PM - Errors Found Importing Night_roundtrip.xml
sequence item: Required element <name> not found for sequence item definition( line 372 )
sequence item: Required element <name> not found for sequence item definition( line 466 )
sequence item: Required element <name> not found for sequence item definition( line 561 )
sequence item: Required element <name> not found for sequence item definition( line 660 )
sequence item: Required element <name> not found for sequence item definition( line 754 )
sequence item: Required element <name> not found for sequence item definition( line 849 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 372 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 372 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 372 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 466 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 466 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 466 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 561 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 561 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 561 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 660 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 660 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 660 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 754 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 754 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 754 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiolevels".( line 849 )
<clipitem>: Unable to get audio <clipitem> for <effect> "audiopan".( line 849 )
<clipitem>: Unable to get video <clipitem> for <effect> "video".( line 849 )
 
Im also getting green lines above the rountrip sequence, indicating rendering required, is this normal?
 
Shawn Nelson said:
Im also getting green lines above the rountrip sequence, indicating rendering required, is this normal?
Click to expand...

Those messages are non-critical, they just have to do with things like audio not seeing all of the original proxies. It's something that I'm working on, but not mission critical.

You will need to change your sequence settings to match whatever codec you transcoded to.

I have an entire forum for this kind of help Shawn, http://www.crimsonworkflow.com/forum

Ian
 
Will it be possible in the future for crimson to load the rsx color data file generated by redalert? And... will crimson be independant from fcp xml, loading a list of r3d's for rendering without matching proxies first?

Keep up the good work!
 
Kjetil Haugen said:
Will it be possible in the future for crimson to load the rsx color data file generated by redalert? And... will crimson be independant from fcp xml, loading a list of r3d's for rendering without matching proxies first?

Keep up the good work!
Click to expand...

Maybe on first one. Depends if there is a better way.

Yes on second one.

IBloom
 
ibloom said:
Maybe on first one. Depends if there is a better way.

Yes on second one.

IBloom
Click to expand...

Would be great with a checkbox in the color tab where we can select either rsx-data (if present) or metadata. That way all our great coloring work in redalert will not go to waste :biggrin:
 
Kjetil Haugen said:
Would be great with a checkbox in the color tab where we can select either rsx-data (if present) or metadata. That way all our great coloring work in redalert will not go to waste :biggrin:
Click to expand...

Makes sense. But if you could do everything you can do in RedAlert in a more project oriented environment, you'd do that instead right?

IBloom
 
YES!!!!!
Actually just sidetripping RedCine would be lovely!

I think if you implemented preview functionality into Crimson, I wouldn't upgrade to build 16 before Crimson was ready....

And than - of course, if you could just send your gluetools dpx directly into a FCP project or color or whatever with a correct edl from Crimson

Or does that perhaps not make sense?
 
You must log in or register to reply here.
Back
Top