DNG Profile Editor 1.0 beta 2 and real color

Where can I introduce the real value of my ColorChecker Chart?
Value of my chart L= 28.3 a= 15.3 b= -45.1
Référence value of the ColorChecker Chart L= 28 a= 19 b= -54

There is no way to do that currently.
However, our reference data is actually taken from the average of several physical charts and its blue patch is about 1.5 DE 1994 units from the blue patch of your chart, so I do not think it will make a huge difference.

Similar Messages

Adobe DNG Profile Editor

Has there been any update to this beyond that in 2008 found on Adobe Labs? (I want to try using it to calibrate ACR for my camera with a shot of a MacBeth Color Chart.)
To be more precise about this, I currently use ACR Calibrator to calibrate ACR for my Canon 1Ds II. I now see there is beta 3 of Adobe DNG Profile Editor but note that it utilises a small subset of the GMB Digital Colorchecker SG target chart.
ACR Calibrator seems to produce quite different results from Adobe DNG Profile Editor. I have followed the steps below when using the latter.
Download DNG Profile Editor and drag to Applications
Launch Photoshop and open the raw file of your macbeth target.
In camera raw, place all settings to zero, curve to linear and turn off any sharpening etc. Click Save Image, choose dng as the file format and save it.
Launch DNG Profile Editor.
File / Open DNG File and choose the dng file you saved previously.
Select the chart tab in DNG Profile Editor.
Move the colored circles to the center of the matching colored corner square in your raw file
Click Create Color Table.
Choose File/Export <Camera> profile... Give it a name and save.
Exit DNG Profile Editor.
Re-launch photoshop and open a raw file. In Camera Raw, on the calibration tab, you should now see the profile you just saved.

ssprengel wrote:
I don't know of any other references or CC Passport numbers other than what Google can come up with. Babelcolor has some standard-deviation of spectrum numbers for a sampling of 20 charts done in 2006 and also some worst-color vs average-color visual comparisons to get an idea of how variable charts or at least their measurements can be. Somewhere it says the me4asurements were done of the standard and also the minichart, mixed together, I assume. I don't know if there is a list of the raw data or not.
To understand the source of the variation you really need to see multiple measurements with the same instrument, with different instruments, and of different charts from different manufacturing runs and different ages and measured in different temperatures and humidities, otherwise it's not easy to say whether the variations we're seeing between the CC standard and the CC passport in the article are within the normal variations or not or if they represent a significant difference not explained by normal variations.
Yes, I know the Babelcolor data and I have already included them in the study.
Obviously I do not have the opportunity to have the information to get an overview of the real things, but by analyzing various measurements I saw that Myers had to be the closest to official data of the CC Passport and instead is the more distant. Hence my doubts about the measurement.
Thanks anyway.
Marco

Camera Profiles and DNG Profile Editor beta 2 now available

Hi everyone,
Beta 2 of the camera profiles and DNG Profile Editor are now available. Please visit here and enjoy:
http://labs.adobe.com/wiki/index.php/DNG_Profiles
I hope to have more detailed release notes/changes for you soon. You are welcome to ask questions, but please note that it may take a while for me to respond.
Eric

Eric,
I followed very carefully your instructions for installing the new beta2 profiles and deleting the beta1 profiles, but have the same problems as many others. I'd like to provide a bit more information. I'm running Windows Vista Home Premium and have installed Photoshop CS4, updated with ACR5.1 and Lightroom 2.1 final release. As others have described, the default for all of my images was set to one of the Camera profiles (Canon faithful beta1), but now the profile name in Lightroom is blank. I tried looking at the other profiles and it does indeed appear that the beta2 profile is being used, but if I then reset the image it now shows ACR4.4, whereas the image had been imported with the camera profile as default. Also, if I open an image in ACR5.1 that was specified to use the same camera profile, it now shows ACR4.4 and it is not using the beta2 profile of what I had been using, I can see this by selecting the other profiles. Going back to Lightoom, I guess I could select all my images and select the Canon faithful beta2 profile, but then the mark shows up bottom right of the image showing that they have all been edited/modified, is there anyway to get all my images using the profile I was using but the beta2 version, without this happening and how about new imports?
Thanks, David.

**-Camera Profiles and DNG Profile Editor FAQ-**

A page containing answers to Frequently Asked Questions about Camera Profiles and the DNG Profile Editor can be found
here

New FAQ entries:
What changed between beta 1 and beta 2?
Is it safe to delete beta 1 profiles? What will happen if I do?
I now have the beta 2 profiles and want to delete the older beta 1 profiles. How do I do this?
Please read carefully.

Colorchecker passport and the DNG profile editor

I finally got around to getting a Colorchecker passport to use with the DNG profile editor.
I was secretly hoping I could save time by shooting the chart on location and make an instant profile out of that - then the colors would be at least "close ballpark" so I would just have to apply white balance and then move on to more specific adjustments. But of course it wasn't that easy, it still takes a fair bit of color tweaking to get right in most circumstances.
So I'm wondering if my energy would be better spent trying to perfect one good dual illuminant general profile. For this I would use 3000 K tungsten at one end and 5500 K studio flash at the other. Or would it be better to use overcast daylight? In either case it's obviously important to ensure the chart is absolutely evenly lit.
And then I should probably have a separate profile for fluorescent tubes.
I'm curious what other people's experiences with the colorchecker/DNG profile editor are? How are you using it?

The color profile changes with the lighting, so a profile that was computed for daylight won’t be right for tungsten or fluorescent. Keep in mind that a custom camera profile is the set of corrections on top of an existing Adobe profile that the DNG has assigned to it, perhaps Adobe Standard, and all Adobe profiles are dual-illuminant profiles, so it makes sense you’d want to also create a dual-illuminant profile for general purpose use that has the same two lighting scenarios as Adobe used: 2850K and 6500K. The 6500K is the tricky one because full sun is warmer, closer to 5000K, and you need the right amount of haze to create 6500K sunlight, unless you are using standard D65 bulbs, indoors, which is likely what Adobe does.
I use a dual-illuminant profile for general purpose use, but since the WB-Tint values of both the tungsten and daylight ends are close to zero, lighting that has a tint not close to zero needs a separate profile. The common example is the greenish light from fluorescents, and I have several single-illuminant profiles for various artificial lighting scenarios with WB-Tint values that are relatively non-zero. I also have ones for very red sunsets and very blue twilight. If I had studio lighting I’d make a profile for that. Sometimes I make a custom profile for a church or other venue that has significant non-neutral walls or ceilings, or where sunlight through the stained-glass windows shining on the walls are giving a significant color-cast including a non-zero tint value to the lighting. If you know you’ll be doing some shots near a large amount of tall, green vegetation then a custom color profile can correct for the green tinge to the ambient lighting coming down from above mixing in with the sunlight.
Adding to the suggestion about wearing neutral clothing, I’d argue for dark neutral clothing because something lighter clothing will reflect environmental colors (sunlit vegetation or brick walls, etc, outdoors) and not be neutral.
Besides non-neutral clothing, try to avoid areas that have green grass or tree leaves or brick buildings that also color the light and reflect off the colorchecker. For the sunlit shots, I put my colorchecker face up on the sidewalk or parking lot, to avoid coloration from the grass and far away from trees or buildings especially in the direction I’m pointing the camera, so the only lighting is direct sun and ambient blue-sky, possibly diffused by hazy clouds. I point the camera down at the colorchecker, at a 45-degree angle and at a compass direction and not directly toward the sun, nor directly away from the sun. I try to shoot the target that is face up on the ground perhaps at a 90-degree angle from the sun to minimize any residual glare from the colorchecker’s slightly non-matte surface. Obviously directly away from the sun, the color-checker will have my shadow on it or I will be blocking the light from the sky near the sun.
I use the same sort of process for the tungsten end, choosing a room with neutral walls and put the target relatively flat on the floor facing up, perhaps tipped up somewhat toward the light, but not so much as to have any glare from the lighting, either, in other words, not with the lighting directly behind the camera, but somewhat over to the side.

I have downloaded DNG Profile Editor 1_0_4 and prepared a profile which I can not see in my Camera Raw 6.0 (I have photoshop CS5). Could you please give me an advice?

I have downloaded DNG Profile Editor 1_0_4 and prepared a profile which I can not see in my Camera Raw 6.0 (I have photoshop CS5). Could you please give me an advice?

Uninstall Trusteer software
http://www.trusteer.com/support/uninstalling-rapport-mac-os-x
Remove Sophos
https://discussions.apple.com/message/21069437#21069437

Camera Profiles and DNG Profile Editor

I saw the lightroom 2.0 eseminar and the presenter mentioned Camera Profiles and the DNG Profile Editor. All I see is ACR4.4 and 4.3. The the FAQ page says I need ACR4.5 and I can't find it and haven't gotten any update notice. Should I just wait for an update or forget it?
Don

>I have CS4. Will this overwrite ACR 5.1 in CS4?
If you have CS4, you should update to ACR 5.2. If you install 4.6, you will break your CS4 install. Either just run the Adobe updater app, or go to http://www.adobe.com/support/downloads/new.jsp to download it. DNG converter is a separate download. Both camera RAW and NDG converter contain the final release version of the new profiles. DNG profile editor can still be downloaded from Adobe Labs: http://labs.adobe.com/wiki/index.php/DNG_Profiles. There is also a profiles download there that you don't need if you install DNG converter 5.2.

DNG Profile editor and white balance

I am very happy to see the practical realization of the extentions announced in the DNG 1.2 specification. This is a great step forward to achieve wide acceptance of DNG.
While reading the User's Guide, I found following statement (in the Tutorial 1):
>3. (Optional) If the image is not already white-balanced, you can perform a click-WB using a context click
Why would one white balance here? What effect does that have on the result? The profile describes, which HSV will be converted in which HSV; this has nothing to do with the WB of a particular image.

The WB feature in the DNG Profile Editor (PE) is there because it is possible that you might open a DNG file in PE that has not already been white balanced. Imagine you photographed an image under tungsten lighting but had the in-camera WB manually set to daylight. If you didn't set the WB before converting the image to a DNG, it will appear very warm when you open it up in PE. So PE's WB feature is designed to save you time by letting you do a click-WB instead of having to go back to CR or LR to adjust the image's WB.
PE is named "profile editor" because it only edits profiles. It is not an image editor. So you are correct, you do not really need an image to edit profiles, technically. However, unless you have an image open you have no way to evaluate how good your adjustments are.
Typically the only reason to make a profile or edit a profile is if there's something about an existing profile that you're unhappy with. And you'd be unhappy because you'd have an example of a "problem" image, where the existing profile doesn't produce the result you want. That's the image you want to bring into the PE, so you can pick out the colors that are "wrong" and fix them.
Then ideally you would open many more images in PE just to verify that your adjustments generalize well.

Questions about DNG Profile Editor recipe code

I have been playing around with DNG Profile Editor. With a text editor I made the following recipe:
I have some questions:
1. Right now I have my control points at 60 saturation. Will using two points for each color (say 70 and 40) make my changes more consistent across darker and lighter shades of the specific color?
2. Does DNG Profile editor respect HueLow and HueHigh, are they just placeholder numbers, or are they ignored if two points are close to each other?
3. What does FeatherAdjust do? I'm guessing it controls the rate of drop off of the corrections. Is the value respected by DNG Profile editor when it creates a profile?
Thanks for your time and attention, -Bruce.

1. For now DNG-only. Here's why:
http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#PEOnlyDNG
http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#WhyNameDNGPE
http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#WhyPESeparate
2. Standalone for now. See above links for why.
3. Use the 'Preview Color Changes' option in the Options menu.
4. You can use 'Apply Raw Adjustments' in the Options menu to see your raw adjustments. This is __not__ recommended for building a general-purpose profile because you are then optimizing a profile with specific image adjustments in mind, rather than building a profile based more on the inherent camera characteristics.
5. True, that is a limitation of this implementation.
6. I am not sure what you mean. The Chart Wizard automatically optimizes the color patches in a test shot based on reference values for many physical charts, which is more practically useful than the numbers printed on the reference card that comes with the chart.
7. Make sure you avoid color casts in the bottom row. The PE is picky about making sure your gray patches are relatively neutral. It is an attempt to help you get a better profile.
8. Use 'Show Affected Colors' from the Options menu.
You may wish to read this page carefully and thoroughly:
documentation
It is the reference online documentation for the DNG Profile Editor and a few of the things you wish to do, such as preview all color changes, apply raw adjustments, and visualize the extent of each color adjustment, are all documented there.

About to use DNG Profile editor

I've had my Colorchecker for a few weeks, and I finally have time to set up my profiles for LR 3.4. In reading the DNG Profile editor tutorial page (http://labs.adobe.com/wiki/index.php/DNG_Profiles:Editor), I have a few questions:
1) If I use Tutorial 5, I am guessing I will have to create a profile for each lighting/WB condition, i.e., one for Tungsten, one for Fluorescent, one for sunny, one for overcast, one for flash, etc... Is that correct? Is there an advantage to doing this vs. going for the dual-illuminant approach explained in Tutorial 6?
2) In Tutorial 6, for the dual illuminant profiles, it states that one of the reference shots should be taken at 6500K. I'm not quite sure how to achieve this, since daylight and flash, to semi-constant WB sources I can easily achieve, are around 5000-5600K.
3) Should I (in LR) White-balance the Colorchecker reference shots, then convert to DNG, prior to bringing the DNG file into DNG Profile editor? Or is it preferable to WB as explained in Tutorial 1, step 3?
4) Finally, it's somewhat unclear how I bring the profiles into LR for use during the Import or Develop phases. Tutorial 1, step 9 mentions a "CameraProfiles directory" for ACR and LR, so I'm guessing I need to go digging through the Adobe folders to locate this directory and place/save my profiles there?

eswrite wrote:
1) If I use Tutorial 5, I am guessing I will have to create a profile for each lighting/WB condition, i.e., one for Tungsten, one for Fluorescent, one for sunny, one for overcast, one for flash, etc... Is that correct?
If you want a broad purpose DNG profile then yes, doing a dual illuminate profile is useful. Shoot a target under tungsten and under daylight and make the dual illuminate profile. There's no real reason you need to spawn off a bunch of other profiles for only slightly different light. The dual illuminate will handle cloudy or overcast just fine. If you also shoot with special lighting sources like fluorescent (which doesn't have a complete spectrum) or other non-standard lighting sources then do a profile for those special conditions. If you are creating a profile specifically for studio flash, you can get by doing only a single illuminate profile for the strobes...but in that case, the profile won't be as accurate if you also try to use it under tungsten–which would be the reason to do a dual illuminate profile.
As far as the D65 color temp, the closer you can get to it the better, but D55 should work fine. The key is to make sure it's evenly lit. The big difference between D65/D50/D55 is the relative amount of the blue light components-all three will be fairly close. Tungsten however has vastly less blue which can impact the sensor's spectral response–which is why the dual illuminate is suggested.
Once you do the CC shot, don't bother with tone/color corrections in ACR before converting to DNG. They won't have a material impact on the profile creation. The CC shot MUST be evenly lit and of an optimal exposure...
As far as where the profile goes, it depends on the system. Once you've created the profile, PE should default to the correct location, otherwise state your system and we can tell you where to put them.

Creative use of CC calibraton in the DNG Profile Editor

The DNG Profile Editor can be used to create profiles that mimic film looks.
I think right now it is manual trial & error process involving changes in hue, saturation and lightness, but it could be theoretically achieved with Color Checker calibration working in reversed order.
- Photograph the CC using your favorite film
- If B&W, develop in your favorite developer
- Scan the film
- Use the scan in the DNG Profile Editor as target values
The current DNG Profile Editor obviously does not allow that, it would require adding a new tab and clone the CC calibration feature and alter it to use the photographed values as target values as opposed to internal values.
I don't know if it would be worth the effort, but I thing the idea is worth of sharing.
By the way, unless I'm doing something wrong, the saturation slides don't seem to go 0%, so creation of B&W profiles is not possible.

Good idea. Yes, I've posted an example on my Flickr.
I chose a picture with good reds and yellows. There are four images in the set:
1. The original, untouched image. This is using the new Adobe Standard beta profile, brought into Lightroom with all default settings, including linear tone curve, no exposure or color adjustments, white balance "as shot", etc. For reference.
2. The image with my test profile applied, but no further adjustment.
3. My original attempt at the image, using the "old fashioned" pre-DNG-profiles raw processing method, for reference. The yellows are orangeish, which isn't that objectionable but also isn't accurate. The reds are weaker than I would like.
4. The "final" image, with my test profile plus additional tweaks -- white balance, tone curve for contrast, crushing out the blacks a bit more, etc. Two or three minutes of total processing, versus quite a bit more for the previous attempt with no "special" profile. The reds and yellows are perfect.
The Flickr set:
http://flickr.com/photos/100mph/sets/72157606547890574/
This was just a first, pretty quick attempt at playing with the DNG Profile Editor. I'm sure it can be tweaked more and even more can be accomplished.
[Edit: note: I changed the "upload date" on the test images so they wouldn't stay at the top of my Flickr page. Ignore the 2007 date, it doesn't mean anything.]

Adobe DNG profile editor bug w/ GH2 files where aspect ratio is not 4:3

Hi,
posting here as Adobe DNG subforum is essentially dead
Panasonic GH2, select aspect ratio 3:2, get .RW2 raw file, convert it to .DNG using Adobe DNG converter (6.4.0.121 beta), try to open w/ Adobe DNG profile editor (1.0.0.39 beta 2) -> error message "DNG Profile Editor could not open the selected image. Note that the selected image must be a valid DNG color image".
XRite software has no issues to process the same .DNG file (converted from the original .RW2 w/ 3:2 aspect ratio).

Eric - just make it easier for you to reproduce the bug - here is the original .RW2 file (certainly ignore the quality of colorchecker shot in terms of how the target is lit, etc - it was not to make a profile actually - it was to illustrate the bug in question) = http://www.box.net/shared/f419prmuo2 ... and I am uploading the converted .DNG file too just in case = http://www.box.net/shared/gy5o9zzi57

DNG Profile Editor won't open DNG from Panasonic LX3

I need help. I've just added a new camera (Panasonic DMC LX3) and I want to create custom camera profiles for use in Lightroom. I have done this with all my cameras before with no problems. The raw files open fine in Lightroom (2.6) and CS-4 Camera Raw (5.6.0.148). First I exported to DNG from Lightroom then tried to open the file in DNG Profile Editor. I received the following error message:
"DNG Profile Editor could not open the selected image. Note that the selected image must be a valid DNG colr image". I tried the usual closing and re-launching the application, restarting the computer, etc. all to no avail. I then downloaded the latest stand alone DNG converter (5.6) and performed a fresh conversion with that. Still no luck. The DNG's all open fine in Lightroom and CS-4. Any suggestions? These profiles have become an important part of my workflow.
Mac Pro 2X 2.8 Quad Xenon, 10GB ram, 4TB HDD, OS-X 10.5.8
and MacBook Pro 2.4GHz 4GB ram, OS-X 10.5.8
Lightroom 2.6 (64 bit)
CS-4
DNG Profile Editor 1.0.0.39 Beta 2

Yes, I used the stand alone converter as well as lightroom. I did find a solution on another post. I changed the dng compatibility in the drop down menu to "Camera Raw 4.6 and later" (it was set to " Camera Raw 5.4 and later") and it worked fine. This worked with both the stand alone DNG converter and exporting as DNG from Lightroom. It seems that the DNG profile editor hasn't been updated since the 2008 beta so It doesn't recognize the newer spec DNG. Thank you for your assistance, I was starting to panic...

DNG Profil editor is always crashing on exit

as the topic says. im using latest beta version.
i7 2600k @4.2 Ghz
240 GB Vertex 3 for catalog and preview
16 GB ram
win7 64 bit
460 GTX 1GB
ps: i hope the question fits in this forum...
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: DNG Profile Editor.exe
Anwendungsversion: 1.0.0.45
Anwendungszeitstempel: 4cb71daa
Fehlermodulname: DNG Profile Editor.exe
Fehlermodulversion: 1.0.0.45
Fehlermodulzeitstempel: 4cb71daa
Ausnahmecode: c0000005
Ausnahmeoffset: 00019b4b
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789

Take your computer to an Apple store or service technician. You may have a hardware problem. This is not normal behavior.

DNG Profile Editor step-by-step usage

I hope all will forgive the long post, trying to both verify my understanding and perhaps help others by providing more detail.
1. Shot the CC with a D300 and D200 outside with cloud cover, exposures within seconds of each other, different lenses but both Nikkor.
2. Brought both nefs into ACR, white balanced (approx. 5500K) and equalized exposure using second neutral patch, applied new Adobe standard beta profiles to each. Very good match, first time I've ever seen truly equal images from the two cameras thru ACR.
3. Created DNG's of each cc image nef with DNG Converter.
4. Used DNG Profile Editor on the D300 image (white balanced), set base profile to Adobe standard beta, selected only the Red, Green, and Blue patches on second row. No changes to three colors, created recipe with "Edit both color tables smimultaneously" checked.
5. Opened recipe file with Wordpad, very interesting to examine, easy to see what's going on since in XML format. Six color adjustment sections, three for 2850 and three for 6500. Also the entire base profile in binary form is encapsulated in the XML file.
6. Opened D200 DNG file in PE, white balanced, used old 4.4 profile as base (deliberately trying to create different colors than D300). Loaded the D300 based recipe, exported new D200 profile.
7. Now back to ACR, loaded D300 cc image with Adobe standard beta profile selected and white balanced, and D200 cc image with old 4.4 profile selected and white balanced and exposure adjusted to match D300 image. Opened both in Photoshop CS3 in ProPhoto space. As expected, there was considerable difference in the color patches, both visually and by the numbers.
8. Back again to ACR, loaded D200 cc image with recipe modified profile from step 6 and white balanced and exposure adjusted to match D300. Brought into PS and compared to D300 image. Now the Red,Green,Blue patches matched well with the D300 image, only slight differences. Actually just selecting those three patches brought all 18 cc patches into a fairly close match.
In conclusion it appears to me that a recipe has enough information, with the color table entries and the embedded base profile, to "move" the same colors in another profile to achieve a good match. And it's apparently moving "both ends" (2850K and 6500K separate sections) of the profile appropriately, although I'm less sure of this. Quite an interesting and useful development by Adobe.
Richard Southworth

I hope all will forgive the long post, trying to both verify my understanding and perhaps help others by providing more detail.
1. Shot the CC with a D300 and D200 outside with cloud cover, exposures within seconds of each other, different lenses but both Nikkor.
2. Brought both nefs into ACR, white balanced (approx. 5500K) and equalized exposure using second neutral patch, applied new Adobe standard beta profiles to each. Very good match, first time I've ever seen truly equal images from the two cameras thru ACR.
3. Created DNG's of each cc image nef with DNG Converter.
4. Used DNG Profile Editor on the D300 image (white balanced), set base profile to Adobe standard beta, selected only the Red, Green, and Blue patches on second row. No changes to three colors, created recipe with "Edit both color tables smimultaneously" checked.
5. Opened recipe file with Wordpad, very interesting to examine, easy to see what's going on since in XML format. Six color adjustment sections, three for 2850 and three for 6500. Also the entire base profile in binary form is encapsulated in the XML file.
6. Opened D200 DNG file in PE, white balanced, used old 4.4 profile as base (deliberately trying to create different colors than D300). Loaded the D300 based recipe, exported new D200 profile.
7. Now back to ACR, loaded D300 cc image with Adobe standard beta profile selected and white balanced, and D200 cc image with old 4.4 profile selected and white balanced and exposure adjusted to match D300 image. Opened both in Photoshop CS3 in ProPhoto space. As expected, there was considerable difference in the color patches, both visually and by the numbers.
8. Back again to ACR, loaded D200 cc image with recipe modified profile from step 6 and white balanced and exposure adjusted to match D300. Brought into PS and compared to D300 image. Now the Red,Green,Blue patches matched well with the D300 image, only slight differences. Actually just selecting those three patches brought all 18 cc patches into a fairly close match.
In conclusion it appears to me that a recipe has enough information, with the color table entries and the embedded base profile, to "move" the same colors in another profile to achieve a good match. And it's apparently moving "both ends" (2850K and 6500K separate sections) of the profile appropriately, although I'm less sure of this. Quite an interesting and useful development by Adobe.
Richard Southworth

DNG Profile Editor 1.0 beta 2 and real color

Similar Messages

Maybe you are looking for