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

Problem> Crimson - RedCine: FAILED TO LOAD CONSTRUCT

F

Fang

Member
Joined
Aug 2, 2008
Messages
15
Reaction score
0
Points
0
In need of urgent help. This is working fine last week.

When I go to load my XML I created in Crimson into RedCine, it doesnt load properly. I get the error "FAILED TO LOAD CONSTRUCT"

Tried the "ADD VOLUME" tip in crimson, had no effect.

Any tips appreciated.
 
I had the SAME problem and fixed it following the troubleshooting on redhax (the link Ian posted above).

Let us know if you get it working.
 
Thanks guys, will try all this today and let you know how I go.
 
Hi guys, that "redcine reset" link is down. Anyone got another download link?

So read that article. Is this is the solution?

"Solving the Problem

In the Intermediates tab in Crimson Workflow, there is a section entitled Troubleshoot Cowboy Intermediate. Enter the name of your boot drive: the boot drive is by default /Volumes/Macintosh HD/ but users often change the second part. If you notice that there are repetitions in the Redcine XML enter the number of Repetitions in the cycle box. (If you put /Volumes/MyDrive/ and cycles 3 for example, you will be adding the prefix /Volumes/MyDrive/Volumes/MyDrive/Volumes/MyDrive/ ) Finally select the Add Prefix checkbox. "

I checked the box and the same problem occured. Any more tips? Do I have to actually edit the xml or rcn file?

Thanks
 
Ok so:

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
 
This seems to work. Cheers Ian. A lot easier to undertand than the wiki btw!
 
Hi
I have the same "failed to load construct" problem.
But my problem is of a different flavor, I think.
I have 6 reels that need to be exported to DPX with Redcine. I use Crimson and Redcine for the job and get very (!!!) weird result. Some reels went very smooth - FCP XML into Crimson, create intermediate and new XML, load footage and XML into Redcine.
But, some reels simply refuse to load in Redcine. I take the same steps, and nothing. The really weird thing, is sometimes after several tries, it suddenly works, and I don't even know why.

All my files sit on a SAN, including the FCP project and all XMLs and intermediates. So the Crimson fix suggested above doesn't apply. On top of that, I compared between the Redcine and Crimson XMLs and they point to the same path.

Right now I have one more reel to go, and simply cannot do it. I split the reel in 2, and in 3 to try to single out a bad file or something but nothing works!

Has anyone got any suggestions?
Thanks
 
I have run into the "failed to load construct" a few different times. On thing to check is your clip names in FCP. They can't contain any strange characters that will confuse the XML parser in RedCine. For Example, it really doesn't like commas.

Another helpful tip is to check the RedCine log file. This will sometimes point you in the right direction.

RedCine log file located:

BootDrive(Macintosh HD) > Library > Redcine > Settings > logs > Redcine.log

Drag the Redcine.log file to a text editor and look for errors.

Hope this helps.
 
No. The file name underscore characters seem to be fine. The problems I ran into were from characters entered inside the Final Cut Pro application. If you use commas, percent, dollar signs, etc. in clip names inside Final Cut Pro they are passed into the XML, then through Crimson without error. But they fail when interpreted by RedCine. I have seen the "Fail to Load Construct" when it hits one of these characters if it is in the Clip name of the XML file. ie. <Clip name=" , % * ">

Make sure your clip names in FCP are standard characters. I know commas will cause this problem.

or

Look at your XML file in a text editor and look at the portion of the file that is <Clip name="______"> Then go back to FCP and change the offending characters. This solved our "Fail to Load Construct" problem.
 
Hi,

I have a similar problem. I created a xml file with fcp and used it with crimson to create a redcine xml. That works fine but now I can´t open the redcine xml in redcine..."Failed to load construct" I tried Ians solution but it didn´t work. I ´ve also checked the characters...everything is fine. But I can´t open the xml in redcine.

Furthermore I can´t open a lot of crimson intermediates. I have a short film with 10 minutes length. If I want to open the complete film/intermediates from the crimson workflow folder redcine crashes and I can´t open it again until I have deleted redcine.log. I just can open scene by scene but not more then one scene rather the complete film.

Can u help me plz to fix this problem especially the problem with the xml files.

Thanks a lot,
Ben
 
With latest RedCine release the xml format is cahanged.
"slot_name" node is replased with node "Slot" and end tag is in new place.

If this is the case, open your xml in text editor and make the changes manually.

Priit
 
I tried that but it didn´t work. Maybe I did something wrong but I don´t think so. Do you have some other ideas how I can fix this?
 
You can send the xml file to priit<at>joosti.ee
I will try to change it.

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