Red FCS Installer v30 - USE CAUTION!!!!

[Dustin Cross]

stay on track

Technically I think this thread drifted from FCS v30 that I started with to problems with Redline, but it is all useful information.


Dusty

 

[Steve Sherrick]

Technically I think this thread drifted from FCS v30 that I started with to problems with Redline, but it is all useful information.


Dusty

:biggrin:

 

[David Battistella]

OK.

Diverting a bit one more time but all relevant.

The 257 build of REDLINE works in terms of making sure Clipfinder creates correct XML's for offline to online workflow, but it is broken in terms of being able to render any files using Clipfinder.

I got a kind e-mail from Hans this afternoon detailing the amount of work involved in getting all of this implemented. He's on it, but it will take some time.

I have faith in him and the RED team.

RED can you help Hans out, he's created a really great tool?

David

 

[Gavin Stokes]

Have you guys found my problem of old projects that worked, not working with the new FCS v30 installer? Everytime I open the project different clips are broken.

Even after regenerating the reference movies? It's quite mysterious that the new plug-in would break old projects; the interface between Color and our framework doesn't change unless Apple changes it. One hurdle is that we don't have any broken projects to test (I PMed you while back asking for one; I know PMs are easy to miss).

I sympathize with your aggravation over the broken projects. If regenerating the reference movies with the revised tools and a script fixes them, this is the way to go. If this does not fix it, and you anticipate having to re-do a lot of old work, let me know. Obviously we want to devote engineering resources where they're going to pay off the most. From your reports, we've found and fixed two bugs that seriously impaired workflow. It's important that people install the new tools, to avoid creating even more corrupt projects with the old ones.

What is the difference between telling redline to --exportPreset or manually inputting exerything in redline?

If I manually put everything into Redline --silent works

If I use --exportPreset I get lots of output even with --silent

This may be just a bug that's triggered by the use of that command-line option. I'll run this by our Redline guy and see if he can find a problem.

 

[Dustin Cross]

Gavin,

I haven't made new wrappers yet because I don't want to overright the old ones yet and not sure I can get Color to reconnect to wrappers in a totally new location.

I don't want to loose all the Color work that has already been done.

Do you want me to send you a Color project to look at? Will it be useful without footage?

I was mostly wondering if you guys have been able to recreate the problem?


Dusty

 

[Kaku Ito]

Lately Hans hasn't post things directly here because he thinks it would violate the forum code since Clipfinder is not free anymore, then he has to be the sponsor to be able talk about Clipfinder. I can see this is influencing the amount of communications. Jarred, can you give him a hand in this because without Clipfinder, we are short handed with the workflow at this point? Man, how much is the banner? I'd pay for it if he can come on and help us online.

 

[David Battistella]

Gavin,

I haven't made new wrappers yet because I don't want to overright the old ones yet and not sure I can get Color to reconnect to wrappers in a totally new location.

I don't want to loose all the Color work that has already been done.

Do you want me to send you a Color project to look at? Will it be useful without footage?

I was mostly wondering if you guys have been able to recreate the problem?


Dusty

Dusty,

When I tested today I did it on a small archived project and it was fine in re-connecting. Can you run a small test?

If it is a B21 to B30 project I would be cautious because the B21 shots are going to be processed and have to be re-graded.

I had no problem reconnecting the files. I can run a test on another archive project tomorrow if you like?

David

 

[Brandon Kraemer]

Gavin,

I haven't made new wrappers yet because I don't want to overright the old ones yet and not sure I can get Color to reconnect to wrappers in a totally new location.

I don't want to loose all the Color work that has already been done.

Dusty

Dusty, you might try the following...

Recreate proxies in new directory. In FCP re-connect to the new proxies. Send to Color, Re-conform old color project to new sequence from FCP.

That might be all it takes, but back up before you try. Save all your grades as they are on your color timeline too.

 

[Gavin Stokes]

I haven't made new wrappers yet because I don't want to overright the old ones yet and not sure I can get Color to reconnect to wrappers in a totally new location.

You could try copying your entire project to a new location, then regenerate (and overwrite) the proxies in the copy and see if it works.

I was mostly wondering if you guys have been able to recreate the problem?

No; once we identified the timecode bug and you verified that the fix for it resolves your problem, there was little to gain by attempting to recreate the problem. What result would you expect to see from doing so?

 

[Matthew Yaeger]

What is the difference between telling redline to --exportPreset or manually inputting exerything in redline?

Using --exportPreset will load settings first from the export preset and then override settings in the preset with the arguments on the command line.

If I manually put everything into Redline --silent works

If I use --exportPreset I get lots of output even with --silent

--silent has nothing to do with presets, however it does look like silent was not being passed along for quicktime and avid exports (bug).