Lightroom color popping when switching monitors?

So, this might be a silly question.  I have lightroom on one monitor and when I drag it over (the program window) to my other monitor it pops (changes color) after about 1/2 a second.  There is a shift in color.  I'm wondering if it is the monitors ICC profile or something weird like that?  anyone else have this issue.  Both of my monitors are samsungs (different models) and they are both using the Samsung natural color profile.  Thanks

The colours should "pop" slightly, but should end up the same after they pop. 
I have two dissimilar monitors (one much wider gamut than the other) but both calibrated/profiled.  If I drag the main LR window from one to the other, momentarily the colour is wrong for 1/2 second or so until LR re-renders in the correct profile for the new monitor.  For example, suppose the main window is on the wide gamut monitor and I drag it to the narrower gamut monitor.  Initially the colours are too pale (as it's using the profile for the wide-gamut monitor), then it re-renders in the correct profile and the colours become correct.
This is what should happen.  If you're saying that colours are not the same on the two different monitors (after allowing the 1/2 second) then I'd guess one or both of the monitor profiles is incorrect or corrupt. 
You say you have two different Samsung model monitors - but are you using the same profile for each?  That could be a problem.  Different monitors are very unlikely to want the same profile.  If these are Samsung-provided profiles, make sure you are using specific profiles for each monitor.  Better still: get a hardware colour calibration device (Spyder, Color Munki etc) and create your own profiles. 
Edit: an additional check.  Display an image on both monitors.  View on the main monitor in Library Loupe view (e.g. type E) and also display the same image on the 2nd monitor in Loupe view (e.g. type "Shift-E" or type the 2nd monitor icon on the film strip tool bar).  The colours should look identical (within the capabilities of the monitors; a wider gamut monitor might display very highly saturated colours more intensely, but most colours should be identical).  If they don't, one or other profiles is incorrect. 

Similar Messages

  • Clicks and pops when switching tracks..

    Ive had my 2ndgen shuffle for about a month now.
    Have started to notice over the last few days that it makes a clicky/poppy noise when switching tracks. Thing is I dont remeber it doing this prior to a few days ago but cant be sure on this point to be honest..
    So to clear this up anyone who notices this particular phenomenon please post so i know i am not cracking up or anything

    Ive had my 2ndgen shuffle for about a month now.
    Have started to notice over the last few days that it
    makes a clicky/poppy noise when switching tracks.
    Thing is I dont remeber it doing this prior to a few
    days ago but cant be sure on this point to be
    honest..
    So to clear this up anyone who notices this
    particular phenomenon please post so i know i am not
    cracking up or anything
    Sorry to post opposing data: I've had mine since 11/1/06 and have not noticed any clicking/popping... You might want to try restoring your Shuffle in iTunes (Settings tab) and seeing IF that cures it of this behavior.

  • 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..

  • Monitor color profile when switching between LR and PS

    I have a calibrated profile in use with PS.PS and LR are set to Adobe RGB color space but I use the calibrated profile. When I export an image from LR to PS it shows the mismatch dialogue box: Embedded Adobe RGB 1998, Working: Monitor calibrated profile.
    should I use the 1)embedded profile instead of working space, 2)convert to working space or 3)discard embedded profile? I will obviously reimport to LR when finished in PS.

    >it shows the mismatch dialogue box: Embedded Adobe RGB 1998, Working: Monitor3-7-08.
    Ow, this means you have Photoshop set up incorrectly. Go to Edit->Color settings and make sure that the top-profile (RGB) says adobeRGB. You should never have a monitor profile there except if you're a web designer.
    >DYP, you can change LR colour space to other than ProPhoto as default.
    No you cannot. You can only change the default profile Lightroom uses to send to Photoshop. Lightroom ALWAYS uses a prophotoRGB-like working space internally for every picture.
    >I set it to Adobe RGB to sync with camera and PS.
    If you shoot RAW, the in-camera setting does not matter and Lightroom will render as wide as prophotoRGB.
    >Would changing to ProPhoto colour space not cancel my calibrated monitor profile? Or am I misunderstanding the principles behind monitor calibration?
    No, they have nothing to do with each other. Color managed apps automatically translate between their working space and the monitor profile. This capability is the basic meaning of being color managed. They get the information about the monitor profile from the OS. You never have to tell them about it. Photoshop just knows it. You do not have to set it up anywhere.

  • Color changes when switching to discrete video card and back to integrated ML 2010 macbook pro

    Anyone experiencing this? It's driving me crazy! When ever the gt330 is activted the color becomes cool. When the intergrated graphics go then its back to a warm tint.

    Still getting this issue. Happens with Photoshop and chrome.

  • Desktop background stops functioning when switchiing monitors

    Thanks, apple forums - you archived my thread before it was solved!
    I have an original Core Duo Macbook Pro 17" with 10.6.2, and an external Samsung 1600x1200 LCD.
    When at home, I use the built-in 1680x1050 LCD for working. When at work, I keep the lid closed and plug in my 1600x1200 LCD using DVI.
    There are three problems that occur when switching monitors:
    1. All desktop icons disappear. No context menu appears with right click. No selection rectangle appears when dragging. This occurs 20% of the time.
    2. Desktop icons move approx 200 pixels right and/or down from their original locations. The selection rectangle does not appear under the mouse cursor but is also shifted by around 200 pixels right and/or down. I can double click on icons but I have to click 200 pixels up/left from where they appear on the screen. This occurs the other 80% of the time.
    3. Mouse cursor is heavily corrupted - it shows up as a random block of pixels approx 100 pixels wide and 20 pixels high. Mouse pointer will come back if I hover over an area of text, for example in Mail. This occurs randomly, around 50% of the time.
    To fix 1 and 2, I can do a "killall Finder" from a Terminal.
    If I have a web browser open when I switch monitors, the mouse location is incorrectly read and I have to close the window to correct this (i.e. when moving the mouse cursor down a drop-down box, the highlighted item is about 200 pixels down from the cursor location).
    It seems to me that there is some code in OS X that is broken when switching between primary monitors that are different resolutions. I'm looking to buy a new Mac but I won't be interested until this problem is fixed since this affects my daily work.
    Thanks.

    The problem occurs with any monitor a different native resolution to the MacBook Pro's built-in 1680x1050 panel.
    The problem does not show up if the externel panel is connected before cold-booting the computer because the nature of the problem is that the problem occurs when changing monitors. I will connect the externel panel before coming out of sleep, or disconnect after going to sleep.

  • Aero switches off when extern monitor is rotated by Nvidia ControlPanel

    Please see subject
    Aero works fully when desktop is expanded to the 2nd monitor in normal view.
    any workaround ?
    Message was edited by: mhoffmann
    sorry, I forgot to mention my hw: Satellite a100-02b ( geforce go 7600 )
    .. and when I reboot Vista behaves a bit strange.
    a few seconds all seems ok but then it sets back the external monitor to 16-bit colour and minimum Vfrequency ( 60 HZ )
    and a message pops up that the "Desktop windows manager" has been closed due to a problem.
    Is this perhaps because..
    1) It's an old CRT, not specially known ( standard pnp-driver )?
    2) the vista capability of the graphics adapter is not sufficient in this configuration ?
    I heard somewhere that there is a switch in the registry, that disables the dwm.exe's test, whether the hardware is
    able to support the aero-technologies. would that be a way to fix that ?

    Hi,
    and thanks!
    > Anyway, I try to understand what you did on the
    > notebook
    > You have switched the display to the second external
    > monitor then you have changed the display position
    > (you have rotated the display) and you have tried to
    > use the Aero on the external monitor.
    > Am I right???
    No I've EXPANDED the desktop to the 2nd monitor. In normal view Aero works right then on BOTH monitors.
    Only when I rotate the extern monitor this problem occurs.
    I think, that this special configuration is a bit unique ( but very comfortable to work on )
    and therefore not foreseen ( eeh, sorry for my english ) by the programmers of the drivers or
    the dwm-team at MS.
    ok, when I add the 1280*800 of the laptop screen and the 768*1024 of the CRT
    I end up at 2048*1024 ( the unused area included )which is quite near to the absolute maximum of 2048*1536 the graphics adapter
    supports on ONE monitor at all. Perhaps that's just too much...
    on the http://support.toshiba-tro.de/kb0/TSB7101O90002R01.htm you mentioned, the limit for aero with my 128 MByte VideoRam
    would be 2.304.000 pixels - but only when one monitor is in use. There's no information about multi-monitor use.
    so what, Aero is not that important, but when I have some time again, I will experiment a bit...
    Ciao !

  • Ps CC: Color Shift On Second Monitor When Using FullScreen Mode

    I have been suffering from a new issue since re-calibrating my external NEC Multisync monitor with an i1 Pro calibrator.
    Though colors across the system as a whole are improved over similar calibrations with a SpyderPro4, whenever I use the full-screen mode in Photoshop CC (using the F key), the color shifts radically red.
    I have tested the other solutions of disabling graphics processing and OpenGL/OpenCL to no avail.
    Some testing has revealed that in full-screen mode the colors most-closely resemble the profile for the connected Macbook Pro Retina.
    Is Pshop loading the wrong ICC profile just when switching to Fullscreen? I can usually get the correct profile back if I command-tab to another program and back again, but this is an unnecessary workaround.
    Any advice would be much appreciated.
    Alex

    this kind of thing just cannot happen with a high-end Eizo or NEC PA - with these units, there is no video card calibration LUT at all, because it's handled internally in the monitor.
    Dag, that's what we expect. But why are the LUTs on the graphics card slightly modified?
    The programs Display Profile, Calibration Tester (and Calibration Loader) belong to the GMB ProfileMaker package.
    Best regards --Gernot Hoffmann
    P.S.:
    Perhaps it works like this:
    In advance to an actual calibration by ColorNavigator, the program writes these modified values with
    equal "deviations" for R,G,B into the graphics card LUTs. Either as a marker or as numerical preparation
    for the hi-res correction in the monitor itself.

  • Command-tab pop-up list of apps switches monitors

    The command-tab pop-up list of apps switches monitors sometimes on my two-monitor system. Why? Why doesn't it always appear on the monitor with menubar specified in Displays preference panel? How do I switch it back when it moves to the wrong monitor? Very annoying because I can't figure out why it moves to the other monitor in the first place!  (actually running OS X 10.9.4 -- not Mavericks -- but you don't seem to have a community for OS X 10.9)

    That unfortunately doesn't work. I just tried it. For the last couple minutes, the command-tab app list has been appearing on my "main" monitor (the one I selected in Display prefs to have the menu bar). When I click in my "secondary" monitor to highlight its menu bar and then type command-tab, the app list still appears on the main monitor. Doesn't make a difference whether I click on the desktop background or a Finder window or an app window on the secondary monitor, when I hit command-tab the app list still appears on the main monitor. And all of that is OK. I'd like to have the command-tab app list ALWAYS appear on the main window.
    The problem is that sometimes the app list switches to the secondary monitor and I don't know why. And after that happens, I can click all I want on the main monitor -- desktop, Finder window, application window -- and the app list still appears on the secondary window when I type command-tab. I'll give up trying to make it switch to the main window and then, at some point, I'll notice that it has switched back to the main window. I can't figure out why it has this behavior, which seems to be random. Or at least I can't figure out what to do to make the pop-up app list return to the main window.

  • I want to connect my IMAC to TV with HDMI cable. I did it before going to Dispaly and Arrangments and then mirror. Now when I go to display I dont have to option of arrangements. Olny {Display and Color} pops up. Any ideas what happend to arrengements?

    I want to connect my IMAC to TV with HDMI cable. I did it before going to Dispaly and Arrangments and then mirror. Now when I go to display I dont have to option of arrangements. Olny {Display and Color} pops up. Any ideas what happend to arrengements?

    For the "Arangements" option to appear, the external display must be turned on with the correct input selected and connected to the computer.  Then close system prefs, reopen, go to "Display" and "Arrangement" will be along the top. 

  • Lose Dock when switching from External monitor

    When I disconnect my external monitor and open my MacBook monitor the Dock is not visible except when I cursor over the Dock area it's starts to reappear? It's very strange.

    I think the problem revolves around the change of resolution when switching back. Because my Windows for Safari are out of whack too. So I am thinking the Dock is position wrong at first.

  • Every click in Color takes 10 seconds when Kona monitoring is turned on

    As an editor getting asked to do more color correction I've decided to move beyond Colorista and am learning Color. Since I have a properly calibrated broadcast monitor there's no reason not to! But what I am finding is when I have external monitoring turned on in Color, via my Kona LHe, then nearly every click and parameter change gives me about a 10 second beach ball until Color catches up and updates the frame in the interface and on the external monitor. It doesn't happen when external monitoring is off. Certainly not a way to work!
    Anyone seen something similar?

    I ain't at home either so I can't properly verify software version but i have never had these issues at all.
    Aja LHe driver 6.0.3 NDD version.
    OSX 10.5.7
    QT, 7.4.6, I think????
    Color 1.0.4 (isn't that latest pre-1.5 version?)
    You might try using the Aja Uninstaller and then reinstalling the software but as you say, this has been happening through various versions, could be a software installation gone bad? Like I say, I've had wonky things happen within Color but nothing involving my LHe.

  • CC window pops up when switching desktops in Mac OS X 10.8.4

    I have just updated all my apps to CC. Everything looks fine so far. The only glaring annoyance I see is that the CC window pops up when switching desktops in Mission Control. I normally work with four to five desktops and switch frequently between them. The CC window keeps popping up from the menu bar icon even though there is nothing new to report or alert. Is this a bug, or is there some way to stop this?
    P.S. I just tried selecting "Open As Window..." and the problem goes away. However, if I then select "Pin to Menu Bar..." again, at first it will seem to stay quiet between desktop switches, but as soon as I open the window the first time and close it again, it will resume the annoying behavior when switching between desktops. Seems like a bug to me.

    Hi Geezjan,
    I recently responded to another user which was reporting the same thing. I've passed this info on to our engineering team. Thanks for letting us know.
    http://forums.adobe.com/thread/1235274?tstart=60
    -Dave

  • Lightroom CC isn't including color labels when images are imported

    I've tried this several times, but it doesn't work. Lightroom CC will import metadata and even star ratings, but it won't import the color label data assigned to the images from within Bridge. How can I get that information to be imported?
    In other words, working in Bridge CC I assigned star ratings and color labels to a folder full of JPG files. When I import those files into Lightroom CC, the images, metadata and the star ratings are imported, but no color label data was imported. None of the images have color labels when viewed in LR. They still retain the color labels when I view the files in Bridge CC, but they don't appear in LR.

    I just struggled with this for an hour. Any changes made to labels inside Lightroom 5 didn't show up in Bridge CC after reading metadata from file, and imports into LR5 did not properly show Bridge CC's label colors. Instead, only a tiny white rectangle at the bottom right of each labeled thumbnail showed in LR5.
    Finally figured it out. In the Lightroom 5 file menu up top, go to:
    Metadata --> Color Label Set --> Bridge Default (select this option)
    'Lightroom Default' was previously selected in mine, as I suspect all Lightroom 5 installs are initially.
    Make sure that the names beside each color are identical in both Bridge & LR, or you will still have syncing problems.
    This should fix your problem!

  • Monitor color profile, fast switch script

    Hi everyone,
    I often switch between two monitor color profile, the default one "LED Cinema Display" and the calibrated one, named with the date of calibration (ex:"22June2011").
    Is there a way to fast switch between this two with a script, without entering in monitor preferences and move to color tab every time? Maybe set an icon on the menu bar... Or an icon on the dock...
    Thanks,
    Filippo

    More important, the question is not about color management, is about scripting.
    Otherwise we're just wasting words, that doesn't seem the right place to speak about profiling...
    Do you want help or not? What you're asking has everything to do profiling and color management. You're going about the use of profiles for your monitor completely wrong.
    Any profile is an image of how that, and only that device displays, captures or reproduces color. The only monitor profile that makes any difference is one you create. Since you're using i1Profiler, then you must be using an i1 Pro to profile the monitor.
    The monitor profile you made with i1Profiler is the only one you should be using. It is an exact description of the white point, black point, gamut and color range of the monitor you are looking at. The canned profile has nothing to do with the monitor in front of you. It's a generic average that is just short of completely useless since it is not a direct description of the monitor you own. Forget the "LED Cinema Display" profile, or any other canned profile on the system.
    I can only assume you're trying to simulate CMYK color in Photoshop. To do that, your start with the monitor profile you have. To create a meaningful CMYK simulation, you need to create your own inks file to use as your CMYK color space in Photoshop.

Maybe you are looking for