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

Help with Possible Workflow Changes using Subclips

flanfan

Member
Joined
Sep 18, 2008
Messages
8
Reaction score
0
Points
0
Hi all,

I'm a bit of a RED newbie, and most of my experience is cutting on Avid MCSoft, anyway. However, I was handed a RED project to cut and so far I think I've done a pretty decent job. I'm getting ready to picture lock, and I need to make sure that I've done everything properly.

I have imported the QT reference videos from the .R3D sources into Final Cut Pro 6.0.4. I have been using the _M format.

HOWEVER, and this is probably because of my Avid training, I tossed all the reference dailies into a sequence, went to my sound reels, and synced up all the clips. Then, I set in and out points, created subclips (which look like miniature sequences anyway), and have been cutting with those in another timeline. (In Avid, after creating subclips I'd autosync them all, which appears to create new files that didn't give me any headaches.)

Is this going to be a problem? I need to eventually move onto Crimson, but when I've taken a peek at the XML files my project creates, it gives me a headache. The clips are listed twice, which I believe is problematic (but might not be).

I'm not sure how to proceed. Is this fine, or do I need to find some way to go through the whole project and actually use transcoded proxies? Do I use something like Clipfinder to fix my issue?


Also, an unrelated issue. Whenever I try to export the sequence to a quicktime video, I get the green bar covering a third of the frame. DVD authoring is not a problem, though. What gives?


Sorry for all the questions, but if anybody could help me out I'd greatly appreciate it.
 
as far as the green bar when rendering/exporting, try exporting out to a different codec like prores...
 
From the cases I have looked at, the XML seems to be structured such that there is one or more <bin> branches which hold the references to the actual media, most importantly the <pathurl>.

Then there are one more <sequence> branches with <clipitem> elements somewhere down in the hierarchy. These reference the actual media via a <masterclipid>.

Thus, it is normal for the same (or very similar) names to appear multiple times in the XML. There should only be one occurrence of <pathurl> per actual clip, though.

If you are concerned that there might be problems when you move to Crimson, why not do a very small test project ? As far as I know there is a free Crimson download that will process a limited number of clips.

Finally, if you were to use Clipfinder to replace the reference files with transcoded files the XML would not be significantly different.

Cheers
Hans
 
I can see why the structure you are creating in FCP is very smart.

I think Crimson can support that XML but it may take some finagling. Why don't you send me some test XMLs and I'll see if I can help you through it.

IBloom
 
Back
Top