AdobeRGB values too red! Prophoto correct??? With calibrated monitor

This is very very frustrating. I calibrated my monitor 2 times in a row because i didnt know what was going on. I downloaded a color chart with the correct RGB values and when opening with a Prophoto profile during Camera RAW all the values are correct. When i switch to AdobeRGB 1998 during RAW the reds are all too high. Same when just opening a JPG (using CS4). When using the Prophoto profile all colors are correct, and when assigning or using the AdobeRGB profile all the reds are way too high. What the heck is the problem here? I cant find an answer anywhere! Please help as i have to adjust the red saturations in every single photo and its driving me crazy. Thank you so much!!!

Don't assign convert.
you only assign when you are trying to find the correct profile when none is embedded.

Similar Messages

Color management problem with calibrated monitor

I'm using a Samsung Syncmaster T220 LCD profiled and calibrated with a Spyder2Express. PC runs Vista 32 SP2, Photoshop CS4. Using Adobe RGB for workspace profile. System profile is set to the Spyder2Express profile.
Open up photo in Photoshop. Colors fine.
Resize for web, convert to sRGB, then check preview in "Save for web..."
Under preview, I preview the following:
-Monitor Color
-Windows (no color management)
-Macintosh (no color management)
-Document Profile
The Preview of Windows, Document Profile settings look exactly right, whereas the Monitor Color setting looks badly darkened. I preview with Firefox, save and view image using IrfanView and Firefox. It's badly darkened. I'm stumped. I don't know what I'm doing wrong. This is similar to another recent posting here, except that I am using a calibrated display with profile.
Anyone know what I'm missing?
Thanks, Luke

I'm a little confused. Previewing through "Monitor Color" and "Windows (no color management)" are both technically not color managed. Perhaps we should distinguish further between "colorspace aware" and "device profile aware". So I can understand when you say that Irfanview will do some color management, but does not use the monitor device profile. But I would have thought that Firefox in non managed-color config would still use the monitor device profile.
I would have thought (and I might turn out to be wrong) that previewing using "Windows (not color managed)" would be the standard for previewing images for stock browser configurations. What photoshop shows me is correct rendering of the image based on what I edited in this mode. But the browser shows me a version that looks like it is not device aware, counter to photoshop's prediction. What is going wrong here? Do none of these major window apps use device profiles? Why does photoshop think that they will?
Another thing that has been suggested is that my monitor is calibrated so far from the stock configuration that sRGB photos displayed on it without the benefit of device profiling will come out far off the mark. But I profiled the monitor in stock hardware configuration and made no adjustments, and don't think that the hardware config of the monitor has changed.
If this turns out to be just a practical issue, then it leaves a major question. What did I accomplish by calibration if my calibration doesn't look like anything I actually display with? I can guess that prepress work will be more accurate in most respects, or I hope so anyway. But how should I manage workflow for developing images for web content if I am unable to match up what I'm editing with what the end user will see?
Or maybe I'm just doing something wrong...or maybe photoshop is...or I don't know what. Where do I go from here? Is WCS implicated in this somewhere?
Luke

Red eye correction creates a black eye

I am using iPhoto 6.0.6 (322) and when I use red eye reduction the command creates a blue-black blob of color that not only covers the red eye, it covers the eye socket and then some. I have used red eye reduction hundreds of times and this is something new. Any ideas out there?
Thanks
Ken

Ken,
There is a hidden feature to control the red-eye and retouch tools:
Type Caps lockControl9
Undo caps lock
Click on Retouch or the Red-Eye Removal tool.
The tab key will toggle between cursor types: a cross or a circle for Red-Eye removal tool, and between darken and lighten in the Retouch tool.
The \[ and \] keys decrease or increase the size accordingly.
NOTE: Using the { and } keys will will change the value next to the circle and that represents the degree of change or intensity that the Retouch tool imparts on each pass. To get a lighter pupil with the red-eye tool, Shift-Click inside the circular cursor.
The keystrokes are awkward at first, but I've found that with this method I get better red-eye correction with iPhoto than I do with Photoshop Elements 4.
Regards.

Large XML Publisher reports fail with client-error-request-value-too-long

We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2 (ATG.H RUP 5), and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
The exact error message is as follows:
lp: unable to print file: client-error-request-value-too-long
Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
Pasta: Error: Preprocess or Print command failed!!!
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
Action: Review your concurrent request log file for more detailed information.
I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
Has anyone had this issue with BI Publisher on Linux?

Thanks for the link. It looks like the sysadmins have throttled cups to low to allow large bitmapped print jobs:
grep MaxRequestSize cupsd.conf
# MaxRequestSize: controls the maximum size of HTTP requests and print files.
MaxRequestSize 10M
I am trying to get a more reasonable size limit.

Large BI Publisher reports fail with client-error-request-value-too-long

We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2, and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
The exact error message is as follows:
lp: unable to print file: client-error-request-value-too-long
Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
Pasta: Error: Preprocess or Print command failed!!!
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
Action: Review your concurrent request log file for more detailed information.
I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
Has anyone had this issue with BI Publisher on Linux?

The linux sysadmins set the cups max_request_size at 10 MB, which was causing this error. Once the restriction was lifted, the reports ran without error.

After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message: "DAVE Networking Dave kernel extensions could not be loaded! Error 71 - Too many levels of remote in path."

After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message:
"DAVE Networking
Dave kernel extensions could not be loaded! Error
71 - Too many levels of remote in path."
I have uninstalled DAVE and used Clean App to remove trace elements of program, however I still get the message and am unable to eliminate the error messages. When I click OK the message goes away briefly and then comes back up.
Any solutions would be great.

Dave,
Thanks....What I did was load the free eval version of Dave 9.0 and then used the uninstaller which must have deleted the kernel giving me the problem.
Thanks for the response.
Razor

RED Raw color correction with "curves"

Hi there,
i was wondering, if, when i am color correcting RED Raw files with the effect "curves" (for example) am I working with the full dynamic range of the RAW footage?
Is the range different, if I work in the RAW-Ediotr that i reach through the "interpret footage" dialogue box?
We are trying optimize the workflow for a certain project and would rather use effects on the footage layers, rather than interpret them (yeah, we´re really lazy).
Thanks a mill,
Björn

Yes, you are working with the full range from the .r3d files when applying effects in After Effects. In fact, you have more problems with colors clipping if you manipulate things like exposure in the RED settings than if you manipulate them in After Effects with effects (though that is better now than it used to be).
You should work with your project in 32-bpc color to make sure that you're preserving color information all the way through the pipeline.

Update trigger fails with value too large for column error on timestamp

Hello there,
I've got a problem with several update triggers. I've several triggers monitoring a set of tables.
Upon each update the updated data is compared with the current values in the table columns.
If different values are detected the update timestamp is set with the current_timestamp. That
way we have a timestamp that reflects real changes in relevant data. I attached an example for
that kind of trigger below. The triggers on each monitored table only differ in the columns that
are compared.
CREATE OR REPLACE TRIGGER T_ava01_obj_cont
BEFORE UPDATE on ava01_obj_cont
FOR EACH ROW
DECLARE
v_changed boolean := false;
BEGIN
IF NOT v_changed THEN
    v_changed := (:old.cr_adv_id IS NULL AND :new.cr_adv_id IS NOT NULL) OR
                 (:old.cr_adv_id IS NOT NULL AND :new.cr_adv_id IS NULL)OR
                 (:old.cr_adv_id IS NOT NULL AND :new.cr_adv_id IS NOT NULL AND :old.cr_adv_id != :new.cr_adv_id);
END IF;
IF NOT v_changed THEN
    v_changed := (:old.is_euzins_relevant IS NULL AND :new.is_euzins_relevant IS NOT NULL) OR
                 (:old.is_euzins_relevant IS NOT NULL AND :new.is_euzins_relevant IS NULL)OR
                 (:old.is_euzins_relevant IS NOT NULL AND :new.is_euzins_relevant IS NOT NULL AND :old.is_euzins_relevant != :new.is_euzins_relevant);
END IF;
[.. more values being compared ..]
    IF v_changed THEN
    :new.update_ts := current_timestamp;
END IF;
END T_ava01_obj_cont;Really relevant is the statement
:new.update_ts := current_timestamp;So far so good. The problem is, it works the most of time. Only sometimes it fails with the following error:
SQL state [72000]; error code [12899]; ORA-12899: value too large for column "LGT_CLASS_AVALOQ"."AVA01_OBJ_CONT"."UPDATE_TS"
(actual: 28, maximum: 11)
I can't see how the value systimestamp or current_timestamp (I tried both) should be too large for
a column defined as TIMESTAMP(6). We've got tables where more updates occur then elsewhere.
Thats where the most of the errors pop up. Other tables with fewer updates show errors only
sporadicly or even never. I can't see a kind of error pattern. It's like that every 10.000th update
or less failes.
I was desperate enough to try some language dependend transformation like
IF v_changed THEN
    l_update_date := systimestamp || '';
    select value into l_timestamp_format from nls_database_parameters where parameter = 'NLS_TIMESTAMP_TZ_FORMAT';
    :new.update_ts := to_timestamp_tz(l_update_date, l_timestamp_format);
END IF;to be sure the format is right. It didn't change a thing.
We are using Oracle Version 10.2.0.4.0 Production.
Did anyone encounter that kind of behaviour and solve it? I'm now pretty certain that it has to
be an oracle bug. What is the forum's opinion on that? Would you suggest to file a bug report?
Thanks in advance for your help.
Kind regards
Jan

Could you please edit your post and use formatting and tags. This is pretty much unreadable and the forum boogered up some of your code.
Instructions are here: http://forums.oracle.com/forums/help.jspa

Methodology that confim the consumption Value is correct with our Actual Su

hI,
What is the methodology that confim the consumption Value is correct with our Actual Supply.

I've only seen this once before in a ConfigMgr 2012 RTM environment and after fighting it for a few days I ended up simply recreating the driver packages.
-Nick O.

ODI Datastore Length differs with the DB length -IKM throws value too large

ODI datastore when reverse engineered shows different length to that of the datalength in the actual db.
ODI Datastore column details: char(44)
Target db column : varchar2(11 char)
The I$ table inserts char44 into varchar2(11char) in the target. As the source column value is empty ODI throws
"ORA-12899: value too large for column (actual: 44, maximum: 11).

Yes. I have reverse engineered the target also.
source datatype varchar2(11 char)
After Reverse Engineering
odi datstore datatype-Source : char(44)
target datatype: varchar2(11 char)
after Reverse Engineering
odi datstore datatype-Target : char(44)
Since the target datastore is char(44) in ODI Datastore and the values in the source column are null/spaces, the IKM inserts them into the target Column which is of 11 Char and the above mentioned value too large error occurs.
There are no junk values seen on the column and I tried with substr(column,1,7) and
Trim functions too and it does not help.

Problems with previously applied red eye corrections

I imported my Aperture 2 library and see that some images that had red eye correction before aren't corrected in AP3. It isn't universal and sometimes one person's eye would be corrected while the other would be red, even though the adjustments indicated both had been corrected.
Anyone else see this?

Me, too. I tried reapplying the red eye on a couple of pictures. After I clicked on the red eye tool, my previous red eye corrections appeared as the target icons on the pictures, but the red eyes didn't get corrected. There doesn't seem to be any way I can correct them, now.

Has anyone experience a bug with red eye correction in LR 5?

No matter what I do, anytime I try to use the red-eye correction tool, I get the message "Unable to find red eye". Even in pictures where the red eye is huge and clearly visible. Has anything changed in LR 5 that would cause this? I have Red Eye Correction enabled. Anyone else experiencing this?
I'm a rather new LR user, so I'd be grateful for someone pointing me in the right direction before I file a bug report.
Thanks!

runningkatze wrote:
Thanks Rob...
You bet .
runningkatze wrote:
In LR 4, the tools seemed so much more forgiving. In LR 5, it is incredible sensitive.
I don't think there have been any algorithmic changes in red-eye, Lr5 vs. Lr4 (certainly none mentioned by Adobe, nor in Victoria Bampton's very thorough list of changes in Lr5, nor that I've noticed in the forums...), so if it is behaving differently (you sure it's not you? ), then it sounds like something is a-wonk now in your Lr5 (or was a-wonk before in your Lr4 ).
~R.

Exporting Page fails with ORA-1401 inserted value too large for column

Hi Everyone,
I have a client what is getting the following error when
attempting to export a page using pageexp.cmd. A simple page
works for them but there main page does not. Here is the error:
Extracting Portal Page Data for Export...
begin
ERROR at line 1:
ORA-01401: inserted value too large for column
ORA-06512: at "PORTAL30.WWUTL_POB_EXPORT", line 660
ORA-06512: at "PORTAL30.WWUTL_POB_EXPORT", line 889
ORA-06512: at line 5
Has anyone seen this before?
Is there any way we can narrow down why this occurs?
There is no logging on this export option and the stored
procedures used are wrapped.
Any ideas?
Thanks
Oracle Portal Version: 3.0.9.8.0

we had this problem.
We talked to some oracle person who said some portlets on a page had trouble exporting.
Sure enough after we deleted all the portlets (one at a time to determine which one was giving us the problem. Turned out none of ours worked) the page exported and imported just fine.
Hopefully this is being worked on...

Professional Calibration for the Powerbook Pro with LED Monitor

This is what I have discovered: The new LED monitor/screen is a better technology for graphics pros because it's brighter, doesn't need to warm up like CRT and LCD, and it's more efficient. I have also discovered that the current Powerbook Pro with LED is not possible to calibrate with a spyder-type device because the computer itself doesn't allow the user to control overall R G and B levels at all...so as to achieve a prcise initial white point setup. Once RGB levels are balanced, only then can a spyder with it's assoc software continue it's recordings with precision. Other problems exist: Apparently the graphics cards in the Powerbook Pro (I have the newest machine, bought Nov 2008, with LED screen) are not able to permit any software (like Monaco Optix) from adjusting the brightness or color levels. As well, to my knowledge, there are not currently any spyders with software which offers LED as an option initially. I tried setting it to LED and LCD with my LED monitor, just to see the difference....and there was a huge one...so it's futile even to use the spyder if the software hasn't been developed with the LED screens in mind.
*What I did was this: I calibrated my LaCie electronBlueIV 22" professional monitor with the sypder...using Monaco Optix and it's XR spyder. Once that was established, I opened a photoshop sample image which has a blue sky, green pine trees, green/yellow grass, a red boat and some white snowcapped peaks. Made a duplicate of it....and placed one copy on the LaCie and the other on my powerbook's monitor just below (I'm running 2 monitors at the same time). Then I went through the "professional" mode of Apple's calibrator. Unfortunately it's not an exact science as one might think. No, you can't work it back and forth until the colors match because of certain ways in which Apple has made their calibrator function. For example, you only set the degrees kelvin at the end...which totally changes all the color levels you have done up until that point....it's complicated to explain, but if you go through it once, you will understand what I'm talking about. Anyhow, so what I did was go through it all the way.....then right before saving the profile....I would go back again (you can go backwards and forwards and it keeps the adjustments you've made already...luckily) and tweak these various adjustments...all the while...*keeping an eye on my 2 images...trying to nudge my powerbook colors/brightness/contrast as close as possible to my calibrated LaCie. Finally, I used the final adjustment (D50/5500/D65 etc....) to put some more warmth into the powerbook's monitor which seems to be much too cold if you only use the calibrator and have no other monitor for reference. I set mine around 5,200......when normally I would be at 5,500 with any other monitor.
It seems I did get my LED monitor pretty close to the values of my calibrated LaCie....as close as I could visually...considering, to my knowledge, there is no current device/software that will calibrate this LED monitor. We're waiting!!
*Just a friendly note to Apple*
Dear Apple,
For years you are aware that it is the creative professionals (photographers, graphic designers, visual artists, printers, architects, etc...) who have been the loyal backbone of your small market share. We have been the ones investing and reinvesting in Apple computers and peripherals since the beginning...before the ipod and the iphone when all of the other yahoos jumped onboard. Also please understand...we love the new generation of powerbooks but we're tired of having to drag around an extra monitor to insure correct colors for printing/color-matching. I'm a professional photographer who is always traveling internationally...and away from my calibrated monitor in my office. Yet, many times I have to retouch on the go and get the images to my clients..and it's just not possible to work on a calibrated monitor at these moments. Yet my work is precise work and the color values are critical to my clients in the world of fashion and beauty.
Realizing this point.....knowing your core clients are concerned with critical color values....why is it that you continue to create portables with absolutely no precise color controls?!!!!!!!! Would it be so difficult to add a utility which allows the user to digitally control RGB levels, contrast, and brightness (withe their associated numeric levels, (for example: brightness=78.3%.) As well, your own calibration assistant..."professional" mode??? HARDLY. Why not build onto this model with another mode...let's call it "super professional" mode (lol) which allows us to access overall RG&B....as well as brightness and even contrast???
That's what I know at this stage. If anyone has any advice which adds to what I have said, or maybe someone can educate me with a more accurate way to calibrate my monitor....I'm all ears...and I'm sure I'm not alone in this quagmire.
S,
Lawrence

I've had the same concerns about the lack of any monitor controls (unless there's something I'm missing), but afraid I don't have any answers myself yet. Just wanted to ask do you mean "Powerbook Pro" or are you talking about a MacbookPro?

Colours do not Print correctly with Photoshop CS4

I am using the Adobe Master Collection CS4, and use an Epson RX650 printer, but for the life of me I cannot get Photoshop to print what is on the screen.
The prints are dark, and no where near the ones on the screen.
I am using genuine Epson Ink, and Premium glossy paper, so as to remove this issue, is this a case of my screen needing to be calibrated?
I have considered buying the Spyde Studio calibrator to ensure that this is correct, (do I need to?) and I have read as much as I can about setting up Adobe to manage the print settings and colours, but still no luck.
My current settings are as follows
In Adobe Bridge, my creative suit color settings are set to Europe General Purpose 2
The in Adobe Photoshop (version 11.0.1) I am selecting under colour management, Document Adoby RGB (1998), Photoshop handles colours, Printer profile is Epson sRGB Colour Space, Rendering intent is Relative Colourimetric, and I have ticked the following boxs, Blackpoint compensation, Match print colours, Gamut warning and Show paper white.
Can some one please advise me?

I too have had problems with prints being much darker than what I see on screen.
Below is my solution which works fairly well for color prints--not as well for grayscale.
I used the huey Pro monitor calibrator purchased only a couple of months back to make my prints look right and be consistent.
1.       Use the huey to calibrate the monitor
2.       From Photoshop (CS4), I select the ICC profile for my Epson 2200 printer and the paper being used. I then set up soft proofing in Photoshop (in the View menu) which allows me to see on screen how the image will be printed. Usually it is a bit darker than I like.
3.       so I adjust the brightness such that in the soft proof view, the image appears as I wish.
4.       There is more yet to do in that you have to set various settings for the print process like letting Photoshop manage colors, setting no color adjustment for the printer. And a few more minor settings regarding the printer
By the way, there is something wrong with the print driver for the 2200 in XP so that when you come to the last screen before printing, the print preview has a very red tint. You simply ignore that since the print has none of that. This is in XP. Possibly Windows Vista has a driver that doesn’t do that.
This has given me good quality consistent prints the first time they are printed—at least on the few I have done since getting the huey

AdobeRGB values too red! Prophoto correct??? With calibrated monitor

Similar Messages

Maybe you are looking for