Welcome to our community

Be a part of something great, join today!

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

CS5 One Light Color Correction

Adam Johnson

Well-known member
Joined
Nov 20, 2009
Messages
1,887
Reaction score
1
Points
38
Location
St. Louis, MO
Is it possible to do a one light color correction in either Redcine-X or RedAlert before or during editing in Premiere Pro CS5?

Since you're editing native r3D files I figured everything would be connected and you could instantly see the changes in your timeline. I'm brand new to PP so any information would be great!

Adam
 
I'm not a Premiere user ...

That said, if you are using the R3D files you can't do work in the RED software and have it reflected in the CS5 timeline.

Most of the CS5 coolness with RED seems to be done working directly with the R3Ds.

If you choose to make changes to the QT reference movies it might work. You'd probably have to close and reopen the timeline or possibly Premiere.

I just don't know if Mercury will work with the RED proxies to accelerate playback.
 
The issue isn't with Premiere being able to read the changes to the R3D file, the issue comes from not being able to save the metadata changes to the R3D file from redcine. Saving changes to the quicktime proxies does not change the original R3D file, and since Premiere works directly with that R3D file, no changes are reflected within premiere.
Premiere does have quite a bit of control over changing the metadata of the R3D file directly within the editing suite, but it does not yet compare to redcine. I have found though that working with a combination of R3D tools in Adobe and using synthetic aperature controls give me plenty of control over the final color grading of the file.
 
There is a solution...

There is a solution...

If you use Cineform you will be able to make changes to the CF Master via their FirstLight software, and it will be reflected on the NLE you are using it. Just go to their website and do some research, and you can verify and/or explore this option. :leaving:
 
I think Adobe are working on having the sidecar RMD files work with a future update. Which would be perfect as you can then use Redcine-X and PPro both to adjust things and have the results show up across programs. Plus I think Adobe want to incorporate some form of Redcine-X linkage as well. But I'll let someone from Adobe confirm or deny this for sure :)

Cheers,

Paul
 
Is it possible to do a one light color correction in either Redcine-X or RedAlert before or during editing in Premiere Pro CS5?

Since you're editing native r3D files I figured everything would be connected and you could instantly see the changes in your timeline. I'm brand new to PP so any information would be great!

Adam

the old redcine was able to run cc while playing back the file in realtime (I think this what you mean by one light color correction, the old telecine style)..

I think PPro will stop playback when you change any color settings, especially interpreting the R3D files..
 
the old redcine was able to run cc while playing back the file in realtime (I think this what you mean by one light color correction, the old telecine style)..

I think PPro will stop playback when you change any color settings, especially interpreting the R3D files..

I believe Adobe is working on adding Flut controls to the Red settings dialog in PPro. Its the same as Red Alert. Not yet Redcine X. When this is done you can do your white balancing right on the timeline no need to use Redcine X. This was clearly demonstrated in one of the Adobe videos from NAB
 
I believe Adobe is working on adding Flut controls to the Red settings dialog in PPro. Its the same as Red Alert. Not yet Redcine X. When this is done you can do your white balancing right on the timeline no need to use Redcine X. This was clearly demonstrated in one of the Adobe videos from NAB

Yes we are going to support flut... You won't have to wait much longer...

Cheers

Dave
 
Yes we are going to support flut... You won't have to wait much longer...

Cheers

Dave
Yippee!!! Can't wait (literally) as my Mysterium-X sensor Red should be winging its way back to me within the week!

If you need beta testers (I was part of the Scully program) let me know via PM or email via my website.

Cheers!

Paul
 
Whilst we are asking, is it possible for Adobe to add mecury acceleration to Adobe cinema DNG by version CS5.5. Its pretty slow.
 
I only tried it as an archival and transfer format. I brought it into CS5 it literally slowed down. You do know that a lot of companies are beginning to support CineDNG as an intermediate format right? I don't currently have a workflow with it I was simply trying it out.
 
I only tried it as an archival and transfer format. I brought it into CS5 it literally slowed down. You do know that a lot of companies are beginning to support CineDNG as an intermediate format right? I don't currently have a workflow with it I was simply trying it out.

Yes we do know companies are beginning to support CinemaDNG, just was interested if a RED user on this format was using it :)

Cheers

Dave
 
Yes we do know companies are beginning to support CinemaDNG, just was interested if a RED user on this format was using it :)

Cheers

Dave

well if redcine-x exported to cine-dng, that would be an intermediate format of choice, the container is better than having millions of tiff16 files
 
well if redcine-x exported to cine-dng, that would be an intermediate format of choice, the container is better than having millions of tiff16 files

I disagree, I love non container codecs, like DPX, as it allows me to render just the frames, that I need to render, without re-rendering all of them in the process. Also, I can stop the render at any time and not lose the whole render as a result, like it happens most of the time with QT. Yes, container codecs are easier to manage, but that is why systems, like Baselight address it on the OS level (FLOS), which is sequence aware. Just think of a container wrapper as a folder. Once DPXs or TIFFs are inside the folder, it looks just like the container.
 
Yes we do know companies are beginning to support CinemaDNG, just was interested if a RED user on this format was using it :)

Cheers

Dave

Dave.
Are you ignoring my questions on the use on a Mac of multiple GPUs for Mercury playback and "send to Resolve" or something you can't answer?:lipsrsealed:
 
I disagree, I love non container codecs, like DPX, as it allows me to render just the frames, that I need to render, without re-rendering all of them in the process. Also, I can stop the render at any time and not lose the whole render as a result, like it happens most of the time with QT. Yes, container codecs are easier to manage, but that is why systems, like Baselight address it on the OS level (FLOS), which is sequence aware. Just think of a container wrapper as a folder. Once DPXs or TIFFs are inside the folder, it looks just like the container.

I guess having different tiff choice codecs is a good thing, plus as opposed to being just a heavy codec, cine-DNG has better Meta-data information than tiff16s or DPX's. so as an intermediate codec it serves both purposes of being able to handle the Raw info of an R3d and still be edited and written to.

I see a limitation for plugin companies with Cuda. Non Cuda third party plugins are now a pain in the ass for me. I think third party plug-in manufacturers porting to 64bit need to get with the program and make their plug-ins Cuda aware :out:.
 
I guess having different tiff choice codecs is a good thing, plus as opposed to being just a heavy codec, cine-DNG has better Meta-data information than tiff16s or DPX's. so as an intermediate codec it serves both purposes of being able to handle the Raw info of an R3d and still be edited and written to.

I see a limitation for plugin companies with Cuda. Non Cuda third party plugins are now a pain in the ass for me. I think third party plug-in manufacturers porting to 64bit need to get with the program and make their plug-ins Cuda aware :out:.
TIFF has no metadata capabilities, therefore it carries no time code, DPX does. That's why DPX is the preferred choice.
 
TIFF has no metadata capabilities, therefore it carries no time code, DPX does. That's why DPX is the preferred choice.

My point exactly, cine-DNG's as opposed to Tiffs can handle raw meta-data. The cine-DNG is 16 or 32bit not limited to YUV or RGB and is superior to 10bit DPX at half the file size. At this point theoretically it should make a great capture, intermediate and Archival format. Its just not widely supported yet.
 
Dave.
Are you ignoring my questions on the use on a Mac of multiple GPUs for Mercury playback and "send to Resolve" or something you can't answer?:lipsrsealed:

Just ignoring you ;)

No I must have missed the question... Plus I only know most things not all... What is the question?

Cheers

Dave
 
Back
Top