Disable or modify default monitoring profiles

We are planning to deploy Ops Center 11g for provisioning and patching, but we's also like to take advantage of its hardware monitoring profiles. But we have other ways of watching CPU, memory, etc. Is there a way to disable the default monitoring profiles that get attached to each "Server" asset? Or modify the default profile to disable some of the monitoring rules?

We found the only way to do bulk changes was through the API. In our case, we've spent enough time digging in the CLI (since it's written in python/jython), we added a couple calls to the API into there and were able to do scripted changes to the profiles. You have to understand the java side of things to get there, but it's easier (IMO) to invoke from the CLI.
Edit: oh, and we copied the defaults, labelled them with our own names, and edited them from there.
Edited by: 925553 on Apr 4, 2012 10:15 AM

Similar Messages

Lightroom/photoshop seem to use the default monitor profile when printing

I had my color workflow setup fine and I have no idea what happened. It's been working as long as I can remember. My monitor is calibrated with an eye-one display 2. When I print, the print colors no longer match the monitor colors. Trying to figure out what is going on, I noticed that if I switch the monitior profile to "Display" the print colors made match the "Display" monitor colors rather than the monitor colors present when its profile is set to the calibrated profile. I get the same behavoir in photoshop and lightroom.
To recap:
1. profile/calibrate the monitor with an eye-one display 2
2. set the monitor profile to the new calibrated profile.
2.5 take a look at the soft proof. everything looks good.
3. make a print using the correct paper profile, lightroom or photoshop managing the color,
4. the print colors don't match the monitor
5. fooling around, set the monitor profile to "Display". Those are the colors that show up on my print.
Any ideas as to what's going on?
The particulars: OSX 10.7.5, Photoshop CS6 13.0.4, Lightroom 4.4
Thanks.

There are lots of colour spaces here!
The image has a colour space. If it's a jpeg it's probably sRGB or Adobe RGB. If it's raw, then it's in the colour space of the camera sensor (which is proprietary, and no use to anyone until it's been rendered by LR, ACR or whatever).
The editing program (LR or Photoshop) has a "working colour space". This is the working space the program does it's image manipulation in. For Photoshop you can choose, for LR it's always ProPhoto RGB (there's no choice). LR and Photoshop internally convert the image from the image's colour space to the working space for editing.
Then the monitor has a colour space. Assuming it's been calibrated and profiled (measured) by a hardware device (Spyder, Colormunki or whatever) then the monitor's colour space is described in the monitor profile.
Assuming the display profile is correctly set (in Windows control panel, color management) to the monitor's profile (which should be done automatically when you calibrate/profile your monitor) then both LR and Photoshop will automatically use the monitor profile when sending image data to the monitor. Both will automatically map (convert) the image from the working color space of the program to the colour space of the monitor. It just happens.
Provided:
The monitor is correctly calibrated and profiled (with a v2 profile if there's a choice, avoid v4 like the plague)
The default profile hasn't subsequently been altered in control panel
then LR will automatically colour manage correctly. There aren't any controls or options in LR to make it not colour manage correctly.
It's much easier to screw up on Photoshop as there are lots of settings you can get wrong in the "Color Settings" panel. So if there's a difference in colour between Lightroom and Photoshop it's virtually always a wrong setting in Photoshop, unless the monitor profile is incorrect.

Trying to configure Windows default Monitor RGB

Hi, I am trying to figure out the Windows color management interface to set up and confirm Monitor RGB.
Also how to set up and confirm that Windows is Defaulting to sRGB in untagged/unmanaged apps.
Thanks in advance for any help...
First DEVICES tab:
In this screen shot, I see Device is set to "Display: Generic PnP Monitor-ATI"
This doesn't look like a monitor profile (what is it)?
I see "Use my settings for this device" is checked
What behavior does that turn off/on?
In ICC Profiles, I see "Starbucks.icm (default)"
This looks like the Default monitor profile, but how/where was it selected?

Okay, I plugged my Vista hard drive into my Mac Pro and booted into Windows Vista and took a deeper look.
Control Panel> Color Management> Device tab:
"Display: Generic PnP Monitor - NVIDIA GeForce 7300 GT" appears to selecting the monitor attached to that card.
To see the actual monitor, go to Device Manager> Monitors (expand): right+click on Generic PnP Monitor> Properties> Details tab> click/expand Property drop menu and scroll to Hardware Ids ("Value" should list monitor). I am not sure what PnP means (plug & play?).
Checking "Use my settings for this device" probably lets me add and select profiles and behaviors to use with this monitor.
Unchecking "Use my settings for this device" probably tells Windows to make these decisions for me behind the mystery curtain (not desired if you like to know what's happening).
To select/change Windows Default Monitor RGB:
For example, if I wanted to switch my Monitor RGB to sRGB, I would click on "Add..." and choose the sRGB profile from the list of profiles installed on the system. Same routine if I had a custom monitor profile....
Once I have the desired monitor profile appearing in Devices> Name — to set it as my Monitor RGB — I would click on it to highlight it, then click on "Set as Default Profile" (and reboot for safe measure and to be sure the change sticks after rebooting).
+++++++
To confirm Windows Default Monitor RGB:
Go to Control Panel> Color Management> Device tab (and note profile "(default)".
This "(default)" designation probably identifies the current Windows default monitor profile, and it is probably where Photoshop picks up its Monitor RGB profile.
In other words, in the above example, Windows is using the "Starbucks.icm" custom monitor profile.
+++++++
To confirm Photoshop's Monitor RGB:
In Photoshop, go to Edit> Color Settings.
See Working Spaces> RGB and click to expand the drop menu.
Photoshop's Monitor RGB is the profile listed to the right of "Monitor RGB - (profile name)".
Note: Never set Working RGB to Monitor RGB (I am only pointing this out so you know where to confirm what profile Photoshop is using for Monitor RGB)...

No monitor profile available. Yellow tint after import

Hello. I have bough last week a new Toshiba notebook which has Windows 8.1 preinstalled on it.
I have noticed a problem that seems other came also on the same issue. When i watch images on a non profile managed software, the images look fine. Once i import them on Lightroom or Photoshop, the images get a yellow tint.
The problem and a possible solution is also described here: http://photography-on-the.net/forum/showthread.php?t=1164320 . This is setting the sRGB as a monitor profile. I know this is not a great solution, but surely better than what i see on my monitor. In any way, this unfortunately this did not work for me.
This is what i mean with the yellow tint (left Lightroom, right Irfan)
Today i tried following:
Step 1
The image is in RAW format. I import it in Lightroom and gets that yellow tint i described.
I export it with sRGB in jpg format. The jpg file has still that yellow tint. Please note here, that others that report similar problems, they mention that after the export they image looks again fine.
Step 2
I open the RAW image with Irfan (not color managed) and save it as jpg. The image is saved "correctly", as you see on the right side of the image above.
Step 3
I import the exported jpeg that was created with Irfan and import it to Lightroom.
The yellow Tint now does not appear on the imported JPEG.
One more tip i can give is: When i do a Soft proofing on Lightroom and choose sRGB i still see that yellow tint.
What exactly is happening ? I try to identify the problem. Why i see just raw images with this yellow tint, no matter the profile i set for my monitor and no matter the proofing options on lightroom.
I don't want to spend 100+ euro for a calibration device and not being able to use the profiles.
Any suggestions for further testing ?

First - Irfanview needs to be at least IV 4.35 and needs to have the LCMS.DLL plug-in installed as well as having the Color Management enabled so that you have some chance of your Photoshop and IrfanView versions of an image matching:
Alright we have the first conflict here.
I have the latest IrfanView version (4.37) , i saw that the Lcms.dll exists in the plugin list, and i have set the settings as suggested.
Furthermore at the moment i have sRGB as my default monitor profile. Still this is how i see things.
IrfanView and Photoshop have the same difference as before. Yes i have rerasted IrfanView on every change. I actually freshly installed also the latest irfanView version with its plugin.
Photoshop - Irfan Side by Side
Monitor Profile Settings 1
Monitor Profile Settings 2
IrfanView Settings
About this
As you can see the Adobe default processing with the Adobe Standard profile, at top left, is a little greenish. This is compared to the default camera processing as viewed in the camera-embedded preview jpg from the CR2 at the bottom right which a white frame around it.
When i open the raw image on LR, i have (from what i can see on my monitor) the same results as your Adobe default processing (Top left) . What confused me on your image above is bottom left image "Adobe processing - Camera standard". What is with Adobe processing meant here? The camera profile? If yes then how can we have Adobe camera profil but also camera standart ? If you mean the process LR provides, mine is set on 2012. But no adobe available for selection. I do not know if this is meant though.
Here is my comparison between Adobe Standart Profile and Camera Standard.
LR: Adobe Profile vs Canon Standart Profile
One more comparison is of the files you made available including the IranView jpg you supplied as compared to the Canon JPG preview that I extracted from the CR2 file:
What you can see is that the CR2 as viewed in LR and LR's exported JPG of that CR2 look about the same (top and bottom left), and the IrfanView and Canon-JPG versions of the CR2 look the same (top and bottom right). This is your IV version of the JPG, not something I made, but I expect IV has just extracted the camera-embedded fullsize preview JPG from the CR2 file just like I did using a different tool, so they look the same, but it is possible your IV is using a Canon-specific plug-in that uses the Canon-supplied SDK library DLLs that can also duplicate Canon processing. I only have the Formats.dll and the CRW.dll but not all the extra SDK DLLs so I expect my IV is only extracting the camera-embedded preview JPG.
Yes i can confirm that also on my environment. The exported CR2 from LR matches the exported JPG as also there is a match between IrfanView CR2 with the Camera standard profile export. Unfortunately i cannot confirm if IrfanView uses a sort of Canon-plugin to make the RAWS rendered automatically with the Canon standard profile.
And if you want your Adobe treatment of CR2 files to look much more similar to your camera's treatment, then use the Camera Standard profile in Lightroom and the PS ACR plug-in.
Question on this. Should i always put a Camera Standart profile on all my images after importing them on LR ?
Also please, let me know what you meant with Adobe Processing. I searched on the web with "Adobe Processing lightroom" , but i could not understand what is meant.
If using the Camera Standard profile doesn't make things look almost the same, then please post a side-by-side of LR's view of the CR2 and IrfanView's JPG extracted from the CR2--what you've linked to, just above.
Here is a comparison between an exported JPG from Lightrom with camera profile (Right) compared to an exported JPG with IrfanView from the RAW (left). As mentioned before the images look identical, with the one exported from LR with Camera profile being a bit more vibrant. But not much of a difference.
IrfanView vs Camera Profile export
So in the end it seems you see also that green-yellowish cast on the RAW image. From what i see on the screenshots you made.
The question now is why i do not see RAW the same as Adobe software ? Could i do this test with an other viewer?
To summerize from my side as well. A monitor calibration is surely good to do. On the other side the cast i see on the RAW in this case has not to do with the profile but rather with Adone profile and the way this image was captured.
PS. I must admit that is one of the best on line support i have ever seen. Thumbs up ssprengel !

Possible to bypass monitor profile when displaying image?

After importing a large photo library into Aperture I noticed that when viewing images, they would change color and in a little under a second the colors looked significantly less "colorful and rich" than before. Sounds "subjective" but it really is not. There is definitely a transformation going on and the colors consistently become duller on every image viewed. It is especially noticeable in a album of images taken in the fall using a circular polarizer where the colors looked really great to begin with and then extremely dull after the transformation. I deleted all of the preview images and set aperture to not regenerate them. Still, same issue occurred. The issue occurs with both RAW and jpg images.
In Canon Image Browser on the Mac colors look great. It's easy to do an A to B comparison of the same file and see that it looks better in every case.
But what I've discovered is that I can get the same "dulling" result to occur using Canon's Image Browser 6.x software just by setting one option.
There is an option checkbox in Preferences that is disabled by default to "Adjust Image Colors Using A Monitor Profile." Prior to setting that option, the colors looked great, just like they looked on the camera LCD, and they same as they look on my PC also using Canon Image Browser software and Irfan view. The rich colors seen when not using monitor profile also match what I see in Safari, Chrome, and Internet Explorer browsers.
In Canon Image Browser when I set the checkbox to "Adjust Image Colors Using A Monitor Profile" the colors become very muted. They look identical to what I see in Aperture. Also, I can get the same effect to occur on the PC version of Canon Image Browser. Microsoft's "Windows Photo Viewer" seems to be monitor profile aware as it shows the same dull colors. "Windows Photo Viewer" offers no option that I can find to improve the look of the color. Maybe this is what you want if you're trying to print your images and have them match exactly what is seen on screen.
I have found that with Photoshop CS5 I can export a jpg to tiff which strips out the color space information and then voila the image "pops" when I bring it into aperture and looks the way it does in Canon Image Browser without using monitor profile. In fact you can really then compare within Aperture how big the difference is between the two, and the only thing I did was resave the image to a new file format without doing anything else in photoshop. It's not feasible to resave evertthing as tiff though.
So my main question is, is there a way within Aperture to bypass the monitor profile so I can see the images with the same colors as they are rendered in the majority of the other tools I use.

I've done some additional testing on a jpeg image.
Test 1:
Canon Image Browser: "Preferences/Adjust Image Colors Using a Monitor Profile" is unhecked
Photoshop CS5: "View/Proof Setup" is set to "Monitor RGB"
Aperture: "Onscreen Proofing" enabled and set to "Generic RGB" Additionally I've tried every other color profile available
Result: The colors look identically rich on Photoshop and Canon Image Browser. Aperture is the only tool I can't get to align with the rich colors.
Test 2
Canon Image Browser: "Preferences/Adjust Image Colors Using a Monitor Profile" is checked. Restart the software to apply change.
Photoshop CS5: "View/Proof Setup" is set to "Internet standard sRGB"
Aperture: "Onscreen Proofing" enabled and set to "sRGB"
Result: The colors match on all 3 tools. The color are very noticeably less rich than in Test 1.
I went ahead and previewed the image in the browsers on the Mac. Chrome and Firefox showed the color the same as Photoshop and Canon Image Browser did in Test 1 which looks better in my opinion.
For Safari color looks the same as Test 2.
Also Apple Preview looks the same as Test 2 no matter which soft proofing setting is applied.
I believe Adobe and Canon have the correct behavior and show either richer or duller colors depending on which "proofing" mode they are in. Only aperture so far cannot be made to do the richer colors.

PSE7 Monitor Profile woes (Huey Pro)

So, I finally upgraded to PSE7 from PSE2 to addresses issues I was having with the Huey Pro from Pantone. Basically, if I calibrate the monitor, the colors look great everywhere (incl. other color managed programs) except in Photoshop - they look almost inverted (skin tones are bright magenta, etc). If I kill the Huey pro sw and revert to a previous monitor profile, all is well. If I turn off color management in PSE7, the screen looks fine, but I give up color management. I've tried disabling the startup programs, etc. to no avail. Obviously, upgrading didn't help, as I'm posting here.
I'm starting to think the monitor profile is being applied twice, but the color settings in PSE are so basic, it's really difficult to tell what it's doing.
I'm running out of ideas, and really like the print layouts that PSE offers, but need color management... anyone seen this? Ideas?
{Windows XP, NVidia 8800GT, Intel Quad Core}
Thanks for looking!

If there were a general problem between Huey's and PSE, I think we'd see more reports here or at Elements Village. So that suggests a problem with your particular configuration.
To see if it's specific to PSE independent of Huey's, try PSE with other display profiles. In the Color Control Panel applet, select sRGB IEC61966-2.1 as the default profile for your display. Do colors in PSE look reasonable? Does your display have a color profile supplied by its manufacturer? Many do -- look on its Web site. Does PSE produce reasonable color with that profile set as the default?
If it does, then that suggests that PSE's handling of display profiles works in general and that it's something specific to Huey's.
To see if it's specific to Huey's independent of PSE, you've already tried other color-managed programs. Note that Firefox 3 is color-managed only if you set some specific options -- by default, I don't believe it is. You could try downloading Microsoft's Windows Live Photo Gallery -- based on knowledge base articles, it seems that WLPG is pretty sensitive to non-standard color profiles. See if WLPG works with the Huey profile.

Monitor Profile incorrect on Dual Monitor Setup

Hello,
I've searched the forums and I can't find an answer to my problem. I've read about dual monitor setups in Windows and how to set the defaults and whatnot, but it doesn't seem to fix my problem.
I am running on an nVidia GeForce 8600M GT, Windows 7 x64, Photoshop CS4 x64. I calibrated my main display (Dell Vostro 1700) as well as the attached monitor (ASUS VK246H) using Datacolor Spyder3Elite. Both monitor profiles seem to load just fine. I've also went into Windows' color manager and set the system defaults for each monitor respectively. The problem I'm having is that if I were to load Photoshop on the 2nd monitor, Photoshop only uses the main display's color profile (Vostro 1700) and not the ASUS VK246H profile. What could be going wrong?
Just to clarify, what I mean by "loading PS on the 2nd monitor" is that when I execute Photoshop.exe, the splash screen and main window shows up on the 2nd monitor, not the main monitor (which is what I want).

function(){return A.apply(null,[this].concat($A(arguments)))}
Chris Cox wrote:
What if the image is in between two monitors?
The piece on each display is corrected for the display it is on.
Is it supposed to work that way? Because it doesn't. Not with Photoshop CS5 x64 at least.
As a test I intentionally misconfigured the profile for my Monitor #1 (left) so that it's REALLY OBVIOUS which profile is being used. When set this way, on Monitor #1 red colors will appear pale orange.
An open document, floating in a window:
If COMPLETELY displayed on Monitor #1, Photoshop will use the Monitor #1 profile.
If even 1 pixel of the edge of the image is moved onto Monitor #2, it will use the Monitor #2 profile on the entire image.
See for yourself:
-Noel

Windows, wide-gamut does Safari Convert to monitor profile?

Hi, I was looking for the Safari Windows forum, but this was the only one I could find.
Can someone with a Wide Gamut monitor (not set to its sRGB preset) using a calibrated custom monitor profile look at the sRGB rollovers here
gballard.net/photoshop/srgb_wide_gamut.html
And tell me if the Tagged image is a dead-on exact "match" to the Untagged rollover?
If the Tagged file looks normal or over-saturated like the Untagged image?
I am trying to determine if Safari for Windows Converts Tagged color to the monitor profile like Photoshop (or only to sRGB) and it should be most obvious on wide-gamut AdobeRGB type monitors.
I've pretty much concluded the Untagged color gets sent straight through to the monitor unchanged (so Untagged images should appear overly red on wide gamut panels).
Thanks...

Okay, I put my Windows Vista Business hard drive back in my Mac Pro and booted off it.
I installed Xrite iMatch 3.6.2 software, connected my eye-one display 2, profiled my monitor with a custom ICC profile, and rebooted.
Now I am seeing exactly the same Safari behavior I see on system 10.6 using this hardware (and my other Mac Pros running profiled 30" Apple displays) --- a slight shift in the untagged sRGB rollover.
The untagged sRGB rollover appears like Safari for Windows is defaulting untagged sRGB to my custom monitor profile now, the same as my OS-X machines, and as I expected it to work on the PC.
+++++
Previously, my Windows system was using whatever profile my NEC 2490WUXi setup by default --- I had a feeling setting a custom profile would provide a clue.
Seeing is believing...

Wide Gamut Monitors & 10.6 Default Monitor RGB

Hi, an Adobe employee just told me Snow Leopard 10.6x defaults untagged and unmanaged color, that SL "uses sRGB for untagged images/graphics, and converts to the profile for each display”.
I no longer have a WIDE GAMUT monitor to test myself.
Can a few people with wide gamut displays running 10.6x and Safari 5 please go to
www(dot).gballard.net/photoshop/srgbwidegamut.html
and roll over the tagged and untagged sRGB images at the top of the page.
And post back if they "match" to prove or disprove his statement?
(By his statement, the tagged and untagged rollovers should "match."
Also, if they shift, how does the untagged sRGB change in appearance?
Thanks (I am trying to get my page updated)...

That's expected, a wide gamut monitor will be a lot redder.
Yes. Just a lot more color range and gamut to view than a "standard" monitor.
Tagged) Photoshop/Safari is reading the embedded profile and CONVERTING to Monitor RGB.
Actually, that's what the OS or Photoshop always does. No matter what you're viewing in Photoshop, and no matter what the CMYK, RGB or grayscale working spaces are set at, the color you view is always your monitor profile, which is the last conversion done before displaying the image in Photoshop to the screen. Which is why I use my monitor profile as my working RGB space. I want my images to contain the color data of the device I'm viewing, not a canned space forced to fit. Here's what I mean. This image is Adobe RGB and my monitor profile overlaid. It's mostly a top down view. That was the best orientation I could turn the 3D map to for the example.
The ghosted map is the monitor space. As you can see, if I were to use Adobe RGB as my working space, I'd be losing all of the color I could be using that extends beyond Adobe RGB (reds through pinks, greens), since Adobe RGB would limit how far I could saturate those colors, as it has to stay within the limits of the profile. On the other side of the coin, the left side shows how much of Adobe RGB extends beyond my monitor space. The even brighter pinks through bright cyans across the top left.
But I don't care about that color. I already get all the saturation I can reasonably use for a photo. I mean, just how unnaturally bright do you want someone's lime green shirt to look? Using a color space your monitor can't display is also a very bad idea in my opinion. Say you're happy with the color you see on your current monitor. Then you get a new monitor at some point with an even wider color range. Suddenly, those bright pinks are way more saturated than you remember. What's wrong? Nothing. Your new monitor is just showing you values that were already in your Adobe RGB tagged image your previous monitor was incapable of displaying. I would much, much rather use my monitor profile for my RGB images. Then when I do move to any even wider range monitor, ColorSync/Photoshop will be able to properly map the color to fit the new monitor profile so the images look identical, or nearly so, as they did on the monitor I was using before.
In short, I consider canned profiles such as Adobe RGB, sRGB, ColorMatch RGB, etc. completely useless. None of them represent the device (monitor) in front of you. Only a properly created monitor profile is accurate to that device.
If the Adobe theory were true, you would NOT see a brighter, redder image on the rollover (they would "match").
Sorry, -g. By, So far, it sounds like his theory is true., I just meant that my tests were following his theory up to that point. After that though, it falls apart.
Can you tell me if Photoshop> Assign Profile (your custom EIZO monitor profile) displays like the Safari untagged rollover (especially level of saturated reds)?
Yes, but it looks that that to start with if I open the untagged image and tell PS to leave the color as is. So PS/ColorSync is already doing the only thing it can do with the color, mapping it to fit the monitor profile.

Monitor profile, i think i did it ok but not 100% sure

After reading several previous discussions and answers i'm still unsure if i do the things ok.
I have calibrated my monitor using a Spyder3 hardware device.
Doing so i think this profile is automatically used by my monitor (Eizo cg243w)
If i'm also correct i have to do NOTHING inside photoshop in order to see on screen the correct colours etc. OR do i have to set Colour settings to: Monitor colours? (Monitorkleur) with Ctrl+Shift+K, then first question like this:
And further more, i work with 2 screens; 1 calibrated (main screen for editting purposes) and 1 screen not calibrated (second screen) for skype, bridge, mail etc.
I suppose, since i open PS on the main calibrated screen, this is not a problem, but again, am i correct?
Thanks in advance

Adobe RGB (1998) is certainly a more appropriate working profille than your monitor profile. But assuming "Uit" means "Off", I'd say the Color Management Policies section may still need work.
No one but you can say whether they're the settings "you should use". We simply don't know your goals, how you want to work, what you want to do when there are mismatches, etc.
Bear in mind there are no "this is the one right way" settings. Every single one of them has a use and a reason for being presented to you.
Here's a snapshot of my particular color preferences. Since I publish a lot online and my inkjet printer prefers sRGB input, I have chosen sRGB IEC61966-2.1 as my default RGB working space. If you're printing more often to wide gamut printers then it may be more appropriate for your Photoshop to prefer to use the wider gamut Adobe RGB (1998) color space - or even others.
-Noel

Change default display profile (colors are horrible)

Hi there,
A few weeks ago I baught a 15" Macbook Pro, but then I noticed the colors were horrible. Way too much brown/gray. I'm not exaggerating. Compared to my normal monitor it look's awfull, and compared to other Macbooks too!
So I tried to make my own color profile, and it looks better. Still not as perfect as it should be... Maybe go back to the store?
Anyways, I want to override the default color profile with my profile, so the Login screen and other accounts have more realistisc colors. Couldn't find any simple way to do that.
Could anybody help me? I'm new to OSX.

Seb99 wrote:
compared to other Macbooks too!
Back to the store.

Can't see user id in Application server after enabling default user profile

Hi,
We have implemented SSO and during that implementation, we had to enable the default user profiles so that the request can move from the web server to the app server without authentication. So as a result of this, we are not able to see the user id for all the logged in users in application server. It shows as "Forgot Password" (which is the name of default profile) for all the connections. Is there anything we can do to see the logged in users user id instead of "Forgot Password"?

Hi Daniel!
I understand that the result you see in the Worklist monitor doesn't help.Did you try the recommendation in the FAQ.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mi/mobile application faq/mam client faq.faq#q-4
If it doesnot help, try the following
(1)In the SPRO under MAM Customizing settings, go in to
"Assign Orders and Stocks to a Technician" and then double click the "Assignment Profile(Assigned to your MAM User ID in User dependant data)" and change the Order Assignment & Notification Assignment to "User-->Employee Number", if it is assigned to a Work Center OR a Planner Group.You can reset this back to the original settings later if required.
(2)Replicate the MAM25_090 & MAM25_095 via transaction MEREP_EX_REPLIC in the middleware.
(3) Synchronize the data from your MI Client
(4) If no data exists Monitor your Worklist as you did earlier.
Let me know.
Thx
Gisk
Message was edited by: Gisk

Odd colorsync monitor profile issue

Hi all
I have my monitor calibrated and its profile is selected in two separate accounts on my Mac. When I start up the Mac and log in to either account on its own all is fine. However as soon as both accounts are logged in then the monitor profile defaults to the Generic RGB profile and if I go to the display preferences I am unable to change the profile, I just get beeps every time I click on any profile in the list. Also if I go into the Colorsync Utility my Display is no longer listed in the Device - Displays list to the left, it is in there after a restart.
This is getting very annoying because I do quite a lot of Photoshop work and need my Monitor to give me an accurate picture whether my Wife is logged in or not and preferably without having to restart every time!
If anyone can throw any advice my way I would be most grateful.
Cheers Derek.

That's the same link I posted above.
Stick DMProxy in every users login items and you won't have to bother going into Terminal every time you log in after your kids
The problem is that *Login items* are ran only when you initially log in. If you simply switch users and then go back to your own user (which is alreaady logged in) the Login items are not ran.
(I've just posted a question about this to check it out)

Monitor profile applied twice?

Hi guys,
the colors in Lightroom (and Photoshop Elements 7 Raw import window as well) look green and flat. I could fix this problem in the PSE7 editor window by switching off the monitor color profile. But I cannot find any similar handle in LR and PSE7 raw importer. So, it seems to me that the monitor profile is applied twice -- once from LR/PSE (which assumes no further color treatment, so does the correction itself), and second the graphics card (which expects uncalibrated color informations as input).
Switching off calibration does not help either.
System is
Vaio VGN-AW31ZJ/F (Laptop, Wide Gamut display)
Windows Vista Home Premium
Datacolor Spyder 3 Pro, SW Version 3.2.1
I'm desperated... I mean, this is not such an unusual combination...
Please advice.

So, last night I've lost my patience with Windoze... All thesepop-ups and advanced and advanced-advanced andadvanced-advanced-advanced options in sub and sub-sub and sub-sub-sub dialogue boxes drive me nuts.... So, I'm back tothe good-old brute force methods:
From the discussionabove it is clear that (a) all I need is the monitor profile and(b) that the problem is related to the system (and not specific to LRor PSE7). Thus I simply have deleted all icc/icm files in the profiles directory, except the one from Spyder -- and surprise, surprise, the colors seem to be correct now (if meanwhile my eyes have not adapted to the wrong colors.....) Will have to cross-check with a printout and perhaps a "calibrated" proof print, if I can find one... But a priori, the test image looks fine now and is consistent with other monitor profile aware viewers. The colors also seems to be consistent with what I get on the Linux side when monitor profile management is enabled (difficult to compare directly in dual boot mode...).
After deleting the "useless files", I still saw a very slight green tint in test image. Then I played a bit with the rendering options perceptive/saturation/relative/absolute in the Windows system settings -- before I could reboot the machine (to make sure that there are no left-over settings floating around), just in this moment SP2 arrived. Switching back to the default settings (perceptive for photos) after installation of SP2, I cannot see the green tint anymore.
There's still some other junk in the Windows profile directory (wscRGB.cdmp, Photo.gmmp, D65.camp,...)... Dunno which harm this does. At least, Bill didn't let me delete it by default... Has anyone any clue what those files are about...?
I also have tried out the v2 ICC profiles. Actually, I was working all the time with v2, which is the default setting in my version of Spyder 3 Pro. However I don't see any difference in the outcome. (Okay, I didn't look at the rendering of the shadows in LR yet.).
Regarding Firefox 3.5, I don't see any problem with color management a in firefox yet. Just want to mention that you can change firefox's color management behavior by typing "about:config" in the URL and then scroll down to gfx.color_management. Here you can type in the name of the monitor profile (display_profile) as well as the "mode": mode is set to 2 by default, but folks report to get better (correct) results when setting mode to 1. Me, myself I haven't seen any difference here (yet). Actually, Jeffrey Friedl has very nice test pictures on pages 1 and 2 of this above mentioned Blog page where you don't need to guess whether CM works at all or whether it's right or wrong. For me, everything comes out correct.
PS: Graphics card is according to the spec sheet an "NVIDIA® GeForce® 9600M GT GPU".

Fully Color Managed Application (using calibrated monitor profiles)

Hi,
I'm new to JAVA 2D so I may be missing something obvious - apologies if I am, but I've been trawling the API and web to try and solve this for many hours - so any help would be much appreciated!
I'm trying to write an application to open a JPEG with an embedded colour profile (in this case AdobeRGB) and display it with correct colour on my monitor, for which I have an accurate custom hardware calibrated profile. In my efforts to do this several problems / queries have arisen.
So, JAVA aside, the concept is simple:
a) Open the image
b) Transform the pixels from AdobeRGB->Monitor Profile (via a PCS such as CIEXYZ).
c) Blit it out to the window.
(a) is fine. I've used the following code snip, and can query the resulting BufferedImage and see it has correctly extracted the AdobeRGB profile. I can even display it (non-color corrected) using the Graphics2D.drawImage() function in my components paint() method.
BufferedImage img = ImageIO.read(new File("my-adobe-rgb.jpg"));(b) Also seems OK (well at least no exceptions)...
ICC_Profile monitorProfile = ICC_Profile.getInstance("Monitor_Calibrated.icm");
    ColorConvertOp convert = new ColorConvertOp(new ICC_ColorSpace(monitorProfile ),null);
    BufferedImage imgColorAdjusted = convert.filter(img,null);[I was feeling hopeful at this point!]
QUESTION 1: Does this conversion go through the CIEXYZ (I hope) rather than sRGB, there seems to be no way to specify and the docs are not clear on this?
(c) Here is the major problem...
When I pass imgColorAdjusted to the Graphic2D.drawImage() in my components paint() method the JVM just hangs and consumes 100% CPU.
QUESTION 2: Any ideas why it hangs?
Pausing in the debugger I found the API was busy transforming by image to sRGB this leads to my third question...
QUESTION 3: If I pass an image with a color model to drawImage() does drawImage do any color conversion, e.g will it transform my adobe image to sRGB (not what I want in this case!)?
And if answer to Q3 is yes, which I suspect it is, then the next question is how to make the J2D understand that I have a calibrated monitor, and to tell it the profile, so that the Graphics2D it provides in paint() has the correct color model. Looking in the API I thought this was provided to J2D through the GraphicsEnviroment->GraphicsDevice->GraphicsConfiguration.getColorModel(). I tried looking at what these configurations were (code below). Result - 10 configurations, all with the JAVA 2D sRGB default, despite my monitor colour management (through the windows display properties dialog) being set to the calibrated profile.
QUESTION 4: Am I just off track here - does Java 2D support monitor profiles other than sRGB? Is what I am trying possible?
GraphicsConfiguration[] cfg = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getConfigurations();
    System.out.println(cfg.length);
    byte[] d;
    for (int j=0; j<cfg.length; j++) {
      System.out.println("CFG:"+j+cfg[j]);
      d = ((ICC_ColorSpace)cfg[j].getColorModel().getColorSpace()).getProfile().getData();
      for (int i=0; i<d.length && i<256; i++){
        if (d[i] != 10 && d[i] != 13){
          System.out.print((char)d);
System.out.println();
Any help much appreciated.
Thanks.

I have had some sucess with this, but it wasn't easy or obvious. The trick is converting the color to the monitor profile and then changing the color model to be sRGB without changing the pixel data. JAI's Format operation does this easily although I'm sure there are other ways to do it. The RGB data is then displayed without being converted to sRGB so that the monitor calibration is maintained. I will answer your questions since I had similar ones.
Q1. Yes the conversion is done using XYZ as it should be.
Q2. I believe paint is just very slow, not hanging. Any color model other than XYZ or sRGB requires conversion before it can be displayed (as sRGB). This is both slow and incorrect for a calibrated monitor.
Q3. Yes that is what I have found, a conversion to sRGB will always happen, unless it appears to be already done as when the color model is sRGB (even though the pixel data is not!).
Q4. It is possible but apparently only with this somewhat strange work around. If there is a way to change the Java display profile to be other than sRGB, I could not find it either. However, calibrated RGB display can be achieved.
Since I have seen many other posts asking for an example of color management, here is some code. This JAI conversion works for many pairs of source and destination profiles including CMYK to RGB. It does require using ICC profiles in external files rather than embedded in the image.
package calibratedrgb;
import com.sun.media.jai.widget.DisplayJAI;
import java.awt.*;
import java.awt.color.*;
import java.awt.image.*;
import java.io.IOException;
import javax.media.jai.*;
import javax.swing.*;
* @author keitht
public class Main {
    public static void main(String[] args) throws IOException {
        String filename = args[0];
        PlanarImage pi = JAI.create("fileload", filename);
        // create a source color model from the image ICC profile
        ICC_Profile sourceProfile = ICC_Profile.getInstance("AdobeRGB1998.icc");
        ICC_ColorSpace sourceCS = new ICC_ColorSpace(sourceProfile);
        ColorModel sourceCM = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), sourceCS, false, false,Transparency.OPAQUE);
        ImageLayout sourceIL = new ImageLayout();
        sourceIL.setColorModel(sourceCM);
        // tag the image with the source profile using format
        RenderingHints sourceHints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, sourceIL);
        ParameterBlockJAI ipb = new ParameterBlockJAI("format");
        ipb.addSource(pi);
        ipb.setParameter("datatype", pi.getSampleModel().getDataType());
        pi = JAI.create("format", ipb, sourceHints);
        // create a destination color model from the monitor ICC profile
        ICC_Profile destinationProfile = ICC_Profile.getInstance("Monitor Profile.icm");
        ICC_ColorSpace destinationCS = new ICC_ColorSpace(destinationProfile);
        ColorModel destinationCM = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), destinationCS, false, false, Transparency.OPAQUE);
        ImageLayout destinationIL = new ImageLayout();
        destinationIL.setColorModel(destinationCM);
        // convert from source to destination profile
        RenderingHints destinationHints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, destinationIL);
        ParameterBlockJAI cpb = new ParameterBlockJAI("colorconvert");
        cpb.addSource(pi);
        cpb.setParameter("colormodel", destinationCM);
        pi = JAI.create("colorconvert", cpb, destinationHints);
        // image is now the calibrated monitor RGB data ready to display, but
        // an unwanted conversion to sRGB will occur without the following...
        // first, create an sRGB color model
        ColorSpace sRGB = ColorSpace.getInstance(ColorSpace.CS_sRGB);
        ColorModel sRGBcm = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), sRGB, false, false, Transparency.OPAQUE);
        ImageLayout sRGBil = new ImageLayout();
        sRGBil.setColorModel(sRGBcm);
        // then avoid the incorrect conversion to sRGB on the way to the display
        // by using format to tag the image as sRGB without changing the data
        RenderingHints sRGBhints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, sRGBil);
        ParameterBlockJAI sRGBpb = new ParameterBlockJAI("format");
        sRGBpb.addSource(pi);
        sRGBpb.setParameter("datatype", pi.getSampleModel().getDataType());
        pi = JAI.create("format", sRGBpb, sRGBhints); // replace color model with sRGB
        // RGB numbers are unaffected and can now be sent without conversion to the display
        // disguised as sRGB data. The platform monitor calibration profile is bypassed
        // by the JRE because sRGB is the default graphics configuration color model profile
        JFrame frame = new JFrame();
        Container contentPane = frame.getContentPane();
        contentPane.setLayout(new BorderLayout());
        DisplayJAI d = new DisplayJAI(pi); // Graphics2D could be used here
        contentPane.add(new JScrollPane(d),BorderLayout.CENTER);
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setSize(600,600);
        frame.setVisible(true);
}

Disable or modify default monitoring profiles

Similar Messages

Maybe you are looking for