Why Invalid Color Space Error?

Hi Everyone,
I am receiving numerous "invalid color space" errors when viewing PDF files in Acrobat Reader (v 11.0.10) on Windows 8, but have not received similar messages when using Acrobat Reader (v 11.0.10) on Mac OSX 10.9.5. I will outline our environment and workflow below.
The PDF file is created via the export of an InDesign CC 2014 document. No errors show up on the preflight panel, and no warnings show up upon export. The file can be opened fine in the Mac environment with both Acrobat Pro 11.0.10 and Acrobat Reader 11.0.10. I can navigate through pages, print, and add comments in both applications.
When this same file is opened on Windows 8 it initially loads, navigates pages, and will allow a few comments to be inserted before showing an "invalid color space" error. If the error occurs during commenting, the comment will disappear, and I am no longer able to scroll through any other pages since the error reappears.
I would think that if it was file corruption the problems would be on both Mac and Windows. Any suggestions would be extremely helpful as all of my searches point to a non-Adobe product (as either the document source or PDF generator) as the culprit with this error.
Thank you!

Hi Racheal ,
Please refer to the following link to see the actual cause for "invalid color space" error and the possible solutions to deal with it.
http://blogs.adobe.com/dmcmahon/2011/05/17/acrobatreader-invalid-colorspace-error-opening- a-pdf/
Regards
Sukrit Dhingra

Similar Messages

Invalid Color Space error after update Reader to 9.3.3

After updating Adobe Reader to 9.3.3 I run into the Invalid Color Space error when trying to open a PDF file created with CorelDraw 12 in the format PDF/X-1A. This format needed by a printing office to print the file. The strange thing is that Reader opens older PDF files exported from CorelDraw in thsi format normally without the error message.
It happens only with PDF exports made after the Reader update. CorelDraw settings are as previously used.
Exports in other formats, other than PDF/x-1, X-1A and X-3 open normally. How to solve this??

any suggestions?

How to resolve Invalid Color Space error with IE ?

We are in the progress of upgrading to Acrobat 9.3.4. We have approximately 1400 fillable PDF templates in our repository, and are getting an error displaying 10 of these forms after upgrading to Acrobat 9.3.4. The error is:
"There was an error processing a page. Invalid ColorSpace." All the forms were created with Adobe InDesign, then embellished with fillable form fields using Acrobat 7. From reading other posts, this seems to point to a corrupt PDF, but we do not believe this to be the case and we believe this is a bug in Acrobat 9. Here is what we've witnessed to back up this conclusion...
1.) The problem only occurs when displaying the PDF from within an Internet Explorer browser window (both IE6 & IE8). It does not occur if we simply open the PDF from the file system within Acrobat.
2.) The problem is random and not consistent. We usually get the error, but sometimes it opens fine.
3.) When the problem occurs, we're able to view the PDF by right clicking on the PDF and toggling the "Resolution" settings in the Page Display Preferences (either toggle from 96 to custom, or change the custom number). However, this is not an acceptable long-term workaround for our end users.
4.) We've tried recreating the PDF by opening it up in Acrobat 9 and doing a "save as...". The problem still occurs with the resulting PDF (we have not yet tried altering any other Acrobat options).
5.) The problem does not occur when opened in the browser with earlier versions of Acrobat (7.x for example).
Please provide any update you may have on this issue.

If you create a new application and try to create a new JSF page there are you still getting this error?
If you do then I think something in your installation went wrong - the first step would then be to delete the system directory at: C:\Documents and Settings\youruser\Application Data\JDeveloper and restart JDeveloper.

Cannot view a PDF in IE on Windows XP - "Invalid Color Space"

I am trying to provide a link to a PDF for online viewing:
http://glencoe.com/sites/common_assets/mathematics/007891647x/LP/FL5MINC3_7_2c_892770_se.p df
Some users can see the PDF with no issue, other users with Acrobat reader 9 on Windows XP receive this error: "Invalid Color Space."
Does anyone know why I'm getting this error, or more importantly, how to fix it?
Thanks,
Rob Underwood

What's the word on this? I am still having the same issue. This is very problematic for many pdfs on many websites! Can someone from Adobe please answer this???

Adding a LOV MAP in a Page resulting page (invalid name space error) error

Hi,
I am trying to add a new LOV to a region in one of the oracle product self service pages.
I am getting the LOV region displayed, but the moment I add lov mappings I am gettting the invalid name space error.
Your help on this is highly appreciated. For your reference I am attaching the error below.
ElementData.java:103) at oracle.adf.mds.internal.Cache.cacheElement(Cache.java:645) at oracle.adf.mds.internal.BaseCache.create(BaseCache.java:157) at oracle.adf.mds.internal.parse.ElementParser.startElement(ElementParser.java:222) at oracle.cabo.share.xml.TreeBuilder$Handler.startElement(Unknown Source) at oracle.cabo.share.xml.ParserAdapter.startElement(Unknown Source) at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149) at oracle.cabo.share.xml.ParserAdapter.parse(Unknown Source) at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source) at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source) at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:283) at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:115) at oracle.adf.mds.adapters.DBAdapter.getElementData(DBAdapter.java:324) at oracle.adf.mds.internal.MetadataManagerBase.findElement(MetadataManagerBase.java:1237) at oracle.adf.mds.MElement.findElement(MElement.java:97) at oracle.apps.fnd.framework.webui.JRAD2AKMapper.getRootMElement(JRAD2AKMapper.java:493) at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getWebBeanTypeDataFromJRAD(OAWebBeanFactoryImpl.java:3783) at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getRootApplicationModuleClass(OAWebBeanFactoryImpl.java:3460) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:988) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418) at oa_html._OA._jspService(_OA.java:88) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:534) oracle.adf.mds.exception.MDSRuntimeException: Invalid namespace: The namespace "null" has not been registered with the MetadataManager at oracle.adf.mds.internal.MetadataManagerBase.getElementDef(MetadataManagerBase.java:330) at oracle.adf.mds.internal.ElementData.(ElementData.java:103) at oracle.adf.mds.internal.Cache.cacheElement(Cache.java:645) at oracle.adf.mds.internal.BaseCache.create(BaseCache.java:157) at oracle.adf.mds.internal.parse.ElementParser.startElement(ElementParser.java:222) at oracle.cabo.share.xml.TreeBuilder$Handler.startElement(Unknown Source) at oracle.cabo.share.xml.ParserAdapter.startElement(Unknown Source) at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149) at oracle.cabo.share.xml.ParserAdapter.parse(Unknown Source) at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source) at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source) at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:283) at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:115) at oracle.adf.mds.adapters.DBAdapter.getElementData(DBAdapter.java:324) at oracle.adf.mds.internal.MetadataManagerBase.findElement(MetadataManagerBase.java:1237) at oracle.adf.mds.MElement.findElement(MElement.java:97) at oracle.apps.fnd.framework.webui.JRAD2AKMapper.getRootMElement(JRAD2AKMapper.java:493) at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getWebBeanTypeDataFromJRAD(OAWebBeanFactoryImpl.java:3783) at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getRootApplicationModuleClass(OAWebBeanFactoryImpl.java:3460) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:988) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418) at oa_html._OA._jspService(_OA.java:88) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119) at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417) at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267) at oracle.jsp.JspServlet.internalService(JspServlet.java:186) at oracle.jsp.JspServlet.service(JspServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:534) ">
oracle.apps.fnd.framework.OAException: No data found for region (/oracle/apps/gl/controls/webui/ControlAssociationsPG).
     at oracle.apps.fnd.framework.webui.JRAD2AKMapper.getRootMElement(JRAD2AKMapper.java:527)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getWebBeanTypeDataFromJRAD(OAWebBeanFactoryImpl.java:3783)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getRootApplicationModuleClass(OAWebBeanFactoryImpl.java:3460)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:988)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418)
     at _oa__html._OA._jspService(_OA.java:88)
     at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
     at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)
     at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)
     at oracle.jsp.JspServlet.internalService(JspServlet.java:186)
     at oracle.jsp.JspServlet.service(JspServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
     at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
     at org.apache.jserv.JServConnection.run(JServConnection.java:294)
     at java.lang.Thread.run(Thread.java:534)
## Detail 0 ##
oracle.adf.mds.exception.MDSRuntimeException: Invalid namespace: The namespace "null" has not been registered with the MetadataManager
     at oracle.adf.mds.internal.MetadataManagerBase.getElementDef(MetadataManagerBase.java:330)
     at oracle.adf.mds.internal.ElementData.<init>(ElementData.java:103)
     at oracle.adf.mds.internal.Cache.cacheElement(Cache.java:645)
     at oracle.adf.mds.internal.BaseCache.create(BaseCache.java:157)
     at oracle.adf.mds.internal.parse.ElementParser.startElement(ElementParser.java:222)
     at oracle.cabo.share.xml.TreeBuilder$Handler.startElement(Unknown Source)
     at oracle.cabo.share.xml.ParserAdapter.startElement(Unknown Source)
     at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
     at oracle.cabo.share.xml.ParserAdapter.parse(Unknown Source)
     at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source)
     at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source)
     at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:283)
     at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:115)
     at oracle.adf.mds.adapters.DBAdapter.getElementData(DBAdapter.java:324)
     at oracle.adf.mds.internal.MetadataManagerBase.findElement(MetadataManagerBase.java:1237)
     at oracle.adf.mds.MElement.findElement(MElement.java:97)
     at oracle.apps.fnd.framework.webui.JRAD2AKMapper.getRootMElement(JRAD2AKMapper.java:493)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getWebBeanTypeDataFromJRAD(OAWebBeanFactoryImpl.java:3783)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getRootApplicationModuleClass(OAWebBeanFactoryImpl.java:3460)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:988)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418)
     at _oa__html._OA._jspService(_OA.java:88)
     at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
     at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)
     at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)
     at oracle.jsp.JspServlet.internalService(JspServlet.java:186)
     at oracle.jsp.JspServlet.service(JspServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
     at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
     at org.apache.jserv.JServConnection.run(JServConnection.java:294)
     at java.lang.Thread.run(Thread.java:534)
oracle.adf.mds.exception.MDSRuntimeException: Invalid namespace: The namespace "null" has not been registered with the MetadataManager
     at oracle.adf.mds.internal.MetadataManagerBase.getElementDef(MetadataManagerBase.java:330)
     at oracle.adf.mds.internal.ElementData.<init>(ElementData.java:103)
     at oracle.adf.mds.internal.Cache.cacheElement(Cache.java:645)
     at oracle.adf.mds.internal.BaseCache.create(BaseCache.java:157)
     at oracle.adf.mds.internal.parse.ElementParser.startElement(ElementParser.java:222)
     at oracle.cabo.share.xml.TreeBuilder$Handler.startElement(Unknown Source)
     at oracle.cabo.share.xml.ParserAdapter.startElement(Unknown Source)
     at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
     at oracle.cabo.share.xml.ParserAdapter.parse(Unknown Source)
     at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source)
     at oracle.cabo.share.xml.TreeBuilder.parse(Unknown Source)
     at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:283)
     at oracle.adf.mds.internal.parse.ParserUtils.createNode(ParserUtils.java:115)
     at oracle.adf.mds.adapters.DBAdapter.getElementData(DBAdapter.java:324)
     at oracle.adf.mds.internal.MetadataManagerBase.findElement(MetadataManagerBase.java:1237)
     at oracle.adf.mds.MElement.findElement(MElement.java:97)
     at oracle.apps.fnd.framework.webui.JRAD2AKMapper.getRootMElement(JRAD2AKMapper.java:493)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getWebBeanTypeDataFromJRAD(OAWebBeanFactoryImpl.java:3783)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.getRootApplicationModuleClass(OAWebBeanFactoryImpl.java:3460)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:988)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418)
     at _oa__html._OA._jspService(_OA.java:88)
     at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
     at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)
     at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)
     at oracle.jsp.JspServlet.internalService(JspServlet.java:186)
     at oracle.jsp.JspServlet.service(JspServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
     at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
     at org.apache.jserv.JServConnection.run(JServConnection.java:294)
     at java.lang.Thread.run(Thread.java:534)

Which version are you using? I believe that adding regions started from CU2. Confirm this.
Did you set the profle FND:OA Enable Defaults? This may not be the cause for your error but I got some LOV map errors because of this. There is a thread in the forum on this.
Ensure that your path and spelling are correct. The error shows ...CostPG. Should it be ...RN perhaps? LOV Regions are usually called RN.
If all else fails open a tar.

"Unsupported Color Space" error trying to open b/w PDF in PS

This glitch has occured periodically in every version of PS I've ever used. I'm sick of getting it. Let me emphasize" I'm working with a b/w all-text image scanned into a PDF using the "text" setting on my scanner. In past attempts with Adobe tech support to get this fixed, it ends up having something to do with a glitch in PS programming, which gets fixed after an hour and a half of being treated like an airhead by the support tech and finally going into the secret settings area of PS and fixing it.

I did some tests on that image (Color Space: Indexed Device Gray) in Acrobat Pro.
If you want to open it in PhotoShop you could convert the whole PDF to RGB.
There is a Single Fix Up in the Preflight section of Acrobat Pro for this.
See screen shot of Acrobat Pro 9 here (in X or XI this feature is also available):
After using that fix up and saving the PDF to a new name, the TouchUp Object tool can use PhotoShop to open the image as an Indexed 8Bit Channel image in PhotoShop.
You can now convert to Grayscale in PhotoShop if you want…
Uwe
Message was edited by: Laubender (some typos)

Color space of TYPE_CMYK

Hi,
I tried to create a color space of type CMYK as follows:
ColorSpace cmykCS = ColorSpace.getInstance(ColorSpace.TYPE_CMYK);But i got "Unknown color space" error message.
Exception in thread "main" java.lang.IllegalArgumentException: Unknown color spaceIt seems like we can only create colorspace of type CS_CIEXYZ, CS_GRAY, CS_LINEAR_RGB, CS_PYCC or CS_sRGB.
Then what is the use of TYPE_CMYK constant?
But it is known that one can use some formulas to convert between RGB and CMYK colorspace.
But is it really possible to create the ColorSpace instance of type CMYK?
any thoughts!!!!

Usually an embedded file is the same color space as the AI file.
Only when you open a PDF generated elsewhere this might also be something like multichannel.

'Unsupported color space' nonsense

Hi all,
I have Photoshop CS2, 9.0.2 and I'm still getting 'can't open file because it uses an unsupported color space' error when I try to edit a graphic object from Acrobat. Is there any way around this problem?
Thanks!

Any image that contains and unexpected channel name is flagged as an unsupported color space = hence the dialog.
Photoshop is expecting to see for example CMYK, RGB, LAB, Index and Bitmap. If the person who created the PDF placed a Greyscale file or Spot color image, the dialog will come up. Duotones are also affected except Quadtones that have the supported naming convention of Cyan, Magenta, Yellow and Black. Also, CMYK with SPOTS and DCS 2 files are affected with additional channels as well as channels of expected CMYK are missing.
If I had Photoshops source code to change the naming of channels to allow a user to input names with no color values in Quadtones, I could confirm this naming issue on the Photoshop end.
So in conclusion it's most probably a filter problem in Acrobat that is making Photoshop barf.
PS-CS-3 extended and Acrobat 8
...and it gets really fun when a client converts the images upon PDF export and they have placed all kinds of flavors in the doument. yea right.

PDF ERROR! ICC Based color space contains/ alternate key

Can somebody help me?
When I put in Rip (Agfa Apogee X) a pdf I receive the follow error: ICC Based color space contains/ alternate key.
I don t know where is the problem? There Is a problem with pdf? or it is a problem in my Rip? how can I solve this?

That's pretty odd, because (techncnically) an ICCBased color space must contain an Alternate key, so why complain about it? It certainly seems specific to your RIP, so I would check with Agfa what it means and whether it is a check you can turn off, or if an update is available.

Error "Expected end of color space" when opening converted OTF - PDF.

Hi experts,
I need help. I'm converting from otf to pdf and it works fine. However when i tried putting a bitmap 256 color to the smartform and generate pdf with CONVERT_OTF FM the pdf result in an error "Expected end of color space" when opening the document and it goes blank.
Can anyone tell why ?
Thanks,
Felix

Hi Peter,
I can open it with another acrobat version. However, the image is not displayed. Do you know why?
Thanks

Image in PDF error - Expected end of color space

Hi friends,
I am displaying a PDF file in an webdynpro application. The contents are coming from the output of a RFC. The pdf file contains an image. While I am running the Webdynpro application the image is not coming. An error popup <b>"Expected end of color space"</b> is generated. But the texts of pdf file is coming properly.
Please help.
With regards,
Sekhar

Hi Sekar
We are facing the same issue. Have you managed to resolve this issue ?
Please advise
Regards
Vivek

Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" while starting my application?

Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" when starting my application created in LabVIEW 7.1? I am starting the application in a PXI rack running Windows XP. I have an executable written in LabVIEW 7.0 that runs without this error. After clicking the Continue button in the error, the application seems to continue happily.
Is there something I need to include when I make the executable?
I would like to understand and eliminate this start up error.
Thanks in advance.
BobNorth

Hi Bob,
I looked through the program and I figured out where the error is coming from, and potentially what is causing it. In a lot of the cases of the program you are searching a 1-D array for the name of the case, and if you don't find it then it skips the function and gives "Error 1 occurred at Config Data Registry.vi(CASENAME) invalid object 0". I attached a screenshot that shows what I mean. The Search 1-D Array.vi is returning a -1 which means it didn't find the case. The reason I believe this is happening is because the shift register for that array is not initialized. While the other cases "reset" and "register" interact with the array shift registers and most likely create the array you need, if the program defaults to the "get data" case then it will try to run that before registering and won't have an array to search. This would also explain why it only has this problem at first and seems to run just fine after that. To fix this you should either make an initial array and wire it into the shift register or make the "reset" case the default as opposed to the "get data" case.
Regards,
Peter W.
Attachments:
Config Data Registry.png ‏55 KB

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

Why Can't Something Simple such as Setting Color Space Be Included??

Seriously, Lightroom is really lacking in that one cannot select a particular color space to be used in Lightroom. This is in Photoshop why not in Lightroom?
I'm sure there would be many others interested in this simple feature.
Cheers
Ron

LR works in a broad color space, similar to, but not exactly Pro Photo, which, when you export to files outside of LR, you can set to a number of color spaces.
RAW files have no color space, or temperature, so you have wide latitude in setting them when you convert a file to TIFF, PSD, JPEG.

Color Space and Bit Depth - What Makes Sense?

I'm constantly confused about which color space and bit depth to choose for various things.
Examples:
- Does it make any sense to choose sRGB and 16-bits? (I thought sRGB was 8-bit by nature, no?)
- Likewise for AdobeRGB - are the upper 8-bits empty if you use 16-bits?
- What is the relationship between Nikon AdobeWide RGB, and AdobeRGB? - if a software supports one, will it support the other?
- ProPhoto/8-bits - is there ever a reason?...
I could go on, but I think you get the idea...
Any help?
Rob

So, it does not really make sense to use ProPhoto/8 for output (or for anything else I guess(?)), even if its supported, since it is optimized for an extended gamut, and if your output device does not encompass the gamut, then you've lost something since your bits will be spread thinner in the "most important" colors.
Correct, you do not want to do prophotoRGB 8bit anything. It is very easy to get posterization with it. Coincidentally, if you print from Lightroom and let the driver manage and do not check 16-bit output, Lightroom outputs prophotoRGB 8bits to the driver. This is rather annoying as it is very easy to get posterizaed prints this way.
It seems that AdobeRGB has been optimized more for "important" colors and so if you have to scrunch down into an 8-bit jpeg, then its the best choice if supported - same would hold true for an 8-bit tif I would think (?)
Correct on both counts. If there is color management and you go 8 bits adobeRGB is a good choice. This is only really true for print targets though as adobeRGB encompasses more of a typical CMYK gamut than sRGB. For display targets such as the web you will be better off always using sRGB as 99% of displays are closer to that and so you don't gain anything. Also, 80% of web browsers is still not color managed.
On a theoretical note: I still don't understand why if image data is 12 or 14 bits and the image format uses 16 bits, why there has to be a boundary drawn around the gamut representation. But for practical purposes, maybe it doesn't really matter.
Do realitze hat the original image in 12 to 14 bits is in linear gamma as that is how the sensor reacts to light. However formats for display are always gamma corrected for efficiency, because the human eye reacts non-linearly to light and because typical displays have a gamma powerlaw response of brightness/darkness. Lightroom internally uses a 16-bit linear space. This is more bits than the 12 or 14 bits simply to avoid aliasing errors and other numeric errors. Similarly the working space is chosen larger than the gamut cameras can capture in order to have some overhead that allows for flexibility and avoids blowing out in intermediary stages of the processing pipeline. You have to choose something and so prophotoRGB, one of the widest RGB spaces out there is used. This is explained quite well here.
- Is there any reason not to standardize 8-bit tif or jpg files on AdobeRGB and leave sRGB for the rare cases when legacy support is more important than color integrity?
Actually legacy issues are rampant. Even now, color management is very spotty, even in shops oriented towards professionals. Also, arguably the largest destination for digital file output, the web, is almost not color managed. sRGB remains king unfortunately. It could be so much better if everybody used Safari or Firefox, but that clearly is not the case yet.
- And standardize 16 bit formats on the widest gamut supported by whatever you're doing with it? - ProPhoto for editing, and maybe whatever gamut is recommended by other software or hardware vendors for special purposes...
Yes, if you go 16 bits, there is no point not doing prophotoRGB.
Personally, all my web photos are presented through Flash, which supports AdobeRGB even if the browser proper does not. So I don't have legacy browsers to worry about myself.
Flash only supports non-sRGB images if you have enabled it yourself. NONE of the included flash templates in Lightroom for example enable it.
that IE was the last browser to be upgraded for colorspace support (ie9)
AFAIK (I don't do windows, so I have not tested IE9 myself), IE 9 still is not color managed. The only thing it does is when it encounters a jpeg with a ICC profile different than sRGB is translate it to sRGB and send that to the monitor without using the monitor profile. That is not color management at all. It is rather useless and completely contrary to what Microsoft themselves said many years ago well behaved browsers should do. It is also contrary to all of Windows 7 included utilities for image display. Really weird! Wide gamut displays are becoming more and more prevalent and this is backwards. Even if IE9 does this halfassed color transform, you can still not standardize on adobeRGB as it will take years for IE versions to really switch over. Many people still use IE6 and only recently has my website's access switched over to mostly IE8. Don't hold your breath for this.
Amazingly, in 2010, the only correctly color managed browser on windows is still Safari as Firefox doesn't support v4 icc monitor profiles and IE9 doesn't color manage at all except for translating between spaces to sRGB which is not very useful. Chrome can be made to color manage on windows apparently with a command line switch. On Macs the situation is better since Safari, Chrome (only correctly on 10.6) and Firefox (only with v2 ICC monitor profiles) all color manage. However, on mobile platforms, not a single browser color manages!

Why Invalid Color Space Error?

Similar Messages

Maybe you are looking for