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

Losing all my color settings and dissolves

Stephen Pruitt

Stephen Pruitt

Well-known member
Joined
Sep 14, 2007
Messages
3,309
Reaction score
40
Points
48
Website
www.thetreemotionpicture.com
Hey guys. . .

. . . I'm losing all my color settings and dissolves when I edit on one machine and then take that timeline into another machine. It's beyond irritating to have to reproduce all that work.

I'm on Premiere Pro CS5.5 and going from Mac to Mac.

Any thoughts as to how to keep that from happening?

Thanks.

Stephen
 
Hi Stephen,

What do you mean by color settings? Do you mean raw metadata that you have changed in R3D's, or color grading effects you have added on to your clips?

Regarding the transitions, that does seem like an odd one. How are you currently moving your project from one machine to another - what does your process involve?
 
Thanks for your post, Brad.

I'm talking about making color changes using the "Source Settings" of PP.

As to how we are moving the program, I just email my project file to my co-editor and when she uploads it into her PP system, all of the color settings are back to "as shot" and all of our dissolves are gone. Stranger, all of my push-ins, recenters, etc. are still there!

Is there something I should be doing differently?

Thanks!

Stephen
 
Stephen-
The Source Settings for the R3Ds are either stored in a seperate application-level folder, or with the R3Ds themselves, depending upon how you are saving them... In either case the settings are NOT stored with the project file, which is why they are getting "lost".
If you are saving the settings as presets, they are stored in their own folder... I don't remember offhand where they are stored, but I believe they are ".ini" files if you want to try a search.

I've never tried what you are attempting, but you may just have to copy that directory of presets over to the other machine. Or better yet, you might want to drop a note to Dave McGavran to see if he has any specific advice regarding this.
-CK
 
CK Olsen said:
Stephen-
The Source Settings for the R3Ds are either stored in a seperate application-level folder, or with the R3Ds themselves, depending upon how you are saving them... In either case the settings are NOT stored with the project file, which is why they are getting "lost".
If you are saving the settings as presets, they are stored in their own folder... I don't remember offhand where they are stored, but I believe they are ".ini" files if you want to try a search.

I've never tried what you are attempting, but you may just have to copy that directory of presets over to the other machine. Or better yet, you might want to drop a note to Dave McGavran to see if he has any specific advice regarding this.
-CK
Click to expand...

This isn't quite true. The settings are in the project. It should be fine what you are doing. Most important is that you have the same versions of the red plugin, otherwise we will reset the settings.

Cheers

Dave
 
Dave. . . how can I confirm that we have the same version of the RED plugin, which I do believe is true. This is beyond irritating, and may be the one thing I most dislike in my otherwise happy love affair with PP.

What about all of my lost transitions???

Stephen
 
Hi Stephen,

Just as something for you to test, have you tried saving your metadata to RMD?

Right click to the clip in your project panel > Source settings > save to RMD.

Then once on the new system (ensuring that the new system is accessing the very same r3d's and rmd's) try the exact same process except select "reload RMD".

This is process is basically ensuring that Premiere is saving your metadata changes back to your red files, and then ensuring that your other copy of premiere is loading those changes from the red metadata file (RMD). It is dependant on both of your editing systems accessing the very same R3D files. If you have a copy of the files for one machine and a seperate copy of the files for another - this won't work.

Really confused about your transitions not coming through though - that one is really odd.

If you like - feel free to email me (brad at unravel dot com dot au), a copy of just the project file and I'll see if the transitions are coming through for me...

Sleep time for me on this side of the world though :P
 
Thanks, Brad. . .

I will email you a project file and you can tell me if the transitions are there. They just vanish when we bring them in to the other machine.

And, yes, sadly, saving the settings won't work, because we have two separate copies of the files for editing. . . one here at home. . . and one at my co-editor's house.

Alas.

I'll send you a file el pronto. And thanks for your help.

Stephen
 
Hi Stephen,

Thanks for sending that project through to me. I can confirm that I do have transitions on my end - both dip to blacks and cross dissolves. This is both good and bad news. Good because it means you're transitions are in that file - bad because I have no idea what would cause your other version of premiere to nuke them all. Both versions of Premiere are the same version with the latest updates?

It sounds like whatever is nuking your transitions could also be nuking those color changes that are stored in the project file (as Dave mentioned). So some ideas and work arounds to try:

1. Re-install Premiere Pro on your machine that isn't reading the transitions. (Which also means installing the latest version of the Epic importer - assuming this was shot on epic or scarlet...)
2. Export out a Final Cut XML and re-import the the XML on the problematic machine to see if transitions come through
3. If you try step 2, you definitely won't have that color information carried across so you would need to save all the information to the RMD's in your main project and then copy all that footage across to your problematic system (I can understand why this will be a bit of a drag for you)

Ultimately though it would be best to get your problematic version of Premiere to behave normally as neither of these things should be a problem based on Premiere's normal behavior. I thought that the R3D's and their metadata could have explained your color problem, but as Dave has told us, those color settings if not saved to the RMD are actually stored in your project file anyway - which means they should be coming through too.
 
Thanks so much, Brad. We obviously have some work to do here to figure it all out.

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