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!!!!

Brent,

Thanks.

I just noticed I was using -i instead of --i but Redline seems to work the same either way.

with --verbose on, it seems to do the first clip just fine and then hangs. Like it is waiting for something to tell it it is done.


Dusty
 
Gavin,

I am not sure what problems Hans was having. I know he had to write a special version of Clipfinder just for the new Redline. Plus now if I do anything that requires redline from Clipfinder it runs tons of instances of redline and kills my system, even for something as simple as making proxies.

I assumed Hans was talking to you guys.


Dusty
 
Dustin Cross said:
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.
Click to expand...

In the event you might need to reference a previous (albeit incorrect) version of the tc proxies, my 2 cents says do not delete, but label them as bad and the new as new. note what version of redcinex/redline you are creating them under. I actually had to jump back to the bad to pull in an edl.
 
Gavin,

Just tried making some wrappers from Clipfinder with Redline 256 and I get new wrappers, with correct timecode, but I also get a redline process that doesn't go away for each clip. I can kill the processes. but ti stays using memory.

Are you guys at Red seeing this same thing or am I doing something wrong?


Dusty
 
Dustin Cross said:
Are you guys at Red seeing this same thing or am I doing something wrong?
Click to expand...

We see it too. Redline is indeed hanging up after the first clip, and we're working to fix it right now. It sounds like this is what Clipfinder was trying to work around. I wonder if Hans tried to report that bug...

So, if I've absorbed the state of affairs correctly, the version-256 builds of RCX and Redline resolve the timecode problems for everybody when they regenerate the reference movies, right?
 
Gavin Stokes said:
So, if I've absorbed the state of affairs correctly, the version-256 builds of RCX and Redline resolve the timecode problems for everybody when they regenerate the reference movies, right?
Click to expand...

Can't speak for everyone, but I believe that to be true.
 
Gavin Stokes said:
So, if I've absorbed the state of affairs correctly, the version-256 builds of RCX and Redline resolve the timecode problems for everybody when they regenerate the reference movies, right?
Click to expand...

Yep. 256 of RC-X and REDLINE does resolve the TC problem if you regenerate the proxies.

I also like the idea of having the batch monitor show "or report" back to the user that the processes are complete.

In my e-mails with Hans he said he was going to report this to you guys so he is aware of the problem.

I'll flip him a note pointing him to this thread.

This is an excellent thread guys and thanks very much for all the work Dusty, Branden and RED team.

David
 
That's good news. Once we get the Redline hang fixed, you should be able to largely automate the regeneration of old reference movies and fix the old projects once and for all.

I have a feeling that the resolution of the timecode bug will address the instability of existing projects, which (I'm told) people have reported historically when our tools were updated.
 
Gavin Stokes said:
That's good news. Once we get the Redline hang fixed, you should be able to largely automate the regeneration of old reference movies and fix the old projects once and for all.

I have a feeling that the resolution of the timecode bug will address the instability of existing projects, which (I'm told) people have reported historically when our tools were updated.
Click to expand...

Thanks Gavin,

We are glad you guys are on it. It's a big help to know that you are working toward a fix.

Threads like this represent reduser at it's best.

David
 
Gavin,

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.

Is this a problem with the wrappers or with Red Color plugin?


Dusty
 
Can anyone in this thread please keep us posted as to how this is progressing.

I have not heard from Hans so he is probably on the case.

David
 
Brent,

Just ran this workflow and it is working for me.

One tip to out there. When you regen the proxies make sure you have your folder view with DATE MODIFIED displaying.

Then when you open the folder you can quickly check to see that the date and time has indeed changed after you regen the proxies.

David
 
David Battistella said:
This is an excellent thread guys and thanks very much for all the work Dusty, Branden and RED team.
David
Click to expand...

I agree. My favorite aspect of REDuser (besides Recon) are threads that take a problem, stay on track, and then ultimately end in a solution. I think they do both RED and endusers a great benefit. If there were more of these types of threads that didn't get personal, didn't venture way off topic, it would be easier to search through information, and get the answers.

Great job everyone involved!
 
Gavin or Brent,

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


redexport: working_dir: /Applications/REDline.app/Contents/MacOS
redexport: export process started with process id: 23221
redexport: connection received from 127.0.0.1:53391
redexport: export_client_listener: received received message from client. 1
redexport: export_server_wait: received buffer complete message from the client. 0 1
redexport: export_server_wait: received frame received message from client. 0
redexport: export_server_wait: received processing complete message from the client. 0 1
redexport: export_server_wait: received buffer complete message from the client. 1 1
redexport: export_server_wait: received frame received message from client. 1
redexport: export_server_wait: received processing complete message from the client. 1 1


I am using a rocket.


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