JPG colors different from Lightroom Display

I am aware of issues when you try to print an image without taking into account the calibrated color profiles of both the printer and your monitor, but not when it comes to displaying 2 images on the same monitor.
To put it simple: I process an image in Lightroom. I get the desired result, create a JPG out of it.
The JPG is very different from what I had in Lightroom. Much lighter among others.
What would be a potential reason to explain such behavior?

CSS Simon wrote:
You said: "I did click "Reset all default Develop settings" and reimported the JPG. Now it does look exactly the way the original RAW image looks."
So I assume you mean "why is the jpeg displayed in another program not the same as the raw (or the jpeg, for that matter) displayed in LR?". Either the other programs aren't colour managed, or the monitor isn't correctly calibrated and profiled? See Jao vdL's post.
Indeed. Now it makes sense. What totally confused me was when the JPG, reimported in LR, did not look the same as the RAW image. I thought that if LR was color managed, then both images should look the same.
After I clicked the "Reset all default Develop settings", the reimported JPG looks "correct". Not sure I fully understand what happened however
CSS Simon wrote: To your other post: Lightroom uses ProPhoto RGB as its working space during editing, so in Develop Module the image displayed is in that colour space. In Library Module, LR displays the previews which are stored in Adobe RGB, I believe. This is true whatever the colour space of the image. This is of no consequence to the user, as LR is colour managed, and whatever working space is used internally is mapped to the monitor colour space by using the monitor profile. Provided there is a correct monitor profile, that is.
Interesting. So if my monitor is not properly calibrated, it would be possible that the image in the library module could look different from the same image in the development module? Good to know
CSS Simon wrote:
Colour management to an output device uses two profiles: the profile of the image (typically sRGB, Adobe RGB, ProPhoto RGB or usually another standard profile) and the profile of the output device (monitor or printer as appropriate). The colour-managed program uses the two profiles to map the RGB data from the image colour space to the device colour space.
Is your monitor calibrated and profiled with a hardware colorimeter (Spyder, Display One, Color Munki etc)? If not, colour displayed by different programs will not always be predictable (and will usually not be correct). Even if it is calibrated and profiled, only colour-manged programs will display the right colour. Programs that are NOT colour managed (or not properly managed) include Internet Explorer (even IE9), Chrome, most Windows components pre Windows 7 (in W7 the photo viewer is colour managed, the desktop and most other components aren't)...
Not calibrated as of now. Will fix it soon now that it seems that it is the reason behind my problem
What you are saying is consistent with what I had read, and this is actually what confused me the most. Because I read that Firefox was color-managed, but the JPG looked the same in FF, IE, Irfanview and LR (JPG reimported before I clicked the "reset settings" button). So it looked to me like if color-managed (FF) and non-color managed (IE) software would display the JPG the same way, but yet my LR RAW image would look different. When Windows Image Viewer displayed the JPG the same way LR did for the RAW, this is where I got totally lost.

Similar Messages

FCPX/Quicktime displaying colors different from everything else

FCPX and Quicktime display videos exactly how I color correct them in FCPX. Opening them in Compressor, VLC, MpegStreamclip, Youtube and Vimeo shows them darker and extremely red.
I've read and done pretty much everything I could find on the net and in my own head to try to work around this. Conversion to various prores formats before editing, doing editing, and after editing, converting to mp4 both by export and by saving in both QT and in MPEGstreamclip. Opening QT and doing the blend/straight alpha method, etc. I'm probably missing one here.
My monitor is a Dell u2711 that I calibrate with an Eyeone display 2. Switching to the built in profile, or doing a custom profile doesn't change the outcome of the color shift. Gamma display changes also don't change the outcome.
This is a screen shot of QT7 and Mpegstreamclip with the same image. The jpg from png compression did make the image slightly different than what I see on screen but not much. These are open side by side on the same monitor.
I'm pretty much at a loss. Could this be colorsync not communicating correctly with things outside the QT workflow? I'm perplexed why compressor also shows the change.
I haven't done any updates that I recall other than the camera raw update that apple told me to do. Not sure that would of effected anything.

Plugged in an old Samsung sycnmaster 971p and put it on 'display' as it's color profile. The images are much better, not as much shift. FCPX and VLC are pretty close to each other on this monitor.
The quicktime preview screen is still pretty red.
Guess it has something more to do with the monitor than I thought. It is a slightly newer monitor we had just started editing on after calibrating it. It displays at a higher resolution than we were previously using, and uses billions of colors instead of millions. Could that of been it's issue? I'll need to read up on wide gamut displays and why they do this shifting.
Vimeo still completely messes with some of the settings but I can blame that on vimeo.

Why does Photoshop display colors differently from the other applications even in sRGB mode ?

Hello all !
Here is my problem :
Photoshop is set to use sRGB workspace (in edit/colors.../workspace/RVB).
If I understand correctly this is how all native windows applications work.
This means Photoshop and the other applications should display the same colors on a file with a sRGB profile.
Now this is the case until I calibrate my monitor.
When I do, Photoshop colors become different from the other applications (irfanview, explorer, browsers...).
The only way I found to let everything display the same colors is to set Photoshop to use Proofing/RVB Monitor.
What upsets me even more is that Photoshop colors look "better" to me (dark grays seem to dark to me in the other applications.)
I have read that this is because Photoshop takes the new profile into account and others applications do not. But I don't think this is relevant here because everything is in sRGB so the only profile is my monitor's and I think calibration is handled globally by windows : everything (including browsers, explorer, and Photoshop) changes color if I choose to apply the monitor's profile or not with windows color management tool ("use my parameters for this device").
Here is my system configuration :
- Photoshop CS4 (11.0.2)
- Windows 7 64 bits
- HP ZR2440W and DELL 2209WA (these are not wide gamut screens)
I have spent two days trying to figure the logics behind this and really am upset. Any help would be greatly appreciated. Don't hesitate to ask me if there is something that is unclear or some information I forgot to mention.
Thanks in advance,
Yannick

That sounds like an invitation to continue to talk about the issue. Fair enough.
I'm not sure where you're getting "insecurity"... I am just trying to help you help others more effectively.
I invite you to re-read just the first sentence of what you wrote very carefully, putting yourself in the shoes of someone struggling with both the terminology and the concepts:
Photoshop (CMS) reads an embedded ICC profile and CONVERTS it to the custom monitor profile for a theoretical 'true color' display
Think about what "Photoshop (CMS)" might mean to a person who doesn't know the acronym might stand for "Color Management System" (which is I assume what you meant). Adobe themselves don't call it "CMS", they use the acronym "CMM" (Color Management Module). The term "CMS" is used in the computer industry for about a dozen different things.
While a color profile might have been embedded in an image file before it was opened by Photoshop, Photoshop works on documents. A profile is not "embedded" in a document, it is maintained by Photoshop with the document and describes the color values in the document. If Photoshop opens a document without an embedded profile, depending on settings and user choices it might assign a profile or it might even operate on the document without color-management. Oversimplification doesn't help people when they're trying to learn new things unless it's described as such, for example, "This is a bit of an oversimplification..." or "Generally speaking..."
Not every monitor profile is a "custom monitor profile". Quite often a standard profile (e.g., sRGB IEC61966-2.1) is associated with a monitor by the operating system as a default, or a factory profile is installed by a driver package or system update. Your use of the term "custom" is a bit ambiguous and could be read as implying the creation of a profile using a calibration and profiling device specific to the particular monitor.
Photoshop's color management code does not convert an embedded ICC profile at all (read carefully what you wrote). As I said, it transforms color values. That was the key error in your description that prompted me to comment.
If ever there is a time to pick words carefully, it's in a color-management discussion.
-Noel

Exported JPEG differs from Lightroom image

Hi all....
When I export my photos from lightroom as JPG, the colors of the photo are dramatically changed. (image looks much colder)
As first, I thought I may be a problem wiht the colour space, but I have try changing them without any success...
Any idea??
Thanks in advance...

Sorry that I didn't answer sooner. I must have missed this thread and your questions.
I haven't started calibrating my monitor yet (I've left it at sRGB for right now), but what I really want is for what I see in Lightroom to be the same as what I (and others) see on Flickr.
The only way to get other people to see close to the same thing as you see in Lightroom is to calibrate and profile your own monitor and export to sRGB. If you have a good monitor yourself, with a gamut close to sRGB, you will get very close correspondence between Lightroom and unmanaged browsers. If your monitor is one of the wide gamut deals or a crappy laptop with a very small gamut, your display in the unmanaged browser will always be completely wrong, even if you use sRGB. Nothing you can do about that. On such displays you basically have to use a managed browser. The Lightroom display will ALWAYS correspond to your browser if the browser is color managed and you correctly calibrated the screen. Color managed browsers include Safari, Firefox (with some problems) and development versions of Chrome.
because my monitors are set to sRGB
You don't want to do that. It is an OK test for a corrupt monitor profile, but it guarantees incorrect color. LR and your unmanaged browser might look the same, but they are both wrong. Calibrate and profile.
If I properly calibrate my monitor, the colors coming out of Lightroom when exporting to sRGB should still be the same as what I see while working in Lightroom, right, or am I better off with sRGB color profiles so that they're always exactly the same?
As I explain above, the colors when you calibrate and export to sRGB will look almost the same in unmanaged browsers except when you have a display with a gamut very different from sRGB. The problem is that under no realistic circumstance can a unmanaged browser show you correct color.

Background color differs from computer to computer

1. I have a page where users can enter some data, some of the fields have back ground color YELLOW on SOME computers (same browser version IE 7...) ,I never seen it on my desktop and some others but I see it on few others.
2. some of the text looked BOLD on some computers.
What could be the reason?
3. some of the buttons seems to be diff than other, Image vs HTML buttons , I saw the threads talk about "rebooting display server". what is display server. I reboot apache but nothing changes. what is display server?

Display server is X.11 server, different from Apache, ask your DBA for bouncing this
Tapash

[SOLVED] ls colors different from tab completion colors

I've been configuring the colored output of ls and I've got ls colors set, but the colored output from tab completion is different sometimes making it hard to read the files/directories. Does anyone know where the file that controls the tab completion colors?
http://i.imgur.com/GwByh.png is a picture showing the issue.
.dir_colors
# Configuration file for dircolors, a utility to help you set the
# LS_COLORS environment variable used by GNU ls with the --color option.
# Copyright (C) 1996, 1999-2011 Free Software Foundation, Inc.
# Copying and distribution of this file, with or without modification,
# are permitted provided the copyright notice and this notice are preserved.
# The keywords COLOR, OPTIONS, and EIGHTBIT (honored by the
# slackware version of dircolors) are recognized but ignored.
# Below, there should be one TERM entry for each termtype that is colorizable
TERM Eterm
TERM ansi
TERM color-xterm
TERM con132x25
TERM con132x30
TERM con132x43
TERM con132x60
TERM con80x25
TERM con80x28
TERM con80x30
TERM con80x43
TERM con80x50
TERM con80x60
TERM cons25
TERM console
TERM cygwin
TERM dtterm
TERM eterm-color
TERM gnome
TERM gnome-256color
TERM jfbterm
TERM konsole
TERM kterm
TERM linux
TERM linux-c
TERM mach-color
TERM mlterm
TERM putty
TERM rxvt
TERM rxvt-256color
TERM rxvt-cygwin
TERM rxvt-cygwin-native
TERM rxvt-unicode
TERM rxvt-unicode-256color
TERM rxvt-unicode256
TERM screen
TERM screen-256color
TERM screen-256color-bce
TERM screen-bce
TERM screen-w
TERM screen.rxvt
TERM screen.linux
TERM terminator
TERM vt100
TERM xterm
TERM xterm-16color
TERM xterm-256color
TERM xterm-88color
TERM xterm-color
TERM xterm-debian
# Below are the color init strings for the basic file types. A color init
# string consists of one or more of the following numeric codes:
# Attribute codes:
# 00=none 01=bold 04=underscore 05=blink 07=reverse 08=concealed
# Text color codes:
# 30=black 31=red 32=green 33=yellow 34=blue 35=magenta 36=cyan 37=white
# Background color codes:
# 40=black 41=red 42=green 43=yellow 44=blue 45=magenta 46=cyan 47=white
#NORMAL 00 # no color code at all
#FILE 00 # regular file: use no color at all
#RESET 0 # reset to "normal" color
DIR 01;34 # directory
LINK 01;36 # symbolic link. (If you set this to 'target' instead of a
# numerical value, the color is as for the file pointed to.)
MULTIHARDLINK 00 # regular file with more than one link
FIFO 40;33 # pipe
SOCK 01;35 # socket
DOOR 01;35 # door
BLK 40;33;01 # block device driver
CHR 40;33;01 # character device driver
ORPHAN 40;31;01 # symlink to nonexistent file, or non-stat'able file
SETUID 37;41 # file that is setuid (u+s)
SETGID 30;40 # file that is setgid (g+s)
CAPABILITY 30;41 # file with capability
STICKY_OTHER_WRITABLE 32;40 # dir that is sticky and other-writable (+t,o+w)
OTHER_WRITABLE 35;40 # dir that is other-writable (o+w) and not sticky
STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable
# This is for files with execute permission:
EXEC 01;32
# List any file extensions like '.gz' or '.tar' that you would like ls
# to colorize below. Put the extension, a space, and the color init string.
# (and any comments you want to add after a '#')
# If you use DOS-style suffixes, you may want to uncomment the following:
#.cmd 01;32 # executables (bright green)
#.exe 01;32
#.com 01;32
#.btm 01;32
#.bat 01;32
# Or if you want to colorize scripts even if they do not have the
# executable bit actually set.
#.sh 01;32
#.csh 01;32
# archives or compressed (bright red)
.tar 01;31
.tgz 01;31
.arj 01;31
.taz 01;31
.lzh 01;31
.lzma 01;31
.tlz 01;31
.txz 01;31
.zip 01;31
.z 01;31
.Z 01;31
.dz 01;31
.gz 01;31
.lz 01;31
.xz 01;31
.bz2 01;31
.bz 01;31
.tbz 01;31
.tbz2 01;31
.tz 01;31
.deb 01;31
.rpm 01;31
.jar 01;31
.war 01;31
.ear 01;31
.sar 01;31
.rar 01;31
.ace 01;31
.zoo 01;31
.cpio 01;31
.7z 01;31
.rz 01;31
# image formats
.jpg 01;35
.jpeg 01;35
.gif 01;35
.bmp 01;35
.pbm 01;35
.pgm 01;35
.ppm 01;35
.tga 01;35
.xbm 01;35
.xpm 01;35
.tif 01;35
.tiff 01;35
.png 01;35
.svg 01;35
.svgz 01;35
.mng 01;35
.pcx 01;35
.mov 01;35
.mpg 01;35
.mpeg 01;35
.m2v 01;35
.mkv 01;35
.ogm 01;35
.mp4 01;35
.m4v 01;35
.mp4v 01;35
.vob 01;35
.qt 01;35
.nuv 01;35
.wmv 01;35
.asf 01;35
.rm 01;35
.rmvb 01;35
.flc 01;35
.avi 01;35
.fli 01;35
.flv 01;35
.gl 01;35
.dl 01;35
.xcf 01;35
.xwd 01;35
.yuv 01;35
.cgm 01;35
.emf 01;35
# http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
.axv 01;35
.anx 01;35
.ogv 01;35
.ogx 01;35
# audio formats
.aac 00;36
.au 00;36
.flac 00;36
.mid 00;36
.midi 00;36
.mka 00;36
.mp3 00;36
.mpc 00;36
.ogg 00;36
.ra 00;36
.wav 00;36
# http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
.axa 00;36
.oga 00;36
.spx 00;36
.xspf 00;36
I'm using zsh.
Last edited by livinglifeback (2011-08-13 18:52:03)

I myself just uses the standard colors and don't change them from default, but I do get the same colors for both ls and completion with this in .zshrc:
eval `dircolors -b`
zstyle ':completion:*' list-colors ${(s.:.)LS_COLORS}

Color space from lightroom to flickr

Can anyone help me with this question....having developed raw images in lightroom, I then may publish some of them on my flickr account. When these images are exported directly from Lightroom to Flickr, are they automatically exported in sRGB?....especially considering that Lightroom is a ProPhoto RGB color managed application. I ask this because I know that people may look @ my images in non-color managed web browsers, like Internet Explorer, and if the images are exported in the ProPhoto RGB color space, the image colors will render poorly on that non-color managed web browser. Are they automatically exported in the web friendly sRGB?? Thanks for your comments:)

Perhaps you could help me with another question. I always shoot in raw and process using ProPhoto RGB throughout my entire workflow. However, 5 years ago, I shot in Jpeg. I couldn't tell you what colour space my camera was set to then. When editing those JPEGS in Lightroom, in what colour space should I apply to those images when I send them over to Photoshop? I know JPEGs already have a colour space applied, but the camera I used then is long gone and therefore can't remember if they were shot in sRGB or Adobe RGB. Also, whatever colour space I do use when exporting from Lightroom to Photoshop, I should set up Photoshop's working colour space to match the image's profile, correct? So, should I apply sRGB or Adobe RGB to my JPEGs when going from Lightroom to Photoshop?? Thanks:)

In Spry menu, can I make the dropdown colors different from the main one?

In this menu at the link, I would like to keep "who we are" in the color it is, but make its submenu colors different. I can't see to find in the CSS where to do that without changing both the main and sub menu colors.
Homepage

Based on the default Spry menu code you are correct that it is all or nothing. The only alternative you could do is create your own custom CSS class to use on all sub-menu items on the drop-down to override the colors. This declaration would need to be after the Spry submenu one that you have found because the browsers will read CSS from start to finish so the later declarations will override the earlier ones.

Opening jpg in photoshop from lightroom

I have Lightroom 4.2 and Photoshop CS6. If I'm viewing a photo in LR and select edit in CS6, the photo doesn't open in camera raw, even though I have CR selected in photoshop preferences as my preference. Is this normal?

You cannot open directly into ACR from Lightroom. Lightroom and ACR perform the same functions. In the transfer from Lightroom to Photoshop the design is for ACR to simply interpret the adjustments made in Lightroom, and apply those adjustments to the image that is opened in Photoshop. Technically speaking, ACR isn't needed for anything else because it is simply a duplication of effort. So if you want to return or enter ACR, you have to do as Rick indicated, and double click on the smart object in the layers panel.

Selected variable value is different from the displayed value

Hi all,
I have an issue with variable selection in portal. I have a IO - customer which is compounded to source system. So I have soem customers with the same key with different sources. And I have a variable created on customer. For ex - i have 3 customers like below.
SA/1234567
BP/1234567
F5/1234567
1 - And when I search for a customer 1234567 - I find only one customer that is SA/1234567. And IO properties are set to read all the masterdata values and not infoprovider or posted values. - thats issue one - I would like to see all the three and let the user select what ever he wants.
2 - Now when I select SA/1234567 and run the report. It shows me data for F5/1234567 - which is correct data for that customer. But in the template I have a info field web item to display the selected variables on the screen. That info field shows the Customer as BP/1234567 - which is wrong and confusing. I checked the properties of the web item and everything seems ok. So in the variable screen I get a value, the result set if of another value and the variable value that shows in the Info tab is another customer. - Driving me nuts
3 - When I recreate the same scenario in 3.x query - everything works the way they should - this only happens in 7.0 query. What am I missing here??
Any pointer or insight is appreciated - sorry for the long post.
Voodi
Edited by: voodi on Jun 8, 2010 2:26 PM

Sorry - its not how its displaying the values rather what its displaying - it misses on 2 other values from the three - though the Bex setting in IO are set to read all the values from materdata table. And in the query I'm using IO properties. And display settings are ok

Colors Different than Cinema Display

I was trying out different desktops, and I noticed that my Cinema Display shows colors significantly brighter than my MacBook Pro (I'm in dual display mode). There seems to be hardly any contrast on the Macbook Pro compared to the Cinema Display... How do I fix this? --To elaborate, I notice the cinema display (20" by the way) shows colors more vibrantly than the MacBook Pro. The MBP looks like it has a gray cast over it (I can especially tell with the Apple desktop picture of the green curled leaf).
AHH!!! Just while writing this (actually when I turned Front Row on for a second), a dead pixel popped up on the screen!!! Can I fix this? Will Apple exchange it? It's been less than 14 days since I bought it...
Thanks.

You would need tools like the ColorVision Spyder 2 or something similar. It requires both hardware (spyder that measures color and brightness of screen) and software. The first step would be to calibrate and profile the MBP and use it's black and white point settings for the ACD reference. Final step would then be to calibrate and profile the ACD using the MBP's black point and white point. The colors, brightness and contrast would be very close, if not visually identical.
http://www.colorvision.com/profis/profis_view.jsp?id=602
Monitors and displays can not be visually calibrated accurately. Only a hardware and software solution is accurate for print etc.

Offline preview differs from online display of Japanese text

I can't figure out why my web site in English and Japanese cannot correctly display the Japanese type when uploaded. The offline preview is fine, but the online version turns the Japanese to gibberish. I have set the charset="UTF-8" in metatags and in the javascript code.
Thinking that I may have missed a supporting file in the upload, as a test, I downloaded the entire directory and opened the file offline, but it again works fine on my desktop. The same browsers (Safari, Chrome and Firefox) used for online and offline viewing.
Why won't my Japanese text display online when the offline preview is fine ?

Have you set the correct charset on your webpage? If not try to put this within the head tags on your page:
<meta http-equiv="Content-Type" content="text/html; charset=shift_jis">
Hope this works.

Red color tint from lightroom

I just processed photo in LR3.6 and PS5.1, and even tried LR4 beta, all have same result. Photos are done, take it into bridge to create a pdf to email and during the conversion all the photos get a redish tint but it's only viewable on other computers. Not running LR or PS. I calibrated my monitor and still the same. I notice when opening the files on my computer they have a red tint then it goes away-using bridge or LR3 or LR4 beta. I assume its a setting somewhere. I first noticed it when in LR4 beta and I did a send to email, all the photos had a red tint applied and that was viewable on my comp.

If the histogram has a red tint, your monitor profile is bad. That is one of the prime symptoms of having a corrupt profile.
You need to get a hardware calibrator and calibrate your screen.
As a stopgap measure, you can go into your operating system and change the default profile to sRGB, but that won't give you true colours, just better ones.
Hal

CS2 problem with 5D MKII RAW files from Lightroom 2.2

Ok, this one is weird. I have tried it on two different computers with the same resulting problem. If I convert a full size RAW 5D MkII to Tiff in the new Lightroom 2.2, then bring it into CS2 and covert it to 8-bit and try to save as JPG, it always comes up with a program error. I tried an sRAW file with the same process and it worked fine.
Just to make sure I did have something else messed up, I converted in DPP to tiff and then went to CS2 and saved as JPG just fine.
Anyone else try this and see a problem? Looks like it's a combination of a problem with the new Lightroom, plus CS2.
It almost seems like CS2 doesn't have enough memory to convert the file to jpeg. I have had this program error before in CS2, but with much larger files. The 5D MKII should not overrun memory.

This is a known bug in CS2 where it trips up because of the (valid) metadata written by Lightroom. You need to delete the xmp metadata written by Lightroom from the file before saving as jpg or export from lIghtroom with minimize metadata checked.

ALV GRID - Handling selected rows? Sorting in OUTTAB is different from ALV

Dear Experts ,
I have a transaction with ALV grid. I have defined several application specific functions to the ALV grid tool bar. My requirement is to handle the ALV tool bar functions only for the selected rows.
Code snippet:
DATA:
LS_GRID_DS TYPE TYS_DS.
TYPES: BEGIN OF TYS_DS.
INCLUDE   TYPE TYS_ALVGRID.
TYPES: STRUCNAME LIKE DD02L-TABNAME.
TYPES: PRETAB    TYPE ZTAB_T,
       OUTTAB    TYPE ZTAB_T,
       OUTTAB_HIDDEN TYPE ZTAB_T,
       OUTTAB_SUM TYPE ZTAB_T,
       OUTTAB_ROLLBACK TYPE ZTAB_T,
       END OF TYS_DS.
LOOP AT ls_grid_ds-marked_rows INTO ss_index_split
       WHERE rowtype IS INITIAL.
( Marked rows is correctly giving the row numbers of the highlighted rows)
READ TABLE ls_grid_ds-outtab INTO ss_sel_rows_ds_split
               INDEX ss_index_split-index.
ISSUE : Sorting in ls_grid_ds-outtab internal table is different from ALV Grid display.
Hence, though ls_grid_ds-marked_rows giving correct rows, I am not able to handle the my requirement correctly.
Why sorting in gs_grid_ds-outtab is different from ALV display? How can they made in sync?
Thank you in Advance.
Sravan.
Edited by: Raja Sravan on Jan 16, 2009 1:13 AM

Hello Raja
The OUTTAB is usually in sync with the display on the frontend grid control because it is a CHANGING parameter (of method SET_TABLE_FOR_FIRST_DISPLAY).
Question: Do you "feed" ls_grid_ds-outtab to the parameter IT_OUTTAB of method SET_TABLE_FOR_FIRST_DISPLAY?
If not then it is obvious why you get discrepancies.
Regards
Uwe

JPG colors different from Lightroom Display

Similar Messages

Maybe you are looking for