Lightroom 4 and Color Efex 4

When I went to edit lightroom 4 with adjustments in Color Efex 4 it recognized the changes back in Lightroom but could no longer make adjustments

Having problems getting into forums.adobe...not liking my sign in. Yes I do have Lightroom 3 and I just tried again passing control to Color Efex 4 then returning to lightroom. Once back in lightroom I can continue to make changes

Similar Messages

Photoshop CS5 | Vivenza works, Silver Efex and Color Efex do not. Can you help?

I have Photoshop CS5 and purchased the Adobe tool suite. The first year all the tools worked and now only the tool Vivenza works. All the other such as Silver Efex and Color Efex do not work. Can you help?

Hi kilotwelve,
Sorry the plug-ins aren't working for you right now.
You might try reinstalling them and seeing if that helps, otherwise I'd go check with Google to get the working versions that work with CS5.
Hope this helps,
Regards
Pete

PSE 9 and Color Efex Pro 4

I installed the trial version of this and every single time I hit the "brush" button at the bottom right of the plug-in it takes me back to PSE 9 (as it should) and then crashes PSE 9....I can't find anything specific to this so thought I would ask if anyone else has had this issue.
Also, does anyone have a link as to how to use that selective brush tool in Color Efex? Thanks so much.

Check with Nik Software. Except HDR Efex Pro 2, it should be compatible.

Réinstallation de la suite Lightroom et Colr efex.

Bonjour,
Fin 2014 j'ai fait l'acquisition de la suite Lightroom Color Efex , début juin 2014 mon pc a planté et mon disque dur a été effacé , je ne dispose donc plus de mon N° de licence pour Lightroom et Color Efex !
Comment puis je les réinstaller ?
Merci pour votre aide !

This is the Adobe Reader forum. Lightroom → http://forums.adobe.com/community/lightroom

Color Efex Pro makes Aperture Flakey?

I have been experimenting with the Nik filters, and everything was fine till I tried out Color Efex Pro this morning. It seems that after I use it, I start getting odd behavior from Aperture - it seems less responsive, I get pictures going all white or all black, sometimes sliders slide but nothing happens, and one time a photo went black and white with banding like an old TV. Neither Dfine nor Viveza seemed to do this.
Quitting and restarting seems to fix it, but use Color Efex Pro again and it starts up again. Has anyone else noticed this?

I've noticed the black and white banding when I'm zooming to 100% or opening a full-screen image on any image that I've adjusted using either Nik's Viveza, Define and Color Efex plug-ins for Aperture. I'm not sure what's going on there? I'm using Nik Software's Complete Collection of Plug-Ins for Aperture

Plug-ins in Color Efex do not work when used with Lightroom? really need help

Dear all,
I am suffering the problem with some plug-ins (some others still okey) of Color Efex when I use them with Lightroom. Specifically, the image I chose to edit in Color Efex turned black as I tried to apply a plug-in, ex Detail extractor. Pls see the pic below:
Before
...and After
I am using Win XP and wondering whether this is the root of this problem? Pls help me for a solution if you know it.
Many thanks for reading and supporting!

Dear all,
I emailed Nik team and it is just exact as what you said, they are very helpful and supportive when provide me several of solutions. Thank god one amongst them solves my issue completely. I performed the following steps:
If you are able to open Color Efex Pro 4and can see part of the interface, see if you can click on the"Settings" button in the lower left.
In Settings locate the section "GPU" and expand it, in this section you will see a check box "Enable GPU Processing", uncheck this so the GPU will be disabled, then close the settings window.
Close out of Color Efex Pro 4 (click Cancel), quit out of any and all host applications (Photoshop,Lightroom, Aperture), and then relaunch Color Efex Pro 4 to see if this corrects this issue.
Thank to Nik team and you guys here. I'm now able to work with my new project better

Color change on exporting from lightroom and saving in Photoshop CS5

I have been having issues with my pictures with color management.    I have Lightroom 4 and Photoshop CS5. I thought over the last 2 years that it was just me.   I have bought a Eizo monitor with a hood, calibrate with a i1display pro, painted my walls gray, updated my strobes from alien bees to elinchrome bxri's.   Updated my sekonic meter to a L 758.   Have done custom white balance with gray card, expodisc, xrite kits.   The problem has been over the years when I work on a picture in lightroom and export it as jpeg or adobe rgb it gets saved to my external hardrive and the colors are really bad !!   You can go back and compare the picture in lightroom to the picture on my iomega external drive and there is a significant difference.   I do some animal photography and I had a dog that had brown fur and when I export it out of lightroom the dogs fur is actually a bright very orange color. Same thing happens with skin tones.     When I import the photos into lightroom the pictures look ok.       The same thing is happening when I go from lightroom to photoshop the picture color looks good but when I go to File-save as - tiff or jpeg the colors are changing.   It does not matter what color space I am in I have tried them all it is still happening.    If anyone has any insight that would be great.
Teresa

         Thanks everyone for the help.   I have only been doing photography for about 2 years and the color managment part has been my hardest thing to get right.   My monitor ColorEdge CG243W LCD.   Wide color gamut of 98%. Has a sensor on front of monitor that detects ambient brightness but this will only work if you are in a custom color mode. Modes are: custom, sRGB,DCI,EBU, Cal1.   I use the Cal 1 to be able to use the Colornavigator software that came with the monitor. You also have to be in custom color mode to be able to manually adjust brightness, contrast, temperature on the monitr itself which I do not use because I use the Cal 1 mode.   I was not sure about the digital input signals.   I am on the DVI-I in which this allows digital signal input and analog signal input.    There is a DVI-D mode that allows only digital input only.    Also did not know if I needed to be concerned about setting the frequency that corresponds to the grahic board in the monitor ?    My bandwith was set to normal and now is on wide.   My digital input is for 1920x1200 resolution.   Appicable signal is Vesa CVT RB. Frequency is 60 Hz.   Yes I did call Eizo twice last year when I got my monitor and did not get very far.     I have also called and spoke to a color specialist at my lab and told him the problems I have been having and he just told me to leave everything in sRGB.   Well I would like to get the most from my monitor's color gamut and when working on my pictures so that is why I am still determined to get this figured out.
I use the i1 Dislpay Pro hardware to calibrate with and the ColorNavigator software.     When calibrating.   I go to create a new target---select enter manually--Gamut ( monitor native--states recommended)--Brightness 100cd---White point (6500k)--set black level (recommemded states mininum 0.2)---gamma 2.20---priority (set automatically to standard, this adjusts gray balance while maintaining the contrast)---then I hit calibrate and it goes through the process.   The results I get are:                                            Target                                               Result
                      Brightness                                        100cd                                              99.9cd
                       Black Level                                    minimum                                       0.15cd
                      contrast ratio                                                                                            647:1
                      White Point                                    6500k                                              6501k
                       Gamma                                           2.20                                             R   0.6774,0.3136
                                                                                                                                        G   0.2031,0.6992
                                                                                                                                        B    0.1498,0.0499
Thanks again for your help I know this is alot of information but I thought it might help ?
Teresa

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

How to make colors looks same in Lightroom and Photoshop?

The colors of JPGs with sRGB colorspace are displayed differently between Lightroom and Photoshop and other image view applications.
I edited RAW images in Lightroom and export them to JPG files with sRGB colorspace, but their colors are eventually different from what I saw in LR.
(I set ProPhoto as the colorspace for my Photoshop.)
Is there anything I can do to solve this problem? Or maybe to reduce the color difference?
What is the best I can do to manage colors for those images that I want to share on the internet?
Thank you !!!

If colours look different between two colour managed applications such as LR and PS then you have either not calibrated your monitor at all or are using a corrupt monitor profile.
If the former you require a calibration device, such as a Spyder (lots of other around). If the second then re calibrate.
In the meantime you can set your monitor to use a colour space such as sRGB as a profile. This is not a solution, it is a temporary fix. Using a colour space as a monitor profile is not colour management, but will at least make the colour appear the same on your monitor.
There are some useful links concerning colour management and LR here you may wish to read.

Lightroom,Nik plugins and color spaces

I'm having an issue and not sure who is holding the smoking gun. I have the Nik ultimate collection installed which covers Lightroom and Photoshop CS5 extended. I work primarily in Lightroom and apply most corrections globally but occasionally i need to do localized adjustments so the photo gets shipped off to Photoshop. Here's a typical scenario:
1) From Lightroom edit in Dfine 2.0 for noise - as copy with Lightroom adjustments which gets copied as a tiff.
2) From Lightroom edit in Viveza 2 - as original since we're now working with a tiff and I don't want a copy for every single thing I'm doing.
3) Edit in Photoshop
Now there's two issues at this point:
1) The edits do not show up in the Lightroom history - it's like nothing happened.
2) Photoshop will complain that the assigned profile is sRGB. Really?
#1 is a PITA because if I want to rewind I have to start all over since there's no history - what exactly is responbsible to set an edit as history? Lightroom or the plugin?
#2 is by far the most serious as it degrades the work in a seriously bad manner. I mean, WTH - I'm moving along in ProPhoto Ferrarri space and all of a sudden - *boom* - I'm running in sRGB moped mode.
I looked at edit->Preferences->External Editing -> Additional External Editor and indeed when I select the Nik plugins from the combo box preferences the default for the plugins is sRGB. I can change to ProPhoto and quit. I repeated this for each plugin assuming that somewhere the setting was remembered. Nope LR acts dumb as a rock and shows sRGB as the defaults for all except the currently selected plugin.
So my questions are:
- who's gonna own up to the problem - LR or Nik?
- how can I work around it?
- how can I make LR remember the settings? Not a registry key nor INI file in sight to set them - so where/how are the plugins tracked?
Thanks for any help!
Jon

Jon,
The User Interface for changing how external editors are invoked is about as smart as your average chunk of granite.
After you change the Color Space to the one you want, you have to click on the Preset box and choose "Save current settings as new preset...". Not exactly intuitive, but there you are.
Hal

Lightroom and GIMP color issue using jpg

Here is what I do:
Using an iMac (Tiger) and have my monitor calibrated using the built in MacOS tool. The profile is stored in the Library/ColorSync/Profiles folder. In the GIMP settings about color management, I have chosen the monitor profile from above as the monitor profile and the RGB profile.
I have a (Canon) RAW image mainly in a neutral, if not slightly yellowish, tone with some beautiful golden pins. Imported the CR2 into Adobe Lightroom and exported in sRGB color space, the jpg looks like this: http://www.ipernity.com/doc/18039/1283133
Now I would love this with a nice frame, so I did a hi quality export, loaded it into GIMP 2.4.3, added a frame, and saved it as full size jpg. When I look at the resulting jpg in MacOS Preview application, it looks fine and so it does when I upload it to the web: http://www.ipernity.com/doc/18039/1284108
But as I manage all my images in Lightroom, I also want to manage this one in Lightroom, so I imported it. And look what's coming out: http://www.ipernity.com/doc/18039/1284100
It's all purple!
It looks the same in Lightroom, Preview and uploaded. Purple. What am I doing wrong? Is there any hidden Lightroom setting I have scambled?
When I am saving TIFF from GIMP, Lightroom imports with proper colors.

The third one (reimported into Lightroom) is indeed purplish. Are you using the latest gimp? Versions of gimp before a while ago could not color manage and will probably forget about the profile. It was only recently added. You should have the working space set to sRGB (so not RGB as you wrote above) in the gimp probably for this image. Also, make sure you do NOT save as a progressive jpeg, but only using baseline compression. Lightroom tends to change the color of progressive jpegs. This is probably what is going on.

Color Differences between Lightroom and Premiere Pro

I have been making color adjustments to movie clips in Photoshop or Lightroom (both of which do a great job), but when I bring the clips into Premiere Pro or Premiere Elements the colors are not the same as what I was seing in the other programs. It is as if the programs are using different color profiles. How do I resolve this problem?

bryanbrowne1 wrote:
I have been making color adjustments to movie clips in Photoshop or Lightroom (both of which do a great job), but when I bring the clips into Premiere Pro or Premiere Elements the colors are not the same as what I was seing in the other programs. It is as if the programs are using different color profiles. How do I resolve this problem?
Photoshop and Lightroom are designed for still photography. Still photographers use a color managed workflow that in general ends in a paper print. Since printers/inks/papers can in general display a wider gamut than computer monitors can display, we use tools manage it, such as soft proofing. The efficient way to control this is through ICC profiles of the printer/ink/paper combinations, of which there are thousands. Thus Photoshop and Lightroom and other still photography tools are esentially required to be color managed.
PPro and film/video have decidedly different requirements. The video workflow ends in a light source display (projection, HDTV, or web video, all are light sources, where a pigment ink print is a reflective source, which has entirely different characteristics). These end displays are not variable workspace displays. HDTV displays only in REC.709 workspace, its gamut, contrast, etc. are tightly defined. Web video uses the sRGB workspace. Etc.
I'm just sayin' that still photography and video have very different requirements. Trying to force still photography methods onto a video workflow is bound to be difficult and full of problems, as you have found.
The answer to your "How do I resolve this problem" question is perhaps to use the still photography tools for still photography, and the video tools for video. A stills workflow for stills, and a video workflow for video.
A video workflow implies doing color correction and color grading on external monitors that natively support the target work space (Rec.709 in the case of HDTV, Blu-ray, or DVD output [OK, technically DVD uses SDTV's REC.601 work space, but 709 is "close enough" that you can get by in all but the most critical applications]). IOW, use a production monitor, or at least an HDTV (calibrated of course), to judge final output.
Trying to color correct video on a computer monitor is just asking for trouble. As you well know by now.
A good place to start learning the video way of things when it comes to color correction and grading is Alexis Van Hurkman's Color Correction Handbook. Highly recommended; it answered questions that I didn't know enough to ask yet. Might for you too, IDK.

I am using PS cs6 and lightroom and I am having a hard time know what color space to choose. The lab that I am using told me that their color space is sRGB. Do I need to have both PS and Lightroom set at sRGB or should I have PS set at adobe RGB and jus

I am using PS cs6 and lightroom and I am having a hard time know what color space to choose. The lab that I am using told me that their color space is sRGB. Do I need to have both PS and Lightroom set at sRGB or should I have PS set at adobe RGB and just set my export from lightroom as sRGB?

Please post in the Photoshop forum.
http://forums.adobe.com/community/photoshop
Bob

I want remove some dark spots on a hand and color it flesh color. I'm very new to Lightroom, can anyone help me with this? Thanks in advance for any help!

I want remove some dark spots on a hand and color it flesh color. I'm very new to Lightroom, can anyone help me with this? Thanks in advance for any help!

Have you tried the Spot Removal tool (press Q key)?
New to Lightroom? Go here: Getting Started with Lightroom CC - YouTube
Spot removal: Lightroom CC - Removing Dust Spots and Imperfections - YouTube

Color spaces in Lightroom and Photoshop

I read that Lightroom uses the large ProPhoto color Space and then again, that it's gamma curve ist close to sRGB. So what is my color space when working in Lightroom? ProPhoto, or sRGb, or something else?
And what kind of a color management workflow between Photoshop and Lightroom do you advocate? Using ProphotoRGB or sRGB as color work space in Photoshop? I used to work in AdobeRGB in Photoshop. Has this to be changed to gain maximum color consistency?
Thanks again for any help!
Johann M Ginther

Hey Claude,
if it did not have an attached profile it is almost definitely in sRGB or, more rarely, Apple RGB. Lightroom always assumes sRGB for untagged files which is typically a safe bet. Photoshop generally uses the working space for untagged images. Since you had adobeRGB there, you should get a more saturated image in photoshop then in Lightroom. The same data is simply interpreted in a different color space leading to different colors. This has nothing to do with the monitor profile therefore and my initial hunch was wrong. So for untagged images in photoshop, you should usually assign sRGB to them instead of working space.
>As for calibration hardware we do use them here so I will use it but since the Mac was brand new out the box I assumed that it was ok...
Unfortunately, in general the canned calibration is not very good on Macs. I find very large differences between the shipped profile and a profile generated by a calibrator. Also, Apple ships profiles that set your display's gamma to 1.8 instead of the standard 2.2. This leads to many images in webbrowsers being too low contrast. Even Apple suggests recalibrating your screen at 2.2 if you do digital photography work (it's in their Aperture help files). In this case though the difference between Lightroom and Photoshop had nothing to do with the monitor profile but was related to photoshop interpreting untagged files in its working space instead of the more likely sRGB space.

Lightroom 4 and Color Efex 4

Similar Messages

Maybe you are looking for