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 :)

Crimson Workflow on MAC PRO

higtonfilm

Member
Joined
Apr 28, 2007
Messages
18
Reaction score
0
Points
0
Hi!

I'm experiencing problems with the Crimson workflow on my mac pro. I have tested this on another mac pro, and the same thing seems to happen.

After loading all the intermediates into redcine, the problem starts when I open the telecine xml exported from crimson. It gives me the failed to load construct. I have tested with less clips in the xml, but it still gives me this error.

However, on the macbook pro it works smoothly, but it takes a year and a half.

Do you guys have any advice on what i need to do to make it work?

Thanks!

Andrew Higton
 
It could be because of the default intermediate location is not working, I always reset it to somewhere that doesn't have the privilege issue like the RAID storage and don't running to issues.
 
It could be because of the default intermediate location is not working, I always reset it to somewhere that doesn't have the privilege issue like the RAID storage and don't running to issues.
I have the same problem and I tried different locations as well .. I even phoned ian bloom and he mentioned something about the way crimson constructs the intermediate but thats all what i got

The application was working fine before I purchased the license and now after i tried many locations, alternatives etc, it gives me the failed to load construct .. it's a double frustration !!

I'm trying to be a fan but I found a total lack of support

thanks

luc
 
Do you have any spaces or special characters in your volume/file/folder names? Avoid them!
 
These are the instructions for troubleshooting cowboy intermediates:

1. Load your intermediates into Redcine

2. Export an XML file from Redcine by changing the file extension to XML in Redcine as you save a project.

3. Look at the XML file from Redcine in a text editing program.

4. Look at the XML file from Crimson in a text editing program.

5. Look at the difference between the <source> tags between the two files.
For example-
Crimson says: /Users/RogerCorman/Documents/...
Redcine says: /Volumes/Macintosh HD/Users/RogerCorman/Documents/...

So to get Crimson on the same page as Redcine we need to add the prefix "/Volumes/Macintosh HD" to every file reference that Crimson is creating.
6. Go into Crimson.

6. Type the prefix that you need into the box labeled "what is the name of your boot drive"

7. Check the box to enable adding the prefix.

8. Regenerate your _telecine XML

9. Return to Redcine and attempt to load the construct.

I hope this helps.

IBloom
 
I've been having the exact same issue. Ian has been very supportive in trouble shooting, however we have not been able to solve the issue. The only difference that we could come up with was a fps issue. I still have not been able to resolve the issue. The one workaround that I've found is to use crimson/redcine on the macbook pro, load the intermediates, load the telecine file, save the crimson project and then open it on my mac pro. Then it functions fine for colorgrading and transcoding the clips.
Cheers,
Jeffrey
www.jeffreybrown.com
 
Jeffrey,

Just to check what's been done:
Have you gone through the instructions above?
Have you tried manually changing the sequence framerate in your _telecine XML?

If both of these aren't working I'd like to look deeper at your specific problem.

Ian
 
OK, tested it. It worked. This is what i had to add to the prefix.

/Volumes/Macintosh HD/Volumes/Macintosh HD

Btw, Ian. What is the exact amount of clips redcine can handle using crimson? And is there a limit to clips using the redline feature in crimson?
 
OK, tested it. It worked. This is what i had to add to the prefix.

/Volumes/Macintosh HD/Volumes/Macintosh HD

Btw, Ian. What is the exact amount of clips redcine can handle using crimson? And is there a limit to clips using the redline feature in crimson?

I don't know the exact amount unfortunately. I think its around 100 2GB chunks.
 
That sounds about right to me, roughly 100 individual R3D files (as opposed to complete takes comprising multiple R3D files).

Be great to get that limit raised to pretty much infinite clips, but in the meantime I'm simply splitting up my timelines into acceptable length chunks - fine for short form, but wouldn't want to do a feature that way!
 
Im going to be doing a feature next year, what workflow for exporting files is recommended? I do not wanna cutting up 90 minutes in 50 different xml files :) You guys have any experience with red feature work?
 
hi i did everything is described and nothing....
i cant; cosntruct, redcine shows the shots but i cant
conform my FCP edit and go back to FCP... any other advice?
 
Manually changing timecode in telecine.xml

Manually changing timecode in telecine.xml

Hi Ian,
I manually matched up the TC's between the Redcine XML and the Crimson telecine xml and that seems to have eliminated the "failed to load construct" error on the Mac Pro.

When using the Mac Book Pro I do not have to do the manual timecode match. Any chance of a bug fix for the Mac Pro in your next version?

Also curious to know when we might see avid support. My favorite editing shop in NYC is Avid only.

thanks,
JB
 
Back
Top