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

New Color 'loop bug' work-around

Nick Shaw

Nick Shaw

Well-known member
Joined
Dec 28, 2006
Messages
1,515
Reaction score
0
Points
0
Age
56
Location
London, UK
I have found a new workaround for the send to Color 'looping' bug, which I think is an improvement on the EDL approach, although it requires a bit of manual input. Maybe it could be automated in Clipfinder (Hans?)

The method is:

1. Offline using your preferred method - proxies, ProRes from REDrushes, Avid, whatever…

2. When the cut is locked, use Clipfinder (in combination with Automatic Duck if you offlined on Avid) to create an FCP time-line using the _H proxies, and then 'send to Color'.

3. In Color make a list of the shot numbers of the clips with the looping problem (the ones that don't have the issue can be left alone.) This is the manual pencil and paper bit!

4. Close Color and go to the Color project file in the Finder, and 'show package contents'.

5. In the 'Shots' folder in the package open the folders for all the clips in your bug list and open the .si files in a text editor. These files are xml files, so all you need to do is make the following changes:

- Replace "_H" with "_001.R3D" in both "<name>" lines - correction, actually only the first one is necessary

- Change "<ext>.mov</ext>" to "<ext></ext>"

- Change the format line to read "<format>R3D</format>"

6. Grade as normal, then 'send to FCP'.

I personally do the grade at 2k, then use Shake to scale the finished edit to the deliverable size, as I do not find the scaling in Color's geometry room to be of satisfactory quality, but whatever works for you…

I have not tested yet what happens if you re-conform a changed edit in Color, so use at your own risk!

I have just successfully graded a pop promo, which was cut on Avid, using this approach and had no problems. If anybody is interested, you can see it here:

http://www.youtube.com/watch?v=FB_XxaZ_1I0
 
I agree it's far from ideal to have to do this kind of thing, but bear in mind you only need to do it for clips which actually cross the span during the shot used in the edit. In the pop promo I mentioned I only had to do it for 6 events in the edit, and virtually all takes spanned multiple R3Ds.

Hopfully Apple will fix the issue some time soon. But given that sending proxies to Color is not an officially aproved method, and Apple have been very slow to fix known bugs in Color before, I'm not holding my breath. Hence the work around for now.
 
5. In the 'Shots' folder in the package open the folders for all the clips in your bug list and open the .si files in a text editor. These files are xml files, so all you need to do is make the following changes:

- Replace "_H.mov" with "_001.R3D" in both "<name>" lines

- Change "<ext>.mov</ext>" to "<ext></ext>"

- Change the format line to read "<format>R3D</format>"
Click to expand...

I'm pretty sure you can use automator or applescript to make a program to do this. Instead of doing that to only the shots with problems, if you're automating the process you can do it to all the shots. I'll give it a shot as this would be a huge help in making the proxy workflow to color doable.
 
NOTE: I have made a minor correction in step 5 of my workflow (italicised)
 
zak forrest said:
I already edit with H proxies so the Clipfinder feature that replaces with H proxies is unnecessary for me.

So how will the new version of Clipfinder help exactly?
Click to expand...

You will be able to 'send to Color', then run Clipfinder which will 'fix' the Color project so you can grade without getting the looping bug. I am testing an alpha version of Clipfinder which has this feature enabled, and so far it looks good.
 
Hans,
Thanks for keeping me from having to learn applescript/automator to make this work.

Love your software, it's that perfect helper app. that makes everything else run smoothly.
 
Instead of doing steps 4-5 manually, I was able to use a free program called "TextWrangler" to do a search and replace across multiple files. The trick is to create an alias of the shots file and place it on your desktop so TextWrangler can search through the package contents.

Worked perfectly until the new version of ClipFinder is out.
 
Nick Shaw said:
You will be able to 'send to Color', then run Clipfinder which will 'fix' the Color project so you can grade without getting the looping bug. I am testing an alpha version of Clipfinder which has this feature enabled, and so far it looks good.
Click to expand...
It's an amazing software :)
 
can anyone help with the process of using clipfinder to fix the 'loop' problem? i'm in the middle of trying this right now and am not having success...
thanks!
 
Ricardo Mehedff said:
can anyone help with the process of using clipfinder to fix the 'loop' problem? i'm in the middle of trying this right now and am not having success...
thanks!
Click to expand...
Sent you a PM.
 
Thanks so much for your effots guys,
Although I'm trying to use clipfinder for a 60 seconds commercial and it's rendering the whole of each and every shot. About an hour of footage:
At 3 frames/second (8-core@3.0Ghz) the total of 76.000 frames put me on hold until tomorrow!
I wished I could only render what I'm using, as if it was some sort of media managing with handles.
Anyway following the post is really interesting and we all appreciate your collaborative work!
 
You must log in or register to reply here.
Back
Top