1.4.1 corrupting the color space
I submit images to Alamy, Photoshelter and others. As of last night I converted an image via LR as a b&w and exported it as a jpeg to my Photoshelter folder. Trying to upload it the Photoshelter system informed me that the jpeg had an unknown ICC space and the upload ground to a halt.
Opened Photoshop and tried to open the same file and sure enough the ICC warning message appears. So, tried the same process with a colour image and it worked as usual - no problems.
Anyone have any idea what's going on here?
Thanks in advance.
Paul
That is really weird! This is not an RGB image, I get the same invalid message in Photoshop, but preview.app opens if normally and says it is in the Gray (instead of RGB) color space and has an adobeRGB profile (which is inconsistent indeed). Whenever I export a greyscale converted image (converted to greyscale in LR) it does the correct RGB color model with sRGB profile (or whatever I select) Definitely something is wrong here. It should not do this. Nothing else touched this file but Lightroom (so no plugins like LR/mogrify)? You exported as a jpeg, not "original"? No Photoshop droplet?
Similar Messages
-
The Organizer does not support the color space in the file
I just purchased and installed PSE 8 as an upgrade to PSE 6. My catalog correctly shows all of my existing images. However, when I try to import photos into the Organizer, I get a message that nothing was imported. The reason given is that "The Organizer does not support the color space in the file." This happens with photos taken on my iPhone as well as those from my Canon PowerShot A1100 IS. Any suggestions?
Here is my system information:
Elements Organizer 8.0.0.0
Core Version: 8.0 (20090905.r.605812)
Language Version: 8.0 (20090905.r.605812)
Current Catalog:
Catalog Name: My Catalog
Catalog Location: C:/Documents and Settings/All Users/Application Data/Adobe/Elements Organizer/Catalogs/My Catalog
Catalog Size: 83.9MB
Catalog Cache Size: 459.8MB
System:
Operating System Name: XP
Operating System Version: 5.1 Service Pack 3
System Architecture: AMD CPU Family:15 Model:11 Stepping:1 with MMX, SSE Integer, SSE FP
Built-in Memory: 2GB
Free Memory: 829MB
Important Drivers / Plug-ins / Libraries:
Microsoft DirectX Version: 9.0
Apple QuickTime Version: 7.65
Adobe Reader Version: 9.2
Adobe Acrobat Version: Not installed
CD and DVD drives:
J: (SONY DVD BUS: 3 ID: 3 Firmware: RW)It turns out that this problem went away after the program crashed. Everything seems to be working well now.
-
Hi
I have a problem with color prints from photoshop elements 12. The pictures are too light and with strange colors. I have a Canon pixma mg615I0 printer and use mac os X yosemite. The pictures are taken with a coanon eos 550d in the color space sRGB. I have followed adobes recommendations and have tried both letting the printer respektive photoshop manage the colors. But nothing works. I see that there are different opinions about which is best to do so I tried both. I have the latest printer driver installed. Can anyone help me with this?Do the following:
Print a test page from the printer. Perhaps the print head needs cleaning via its maintenance facility.
Let the printer manage colors, not PSE
Calibrate the monitor -
How to find the Color Space name for a PDEElement
Hi
I am trying to find out the color space for each PDEElement in my PDF file. While doing this,
I put some debug statements ( cout stmts ) that print the color_space as integer values. I gave this list
after the code. I belive the color spaces should be something like CMYK, DeviceRGB,DeviceGray..etc.
How can I know the actual color space name coresponding to these numbers printed in Debug statements.
Kindly please help me..
void ProcessElementDetails(PDEElement element)
PDEGraphicState gfx_state;
ASInt32 pdeType = PDEObjectGetType(reinterpret_cast<PDEObject>(element));
ofstream outfile("E:\\temp\\test.txt",ios::app);
outfile<<"ProcessElementDetails\n";
if ( pdeType == kPDEText )
outfile<<"PDE Text type\n";
PDEText pde_text = (PDEText) element;
ASInt32 num_run,i;
num_run = PDETextGetNumRuns(pde_text);
outfile<<"Number of Runs for PDEText :"<<num_run<<"\n";
for (i = 0; i < num_run; i++)
PDETextGetGState(pde_text,kPDETextRun,i,&gfx_state, sizeof (PDEGraphicState));
ASAtom color_space = PDEColorSpaceGetName(gfx_state.fillColorSpec.space);
outfile<<"Color Space :"<<color_space<<"\n";
if (pdeType == kPDEImage )
outfile<<"PDE Image type\n";
PDEElementGetGState(element,&gfx_state,sizeof (PDEGraphicState));
ASAtom color_space = PDEColorSpaceGetName(gfx_state.fillColorSpec.space);
outfile<<"Color Space :"<<color_space<<"\n";
if (pdeType == kPDEContainer)
outfile<<"PDE Container type\n";
PDEContent content = PDEContainerGetContent(reinterpret_cast<PDEContainer>(element));
ASInt32 numElem = PDEContentGetNumElems(content);
for (ASInt32 i = 0; i < numElem; i++)
element = PDEContentGetElem(content, i);
ProcessElementDetails(element);
Debug statements with color numbers:
====================================
ProcessElementDetails
PDE Image type
Color Space :700
ProcessElementDetails
PDE Text type
Number of Runs for PDEText :63
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
ProcessElementDetails
ProcessElementDetails
PDE Text type
Number of Runs for PDEText :38
Color Space :389
Color Space :700
Color Space :390
Color Space :388
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :389
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
SeparateColorPlates
PDF file exists
Number of Pages:1
Number of Elements:5As you may have noticed, the "numbers" you see are actually of type ASAtom -
which is a type declared in the SDK to represent reused strings. You have to
read the relevant documentation to learn how to use the SDK - there is no
way around it. The Acrobat SDK is very powerful, but also a lot more
complicated than most people expect when they start to work with it. Take
your time to learn how to use it.
In this particular case, you need to call this function to convert the
ASAtom to a string:
const char* ASAtomGetString<http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html#ASAtomGetString135%28%29>
(ASAtom<http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html#ASAtom>atm)
(from
http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html
Karl Heinz Kremer
PDF Acrobatics Without a Net
[email protected]
http://www.khkonsulting.com -
Possible to get the color space and resolution from the .eps file
Hi all,
We have using the InDesign CS3 5.0.4, windows, javascript. We need to get the color space and resolution of the graphics (.eps) file using scripting.
The properties of the image like (actualPpi and effectivePpi will return the value only for the .tiff. and .jpg etc) but it will not return the .eps file resolution values.
Kindly give me the suggesting for the decrepancies.
Regards,
Nagaraj... open them programmatically in PhotoShop, read out resolution and color space ...
On opening them in Photoshop, it asks you "what resolution shall I use, and what color space shall I apply?"
A single EPS may contain any number of embedded bitmaps, with any horizontal and vertical resolution, and in any color space. You can use only a few of these with Illustrator -- and even only one at a time with Photoshop --, but other programs allow just about every possible combination.
Not to mention procedurally generated bitmaps, also possible with PostScript. -
Photoshop Elements 12 does not support the color space
I recently installed Photoshop 12 on my computer after a reformat. I was previously using Elements 10. i am not getting this error when trying to import photos from my camera. Photoshop Elements does not support the color space. I am using a Nikon D3200 camera to download from. I never had this problem with Elements 10 using the same camera. How do I fix this?
It turns out that this problem went away after the program crashed. Everything seems to be working well now.
-
I've been having an ongoing problem with some of my images changing color/luminance values after merging or flattening an image. This seems to most often happen if I use one of the filters (like crosshatch or notepaper, not sharpen or blur). I can make a copy using command/option/shift + E which most often will look exactly like what's on screen.
Some people have suggested that it's to do with resolution, PS showing me a low resolution image but I don't think so because the histogram changes -- sometimes in a big way, but most often those spikes in the luminance levels are shaved off. Also, when I have the image open at 100% and effect a merge/flatten, the color changes.
I'd like to know if there's a way to have PS show me one for one what I'm working on while I'm working on it, or if there is a way to control the color profiles when I'm saving. My best guess at this point is that there is a color profile mismatch going on somewhere. I just don't know where to look for it.
Typically I work in 16 bit, so my color space is set to ProPhoto RGB; my camera is set to the Adobe color space;
color management policies are set to preserve color profiles;
conversion options --> intent is set to relative colorimetric.But it is calibrated. I use Xrite 1 and update it every month (on the first).
The colors can be really off. Here's an example.
https://flic.kr/p/r6A1Zd (what I want) https://flic.kr/p/qc5QTD (not what I want)
Also, I can't see how the bit depth will have any effect since the change in color happens in PS when I merge or flatten. It's 8 bit through the editing and 8 bit when I flatten it.
Have you any suggestions on what I can do on the computer side? -
Spyder makes the color space too small
Hello,
I just bought a NEC MultiSync LCD2690WUXi monitor which has a fairly large color space. Then I made a monitor profile for it using the spyder2pro. There is also an original icm profile for the monitor which I downloaded on the NEC website, and this one is distinctly larger than my spyder-made profile. I was looking forward to having a monitor which can display 95% of the Adobe RGB color space, but once I calibrate the monitor the profile doesn't even cover the sRGB space, it's simply too small.
I saw the difference on a website called iccview.de (unfortunately it's in German) where you can upload your profiles and compare them to standard profiles in form of 3D graphics.
Without calibrating the monitor at all I could see a lot of amazing colors, but it was also definitely too saturated and unbalanced, ecpecially in the reds. So does this mean you have the choice between a large color space but colors out of control on the one side - and well-balanced colors but smaller color space on the other? Is the spyder to blame?
I use Windows XP Home and a GeForce 6600 GT.
Thanks in advance for your timeThe color matrix for that device probably doesn't expect to be looking at a wide gamut display and producing issues in measurements. Also, NEC doesn't recommend this instrument (yes I know, the software supports it).
-
Is the color space conversion needed for optimal uploads to Blurb using the book module automatic?
Just uploaded my first book to Blurb using the module in LR4. Blurb recommendations are to upload sRGB if using their software, or to convert to their cmyk profile if using Indesign or a pdf workflow ( I think).
So, I hope that the proper conversion is done automatically when uploading using the new book module. I uploaded a mix of edited raw nefs, edited tifs, psd's, jpegs which normally I would convert upon export to srgb to use in the stand alone booksmart app with great success color wise. I'll see my new books in a couple of weeks, but I'd like to rest easy till then.Yes, the direct export sends sRGB to Blurb.
-
The availability of color space in RAW, TIFF and JPEG files
This is useful if your new to DSLR photography.
This is Nikon response on my question in the discussion: View photo metadata
I'm assuming that you know that Adobe RGB shows about 50% and sRGB 35% of CIELAB color space.
In a DSLR camera like the Nikon D800 you can select a color space (Adobe RGB or sRGB) in the shooting menu.
In Adobe Lightroom 4.3 the RAW metadata shows no color space info. Therefore I asked why not?
In the (Dutch) Nikon D800 manual on page 84 (about RAW) and 274 (about color space) and Nikon FAQ website there is no descripton about the color space availability/behavior in RAW, JPEG and TIFF files.
In the book "Mastering the Nikon D800 by Darrel Young" on page 125 - 126 is written: "If you shoot in RAW format a lot, you may want to consider using Adobe RGB....."
All experts on this forum answered: color space does not apply/affect the RAW data file or RAW files have no color space.
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are always physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available. So the forum experts gave the correct answer!
Of course you can convert afterwards a JPEG or TIFF file with sRGB color space to Adobe RGB but you don't get more colors.
When you install the Microsoft Camera Codec Pack or FastPictureViewer Codec Pack they only show color space metadata for JPEG and TIFF files and nothing for RAW because color space "doesn't exist". I thought the codec packs removed the color space metadata for my RAW files.
Adobe Lightroom also can not show color space for RAW files because that "doesn't exist".Van-Paul wrote:
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available.
I still think this is an evasive answer that doesn't really pinpoint the exact chain of events that take place. They are:
1. The raw file contains the naked data captured by the sensor. This is just a very dark grayscale image.
2. In the raw converter it is encoded into a working color space to process the information. In Lightroom this is known as "Melissa RGB", or linear gamma Prophoto. It is also demosaiced to bring back the color information.
3. From Lightroom it can be exported to one of the familiar color spaces like sRGB or Adobe RGB. This is, in principle at least, a normal profile conversion.
These three steps are what the camera does to produce a jpeg. So the basic steps are the same, the camera is just doing it automatically (and usually butchering the image in the process...).
This Darrell Young is, I'm sure, an excellent photographer, but in this he is seriously confused and just propagating a common myth. Anyway, thanks for bringing up this discussion, hope you didn't object too much to the tone of the answers... Our only concern here was to get this right and with no room for misunderstanding. -
I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
MichaelOkay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings.. -
I have some pictures that don't show a thumbnail in iPhoto. The info dialog for them says the Color Space is "Gray" and the Profile name is "Gr?skala - gamma 2,2". If I double-click on of these the enlarged image seems somewhat faded. The picture looks fine if I just view it directly in Preview, or ColorSync Utility. It seems most pictures have a Color Space of RGB, how to I change the Color Space of these files to RGB?
Justin:
Download the Automator application "Embed sRGB Profile" from Toad's Cellar and unzip it. Then locate the original files for those problem images and drop them on it. Next launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library and select the first three options. This should get those images compatible with iPhoto.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file. -
Why the colors look so different betweet my Camera Raw and Bridge?
We know that after editing images in Camera Raw, thumbnails in Bridge will updated according to the new xmp files.
However, for some of my Raw files, the colors look very different in Bridge after makeing adjustments in Camera Raw, I can see more red in those phoots. But when I reopen the file in Camera Raw, all the colors are just correct.
For those photos without applying xmp files the colors looks exactly the same in Camera Raw and Bridge.
Does this means that my Camera Raw and Bridge use different color space? How can I fix this problem? Thank youIf you want help, you need to specify your platform (Mac or Windows), the exact versions of your Operating System, Photoshop, ACR plug-in and Bridge.
Also look at your Bridge preferences and tell us what you have your Thumbnail preferences set to.
Re-setting your preferences and purging the cache would also help. It could be something as simple as a corrupt cache.
Bridge is Color Managed, but it does not use a color space of its own. It applies the color space with which each image is tagged, it assigns sRGB to untagged files.
When was the last time you calibrated and profiled your monitor?
Details would help.
Wo Tai Lao Le
我太老了 -
Can anyone tell me why this picture changes color when I try to download/upload it? It is the exact same picture I have taken from the same location. The image on the left is via preview and the image on the right is what is shows like when I try to download it. I have emailed it to myself and it shows fine on the computer and in CS4, but when I look at the download via my phone or on another computer it shows the wonky color on the right. I have checked the color space shows RGB/8 bit. Any ideas why or how to fix it? It isn't with any one specific session.... and I've tried it on both my desktop and my laptop- saved image to an external hard drive and to drop box. I've tried sending the image to canvas on demand, my email, mpxipro, POST editing- all the same result. Please HELP!! What am I doing wrong?
Most of the time you see something like that. The image in question has a color profile other then sRGB. Some image viewers/displayers are color managed and others are not. So the image do not look the same in all of the applications you use. So colors seem to change.
Try converting it to sRGB color and see if then looks the same all around. Also I think PC and Mac displays are set to different gamma something like 1.8 and 2.2
Though I'm colorblind I even see color variations. -
Windows XP Bridge CS3
ACR 3.7 and previous used to give the option to convert to various colour spaces (profiles I always get confused here).
I've noticed that my Canon raw files show up in bridge as "colour mode RGB"
If I edit in ACR4.1 and save; they show up as "colour mode RGB and colour profile Adobe RGB" which is the color space of the camera (20D).
Files that I have previosly edited in lightroom (ACR 4) show up as "pro photo RGB"
I have my colour space in photoshop set to pro photo RGB so lightroom edited files open without a mismatch whereas files edited in ACR4.1 in bridge produce a colour space mismatch.
Am I missing something? or has the behavior of ACR changed in this respect since the comming of version 4?It sounds like you have Camera Raw set to Adobe RGB. You can change that to Pro Photo RGB.
Along the bottom of the Camera Raw dialog box there should be a link that lists the color space, bit depth, file size, and resolution. Click on that change the Space from Adobe RGB to ProPhoto RGB.
Maybe you are looking for
-
How do I make multiple different objects look like they belong in another environment?
For example, photos of city buildings put onto a green field. The colors do not match and the lighting is all wrong, im sorry if this is a really basic question to ask but please help, thanks!
-
?I have the Zen Touch 40 GB. I want to jog with it, but it's not recommended to do this with a hard disk based player, only flash players. But I'm wondering if it's really that much of a risk. So, opinions, is jogging?with a hard disk based player: ?
-
Blinking of everything or just spots of the srceen. every time i do anything out side of firefox4
every time i do something out side of firefox4 it star to blink or flickering
-
Need help, Win7 64-bit, USB 8G, Mac Mini, boot camp install.
When i run win installation it stops. I try to formate "bootcamp" drive and press next, and then the error message appears. Please help.
-
HT1657 Is 18 hours normal to download an HD movie with a good broadband connection?
Is 18 hours normal to download an HD movie with a good broadband hardwired connection?? This is my first attempt to rent an HD movie for the evening. At this rate, will be watching it tomorrow. Anything I can do on my end? Help!