Color space, gamma, and code value range data

Greetings!
I'm getting close to submitting my film for professional DCP creation.  It's a ProRes 422 4096 by 1716, 2.39 - 1 file, created as a "master file" in a Premiere Pro CC export (the sequence being an "online" of sorts, built from SpeedGrade color-corrected DPX files).
The Guidelines for "Digital Cinema Source Delivery" require me to provide information about Color Space, Gamma, and Code Value Range Information (head vs full).  Specifically, an order form asks for TRT, Color-Space, and Full or Head. 
This is simply all Greek to me.  I know my film looks gorgeous, and the rest of what I've told you, but that's the limit of my experience.
Can someone help me out?  Specifics are preferred to broad strokes.  Many thanks in advance.

This is probably too late now for you anyway but here is some extra information:
The "Digital Source Master" is the video footage before any D-Cinema formatting or encoding has been done.
It can be literally anything. The DCI specification did not specify this.
They did however specify exactly what the transcoded verison has to look like. The "D-Cinema Distribution Master" (16bit TIFF, XYZ)
So in other words, you need to tell your service provider:
The resolution, fileformat, frame rate and especially the colourspace that you used.
For example r709 for HD or any other RGB colourspace with applied gamma value (2.3 for example).

Similar Messages

  • Need to display different colors for Actuals and forecasting values in WAD

    Hi Gurus,
    My requirement in the report is, I need to display different colors for particular values like Actuals(say value type 10) and for forecasting values(say value type 20) , and data will uploaded from flat file.
    Scenario : If I upload the data for March Month, I receive actual values upto March(Jan to March month) and from April to Dec(Forecast values with value type 20),  Every month I will be getting file and similarly for subsequent months, i will get current month actual values and forwarding months forecasting values,
    Now , my requirement is, When ever i execute the Report, Say if i execute for April Month, Upto April( Jan to April for actual values should be displayed in one color) and from May to Dec ( forecast values should be displayed in different color).
    I had tried with following options like exceptions and could not display , as it runs based on key figure values where as my requiremnet is based on the CALMONTH , i need to show different colors for both actual and forecast values.
    Kindly, help me out from this,
    Thanks

    Hi,
    it is not necesseary that you need to do that in WAD , you can do the same in BEx platform, Since WAD is build above the bex reports. so automatially any changes done in Report will be replicated in WAD
    Go for Exceptions in Bex. Give some range for Actuals and Forcasting at the creation of the exception.
    if you do those changes in BEX automatically it will replicate in the WAD.
    for more information please read this link
    http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/content.htm
    hope this will solve your problem.
    Santosh

  • Function Module required for getting Value Range data

    I need a function module where in i can get the data from a value range in a domain.
    Message was edited by:
            Gurpreet Singh

    Hi,
    You can use this code to get the Doman's fixed values.
    DATA:  lt_fixed_values     TYPE ddfixvalues,
      CALL METHOD cl_abap_typedescr=>describe_by_name
        EXPORTING
          p_data      = 'Domain_name' " Pass the domain name here
        RECEIVING
          p_descr_ref = lcl_abap_typedescr.
      TRY.
          lcl_abap_elemdescr ?= lcl_abap_typedescr.
        CATCH cx_sy_move_cast_error.
      ENDTRY.
      IF lcl_abap_elemdescr IS BOUND.
        CALL METHOD lcl_abap_elemdescr->get_ddic_fixed_values
          EXPORTING
            p_langu        = sy-langu " Give the language
          RECEIVING
            p_fixed_values = lt_fixed_values " This table will have the fixed values
          EXCEPTIONS
            not_found      = 1
            no_ddic_type   = 2
            OTHERS         = 3.
      ENDIF.
    Regards,
    Sesh

  • Color Spaces CIE and Adobe RGB

    Looking at monitor specs, usually, the color space of the monitor is given in terms of a target color space, like 96% Adobe RGB. Some give several, but along comes Dell, u2412, and they supply one: 82% CIE.
    I know what CIE is, but making a guesstimate from the Dell spec requires more than what I presently know about such matters.
    So, what are the expectations? Is that a meaningful spec for comparison sake? IOW, how much does Adobe RGB enclose CIE 1976?
    TIA
    Lawrence

    I went back to here:
    http://forums.adobe.com/thread/916368?start=0&tstart=0
    and ran some of those checks with the various presentations. Also, embarrassingly, I did know about the site but failed to go back when I looked for any test results for the 2412.
    sic transit Gloria!
    I also generated  a step tablet in PS, as well as doing several calibration reruns. I did a calibration in "Standard"ode and one in "Custom" where I had access to RGB controls.
    TFT Central did the same and claimed that the Custom was more troublesome and didn't yield any significant improvement. I beg to differ!
    Also, they made available the results of the Standard and Custom as an ICC profile for users and I defy anyone to tell me there is no significant difference. Between my two calibrations and TFT's, I have 4 flavors from which to choose. Wow! I'm impressed (NOT!)
    At any rate I settled on using my custom version as it shows the most neutral gray. It also showed the smaller dE both average and max deviation, 0.34 and 1.2 respectively, the only one exceeding 1.0. It also was close to the factory default than the others.
    What a way to run a railroad!
    The other fussbudget item is X-Rite. I doesn't like calibrating LCD. It manages to skip over steps along the way, and if I hadn't the experience and expectations step to step with my crt, I would probably be returning the Dell at this time. The differences from the data pov between my Custom and Average should be barely visible, but in fact, it is visually significant. Normal conclusions would hold the monitor at fault.
    Off to contact X-Rite.
    Lawrence

  • ALV, domain and F4 value ranges.

    Hi all
    I'm having trouble with getting F4 value range help up and running on a cell in my ALV. The main reason for my problems is because I'm not using a DDIC structure, but one I defined locally. The structure's field is associated with a domain type defined in the DDIC and as such I'd like to pull the value range from there.
    Here's what more-or-less what I'm doing:
    - Create a local structure type corresponding to fields of a DDIC table.
    - Select from the table into the structure.
    - Load ALV with structure.
    Is there anyway to get the F4 help on a cell?
    Ps. ref-table and ref-field doesn't work.

    As I'm not at the office at the moment I can't test anything, so I'll give you a progress update tomorrow, but in the mean time:
    Anjali - I'll have a look at that link. I'm still fairly new to ABAP so I can't tell off hand if that's what I'm looking for, but I'll know for sure when I have a look at the demo applications.
    Vijay - I do have value ranges for the domain of the type used by my structure. I believe ref-table and ref-field isn't working because my internal table is of type local structure rather than DDIC table type.
    Sekhar - I did try setting F4AVAILABL to 'X', but all that does is display the 'value range button' (which you can click to get the same effect as pressing F4), without actualling doing anything else.
    Thanks for the help thus far.

  • Color Settings, Gamma and such

    Hi all
    Since the LED display from the MBP is too oversaturated and contrasted, I cannot obtain a good image feedback when editing images with it. The Calibration Management Tool from the Mac isn't accurate in terms of sliders and controls, so I'm wondering if there is an app to tweak all this stuff with presicion.
    Thanks in advance.
    Ø3

    This is probably too late now for you anyway but here is some extra information:
    The "Digital Source Master" is the video footage before any D-Cinema formatting or encoding has been done.
    It can be literally anything. The DCI specification did not specify this.
    They did however specify exactly what the transcoded verison has to look like. The "D-Cinema Distribution Master" (16bit TIFF, XYZ)
    So in other words, you need to tell your service provider:
    The resolution, fileformat, frame rate and especially the colourspace that you used.
    For example r709 for HD or any other RGB colourspace with applied gamma value (2.3 for example).

  • 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..

  • Import code coloring xml and code snippets into dreamweaver cc 2014

    How do I import my code coloring xml file and code snippets from the earlier version of dreamweaver into cc 2014?

    Thanks, Preran. After uninstalling the 2014.1 update and reinstalling the previous version, I now installed the 2014.1 update again. Instead of jumping straight into restoring the preferences, I decided to test it out as-is, and it worked! No problems with pasting after opening any of my five browsers. I wonder what may have gone wrong the first time...or what was corrected during the uninstall/reinstall process. In any case, it is working again now and I am grateful. Thanks!

  • Export Color Space, etc?

    I'm a couple of days into a trial of Fireworks and I got it
    only for two reasons: First to be able to create navigation bars
    with popup menus on some of the menu options and second, to more
    easily create photo galleries for my web site. (I'm quite
    comfortable with PhotoShop and creating web-optimized images.)
    Anyway, I've run into a couple of things that have got me
    stumped...
    If I use FW CS3 to optimize a JPG image for the web (either
    from directly within FW or via the Create Web Photo Album command
    from within Dreamweaver CS3) the resulting images no longer have a
    color space embedded. And I can't find out how to embed one. The
    original JPG images were created in PS CS3 and had the sRBG color
    space embedded and the colors displayed as expected in a web
    browser. The resulting "optimized" images no
    longer have a color space embedded and the colors appear quite off.
    This might be acceptable with some vector graphics or logos but
    it's not acceptable with photgraphs, especially for a photography
    web site.
    (It's quite well-known, at least in photography circles that
    for proper display of the colors, images designed for the web
    should be in sRGB with that space embedded, as that is what web
    browsers are optimized for. Anything else, including not embedding
    a color space results in colors that are "off".)
    A related issue is that when using the Create Web Photo Album
    from within DW CS3 the resulting files all have a new suffix of
    "_jpg" added to the name. Meaning that my
    original "name.jpg" gets named
    "name_jpg.jpg". I really don't like that, and
    can't find how to turn it off.
    (I went to a large bookstore to buy a FW book today but they
    didn't have any. And the only one they even listed on their
    computer is due to be published at the end of February!)
    Any help would be greatly appreciated. Thanks.
    Eldor - Montreal

    quote:
    Originally posted by:
    Newsgroup User
    EldorG wrote:
    > As I said, PEBCAK error. But that still leaves me
    with the file name 'problem'
    > I mentioned... that my images get named from
    'name.jpg' to 'name_jpg.jpg'.
    > This happens when I use the 'Create Web Photo Album'
    from Dreamweaver CS3
    > (which in turn calls FW to do the work). Should I
    post that in the DW forum,
    > or is it a FW thing? Thanks very much! Eldor
    Don't name them in FW. Allow them to be exported with the
    names they
    already have.
    Linda Rathgeber [PVII] *Adobe Community Expert-Fireworks*
    http://www.projectseven.com
    Fireworks Newsgroup:
    news://forums.projectseven.com/fireworks/
    CSS Newsgroup: news://forums.projectseven.com/css/
    http://www.adobe.com/communities/experts/
    Linda, I'm
    not naming the images in FW. As a matter of fact, I never
    even see a FW dialog. If I optimize an image directly from within
    FW, there is no problem. But doing so from Dreamweaver (through the
    Create Web Photo Album command which seems to call FW to automate
    the work) causes the images to be reduntantly renamed. And I don't
    see an option anywhere to change this.
    As I said, I'm not sure if this is something I should be
    asking in the FW forum or the DW forum. But since this option
    doesn't even exist in DW until FW is installed and FW is called
    from DW to do this, I really don't know where to ask.
    How does that FW automation work? Is there a script file or
    something somewhere that I might find and modify?
    That option in DW not only optimizes a bunch of images, it
    creates thumbnails as well, and writes all the stuff into HTML code
    to produce a table of the images. So I can't just go to FW and
    manually optimize an image.
    Regards...
    Eldor

  • Why are the colors in Illustrator and Photoshop so off?

    Hi,
    Let me just start off by saying I have the color mode in both Illustrator and Photoshop set to RGB. Yet, there is a noticeable color difference between a picture on the internet and when I paste it in for example Photoshop.
    Picture from the internet:
    Picture when pasted in Photoshop:
    It's the same thing in Illustrator. And this is not just with pictures by the way, it's affects all the colors I use, which is a major pain in the rear.
    Anyone know a fix?

    Well, my suggestion in post #13, was to help me find out what the cause of your problem is. It doesn’t solve your problem permanently but temporarily, only for the current session of Photoshop or Illustrator by making these programs show your image without applying any color management conversions.  So, you have to do this every time you open such files in these programs.
    If you want to understand what is going on and be in control, you have to go through a lot of walls of text unfortunately .
    I’ll try to explain it roughly but if you don’t understand it you need to read more about color management.
    You are using Safari and this is how its color management  works:
    https://developer.apple.com/library/safari/technotes/tn2220/_index.html
    on that page it says:
    "Important: For images that are not tagged with a color profile, their color values will be displayed on the screen by Safari with no optimization or adjustment for differences between devices in how they render colors. This may result in the colors not being displayed as originally intended"
    This made me think that like most images on the web, the image you are using doesn’t have a color profile. In that case, assuming a certain scenario based on your input, the reason it is displayed differently from Photoshop and Illustrator is because you have a color profile of your monitor used by your system that is different than the color space used for the display of the image. By default RGB Images without a color profile are displayed using  the color space set for the working space in the Color Settings of Photoshop and Illustrator. Also by default this color space is sRGB.  If your monitor was also with an sRGB profile assigned in the system, which is the case with all monitors that come without a color profile provided from the manufacturer, you should have not experienced this problem because Photoshop and Illustrator will see that the color space you want to display your image is sRGB and your monitor is sRGB, and there will be no color conversions because both color spaces, source and destination are the same.  Unless someone else has setup your system ,color management, and installed a monitor profile,  my guess is that the manufacturer of your monitor has provided a color profile installed in your system that is not sRGB.
    When you choose View > Proof Setup > Monitor RGB, this in effect turns off the color management because you are displaying the image in the same color space as the one assigned to your monitor.
    If you want to turn off the color management permanently which will be valid only when displaying images in the sRGB color space, you can assign the sRGB color profile to your monitor. This will show the images on your monitor with the same colors as those displayed without color management in the other applications and choosing View > Proof Setup > Monitor RGB will make no difference.
    Non color managed programs can display the color only in the way your monitor displays it. Color managed programs simulate other outputs on your monitor. The only way to match the display in color managed and non color managed software is to turn off the color managed software. This will display the same color values with the same color in all programs on your monitor.
    The purpose of the color management is to allow the viewer  see the colors as intended (the way the creator sees them when creating the image). Different devices and media output the same color values differently resulting in different color. Therefore, when the viewer uses different device or media the colors if not color managed properly will look different or not as close as possible.
    When you turn off the color management, or even when it is on but not properly applied, which I suspect is the case in your situation, you can’t be sure that the colors you see are as intended. In other words, you can’t tell if an image is supposed to look the way you see it, and you can’t create images providing means that will allow others to see them the way you see them. 
    So, for whatever reasons you want to make colors look the same in all your programs, have in mind that this is valid only on the current state of your monitor, and this also cuts the possibility to see and send to others colors as intended.

  • Monitor Color Space

    My camera records in RGB and my printer prints in CMYK.
    My question, what color space for my LCD monitor?
    If I don't calibrate, I am given the choice of Samsung 213T factory color space, sRGB and RGB.
    Thanks
    Richard Cooper

    In a perfect world, the 213T colorspace would be precisely the right choice. I'd use that, but I'd start by loading it into the Adobe Gamma utility to "massage" the profile for use by the gamma loader. At some time, you may want to look for a bargain on a hardware package like the Monaco Optix XR Pro for a more precise profiling. Depends on your needs and budget.
    Brent
    [edit]
    Once you load the profile into the Adobe Gamma Wizard, immediately click OK , to save the result as your custom profile, under another name.
    BB

  • Color space conversion problem when importing JPEG's

    Hi,
    I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
    Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
    The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
    Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
    /Steffen

    Hi Uli,
    thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
    I did some more experiments yesterday with interesting results:
    1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
    2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
    3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
    My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
    Can you confirm this behaviour?
    Steffen

  • 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

  • RGB / CMYK Color Space View

    This might be a really basic question, but can anyone tell me how I can toggle between the "RGB Color Space View" and "CMYK Color Space View" in the color picker menu box? Thanks.

    To the best of my knowledge, there is no CMYK Color Space View in the color picker. You determine whether the swatch you create is RGB, CMYK or LAB by clicking in one of the fields of each color model.
    Peter

  • Detecting multiple occurences of a value in data? (conundrum)

    Ok, if there are any good java utilities to help, this is where I'm going to find them...
    I'm trying to detect multiple occurences in a data set. Piling them into an array and using Array.sort() was a good start - I'm trying to find the max and min value of data that occurs more than once in the set.
    However, when the data set becomes much larger, I can't hold the set in memory. Is there an elegant solution to this? I'm at a loss to find a nice way of doing it. Its an interesting problem...
    Thanks,
    Steve

    Hi Steve!
    You can do this with a bit of programming yourself :-) If all values don't fit into your memory, just split them into smaller pieces. Do you need to sort out all duplicates or do you need to detect them only?
    The idea:
    Create a new ArrayList oder a Set of your choice and put some elements in it (a fixed number or just wait for an OutOfMemoryException to be thrown and catch this). Then sort the ArrayList and write it to a temporary file, store the file handle or name in a seperate list. Go on like this until all your data is sorted.
    After that, build one loop fetching just one value from each file and compare them - mainly this is mergesort. If duplicate values occur then, well, you have dupes :-)
    If needed I could look for the source...
    Cheers,
    Jan

Maybe you are looking for