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.

I wish you many customers, Ian. You can count on me being one of them.
 
Our first day out we are having some problems. I've been on various forms of electronic communication all day. We'll work em out.

Please refrain from purchasing until the demo is working for you.

IBloom
 
I purchased the software minutes after the announcement yesterday... Without using the demo first...

I trusted Mark from Offhollywood's glowing praise about how kick ass this solution was, so I just whipped out the credit card! :)

Glad I did.

So all that said, I had some issues once I actually used the software:

I was able to properly load the FCP XML and match my proxy footage to the R3Ds. I was able to make 'Intermediate' R3D files and export a RedCine XML.

Trying to load that RedCine XML stopped the show cold. 'Failed to Load Construct' error.

I joined the CrimsonWorkflow forum and found that there were a few others with the same problem. I posted my experience and got a phone call from Ian. We iChatted for about an hour today trying to nail down the issue.

Solved the issue.

Not sure whether Leopard is the issue, but as long as your intermediates are stored on your internal system drive, there's a weird path thing where RedCine can't load the intermediates. If you store the intermediates on an external drive, the full path is notated in a way that RedCine likes, and your timeline will load.

Here's another tip that Ian wanted me to pass on... When you load all the footage in RedCine, make sure you load the intermediate files, not the original R3Ds before loading your timeline.

Ian is great, and the software is very powerful. Can't wait to get the documentation, but already I can properly and accurately conform my edits.

Great job and great service Ian!
 
Hi guys,

I'm just wondering.... with these lastest directions I managed to get RED intermediate files and the XML into REDCine and my edit is there, great !!

But, and please correct me if I'm wrong or just plain stupid:usd: .. what I don't understand is: why I'm I importing the intermediates into RedCine and not the original R3D files..? I'm I skipping a step?

Thanx..
 
Martinez said:
But, and please correct me if I'm wrong or just plain stupid:usd: .. what I don't understand is: why I'm I importing the intermediates into RedCine and not the original R3D files..? I'm I skipping a step?

Thanx..
Click to expand...

You are not stupid. The term "intermediates" is a bit mis-leading. They are "clever" aliases to the .r3d files. If you look at the "intermediates" - you will see they are alias files.
 
kenn michael said:
Great job and great service Ian!
Click to expand...

Kenn is the best possible customer. Thanks for your help and patience dude. I'm moving Redline renders to read directly off the matched files, so intermediates will only be used for Redcine. That will make the next build alot more robust. And I'm working out issues with "no intermediates". In this case, it won't be pretty when you go into Redcine, but you will get the job done.

Rebooting the system before you generate a "Cowboy" intermediate, (they are special aliases, a little deeper than Finder aliases) often helpful when Redcine or RedAlert won't recognize linked files.

IBloom
 
Respect!!:matrix:

I can truly say that Crimson is the first real working solution to a reliable workflow (atleast for us, doing the finishing and grading on Quantel IQ)

Good work!
 
Uhm...oh oh. Help!

For some reason Crimson has no intention of working today... I have already reinstalled and rebooted my iMac, but without any results.

Any suggestions..??
 
Great! Thanx
 
Ian, I am extremely excited about what you are doing here! I'm building me a new Mac Pro system and a big reason is so I can get up and running with your Crimson. A few questions I have though.

In order to do the whole FCP->Crimson->RedCine->2kDPXSeq->AfterEffects(for cc/grade using colorista and fx)...does this mean that when cutting in FCP I have to avoid doing anything in FCP except plain cuts? Obviously I wouldn't do any visual filters, that would be saved for AE, but does that mean no transitions? No garbage mattes, overlays, etc.? It seems FCP becomes just a grunt assembler. Is this true?
 
Shawn Nelson said:
Ian, I am extremely excited about what you are doing here! I'm building me a new Mac Pro system and a big reason is so I can get up and running with your Crimson. A few questions I have though.

In order to do the whole FCP->Crimson->RedCine->2kDPXSeq->AfterEffects(for cc/grade using colorista and fx)...does this mean that when cutting in FCP I have to avoid doing anything in FCP except plain cuts? Obviously I wouldn't do any visual filters, that would be saved for AE, but does that mean no transitions? No garbage mattes, overlays, etc.? It seems FCP becomes just a grunt assembler. Is this true?
Click to expand...

Crimson is very good at ignoring all of the complicated things people do in Final Cut Pro. It takes your FCP sequence XML and tries to figure which clips are referencing R3D and allows you too manipulate those clips, then on roundtrip, it reinserts the newly rendered clips into an FCP XML.

As I get closer, I will use the same technique for Avid, Premiere and CMX3600 EDL.

That being said. Your life will always be better and easier if you keep all your source video on track 1. That's a good habit to have as an editor anyways.

As far as getting image sequences into After Effects goes, it's difficult, currently you could make it work with Crimson, perhaps if you had both Glue Tools and Automatic Duck. Crimson would then take care of the first part....Finding R3Ds and onlining them.

All I can say for now is.
I want this too.

Ian
 
So what's Next...?

So what's Next...?

Ok so I've got my xml out of FCP and done the intermediate thing. Then I've managed to confiorm my sequence in Redcine (I was getting the failure to load construct thing until I realised you have to import all of your aliases and then import the redcine xml....But hey I was assuming you open redcine, open xml from crimson - what with there being no instructions and all!)

So what happens now? Those that have said they have it working what do you do - export a redcine xml? Fumbling in the dark for now - Ian how long till the rest of your tutorial vids are online? A list would be good for now like:

1 Export xml from fcp sequence.

2. Import xml into crimson.

3. Match your files to the source R3ds

4. Export a redcine xml, with or without handles.....

Anything for now would be great. I've never been one for Religious/Pagan festivals and I've got the weekend to play before a couple of big jobs.

Loving the app and will pay as soon as I know how it works and that it does actually work!

Thanks in advance.

Jeff Brown
#708
 
ibloom said:
As far as getting image sequences into After Effects goes, it's difficult, currently you could make it work with Crimson, perhaps if you had both Glue Tools and Automatic Duck. Crimson would then take care of the first part....Finding R3Ds and onlining them.

All I can say for now is.
I want this too.

Ian
Click to expand...

Whoa, why would automatic duck be involved? I want to take the seq from RedCine into AE via 2kDPX. Dang it, that's what I'm aiming for. I guess I could always loose that it's a seq and just export the seq into AE.

Will you be adding the ability to go from RedCine out to AE? with the seq in tact?
 
Jeff Brown said:
Ok so I've got my xml out of FCP and done the intermediate thing. Then I've managed to confiorm my sequence in Redcine (I was getting the failure to load construct thing until I realised you have to import all of your aliases and then import the redcine xml....But hey I was assuming you open redcine, open xml from crimson - what with there being no instructions and all!)

So what happens now? Those that have said they have it working what do you do - export a redcine xml? Fumbling in the dark for now - Ian how long till the rest of your tutorial vids are online? A list would be good for now like:

1 Export xml from fcp sequence.

2. Import xml into crimson.

3. Match your files to the source R3ds

4. Export a redcine xml, with or without handles.....

Anything for now would be great. I've never been one for Religious/Pagan festivals and I've got the weekend to play before a couple of big jobs.

Loving the app and will pay as soon as I know how it works and that it does actually work!

Thanks in advance.

Jeff Brown
#708
Click to expand...

Jeff 0.8.3 should be up tonight. Many solid bugfixes in there and REDline seems to be working alot better. I'm juggling between coding and trying to explain how it works...

Once you've gone through those first four steps, you can render in Redcine or REDline and then your files should match up to what are listed as output files in Crimson. The output files are what will be reinserted into your Final Cut Pro Sequence when you make a Roundtrip XML, I hope this helps.

Shawn Nelson said:
Dang it, that's what I'm aiming for.
Click to expand...
Such language, this is a public forum Shawn.

Ok I'm hearing you loud and clear. If, you export to DPX or TIFF using REDline you will have many folders with image sequences within them. If you transfer in and out points to your render you can import those sequences into AfterEffects in the event order one after the other.

Automatic duck would be needed to export a complicated FCP timeline into After Effects, but I will look into some limited direct support for After Effects, if all you want to do is send a sequence from Redcine into After Effects, I think that can be done. No promises.

Get 0.8.3 Tonight or a little bit later and play with it.

IBloom
 
You must log in or register to reply here.
Back
Top