RGB Curves & Samplers

What a great addition to have individual RGB curves. This is a great enhancement to LR's ability to correct color. Used in concert with the RGB percentages in the histogram window I just did a quick correction and it worked great. Something I'd love to see included in the future would be the ability to lay down color samplers for shadow, midtone, and highlight references. Using the targetted adjustment tool I was able to focus on an area of (supposed to be) neutral midtone and adjust each curve. The challenge is when going back to the same spot if you're not precise you'll add another target location and screw up the curve. Granted, you can directly control the previously created point on the curve and use the before/after RGB percentage values in the curve window but you lose sight of the other channels. Perhaps in lieu of samplers having a window that showed all RGB values as well?

As it may not make the final release, and we wouldn't want the request to get lost in beta land, might I suggest adding the request to the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked? If you post the link to your request here, others can also vote on your request.

Similar Messages

Is there a way to create an RGB curve preset in ACR that WON'T affect separate R G B curve settings?

I'm currently try to create an RGB curve that produces a fade to the picture. Outside of this I would like to save it as a preset for just the MAIN RGB curve because I have images that have custom separate R G B curve settings. I can't seem to do this AT ALL. I've viewed the XMP data in text editor and the only adjustments that are there are for the main tone curve yet it STILL ends up flatten my separate R G B curve adjustments.
This doesn't seem to be an issue in Lightroom yet I can't get it to work in ACR. BTW I'm using PS CC 2014 with ACR 8.6. Any help would be MUCH appreciated. Is there some code I could input into the XMP text so that it would NOT do this?

Yes... this is possible in Lr... but doesn't seem possible in ACR for some strange reason.

Flickering Issue with RGB Curves in Adobe Premiere CC (2014) version

I've been an Adobe Premiere user since Premiere 6.5 and have never encountered any serious issues with the software. However in this most recent Creative Cloud update I am have a flickering issue when using RGB Curves, the color correction effect I use most often. When the effect is applied, there seems to be a shift in the shadows between a "crushed" black and a "flat, or faded" black every other frame. I've been using this latest update for about a week and haven't had any other issues aside from this one.
Unfortunately this is huge issue at the moment due to a deadline I am facing in which RGB Curves has been used as the primary color correction tool on the entire project (multiple episodes). I would simply revert to a previous version of CC but I know that the new updates are never backwards compatible. Since the project has been saved in the CC (2014) update, reverting to previous software versions would be impossible. I am currently exploring exporting the XML from the CC (2014) projects and importing it into a previous version of the software.
Please let me know if anyone out there is experiencing any similar issues or if there are any suggestions on how to solve this issue. Thanks!

I am experiencing flickering issues as well. However my issues are with the Fast Color Corrector and the Three Way Color Corrector. It seems as if the color correction tools are causing intermittent flickering on some people's systems.
Additionally when I converted some old PPCC 7.2.2 projects which had the Three Way Color Corrector applied, some clips in sequences would come up as a green screen in the program monitor. If I turned the TWCC off the footage would display correctly in the program window. If I turn the TWCC back on it would display the green screen again.
I haven't found a solution to the flickering but to solve the green screen issue I have to remove the effect, then re apply it. I guess for whatever reason, the 2014 version of PP has issues with 7.2.2 projects where the TWCC was applied.
I'm hoping Adobe will address this soon with an update for the various bugs that have been reported.
PPCC 2014 8.0.1
Win 7 Pro

Premiere Pro Freezes mac while rendering Fast Color Corrector & Rgb curves

I am having a problem that is impacting our business. We are doing commercials that we are doing color correction of the subject using Fast Color Corrector and RGB curves. When these effects are added to the sequenced video, the performance of the Mac Pro slows down considerably.
Then when we go to render the project so that we can see the effects in real time, the computer freezes completely. The program usually informs us that it must close due to a serious error. I have attempted to restart the computer, clean up permissions etc to solve this problem but to no avail. Why would this happen? Any ideas on how to solve it?
Here are the specs:
Using Premiere Pro CC 7.2.1 (4)
Mac Pro: 3.2 Ghz Quad-Core Intel Xeon
Memory: 24 GB
ATI Radeon HD 5770 (1024 MB)
OS: 10.8.5

Yes. I experimented on my own and got confirms from a couple of sources. Where the problem was is bad suggestions about what settings to use in Premiere Pro.
The first setting you want to check (although Premiere Pro will probably see the card right away is:
File > Project Settings > General - Make sure that Mercury Playback Engine GPU Acceleration is selected. Everyone agrees on this.
Now is where the fun begins. There is a school of thought that says to go here:
Sequence > Sequence Setttings - Under Video Previews, they want you to check off Maximum Render Quality. Once you do this, you must also go to:
Preferences > Memory - and change Optimize Rendering for Performance
DO NOT DO THIS! What I found is that this significantly slows down your system and makes rendering and exporting take over your computer (and I have a lot of ram). Leave your change with the setting Mercury Playback Engine GPU Acceleration and you should be great.
I have found a significant change in running color correction effects, exporting and rendering. You will too.
Let me know how you make out after your setup.
Have a great day!

Composite RGB Curve math

In Photoshop's Curves dialog (CS3), you can add control points to the composite RGB curve by command-clicking an area of the image. I've tried to figure out how the location of the added control point is determined from the color that was clicked on, without success.
For example, command-clicking on a solid of RGB (127,127,190) results in a control point at 134,134. I can't figure out the relationship between the source color and the control point.
It's not the average, max, H, S, L, etc.
Anyone know?
Thanks,
--Rich Wagner

It seems to be based on Photoshop’s “luminosity” calculation (Adobe’s invented word for what video people call “luma”) – in other words a weighted sum of the numerical values of the three channels. See http://en.wikipedia.org/wiki/Luma_(video)
This is sort of silly, since the actual effect of the composite channel has nothing to do with “luminosity”, but instead acts on each channel independently, and therefore unless a pixel’s color is a neutral gray, the curve will affect each of its component values independently. The clicked-on pixel might not be at the chosen point on the curve in any of the three components.
Basically, think of it as just a relatively arbitrary point that doesn’t bear much relation to the effect the curve will have on the clicked pixel, unless that pixel happens to be gray.

I would like an RGB Curves adjustment.

I switched from Aperture 3 to Lightroom 3 for the ColorChecker Passport integration, but I really miss the RGB Curves in both Aperture 3 and Photoshop. I've been using Curves in Photoshop for years. I really wish there was one in Lightroom 3.
If anyone agrees with me, please add your vote.

Aye!
+1 vote
It's just not possible to get the sophisticated cross-processing look without RGB curves adjustment.

Spurious colours from RGB Curves and Track Matte...

Hello people of the forums.
I am working on a music video.
In a couple of places in the sequence where there are two or more visible layers overlapping with top layer/s having less than 100% opacity there is some unwanted 'extra' colours appearing which can be seen in the attached image below.
In the left image the unwanted colour appears in the center above the mans head, it is grey coloured.
In the right image the unwanted colour is the red.
All blending modes are Normal. There are Track Mattes in use. There are RGB curves being used.
As a result of trying to gather pertinent information for this post I found a cure, hahaha.
For the left images situation I found that turning the RGB curves off removed the colours, so I replaced the curves with Levels and the issue went away...
So for the right images situation I added a levels below the track matte and above the RGB curves, and the issue went away, no adjustment to the levels at all... I moved the levels from between the Track Matte and the Curves and the issue reapeared.
I will post this anyway but not as a question.
All the best
Peter

Hi Bill,
This is so weried I know how to do this where to point ect ect.
If i move the clip with the track matte on I get a crash.
I made a new seq and used same clip and it works. so I made a second clip next to it and it worked. I copyed those clips back to the old seq and it did not work...
It's been going on for a long time.. what do you know about seq setting with track mattes? do they only work well on some and porly on others.. all Ideas to find a answer.
answer to your above quest yes I am doing it right and why should I get a crash if I move the clip with the track matte on.
I think if we can answer that we will have fixed it.
over to you Bill
thanks for hanging in there.
Best
trevor

Color Key plus RGB curves slowing down computer

Just updated to Premiere CC 7.2.1 and when I use color Key and add RGB curves to a clip my computer shows down to an almost unsuseable level. Slow is the new normal.

Hello,
I'm sorry your experiencing this problem. Same question as Jim. Are you on Mac?
We are aware of the performance issues that were introduced in version 7.2 with certain AMD GPU cards.
We're investigating the problem now.
I know this is not ideal but in the mean time here's a few workarounds:
- Revert back to 7.1
- Disable GPU acceleration when using those effects
Here's a list of effects that seem most problematic:
*Fast Color Corrector
*RGB Curves
*ProcAmp
*Edge Feather
*Lumetri Looks
These effects do not appear hinder the performance in my testing:
*All Blurs Effects
*Three Way Color
*Crop
*Garbage Mattes
*Levels
Again, I apologies the the inconvenience.
Best,
Peter Garaway
Adobe
Premiere Pro

RGB Curves crashing Premiere after update

I just updated Premiere CC and every sequence that uses RGB curves has been crashing on me. Premiere starts acting as if it is being asked to do way to much. The video starts displaying still images every ten seconds from the video until the entire program becomes unresponsive. When I pass the buck to media encoder and watch my CPU usage it tells me that I am using 775% of the CPU. I've opened sequences where is hasn't had curves and applied them and immediately the program begins to slow down and crash. Anyone else having this issue?
- Adobe CC
- iMac 3.4 GHz i7

Hello,
I'm sorry for the trouble this is causing. We are aware of the performance issues that were introduced in version 7.2 with certain AMD GPU cards.
We're investigating the problem now.
I know this is not ideal but in the mean time here's a few workarounds:
- Revert back to 7.1
- Disable GPU acceleration when using those effects
Here's a list of effects that seem most problematic:
*Fast Color Corrector
*RGB Curves
*ProcAmp
*Edge Feather
*Lumetri Looks
These effects do not appear hinder the performance in my testing:
*All Blurs Effects
*Three Way Color
*Crop
*Garbage Mattes
*Levels
Again, I apologize for the inconvenience.
Best,
Peter Garaway
Adobe
Premiere Pro

Encoding fails with RGB Curves after update.

I'm trying to finish a project, but Premiere is gving me troubles..
I'm uisng Creative Cloud and I saw that there was a update for Premiere and i thought: "Why not, it can't hurt..", but boy was I wrong!
Before the update I could play and export my sequence without any problems (except laggy Playback), but after the update Premier wouldn't play the sequences (only audio) and when I tried to render previews I got an generic error.
After some investigation I found that there could be a problem with RGB Curves, and sure enough, after disabling the RGB Curve-effects on the Clips it worked fine!
I also found that it should work fine with GPU acceleration enabled, so I activated it. Now my project played fine in PP (with RGB Curves), and thanks to the GPU it didn't laily
Happily I started the export and went for a walk, but when I got back the exports had stopped and there was an generic error!
So, apparentely the exporter(/media encoder) doesn't use the GPU (*sadface*) and so is affected by this weird bug.
What should I do now??
I use RGB Curve for color correction and grading through the whole sequence, so I guess I need to find another effect that gives me the same result..
Windows 8 64bit

I generally try to be careful with updates, and I should have known better (especially than update in the middle of a project). But given it was a minor update and that minor updates is supposed to fix bugs (and not introduce new features/bugs..) I thought it would be safe.. But it's a weird bug (that couldn't have been fixed by replacing the RGB Curve effect file with an older version!?) and even weirder is that the text I read was for CS5.5..
Luckily I had also installed PP on my laptop, so I just copied the program files from the laptop to my workstation and I could carry on and finnish the project.
The thing about waiting with updates of this kind is that you don't get the bug fixes. It's one thing to wait before you jump on the next big update (like CS5.5 to CS6 etc) and another to install "bug fix updates".
There is no real "infancy period" for minor updates, they do not mature, there is one update, if that update introduces a bug, then that's fixed by the next update etc etc.
In the end, you don't gain that much by waiting to do minor updates (albeit you should avoid it during a project), since minor updates should fix the bugs that your software currently has and you could, theoritically, just end up with more problems when you do decide to do that update.
One solution could be to never update, but then you're stuck with the original bugs..
The best thing to do is to do a backup before updating (and I should've done that..).
What would've happened if I decided to install Premiere Pro a week later?? Then I probably would've gotten the latest version with the update and so the bug!?

RGB Curves / Levels

Having used Lightroom since it was in beta - pre version 1 release - there is one feature that I find myself swapping to Photoshop for more than anything else.
That is the levels adjustment layers and auto levels feature. Specifically, the ability to control not just the overall levels but the levels of each of the RGB channels.
I find the curves adjustment in Lightroom far easier to use than the curves in Photoshop, so if Lightroom's curves could do RGB as well as overall I would be very happy.
I find it strange that the Lightroom histogram shows levels for RGB and CMYK but you cannot control them...

Simon, I see what you're saying, but there are features in Lightroom as it stands that probably aren't used by the majority of users. I know I rarely use some options in the develop module.
I think if an 'auto levels' option, like in Photoshop, was available this would please a lot of users who think the current auto tone options don't always fit the job.
If you have an 'auto adjust' button you then have two basic options: 1) undo the changes, 2) accept the changes. You also have a third, more advanced option of accepting the changes and 'tweaking' the settings to your hearts content.
Your average user, myself included, would most frequently use the first two options, saving time and disk space of editing in PS.
Unless there are other ways to remove colour casts from images? As an example, I recently took photos which included lots of snow with clear blue skies. They were too blue all over for my liking and the white balance in LR didn't do it. I export to PS and auto level, slight tweak and I'm happy.
This would probably require a bunch of changes to Adobe Camera RAW, so probably not an option for the current version. Would be nice to have the option, or indeed an SDK in future releases.
Cheers, Damon.

Color samplers - dark, light & grey point - how to adjust curves

Hi all
I've set dark, light & grey point in an image. Wondering how to adjust the curves based on the color samplers. Manually i invoke the curve dialog box and select the dark pen and choose sampler no1, select light pen and choose sampler no2, select grey pen and choose sampler no3. Any idea how this can be done in script?

I’m stymied by the gray point at current, it does not seem to use the measured values directly.
The white and black points seem to be straightforward and can be set easily with a Script when one knows the values.
#target photoshop
var theArray = [[17, 224], [0, 255], [27, 215], [0, 255], [28, 206], [0, 255]];
rgbCurvesLayer (theArray);
////// make rgb curves layer //////
function rgbCurvesLayer (theArray) {
// =======================================================
var idMk = charIDToTypeID( "Mk " );
    var desc5 = new ActionDescriptor();
    var idnull = charIDToTypeID( "null" );
        var ref2 = new ActionReference();
        var idAdjL = charIDToTypeID( "AdjL" );
        ref2.putClass( idAdjL );
    desc5.putReference( idnull, ref2 );
    var idUsng = charIDToTypeID( "Usng" );
        var desc6 = new ActionDescriptor();
        var idType = charIDToTypeID( "Type" );
            var desc7 = new ActionDescriptor();
            var idpresetKind = stringIDToTypeID( "presetKind" );
            var idpresetKindType = stringIDToTypeID( "presetKindType" );
            var idpresetKindDefault = stringIDToTypeID( "presetKindDefault" );
            desc7.putEnumerated( idpresetKind, idpresetKindType, idpresetKindDefault );
        var idCrvs = charIDToTypeID( "Crvs" );
        desc6.putObject( idType, idCrvs, desc7 );
    var idAdjL = charIDToTypeID( "AdjL" );
    desc5.putObject( idUsng, idAdjL, desc6 );
executeAction( idMk, desc5, DialogModes.NO );
// =======================================================
var idsetd = charIDToTypeID( "setd" );
    var desc8 = new ActionDescriptor();
    var idnull = charIDToTypeID( "null" );
        var ref3 = new ActionReference();
        var idAdjL = charIDToTypeID( "AdjL" );
        var idOrdn = charIDToTypeID( "Ordn" );
        var idTrgt = charIDToTypeID( "Trgt" );
        ref3.putEnumerated( idAdjL, idOrdn, idTrgt );
    desc8.putReference( idnull, ref3 );
    var idT = charIDToTypeID( "T   " );
        var desc9 = new ActionDescriptor();
        var idpresetKind = stringIDToTypeID( "presetKind" );
        var idpresetKindType = stringIDToTypeID( "presetKindType" );
        var idpresetKindCustom = stringIDToTypeID( "presetKindCustom" );
        desc9.putEnumerated( idpresetKind, idpresetKindType, idpresetKindCustom );
        var idAdjs = charIDToTypeID( "Adjs" );
            var list1 = new ActionList();
                var desc10 = new ActionDescriptor();
                var idChnl = charIDToTypeID( "Chnl" );
                    var ref4 = new ActionReference();
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idRd = charIDToTypeID( "Rd " );
                    ref4.putEnumerated( idChnl, idChnl, idRd );
                desc10.putReference( idChnl, ref4 );
                var idCrv = charIDToTypeID( "Crv " );
                    var list2 = new ActionList();
// add r points;
for (var m = 0; m < theArray[0].length; m++) {
          addCurvePoint (list2, theArray[0][m], theArray[1][m])
                desc10.putList( idCrv, list2 );
            var idCrvA = charIDToTypeID( "CrvA" );
            list1.putObject( idCrvA, desc10 );
                var desc15 = new ActionDescriptor();
                var idChnl = charIDToTypeID( "Chnl" );
                    var ref5 = new ActionReference();
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idGrn = charIDToTypeID( "Grn " );
                    ref5.putEnumerated( idChnl, idChnl, idGrn );
                desc15.putReference( idChnl, ref5 );
                var idCrv = charIDToTypeID( "Crv " );
                    var list3 = new ActionList();
// add g points;
for (var m = 0; m < theArray[2].length; m++) {
          addCurvePoint (list3, theArray[2][m], theArray[3][m])
                desc15.putList( idCrv, list3 );
            var idCrvA = charIDToTypeID( "CrvA" );
            list1.putObject( idCrvA, desc15 );
                var desc20 = new ActionDescriptor();
                var idChnl = charIDToTypeID( "Chnl" );
                    var ref6 = new ActionReference();
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idChnl = charIDToTypeID( "Chnl" );
                    var idBl = charIDToTypeID( "Bl " );
                    ref6.putEnumerated( idChnl, idChnl, idBl );
                desc20.putReference( idChnl, ref6 );
                var idCrv = charIDToTypeID( "Crv " );
                    var list4 = new ActionList();
// add b points;
for (var m = 0; m < theArray[4].length; m++) {
          addCurvePoint (list4, theArray[4][m], theArray[5][m])
                desc20.putList( idCrv, list4 );
            var idCrvA = charIDToTypeID( "CrvA" );
            list1.putObject( idCrvA, desc20 );
        desc9.putList( idAdjs, list1 );
    var idCrvs = charIDToTypeID( "Crvs" );
    desc8.putObject( idT, idCrvs, desc9 );
executeAction( idsetd, desc8, DialogModes.NO );
return app.activeDocument.activeLayer;
////// add curve point //////
function addCurvePoint (theList, valueHor, valueVer) {
var desc11 = new ActionDescriptor();
var idHrzn = charIDToTypeID( "Hrzn" );
desc11.putDouble( idHrzn, valueHor );
var idVrtc = charIDToTypeID( "Vrtc" );
desc11.putDouble( idVrtc, valueVer );
var idPnt = charIDToTypeID( "Pnt " );
theList.putObject( idPnt, desc11 );
Edit: I had assumed the gray point picker would set the input values of the point picked to output 127/127/127, but he operation seems to be quite different.

Camera Raw - Enable RGB Tone Curves

In Camera Raw, the Tone Curve Channel selection is disabled. How can I enable it to allow me to adjust specific colors in Camera Raw?
I’m using Photoshop CS5, Camera Raw version 6.7.0.339 on a Windows Vista 64 bit system, and my camera is a Nikon D90.
Thanks,
Jack

I don't think you can...ACR 6.7 was a crossover version tho have compatibility with LR 4 when it was released, as a result it was set to allow processing of certain features that were in LR 4 (and ACR 7). While the RGB curves show up dimmed, I don't think ACR 6.7 allows actually adjusting the RGB curves. I think the only way to get them is update to CS6 and ACR 7.x.

New RGB Tone Curve also a Basic Levels Adjustment?

Adobe Staff: at first I was pleased and then let down about the new RGB Tone Curve feature because I thought it allowed for Levels Addustments - as with so many other photo editing software including Adobe PS Elements where you can squeeze in the left and right triangles to ajust the blacks and highlights and midtones.
I was playing with the Lr4b RGB curve yesterday and - is it correct that it does essentially act the same as "Levels Adjustment" by squeezing inwards the blacks (lower left) and whites (upper right) points?
Thank-you

Yeah, but blacks and whites in the basic panel are better, and usually should be applied after you've appled the others.

Recreating merged curves layer by guesswork

Hi folks, I have a picture I once added a curves adjustment layer to. Unfortunatley I don't have the .psd anymore, only a composite .png (the final image) and the source image.
I tried to recreate the curves adjustment layer on top of the source image and compare it to the final image, but I don't get anywhere close to it. I must say though, that generally speaking I have decent curves skills I would say, I intuitively know how they react and affect the output. But the curves layer I used back then involved independent R,G and B curves plus a RGB curve, with about 3 to 4 control points each.
So intuition and guesswork didn't get me anywhere, that's why I was wondering if there was something like a more strategic method defined by rules which would inevitably lead to the correct result if followed correctly ?
If not, is there a different way of recreating the final image from the source image?
Many thanks.

If its just one curve, you can probably do it. But all three, plus a master adjustment might prove too much if the change were drastic. Still worth a go. Even if you just place the 4 color samplers in quarter tones, you might have some luck.
As I said above, it doesn't matter whether it's 1 or 3 curves, because
the RGB channels are treated independently (both by color picker and the
curves layer). The master adjustment is more problematic, right,
but theoretically it shouldn't be a problem either, because two curves
can be "merged" ... well, not in Photoshop (I might suggest that as a
feature one day), but mathematically.
Curves are functions. Take an easy function like f(x) = 1.5*x + 2x
this equates to: f(x) = 1.75 * x
(where x = input and f(x) = output in Photoshop curves adjustment)
I have started working with this method and so far it looks promising,
hope it turns out right
I'll let you know
You inspired me to finally get at what Martin Evening was doing below. If you only had a gray strip in each channel...
http://photoshopnews.com/2007/09/05/how-to-express-blend-modes-as-curves/
Looks very interesting. I'll have a look at it one rainy day ...

RGB Curves & Samplers

Similar Messages

Maybe you are looking for