Convex cuboid hulls in RGB space

Greetings,
imagine an RGB (Red, Green, Blue) cube with quite a bit of resolution, i.e. all R, G, and B can have
values between [0, (1<<20)-1] (twenty bits resolution). These values are read from three ADC's
(Analog to Digital Converters), part of a 'colour sensor'.
These sensors are fast: they can 'sense' a colour value (RGB) within less than a millisecond and
above all: they can read those values very accurately. The hardware stuff is beyond me, I'm just a
silly math guy, but in short, every colour RGB is represented by three twenty bits values.
A sensor has an Atmel micro processor on board. I've written some software for that Atmel,
testing those sample RGB colour values against a set of RGB cuboids, i.e. if a colour value
RGB (a three dimensional point) lies within some cuboid (a finite sub space of the entire RGB cube)
something is wrong/wright.
Allow me to elaborate on this: one application for those sensors is controlling the quality of broken eggs
(don't laugh ;-) Eggs are broken and egg-white is separated from the rest. Sometimes this breaking
process (a mechanical process) fails, i.e. there's no pure egg-white. We're talking a few million eggs
per machine here. Pure egg-white is used for a zillion purposes; don't ask me to elaborate here ...
Egg-white has a certain (RGB) colour range with a certain illumination intensity. In this RGB cube (see
above), the colour of egg-white can be represented by a set of cuboids within this RGB cube, i.e. if
a sensored values set lies within a set of cuboids, the sensor just sampled egg-white, otherwise
something else must've passed the sensor's 'eye' (think of shell particles, blood in case of a 'naughty
egg', etc. etc.)
Suppose there's a set of n samples rgb_1, rgb_2, ... rgb_n, given a number m, the maximum number
of cuboids that contain all samples rgb_i, find the cuboids c_1, c_2 ... c_m such that the sum of the
'volumes' of those cuboids is minimal. (n > m).
I have a nice and fast heuristic up and running right now, but I'm very interested in more ideas, formal
problem definitions, applicability of an LP (simplex) problem definition, oct-trees, etc. etc.
If you need more information, don't hesitate to ask (my email is available somewhere in my profile also).
Thanks in advance for any sensible reply and,
kind regards,
Jos
ps. this hardware stuff also does its dirty deeds in plastic-granulate quality testing, BMW/Mercedes
dashboard colour quality control and a few other applications.

given your space constraints the cuboids probably make better sense than a regression tree, none the less, you have still given no justification for why you want to minimize the volume of any cuboid.
Presumably the thing you are trying to optimize is the classification value of the resultant set of boxes and it seems unlikely to me that minimum cuboid size in any way does that. In fact, if you are not careful, choosing a strict tolerance based on an existing data set, will make your system too fragile.
I assume that in your model you will have cuboids that are indicators of good points and other cuboids that are indicators of bad points, and I further assume that you have a set of training data of properly labled points.
You could take any collection of cuboids whatsoever, overlapping or otherwise and you get a bit vector that is the result of the simultaneous tests against all the cuboids. (if you were imagining a disjoint set of cuboids you were imagining a bit vector with at most a single bit set. In the more general model where more than one bit could be set, you introduce some means of conflict resolution, like choose the first on bit, or you vote, or you take some weighted average)
In any case, a single bit vector represents a region in space (a complicated voting model will affect the shapes of the regions that you are modeling), and for any such region you can get a correct baysian probability for the classification of objects within that region.
You can then talk about the classification probabilities for that particular set of cubes. You can measure the number correctly classified and the number incorrectly classified. Presumably you want a high ratio on that.
I have perhaps confused the issue by introducing this bit vector representation. My real point is this. It makes little sense to me to write a routine to optimize one thing (like minimization of cuboid volume) and then see if the results conform to your intuition and just happen to optimize the thing you are actually trying to optimize for which is a good color classifier, rather than just starting right out and attempting to construct the optimal classifier.
If I were faced with this problem, even if I were to stick with the cuboid representation that you have choosen, I would focus on defining the classification function that I want to optimize and then attempt to maximize that. Any grubby old optimization technique like a GA should be able to give you a decent set of cuboids.
You also wanted some other names. Kohonen networks, Neural Gas and of course good old Nearest Neighbor classifications are perfectly fine classification algorithms and could get you there.
The Neural Gas model, if you are not familar with it already, is perhaps the easiest one to quickly grasp. Is it essentially a continuous K-means process. You create m random cuboids. You choose a sample point at random from you training set. Find the box that is nearest the sample point. Slide the center of the winning box a little closer (like maybe a tenth of the way) toward the sample point and expand the box slightly (or shrink it if it was already inside). Of course if the point was a "bad sample" you do the reverse, you push the box away a bit a bit. You can also keep an age on each box, (length of time since last hit) and retire a box if it "gets too old" and thus is not capturing and representing the samples. When you retire a box the tradition is to introduce a new one near the boxes that are getting the most activity.
Of course you can simultaneously grow both a set of cubes for positive results as well as for negtative results.
But trust me, having built classifiers before, you would do well to spend some time up front in defining what you mean by a well performing classifier. With a quantative measure for the quality of your final classifier, you will be in a much better position to search for and to evaluate design solutions that fit your space and speed constraints.
Enjoy!

Similar Messages

  • Open in external editor -- original color space workaround

    I was frustrated--like other's whose posts I've read--by the fact that when opening files (tiff, jpeg, psd) in an external editor they are all converted to the Adobe 1998 rgb space.
    I am working around this comfortably and by using some Automator actions that I got from Ben Long's Complete Digital Photography site: http://www.completedigitalphotography.com/?p=414#more-414
    In my Pictures folder I have an Auto Processing subfolder with Photoshop droplets and lots of 'hot folders' tied to Applescript folder actions. I made two new folders: OPEN in Photoshop & IMPORT to Aperture
    The Open in Photoshop folder has attached from Automator the following actions from the default Finder suite: Open Finder Items and Move to Trash.
    The Open action is self explanitory, the next step of moving the recently opened file to the trash guarantees that I can't save to the source file. This forces Photoshop to do a Save As even if I hit command + S. The Save As prompts me for a location and I choose the Import to Aperture folder.
    The IMPORT to Aperture folder has attached the Import Photos action from Ben Long's Aperture suite. By selecting the Delete the Source Images After Importing Them option and the Show Action When Run option I get a prompt asking what project to add the new files to and the old files are deleted from my hot folder after the import.
    This isn't a perfect round trip solution because I still end up with two copies of the image in Aperture--even if I was just opening the source image to tweak an adjustment layer. I might create an Applescript that would prompt the user and delete the precvious copy of the image if desired.
    Like many of you I was feeling blue yesterday about rumors of changes in the Aperture team at Adobe. Blue not because I beleive Aperture's going away, instead because I expect if this rumor is true that we will see some delays in the short term while the new team gets up to speed.
    While I am waiting for that to happen I intend to use this discussion site to find creative workarounds for Aperture's current limitations and share them as widely as possible. Many of you are already doing the same.
    Thanks!

    Yes you could do that.
    I was part of the alpha/beta test group for Adobe CS2. Most of my work was with scripting and automation, especially for Bridge. I did have a very good dialog with Bruce Fraser, Seth Resnick and other testers whose opinions are as good as fact in my book.
    The consensus was that most digital cameras--certainly the pro models--had a color gamut substantially larger than Adobe RGB (1998). Note that ACR give the option of developing an image into sRGB, Adobe RGB, Color Match RGB, or Pro Photo RGB; 8-bit or 16-bit. That's the way I want it in Aperture.
    If you use the perceptial rendering intent (this is almost certainly what Aperture is using as its undisclosed default setting) then you will compress the wider gamut of the camera into the smaller Adobe RGB (1998) gamut. If in Photoshop you used the Convert to profile command and choose the perceptial rendering you would probably expand the color gamut back out a little bit. Why bother? Aperture really should have options for open in external editor like the very good export version settings.
    I have in my Aperture library a bunch of 16-bit grayscale scans and some CYMK files that seem to be working fine with the workflow above and Automator actions. (Lab files won't import.) I wouldn't want to go through the convert to Adobe RGB (1998) and reconvert to proper space with these files. My workflow is letting my store these files in Aperture and still edit in native color spaces in Photoshop with minimal effort for a round trip. I like it.
    P.S. I said in my original post that it would be easy to write an Applscript to delete the orignial file in Aperture when reimporting a slightly modified Photoshop version. It may be possible but its not easy in the current version which only has a bare skeleton of Applescript functionality.

  • How to convert CMYK to RGB programmatically.

    Hi,
    I have a CMYK colorspace in indesign, i want to convert that as RGB color space, I got some codes, but I am getting incorrect data.
    Some of the codes which I tried are given below
            double cyan = 35.0;
            double magenta = 29.0;
            double yellow = 0.0;
            double black = 16.0;
            cyan = Math.min(255, cyan + black); //black is from K
            magenta = Math.min(255, magenta + black);
            yellow = Math.min(255, yellow + black);
            l_res[0] = 255 - cyan;
            l_res[1] = 255 - magenta;
            l_res[2] = 255 - yellow;
    @Override
        public float[] toRGB(float[] p_colorvalue) {
            float[] l_res = {0,0,0};
            if (p_colorvalue.length >= 4)
                float l_black = (float)1.0 - p_colorvalue[3];
                l_res[0] = l_black * ((float)1.0 - p_colorvalue[0]);
                l_res[1] = l_black * ((float)1.0 - p_colorvalue[1]);
                l_res[2] = l_black * ((float)1.0 - p_colorvalue[2]);
            return (l_res);
    The values are C=35, M = 29, Y = 0, K = 16 in CMYK color space and the correct RGB values are R = 142, G = 148, B = 186.
    In adobe indesign, using swatches we can change the mode to CMYK or to RGB.
    But I want to do that programmatically, Can I get any algorithm to convert CMYK to RGB which will give the correct RGB values.
    And one more question, if the alpha value for RGB is 1 then what will be the alpha value for CMYK?
    Can anyone help me to solve these issues... Thanks in advance.

    All you have to do is loop thru the swatches and change the space to RGB. Below is an AppleScript, but it shouldn't be too difficult to come up with the equivalent JavaScript. Your document's assigned RGB space will determine what RGB space the CMYK converts to, so if you are looking for sRGB, then Edit>Assign Profiles...>Assign Profile: sRGB
    tell application "Adobe InDesign CS3"
    tell document 1
    repeat with a from 1 to count of every swatch
    try
    set space of color a to RGB
    end try
    end repeat
    display dialog "All swatches have been converted to RGB color"
    end tell
    end tell

  • Problems with RGB colors in Illustrator

    Hello,
    i have a problem with saving my artwork which is done in illustrator in PDF file. This artwork needs to be saved in PDF in RGB colors. It seams  that I cannot do this. Originaly artwork was done in CMYK. Option Edit/Edit Colors/conver to RBG is not working that is this option is not possible.
    Any suggestions please. Printing company cannot process it if PDF is not in RGB colors.
    Thank you in advance.

    But there is no difference in either case as the file will not be overwritten.
    True that the file will not be overwritten if you're careful not to do a regular save, but there is a difference.
    When you switch from CMYK to RGB document mode in Illustrator, AI simply converts to whatever you've set as your RGB working space. Yes, of course, you can go into Color Settings and change your workspace profile if need be, but now you're monkeying with settings that you might not want to be changing frequently.
    Why not, instead, take advantage of a feature that's there specifically to deal with workflow issues like this?
    If the printer requires a specific RGB space that's different from your normal working space, it's much easier to select it from the destination color dropdown during PDF creation. If you'll be creating more files for this particular printer, simply record a custom PDF (job options) preset.
    Even if one chooses to do it the Wade Zimmerman way, one should make sure to look at the color panel during PDF creation to make sure no unwanted space conversions are taking place.

  • Wide Gamut Monitors & 10.6 Default Monitor RGB

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

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

  • HSB Color Space Question - How Many Colors Are There In Photoshop

    Hello guys, I have a sort of basic question that I have been trying to figure out for a few days.
    I am trying to find out how many colors there are in the Color Picker  when the Hue radio button is selected.
    I know there are 256^3 RGB (#Hex) colors, and I am trying to find some relationship when I am coloring with HSB color space in Photoshop.
    It just confuses me because the Hue slider goes from 0-359 and the S and B goes from 0-99...
    So how many HSB colors in Photoshop are there?  Am I missing out on some colors by using HSB color space in Photoshop as oposed to using RGB?
    Are there the exact same amount?  Are there more and there are duplicates in HSB space mode?
    Thank you all for all your help, much appreciated
    Travis

    misterfowly wrote:
    I know there are 256^3 RGB (#Hex) colors, and I am trying to find some relationship when I am coloring with HSB color space in Photoshop.
    It just confuses me because the Hue slider goes from 0-359 and the S and B goes from 0-99...
    So how many HSB colors in Photoshop are there?  Am I missing out on some colors by using HSB color space in Photoshop as oposed to using RGB?
    The deficiency of such mathematical models is that they do not take into account noise and human perception. In an 24 bit RGB space (8 bits per channel) there may be 16 million colors, but this assumes that there are 256 discrete levels in each color channel. You could increase the number of colors by using a 48 bit space. In practice, noise will reduce the number of discrete levels, and this will vary with the camera and ISO used in that camera. For example, consider the Nikon D5000 as evaluated by DXO. At  base ISO the camera can resolve only 21.8 bits of color information and this decreases to 15.6 bits at an effective ISO of 2079 (camera ISO setting of 3200).
    http://www.dxomark.com/index.php/eng/Image-Quality-Database/Nikon/D5000
    Then you have to consider how many of these colors can actually be differentiated by the human visual system. If you can't see a difference, it really doesn't matter.These differences are difficult to quantitate. One such effort uses MacAdam ellipses shown in this Wikipedia article on a CIE 1931 xy plot. How many of these ellipses are contained in the CIE xy space? The DXO site has similar ellipses for real world camera images.
    http://en.wikipedia.org/wiki/MacAdam_ellipse
    See this RIT FAQ for a more sober real world analysis. The actual number of colors is in the millions, but likely not 16 million.
    http://www.cis.rit.edu/mcsl/outreach/faq.php?catnum=1#219
    In a real world situation, I would not be overly concerned about differences between the RGB and HSB spaces, but one could increase precision by using a 48 bit space.

  • LR CMYK Soft Proofing: CMYK ICC to RGB ICC Conversion workaround?

    Okay, here's a long shot:
    So, CMYK isn't supported in LR. Got it. Annoying, but whatever.
    Here's my longshot question: Is there a method to mimic the CMYK colourspace available in my CMYK ICC profile by creating a limited RGB space similar to it? For example, a method of converting a CMYK ICC profile to an RGB one? It doesn't have to be exact down to the letter but I need a general idea.
    As background: I'm looking to quickly softproof the images in the limited space - I work for a daily newspaper and don't want to run through photoshop to proof them as it's not essential, though it's definately worthwhile to get a general idea for frontpages and the like to avoid major mishaps on important shots, and to ensure the images are as punchy as they can be.
    Any ideas would be greatly appriciated!
    Cheers,
    L

    Luka_k wrote:
    Here's my longshot question: Is there a method to mimic the CMYK colourspace available in my CMYK ICC profile by creating a limited RGB space similar to it?
    Actually yes, you'll need to fork over money for ColorThink Pro. The optional ColorCast module can "embed" the proofing effect of any ICC profile (RGB, CMYK, or more channels) INTO an existing RGB profile like sRGB which is what gets sent to Blurb. The big issue is, you don't really have an actual CMYK profile that defines Blurb's output conditions. Oh sure, they provide some generic CMYK profile they would like you to think is used for output but it's not (how can it? They have multiple papers and maybe even differing press technologies, one profile can't define all those output conditions). IF you could actually get a true output profile that is used for the printing, in theory one could build an RGB profile with ColorThink Pro that could produce the simulation. Maybe Blurb needs to contact CHROMIX and license this.
    Now IF you have actual output profiles for your presses, you could do this.

  • Consistent RGB Color Values with Photoshop CS4: An Impossibility??

    What I want is very simple: I want the Photoshop files I am working on and the rendered PNGs in my browser to have the same color values. I don't care if my web images look the same color on other screens or anything like that. All I want is for the screenshots of PNGs my web browser to match the color values I have used in Photoshop. I've had it up to here with color shiftsthis did not used to be an issue in CS3.
    Moreover, if I save a file on my Mac, and a color value is, say, #cf4640, I want someone who opens the file on a Windows box to get the same color value for that pixel. Ditto for the images I have saved for the webI want the RGB values to be consistent. This does not seem like too much to ask, does it?
    Right now, I have turned all color management policies set to Off, working spaces are all set to Generics, and documents are set to "Don't Color Manage"my Windows colleagues also have these same settings. This used to work as expected in CS3we all got the same color values on the same files, and colors didn't shift when viewed in a browser.
    Once again, I don't care if the colors *look* the same from platform to platform or screen to screen. I just want consistent RGB values.
    Color management has never caused me anything but headachesleave my colors alone, Photoshop! I really really wish there was a "Work Like Photoshop 4" setting for color management.
    Does anyone have any ideas how I might solve my problems?
    Thanks very much.
    Oh, and, incidentally, I was originally thinking of calling Adobe about this; how foolish of me. I looked into it, and can I just say how fantastic it is that you have to pay extra money for actual first-party tech support on a $700 piece of software?

    The sounds/language analogy isn't really relevant to this problem, because it suggests transforming between two entirely different media. One medium: the medium of sound information, to another entirely different medium: the medium of thoughts and meanings. That's something that simply can't be done without an intermediate translation. That's not the case with color transforms in the RGB space, where it's just a matter of taking RGB values and pushing them through a matrix to produce other RGB values. That's the process that messes everyone up and creates all the confusing color output, and frankly it's an unnecessary process. Your assertion that the values in a source image have no meaning without an associated profile isn't entirely true. What if those source values were simply pushed directly though to the display? After all, a display simply renders 8 bits of R, 8 bits of G, and 8 bits of B for each pixel.
    I think the original poster has some very valid concerns. Sometimes we just want to set some color values, and know that everybody's display, on every platform, will render those color values the same way. As he said, they may not look identical to the eye, but the values going through that DVI cable will be setting that pixel to the same 24-bit value no matter what. That's how things would be if there were no such thing as color management. That's how things used to be long ago, and in many ways the world of color was far more predictable and less confusing back then.
    Here's my vision for a perfect world: color management doesn't exist in the RGB space. None. No such thing. Source RGB values in images get pushed right through to the display. The onus is on the display manufacturers to produce hardware that renders those values as consistently as possible. In the world of print, sure- color management is incredibly useful. But if only we could go back in time and keep color profiles out of our RGB, I believe we'd be much better off today.

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

  • Problems exporting an RGB file as PDF

    Hello,
    Here is my problem.
    I made a 10 pages file in InDesign, RGB space designed for web. Created some masters. After exporting (smallest file size as well as others too) to pdf the result gives me different tint of colour on pages even if i used the same master. So, if page 2 uses Master A and page 4 uses the same master A, in pdf they have a different color, more like they have a different color managment.
    Please help me with this issue and sorry if i couldnt explain very well.
    Ana

    So in the screen capture, ive got up 2 pages, and down, another 2 pages. From left to right up is cover 2 and then page 1, then down, page 2 and page 3. The psd files Ive used for all masters are the same, using the same color space, using the same save options. Up, the green displayed for both background images is lighter and looks more like a CMYK green. Down, the green displayed is the RGB correct green. As i checked many times psd files are good and is nothign wrong with them from what I saw. There must be something I do wrong or I didnt notice in InDesign. As I said, space it is set for RGB, blending mode it is RGB and I do not use any other transparency objects on any of the page. So, Ive got only the background images files, and text from indesign, that is all. Still, I might do something wrong and I am not aware of, because I work usualy only for offset printing purposes, not for screen purposes set as RGB.
    My monitor behave the same as the example you gave, unevenly from top to bottom, still this is one of the first things I check if I see something wrong with colors, being aware of monitor behaviour.
    As you said the difference is not that big, but it still is and bothers me as long as I want to look everything the way I designed. Not important for this topic, still I am explaining to understand why I need everything as good as it can be. The final pdf file will be available for download on a website I design for an artist. She created an art character who has a background story developed. It is a special page on her website, designed only for this character with his story. The site will be seen in some expositional spaces by many people, so, for this purposes, I really need everything to look good, without evident issues.
    Thank you.

  • Where does Lightroom display color space?

    Where does Lightroom display color space assigned to an image? It should be in the metadata panel. In Bridge it displays Color Mode: RGB/B&W and Color Space: sRGB/Gray Gamma 2.2. Or does Lightroom convert everything to Adobe RGB or ProPhoto RGB?

    LR's internal working space is a variation of the ProPhoto RGB space, ProPhoto RGB's gamut but with a linear tone curve instead of the standard gamma 1.8 curve. This is because it is primarily a Raw editor and Raw sensor data is linear and because the ProPhoto gamut will more or less include all the colors most digital cameras can capture (depending on the filters in front of the lens, some cameras may capture ultra-red that is outside ProPhoto RGB). Retaining the linearity of the data makes editing calculations easier, faster, more flexible and more accurate since data has not been lost to the quantization errors involved in gamma correction. So for a Raw file the workflow is the assignation of the camera profile and conversion from that to linear ProPhoto RGB. However, the display data from the Develop module (the data sent to your monitor) undergoes a further conversion that involves the application of the sRGB tone curve, which is sort of gamma 2.2 but not exactly. This is because linear image data looks terrible - very dark and flat. Thus, the display is in a hybrid space called Melissa RGB, ProPhoto primaries and sRGB tonal response curve. At the time of export or printing a conversion is done from linear ProPhoto RGB to the output space designated by the user, which can be any RGB space - ProPhoto RGB, Adobe RGB, sRGB or any other one, provided you have an ICC profile for it in your OS's Color folder..
    Previews used by the Library module are jpgs in the Adobe RGB space.

  • Color space conversions to/from XYZ broken?

    I have just started writing a plug-in in which I need to convert data from an RGB space to XYZ and back again. For this I am using the sPSColorSpace->Convert16 function.
    Unfortunately, it seems that the conversions to and from XYZ are not performed correctly. I do not know exactly what *is* calculated, but XYZ it's not. One of the giveaways is that the result of the conversion depends on the color space of the RGB data, including the gamma. Instead, the XYZ values should be uniquely defined, independent of the source RGB space.
    I have since created a work-around, by using the sPSColorSpace->Convert16 function to convert RGB values to Lab, and converting those to XYZ and back again with my own code. In this way, everything works as expected. However, it's unsatisfactory for two reasons: (1) a basic SDK function seems to be broken, and (2) my workaround is very slow, introducing 4(!) redundant nonlinear transforms per pixel.
    Does anyone have similar or contrary experiences? And, assuming I haven't messed up, how should one go about notifying Adobe about this? Thanks in advance!
    Simon

    >XYZ is a device independent color space, not a transformation of RGB (like HSB).
    That is exactly what I meant. Sorry for expressing myself poorly.
    The test I did was as follows. I applied my filter as a smart filter to an RGB smart object. I then *converted* (not assigned) the RGB object to another color space using a relative colorimetric conversion. Because my filter operates in the XYZ space, the (visual) output should be unaffected by the color space conversion. Unfortunately, the output changed.
    When I changed my filter to use Convert16 to convert to Lab (instead of XYZ) and back, and manually performed the Lab<->XYZ conversion, the (visual) output was indeed independent of the source color space.
    My conclusion is that XYZ as calculated by the Convert16 function *is* a 'transformation of RGB', but, you are correct, it shouldn't be. The conversion does not properly account for the source RGB space.
    Simon

  • Help problem with workspace e.g. colour space!

    Hi everyone, made a bit of a mistake...I completed a whole short project with alot of shots from after effects.  However I did not select a workspace, so for a long time now I have been going mad trying to work out why the project wasn't coming up to scratch after I exported it.  The colours were becoming way to saturated, and darker.
    Now I have realized that its because of the workspace, but now if I select a preset the whole scene will change.  This is especially apparent with one shot which I have done with a 3D camera, and lighting.  What ever colour space I select effect how the image looks, either it will be too dark, to light or too saturated.  I am working in HDV, so the most obvious colour space to use is the one for that.  However the image becomes low in contrast, and due to the nature of many differnt items in one shot, they are all effected differently...
    Is there any easy way I can export the video with no colour space, without the colours changing in the render?  Or is there a way I can use the presets without effecting what I have already done?  With no colour space selected, what are the colour settings?  Many thanks.

    Is there any easy way I can export the video with no colour space,
    without the colours changing in the render?  Or is there a way I can
    use the presets without effecting what I have already done?  With no
    colour space selected, what are the colour settings?  Many thanks.
    That's a complicated question, Will. Many people turn off Color Management (in applications tha traditionally had Color Management, I mean) because they hope that turning it off means avoiding color management. It probably means bad color management
    But that's a long subject. There's also room for opinion.
    The very, very short answer could be: if the Project Working Space is the one you should use for your target medium (say, HDTV REC.709), and you make sure source files are intepreted correctly (HDV files should automatically show an embedded profile, but you can manually assign an HDTV. REC 709 Input profile if they don't.), then color rendering should behave even better than the generic RGB space used when there's no Project Working Space assigned (CM off).
    Two things are true, though. One is that turning on Color Management if you're not familiar with what you're doing could do more harm than good (there's a very good white paper on Color Management available from Adobe).
    For example:
    Do not use an output profile in the Render Queue unless you know why you are doing it.
    Do not use display management/device simulation if your computer monitor is not calibrated.
    Do not linerize the project or enable the option to blend using 1.0 gamma unless you know what you're doing.
    And the other, that people have been using AE without CM (it debuted in CS3) without getting color or luminance shifts. If you see very noticeable shifts, it probably is because of something else (or bad use of CM).
    An imporant question - the color shifts you are seeing, are these evident in the Comp panel as soon as you assign a project working space (like HDTV. REC 709) or do they appear later in the rendered file? Because changes introduced by the project space should be immediately noticeable in the Comp panel. If they appear in the rendered file only, then it's most likely something else (the rendering options, the format/codec you're exporting to, etc).

  • IPhoto color space

    What color space does iPhoto use to import digital photos from a digital camera, if the camera does not embed its own profiles? I read that iPhoto uses Colorsync default settings, but even though I set the RGB space to Adobe RGB1998, the photos seem to be embedded with sRGB IEC61966-2.1 profile when opened in Photoshop CS. There are no preferences settings in iPhoto for choice of color space for importing.
    Any help is appreciated.

    Joe:
    Welcome to the Apple Discussions. I'll try to answer those that I can.
    Linescreen - not familiar with that term but read a while ago that 150 lpi printers were used. Don't know if that's related or not. Also there seems to be a difference (for large book at least) between those printed at the West coast site and those from the East coast site. The west coast books were reported better.
    Print resolution - large books are printed at 150 dpi. However, you can change the dpi resolution of the pdf file that gets created for uploading and printing as follows:
    Method to increase the print resolution for books:
    1 - download and run Pref Setter.
    2 - open the iPhoto preference file from within Pref Setter.
    3 - locate the Keys titled BookTargetMediumImageDPI, BookTargetSmallImageDPI and BookTargetImageDPI.
    4 - change their current values to 300.
    5 - save and quit Pref Setter.
    Colorspace - I've used sRGB but don't know if that's the optimal one. My results have been OK in my mind.
    Files accepted - all those you've listed are acceptable. Tiff file shouldn't have alpha layers as iPhoto doesn't play well with them.
    Dot gain - don't know what that is.
    For sharpening of those I've sharpened I used Photoshop's Unsharp Mask filter.

  • 4 color space in ACR?

    HI
    do you think it's enough 4 color space in ACR? i meen way only
    pRGB, sRGb,aRGB and rRGB?
    thank

    Kokii,
    A RAW digital image in its pure form is a matrix of B&W data captured through red, green and blue filters, and really does NOT have any true color until we render it using a RAW converter. When you set the color temperature, tint, contrast, brightness, etc, you are instructing the RAW converter to convert and 'dematrix' the file, and while doing so, make sure that the file is rendered in color as an sRGB, Adobe RGB, ColorMatch RGB or Prophoto RGB file.
    So, if you choose ProPhoto RGB as your space in ACR, the conversions will be made to fit your file's data into the ProPhoto editing space, using the endpoints, color temp, etc, and other adjustments you made in ACR. When it arrives in Photoshop, it
    IS a Prophoto RGB file...period. At that point, you can choose to convert to another profile if you wish, or leave it in ProPhoto. Assigning another profile at that point will change the colors, which is usually not the desired result.
    Most images don't need ProPhoto RGB and come nowhere near needing its extended gamut. Converting a typical CMYK to ProPhoto RGB is usually silly, since the CMYK file has a VERY limited gamut. Usually Adobe RGB or sRGB is more than adequate. Even if these spaces clip a few colors, they are rarely noticeable. Most monitors cannot display the full Adobe RGB space, and most output devices are smaller than Adobe RGB, though some colors lie marginally outside ARGB.
    I'm really not sure what you are trying to accomplish. Personally, I am not a proponent of ProPhoto, and never use it for editing. Others do, and that is fine, as long as they are knowledgeable and work in 16 bit. The only time I do use it is as an intermediate space when converting a file from ACR, and only on a handful of images. As soon as that file arrives in Photoshop, I immediately convert to PhotoGamut RGB if I need extended gamut for printing. To each his own. But normally, I find that sRGB is adequate for about 75% the files I print, and with very few exceptions, the remainder are adequately covered by using Adobe RGB. So, I generally use those spaces when converting in ACR. Those files arrive in PS as srgb or adobe rgb files.
    I don't know if that explains things or not, but hopefully it is a bit clearer.
    I certainly hope this doesn't degenerate into a discussion of the pro's and con's of ProPhoto vs other editing spaces. We've beaten that to death.
    Lou

Maybe you are looking for