Jeff Schewe wrote:
If you want to argue the relative merits of optimizing image adjustments with Thomas Knoll, you go right ahead.
I'd love to because I know a discussion with him would have logic as a common ground and he would not resort to quoting "authorities" when he runs out of arguments.
You may also acknowledge that I didn't say that the whole "image adaptive" approach is flawed. I only take issue with "0" not meaning zero and with certain behaviour being non-optional, as useful it may be in the majority of cases.
By quoting Eric Chan I demonstrated that your statements were wrong and now that you don't have to say anything anymore you appeal to authorities and claim I haven't gained any "traction". I give you that, I give up trying to achieve "traction" with you.
P.S.: FYI, I've listened to many George Jardine Adobe podcasts featuring Thomas Knoll and others, including you. What Thomas Knoll said always made sense and you may remember that he now and then disagreed with what Mark Hamburg or you said.
"It is not "my" idea of neutral. It is a technical definition."
Can you point me to that technical definition?
"The gamma encoding is not arbitrary. In the past there was a difference between Macs (1.8) and PCs (2.2) but nowadays Apple also uses 2.2."
So, you mean it used to be arbitrary, but it isn't any more?
The main purpose of gamma correction is to provide perceptually uniform encoding. It's not about providing any particular "look" to an image. And, in fact, the gamma curve is removed before display by an inverse curve (allowing for the response of the display device). Macs before Snow Leopard used a look-up table in Quick Draw with a transfer function of approximately 1.8 gamma. Now it's the same as PCs with 2.2 gamma.
"ACR could even access the current display gamma from the display profile and use it accordingly."
Now that really would be a bad idea! The gamma information from the monitor profile is correction information to overcome non-linearity in the monitor. In addition, a gamma of (typically) 2.2 is conventionally imposed - but the colour management process of mapping an image from the program's working space to monitor space is designed to deliver an overal linear gamma.
The purpose of photography (before we apply "artistic interpretation") is to produce an image that matches the original scene. Therefore the overall system gamma from camera through to to display must be linear. Otherwise the image won't look like the original scene.
CSS Simon wrote:
Can you point me to that technical definition?
I have already explained what neutral RAW development means in this thread.
CSS Simon wrote:
So, you mean it used to be arbitrary, but it isn't any more?
No. There used to be two incompatible systems and images could only be correctly encoded for either of them.
CSS Simon wrote:
The purpose of photography (before we apply "artistic interpretation") is to produce an image that matches the original scene. Therefore the overall system gamma from camera through to to display must be linear. Otherwise the image won't look like the original scene.
What you are trying to say is that the gamma encoding must match the gamma decoding value. Otherwise the non-linear encoding inbetween will result in tonal distortation.
That is why the gamma encoder (here, the RAW converter) must always use the same value as the gamma decoder (here the display). That's why I said the RAW converter could consult the display about which gamma value to use. In most cases 2.2 would be just fine to use, but some people prefer 1.8 or other values because they want to optimise for printing output or compensate for viewing conditions.
TK, we're probably talking slightly at cross purposes. The gamma curve applied to an image is a matter of coding efficiency to minimse quantisation error and noise. This doesn't realy matter in 16-bit systems, but in 8-bit systems (such as jpeg) then if you don't apply a perceptually uniform coding system (a gamma of 1.8, 2.2 or the quaint sRGB curve) then you end up with more noise. The exact gamma number you use doesn't really matter, so long as the display system removes it. In a colour-managed system, the software will remove any curve in the source image and apply the curve that the destination device is expecting, to make the overall system linear. The only time a user needs to interfere with this and specify a gamma is if the system isn't end-to-end colour managed.
I think this is the same as you are saying, forgive me if it isn't.
The tone curve used internally in a program's working space is somewhat arbitrary. For example: Lightroom uses linear mapping for most processing, but with an sRGB tone curve for displaying histograms and Adobe RGB with 2.2 gamma for the library previews. For exporting it uses whatever you say (e.g. sRGB tone curve) and for display it uses whatever the monitor profile says.
A separate issue is tone mapping for subjective or artistic reasons, and where this thread started (I think), was "is there a neutral starting point for subjective/artistic tone mapping?".
In this respect, in theory you're right and I was wrong (sorry about that), but I think not in practice!
That is, in theory, a neutral starting point is a raw iamge with any sensor non-linearity removed and no other tone curve applied (other than as part of the colour management process). This is where my knowledge of colour science as applied to image (sensor) data rapidly runs out, and a wiser man than I would shut up at this point. However, my (limited) understanding is that in practice a flat scene-rendered tone mapping (as close as possible to the tone mapping of the original scene), won't necessarily look neutral. This is where the subjective element comes in to decide "what is a neutral tone rendering?" Adobe go further and make that default mapping adaptive to optimise the two ends of the scale.
I'm not aware of any raw convertor that attempts a truly neutral scene-related tone mapping. Neither PV2010 or PV2012 do that, and I'm not sure it would be very useful as a starting point.
Jeff Schewe wrote:
TK2142 wrote:
In thread http://forums.adobe.com/message/4166542, Eric acknowledges that the above two things have "
Uh huh...did you actually read what he wrote? "Dorin, the automatic aspect has to do with the endpoint (i.e., white point & black point) handling. The shape of the curve is calculated automatically to make transitions smoother as you approach clipping (to pure white or pure black). Otherwise you'd get the traditional digital "hard clip" which can be rather rough, esp. in the shadows."
So, I ask again, do you understand what Eric is talking about? That the highlights and shadows aren't being automatically being set but the RANGE is? The "image adaptive" aspect is setting the end points for highlights and shadows? So that the range of the PV 2012 adjustments are image dependent?
Again, that's considerably different that saying highlights and shadows are being set "Automatically".
TK2142 wrote:
Please do not accuse someone of not knowing what is going on when you are not sure.
Well, I seem to be just a bit more sure of what's going on than you are...correct me if I'm wrong.
The "image adaptive" adjustments that ACR7/LR4 performs are not clear to me (and apparently others). Certainly, the technical paper on LaPlacian operators is incomprehensible to me and likely most other readers of this thread. Rather than attempting to parse Eric's statements, a bit of empirical observation can shed some light on the matter.
A Stouffer wedge is a good way to evaluate the tone curve, since each step is 0.1 OD or approximately 3 steps per f/stop. Here is the wedge exposed so that step 1 is just short of clipping in the green channel and rendered into sRGB with ACR 6.6 with a linear tone curve (sliders 0 on the main tab and point curve set to linear). The image is approximately scene referred and approximates how the wedge appeared to the eye.
Step one has an OD of 0.05, but I placed it at a pixel value of 255. Steps 8 and 9 are near mid-gray (18%). Calculated values are shown in this Excel spreadsheet. The values A, M and B correspond to the steps on a Kodak Q14 chart which represents the values in many real scenes for highlight, midtone, and shadows.
Here is the ACR 7.0 PV2010 preview with the rendered sRGB values. An exposure of -0.5 EV was necessary to allow for the BaselineOffset that PV2010 uses.
And here is the PV2012 view with default settings. The highlights are too bright and scrunched together.
And here are the settings needed with PV2012 to approximate the linear curve in PV2010. I had to invoke the point curve to place the midtones as I could not get the proper values for the mid-tones with the sliders.
And now to the subject of automatic highlight recovery. It is necessary to use a special program to reveal the true status of the raw file, and I used Rawdigger. The histograms of the normally exposed image (05) and an image overexposed by 2/3 stop (image 03) are shown. In the overexposed shot the green channels are clipped and the red and blue channels are short of clipping, enabling highlight recovery.
And finally, here is the overexposed image (03) with the default PV2012 settings. It is clear that automatic highlight recovery has been performed as step 1 is now at a pixel value of 254 (I used an exposure of -0.05 EV to show that the pixel value was likely not clipped to 255). This is OK with me, but it does mean that proper ETTR exposure is diffucult to judge with PV2012 because of the automatic recovery. I anticipate that some readers will reply that they take photos of real scenes and not stepwedges and that scene referred images appear flat.
Personally, I am quite pleased with the changes in PV2012 for processing of real world images, but one does need to learn how to best use the new tools.
TK2142 wrote:
I'd love to because I know a discussion with him would have logic as a common ground and he would not resort to quoting "authorities" when he runs out of arguments.
I've not run out of aurguments, I was simply addressing your statement "With less "we know what users want"-attitude the commonplace love/hate relationship could have been a love-only relationship." and letting you know who the "we" is...
Bill_Janes wrote:
Rather than attempting to parse Eric's statements, a bit of empirical observation can shed some light on the matter.
Great stuff, Bill, and visual proof of the mess LR4 creates in order to implement what someone else decided what "is good for me, always". It would all be fine (and perhaps I'll end up using the auto stuff for most real world images myself) if all this were optional.
There is another thread in which someone complains that LR4 auto-corrects his white product shot backgrounds for him and that he cannot blow them out with a single slider without washing out the product as well. His pain wouldn't be necessary if the auto highlight recovery were optional.
I furthermore cannot understand why there isn't a single slider anymore (was "exposure" in LR3) which allows me to negate any exposure compensation I chose as a camera setting. It seems in LR4 that one has to use a multitude of sliders to achieve that simple step.
Jeff Schewe wrote:
I've not run out of aurguments, I was simply addressing your statement "With less "we know what users want"-attitude the commonplace love/hate relationship could have been a love-only relationship." and letting you know who the "we" is...
It does not matter who the "we" is. The only thing that matters in a discussion based on logic is who is right. I could just as well claim that there are only four elements (earth, air, fire, water) because Aristotle said so.
BTW, maybe an apology is in order. Or should we adopt the notion that there is no automatic highlight recovery in LR4 because you say so, despite all the evidence to the contrary?
Mess? Let's talk about a mess.
I tried PV 2010 zeroed, and that is a massive mess. It's like the ultimate "make my image look like crap" button - horrible skin tones, nasty colors on everything. The only way that would be usable is if I also created a custom color profile designed for that tone curve. The first thing I did was use the controls to undo most of what it did.
The profiles and the tone curves are designed to work togethger to produce a "pleasing", rather than scientifically accurate image. The second is really only usable for science (spectroscopy, for example).
This is all a major tempest in a teapot in my opinion. PV2010 zeroed on the top, PV2012 defaults on the bottom.
TK2142 wrote:
BTW, maybe an apology is in order.
I would be happy to accept your apology…the upside is that after all this time (and discussion) maybe you've learned something? Heck even Micheal Frye has said "I'm not thrilled about losing a true linear point curve. But I can live with it."...
If he can, why can't you? Do you have some sort of personal agenda?
Lee Jay wrote:
Mess? Let's talk about a mess.
I tried PV 2010 zeroed, and that is a massive mess. It's like the ultimate "make my image look like crap" button - horrible skin tones, nasty colors on everything. The only way that would be usable is if I also created a custom color profile designed for that tone curve. The first thing I did was use the controls to undo most of what it did.
The profiles and the tone curves are designed to work togethger to produce a "pleasing", rather than scientifically accurate image. The second is really only usable for science (spectroscopy, for example).
This is all a major tempest in a teapot in my opinion. PV2010 zeroed on the top, PV2012 defaults on the bottom.
I don't think anyone is recommending zeroed PV2010 for fine art reproduction, but sometimes linearized output is desirable for technical analysis and specialized purposes. Of course, this "linear" output is still gamma encoded and one must remove the gamma encoding (see the link to the ICC web site for further explanation) for a scene referred image. ACR/LR is intended more for visual editing of images than for technical analysis and more specialized tools such as DCRaw or Iris can be used when needed.
If we had true high dynamic range displays, a scene referred image would look fine since it would reproduce the actual scene. However, for prints one must tone map the image so that a high dynamic range appears pleasing with a low dynamic range print. This is ably described by Karl Lang in his white paper on the Adobe web site (second link below). A simple S curve is a relatively crude method for tone mapping that is applied globally. Localized adaption is used for rendering of HDR images, but the results can appear unnatural if overdone.
While many photographers (myself included) are leery of automatic corrections, if PV2012 can give me better images with less work, I am all for it. I would be more interested in learning about the image specefic adaptions that ACR/LR performs. Of course, one can currently revert to PV2010 if he doesn't like PV2012, but that option may not be available in the future.
Just to be perfectly clear, when ACR/LR designates a Process Version, it means it will stay in place for the future (assuming Adobe stays in business). That's the whole reason for that line in the sand...
With regards to PV 2012: Eric said: There are two separate ways in which PV 2012 is retrieving more highlight detail compared to PV 2010.
One is the improved highlight rendering logic, when one or two channels are clipped. This is the "auto" part which happens even at default settings (e.g., Exposure 0, Highlights 0, etc.). Previously in PV 2003/2010, the clipped channels would simply get clipped, so tones would be lost and colors could be shifted (e.g., skies would turn from blue to cyan). You could get PV 2003/2010 to try to repair the partially clipped colors by using minus Exposure and/or Recovery. In PV 2012, the new logic helps to preserve tonal distinctions and prevent color shifts, and this happens even without the user touching any controls.
The second way is the image-adaptive logic and new algorithms behind the controls (e.g., the tech driving the Highlights slider). This part isn't automatic, because it only kicks in once the user starts adjusting things (e.g., setting Highlights to a non-zero value).
I tended to fixate on the second explanation vs. the first...if I have incorrectly described the wan PV 2012 is working, I'm sorry...(so I guess that counts as an apology, right?)
Interesting.... Has anyone who shoots panoramas, where you spend a fair amount of effort keeping exposure constant between shots had any difficulty blending panos where PV 2012 attempts to optimize differently for each image? I guess I could download the trial and find out for myself...
My playing with the beta found that the optimization of white and black points worked really well for most images with the biggest exception being those where I wanted to blow out the background deliberately. And as I shoot on white virtually never these days, it's not a big drama-I suspect tweaking the lighting to ensure more thorough blow out of the background would fix this anyway.
That's a very good question! I'll experiment when I get a chance.
My guess would be this: the auto adjustments that happen even before you touch a slider are to protect clipped highlights (and I thought blacks, though Jeff doesn't mention that above). So they would not affect exposure and contrast of the image except right at the top (and maybe bottom) and then only to repair "damaged" parts. Hence it would not cause problems with panoramas.
Jeff Schewe wrote:
With regards to PV 2012: Eric said: ...
Thanks for sharing Eric's response. Was that from private communication or did he post that somewhere?
P.S.: I don't have an agenda. I'm just passionate about LR because it is so good in many ways. As much as PhotoDirector3, AfterShotPro, Aperture, etc. are better in some ways, LR (3.6) currently is still my first choice. Hence I want LR to be the best I can imagine.
Michael Frye's second video on the PV 2012 controls is out.
(Partial) Summary:
The video contains some further images which demonstrate the above points. To me all this reinforces that it was a baid idea to choose "0" to mean an arbitrary Adobe default whose built-in contrast and brightness boosts are not suited for certain images.
If you can learn something from the video, great!
If you still disagree with me, you don't have to tell me again. ![]()
TK2142 wrote:
If you still disagree with me, you don't have to tell me again.
The only point I would still argue is that there's a reason Eric said what he said...if you don't first set the overall tone in Exposure then you're working on an image whose overall tone is wrong. Exposure and Contrast first does set up Highlights and Shadows nicely making Whites and Blacks being relegated to fine tuning (or jumping to Curves).
Note, I don't think Curves use (point or parametric) has been eliminated, but I think the need to go to curves has been reduced...
Hi TK,
I don't have much of an opinion about the '0' points.
But have you created the lowered contrast DNG profile yet?
That's a good solution for the "linear" tone curve being contrastier in PV2012.
In fact, it's a good solution for anytime you want a different tonal starting point, since that way you don't have to start with a bunch of points already on the curve.
But note: the tone curve in the profile does not provide the input to the basic sliders - they operate on the raw data the same way regardless of the tone curve in the profile. It's more like it sits between the basic sliders and the tone curve control in Lightroom, so to speak (or maybe "under" the Lightroom tone curve...). Anyway, one can not use a DNG profile to alter the behavior of the basic sliders, only to get a head start on tonal adjustment via the Lightroom curves, or obviate the need for it...
Regarding blacks & whites:
----------------------------------
- Not always a good idea to do them first, but not always a good idea to leave them till last either. The sliders in PV2012 are like a team - I rarely adjust one without adjusting one or more (or all) the others too, up until the last adjustment I mean
. Like all other PV2012 sliders, blacks & whites sometimes only need small tweaks (or none), but sometimes they need big ones. They are really not the same as setting black/white point as in days of old...
The original conception and intent may have been for fine-tuning, but that does not always pan out in practice, - not for me.
PV2012 rocks!
(except when it doesn't
).
Cheers,
Rob
Jeff Schewe wrote:
TK2142 wrote:
If you still disagree with me, you don't have to tell me again.
The only point I would still argue is that there's a reason Eric said what he said...if you don't first set the overall tone in Exposure then you're working on an image whose overall tone is wrong. Exposure and Contrast first does set up Highlights and Shadows nicely making Whites and Blacks being relegated to fine tuning (or jumping to Curves).
Note, I don't think Curves use (point or parametric) has been eliminated, but I think the need to go to curves has been reduced...
I agree that it makes sense get exposure right before proceeding to other corrections, but the behavior of exposure is different in PV2012 from PV2010. In PV2012 the black and white points are automatically set (within limits), and my current understanding is that one would use exposure to set the midtones. In PV2012, the exposure slider targets the midtones as shown on the LR histogram, but it is essentially a linear operator if recovery is not being performed and it also affects the highlilghts. One could then direct attention to the highlights to extract maximum tonality.
In your previous LuLa ACR tutorial Thomas Knoll reported that when editing images (that would be with PV2010), he first sets the white point with exposure. The midtones might then need a correction with brightness. He stated that an alternate method would be to set the midtones with exposure, and then the white point with recovery. This alternate method appears to be needed in PV2012 since there is no brightness slider. The highlight slider does affect the midtones to some extent, but it operates mainly in the highlight region as its name indicates. Your comments would be welcome.
Bill_Janes wrote:
In your previous LuLa ACR tutorial Thomas Knoll reported that when editing images (that would be with PV2010), he first sets the white point with exposure. The midtones might then need a correction with brightness.
I understand the "Exposure" slider in PV 2012 is more akin to PV 2010 "brightness" than PV 2010 "exposure". Hence the equivalent of the above suggested approach in PV 2012 is to first set the white point with "Whites" and then use "Exposure".
If white point is off, I don't quite see the point of using PV 2012 "Exposure" to move it slightly but mainly increase brightness with a resulting loss in contrast in the highlights.
Y'all need to be careful about applying legacy thinking to PV2012.
e.g. Highlights slider sometimes pulls the white point down more than the whites slider, and sometimes not.
PV2012 is not a deterministic thing that you can apply formulaic editing procedures to.
Best to be loose and use the sliders as they work best on the image you are editing...
That's been my experience anyway. Otherwise you'll find you have a fight on your hands when you edit images where the previous "formula" doesn't work so well...
Neither whites nor exposure sets the white-point... - they work with highlights as a team to set the upper end toning...
exposure & contrast & highlights & whites mostly determine upper end toning
exposure & contrast & shadows & blacks mostly determine bottom end toning
exposure & contrast mostly determine midtoning.
Note the common ingredients - exposure and contrast are critical to midtoning, upper and bottom end toning, thus they must be right on the money to get proper tone in all three regions.
Of exposure & contrast, exposure is the most critical to proper tone levels, since contrast does not alter midtone level, but exposure does.
Whether you set exposure first, or whites, or both together - be sure to revisit both before you're done...
Note: In PV2010 I used a "debrightened" version of Adobe Standard as default (created with DNG Profile Editor) - aimed at preserving highlight detail as much as possible.
In PV2012, I usually use +whites -exposure.
I think Adobe likes midtones to be brighter than me (and brighter than Nikon & Canon like them, judging from the difference in Adobe Standard versus the camera matching profiles).
+whites -exposure in PV2012 has some of the same effect as the debrightening tone curve in the DNG profile - drops midtone level and enhances highlights.
Rob
Lee Jay,
I'm trying to share my experience of what works best for me, in case it might help somebody find what works best for them.
Rather than taking one thing out of context and claiming that it's wrong, why don't you share what works best for you too?
What I meant by that comment (in previous post) is: In my experience, due to the way PV2012 adapts the slider behavior for each image, and re-adapts the slider behavior again when I change exposure... that it pays to be flexible and not assume... Although PV2012 is totally deterministic to Eric Chan, for some of us, a successful procedure for editing one image does not always make for a successful formula to edit the next image...
PS - Your edge/extreme cases may be other people's every-day shots...
Rob
I have.
Defaults are Adobe Standard, Clarity +10, Vibrance +5, Sharpening 40, Masking 40, L-NR 40, Detail 80, C-NR 25.
Set WB.
If the image needs fill, use my fill-light presets.
Adjust exposure, then fiddle with +shadows and -highlights until things are about right. If the exposure was set correctly, the two numbers will be the same but opposite in sign. If they aren't, adjust exposure.
Use locals if necessary. Done.
In difficult cases, use whites, blacks, and maybe tone curve.
Rob Cole wrote:
Best to be loose and use the sliders as they work best on the image you are editing...
Isn't that called "fiddling"?
I prefer controls that achieve predictable results, independently of image content. I prefer adjustments to be based on simple low level data manipulation, like a true exposure slider that simply undoes a camera exposure compensation (without trying to help me with built-in highlight and shadow shoulders).
I'm fine with advanced adjustment operators, e.g., those that build masks but they should be predictable in their effect and allow intuitive control rather than forcing one to go back and forth and back and fourth between four to five sliders, always guided by visual feedback rather than knowing what should happen.
Yeah, I could stay with PV 2010 but what about the other extras (e.g., regarding the adjustment brush) that only come with PV 2012? Too bad that Adobe does not allow a "Picasa" style basic control panel (the current PV 2012) and "technical" basic control panel as alternatives (both using the same PV but catering to different audiences).
P.S.: I have just read that LR 4.1 RC2 has added new "Defringe controls". Isn't that a violation of the "UI freeze" policy?
Lee Jay wrote:
Adjust exposure, then fiddle with +shadows and -highlights until things are about right. If the exposure was set correctly, the two numbers will be the same but opposite in sign. If they aren't, adjust exposure.
Interesting that you should use the term "fiddle". ![]()
In any event, you do not seem to have images that require more sophisticated adjustments. If your approach worked for everything then Adobe should have provided just one "shadows/highligts" slider to be adjusted in conjunction with "exposure". It does not make sense to allow different values for "shadows" and "highlights" when the best setting always requires them to have the same value anyhow.
TK2142 wrote:
Lee Jay wrote:
Adjust exposure, then fiddle with +shadows and -highlights until things are about right. If the exposure was set correctly, the two numbers will be the same but opposite in sign. If they aren't, adjust exposure.
Interesting that you should use the term "fiddle".
In any event, you do not seem to have images that require more sophisticated adjustments. If your approach worked for everything then Adobe should have provided just one "shadows/highligts" slider to be adjusted in conjunction with "exposure". It does not make sense to allow different values for "shadows" and "highlights" when the best setting always requires them to have the same value anyhow.
I do, but they are rare. A good 90+% of my images can be satisfactorily adjusted using this basic approach. Every once in a while I have a pathological case that needs more fiddling.
I'm not going for "effect", I'm going for "realistic". PS is the effects tool.
PV2012 allows one to tone most photos nicely, from end to end, without using the tone curve, using only 6 sliders. That would have been very hard to do without the image adaptive behavior. I'm not disagreeing with you, merely reminding why PV2012 is how it is (slider count and names were dictated from above, but how they behaved was left to developer).
PS - PV2012 requires a lot less fiddling if:
* You don't use blacks & whites sliders much
* Your toning tastes are aligned with what PV2012 does without blacks & whites sliders.
* You are willing to sacrifice midtone contrast to fill shadows and have highlight detail.
blacks & whites are critical to almost every photo, for me.
I often have -highlights with same value as +shadows, but the flexibility to have them different is critical, especially for shots where abnormal exposure will be set, since it's a primary determiner of the partition of effect between shadows and highlights sliders, and also one may simpy want midtone level to be proportionally lower or higher for some photos..., or highlights, or shadows...
As the avid forumers already know, I'm a huge fan of PV2012 - not because of how straight-forward it is, but because of the results I've been able to get *after* paying my dues...
Rob
Seán McCormack wrote:
X.1 versions have had feature additions before. It's X.2 and beyond that are camera/lens profile additions and bug fix versions.
Thanks for clarifying, Seán.
Jeff Schewe mentioned a good while earlier that all discussions that would imply UI changes would be moot because of UI freeze (e.g., for book authors).
TK2142 wrote:
Jeff Schewe mentioned a good while earlier that all discussions that would imply UI changes would be moot because of UI freeze (e.g., for book authors).
That related to the public beta of 4.0 relative to the GM retail release of 4.0. As long as Adobe can ship new features or functionality within the quater that the app shipped,new features can be added. But that is not true between the public beta and the .0 releases...
North America
Europe, Middle East and Africa
Asia Pacific