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

Red FCS Installer v30 - USE CAUTION!!!!

D

Dustin Cross

Well-known member
Joined
Mar 6, 2007
Messages
1,240
Reaction score
0
Points
0
Location
Austin, Texas
Website
www.sandust.com
Red,

FCS Installer v30 has completely broken the conform to _H proxy and send to Color workflow. My old project that were working now have random problem in them. Open the Color project once and it has one bad clip, open it again and it has 30 bad clips. Random every time. I thought I have fixed all the problems, but the next time I open the project a new group of clips have problems. This is INSANE!!!!!!! These projects worked perfectly before I installed v30.

The other project that was giving me problems I had to L&T all the footage and reconnect to that to get it to work. I guess I am going to have to do the same for this project now.

The problem is L&T SUCKS for working. I have a Rocket and do color work in RCX or Clipfinder and render fast for the offline edit. having to go back to L&T after I already have done the transfer is bad. It wastes time and space.

PLEASE FIX THIS ISSUE!!!!!!!

Anyone who uses Clipfinder or such to conform to Proxies and send to Color, use EXTREME CAUTION before installing FCS Install v30. Going back does not fix the problems it causes.


Dusty
 
I can confirm that I am having the same problem. It seems the TC is not being read correctly into the FCP after the XML's are made.

I'm going back to the old installer with the Beta Color plugin.


David
 
Tim,

YES. I have done lots of projects through Color. And used to use Clipfinder to Color almost daily until these problems.

These are project that were working perfectly! All the Color work was done and rendered. The director wanted to changes and now everything is crazy. Open the project and a clip is offline. Close the project and open again and that clip is back online and a totally new clip is offline, etc, etc, etc..... This is actually the fifth time this project has been rendered from Color because the director keeps changing his mind about what he wants. No problems the first four times, now its a nightmare.

Also some clips don't know their timecode now. Clips that used to work fine, now all I get is the first frame of the clip because Color gets confused about the timecode between the proxie and the R3D. Proxies on these clips haven't been changed in months.

Whatever Color does to get from the proxie to the R3D data is getting very confused.


Dusty
 
This sounds like it is possibly related to the issue we had the other day. We had proxies generated by RCX, before the most recent build, and the proxies had bad time code (created by a bug in RCX).

I don't send to Color with H proxies, always use transcodes, but my issues were very similar, I couldn't conform by time code in FCP. Solution was to regenerate proxies with build 256 and relink my old proxies with the new.

It also seems as though the newer codec that supports MX has a bug where camera created proxies of pre-MX footage loose their link to the .R3D data and constantly try to relink.

If you regenerate our H proxies into a new directory (keeping the old) and relink your clips to the new proxies, will it put your clips back into frame accuracy with in color?
 
Brandon,

I haven't tried making new proxies. These proxies are from the camera, build 17, and have been working fine since. I can try to make new proxies, in a new folder, with RCX 256 and see if that fixes anything.

Proxies I made in RCX 252 ruined a lot of stuff and there has never been a note in the release notes that that was fixed, so I have been avoiding making proxies until I see something in the release notes that that is fixed. I have had a couple Red people tell me it is fixed, but it is not in the release notes.


Dusty
 
Yes,

I have confirmed that the R3D TC being read by FCP is WRONG. So, a clip that is a 09hr TC in clipfinder or RC-X reads as a ZERO start TC in FCP.

It's sporadic so tough to find what the problem is or where it lies. I have send Hans a bunch of samples to help figure out what is going wrong.

It has something to do with how FCP is reading the metadata from the R3D.

Not sure if it is the plugin, clipfinder, fcp or the plugin yet.

David
 
David,

I don't think it has anything to do with Clipfinder.

It seems to have something to do with how the Proxies connect to the R3D files. FCP does okay, but Color does not.

Plus there was the seperate problem of proxies being created with the wrong timecode.


Dusty
 
Dustin Cross said:
Brandon,

I haven't tried making new proxies. These proxies are from the camera, build 17, and have been working fine since. I can try to make new proxies, in a new folder, with RCX 256 and see if that fixes anything.
Click to expand...

It's worth a shot and might uncover the source of the issue.

Dustin Cross said:
Proxies I made in RCX 252 ruined a lot of stuff and there has never been a note in the release notes that that was fixed, so I have been avoiding making proxies until I see something in the release notes that that is fixed.

Dusty
Click to expand...

We tested 256 generated proxies against the .R3D TC and they have been matching so far.

bk
 
David Battistella said:
Yes,

I have confirmed that the R3D TC being read by FCP is WRONG. So, a clip that is a 09hr TC in clipfinder or RC-X reads as a ZERO start TC in FCP.
Click to expand...

This is how the faulty proxies appeared as well... 0 hour TC.
 
Dustin Cross said:
David,

I don't think it has anything to do with Clipfinder.

It seems to have something to do with how the Proxies connect to the R3D files. FCP does okay, but Color does not.

Plus there was the seperate problem of proxies being created with the wrong timecode.


Dusty
Click to expand...

Regernerated QT's in CLipfinder is not working for me at this time.

David
 
David Battistella said:
Regernerated QT's in CLipfinder is not working for me at this time.

David
Click to expand...

If clipfinder uses Redline, wouldn't that create the same issue if redline is causing the proxies TC to be bad? Just a thought. Are you on redline 256?
 
Found it Brandon and by regenerating the wrappers this way it is indeed fixed.

David
 
Brandon Kraemer said:
If clipfinder uses Redline, wouldn't that create the same issue if redline is causing the proxies TC to be bad? Just a thought. Are you on redline 256?
Click to expand...

I had initially recreated the wrappers in CLipfinder and this appears to be broken as those wrappers were creating the ZERO start time clips.

Now I see the code from the clips with no issue after creating the wrappers in RCX.

Lots of clips (going back to build 15) to start re-wrapping. Can anyone write a small script for this?

David
 
David,

I can write a small script to use REDline, but if Redline is still broke....

If you need to use RCX 256, then it might be easiest to bring the clips into Clipfinder, send to RCX, make proxies (wrappers) from there.

If REDline 256 is working for making Proxies here is a script:

for FILE in $(find /Volumes/Fileserver/DELETE/* -name *_001.R3D 2>&1 | awk -F "_001.R3D" '{print $1}'); do redline -i `echo $FILE"_001.R3D"` -w 10 --useRSX 2 -o `echo $FILE` ; echo "Finished with $FILE" ; done

You will need to change where it searches for your R3D files. /Volumes/Fileserver/DELETE/*

If you don't want to overwrite the existing proxies, use this one. Just change the /Volumes/Fileserver/DELETE/ to where you want it to write the proxies.


for FILE in $(find /Volumes/Fileserver/DELETE/* -name *_001.R3D 2>&1 | awk -F "_001.R3D" '{print $1}'); do redline -i `echo $FILE"_001.R3D"` -w 10 --useRSX 2 -outDir /Volumes/Fileserver/DELETE/PROXIES/ -o `echo $FILE` ; echo "Finished with $FILE" ; done


I just tried this script and it doesn't work. Not sure why, but Redline only does the first file and then hangs. I don't think I typoed anything. I know Hans was saying he is having problems with the new Redline.


Dusty
 
Anyone from Red have a reason why this script only does the first file and then hangs? Something seems to be wrong with Redline.

if I change out "do redline" with "do anything" else it works fine.

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