This content has been marked as final. Show 677 replies
> tsk. tsk. sarcasm begets sarcasm. :-)
Sarcasm. Sarcasm? Every word was deeply infused with the sincerest of warm and fuzzy heart-feelings! I mean, I even thought for a moment there about proposing a group hug! Mega-kudos to you, by the way, for having the patience and stamina to read through all that. :)
My 2 US cents (1.6 Eurocents?) ..
1. For the cancel warning, use the image counter and show dialog only if > one (or insert favorite warning threshold) images are being cancelled.
2. A way to quickly display the non-processed histogram of the raw file "As Shot". Is this the same as displaying with every slider set to 0, the curve to linear and the WB set to "As Shot" (I'm still confused why it doesn't display the original camera-selected WB setting for reference :-)?
3. A way to display individual channel histograms (checkmarks next to each R-G-B reading above the graph?). My simple brain gets overwhelmed by the integrated display after a while when detailed analysis is required.
4. Adding an EXIF user comment to the actual RAW file, to multiple selected files. This could also be applicable to the Bridge app. I use this to add lens information for non-Canon lenses to my Canon body, which is most of the time. I currently use Canon's Zoom Browser app to do this but it's a very tedious part of the workflow.
5. Moveable toolbox - it would be nice to at least be able to position it next to the preview checkmarks. I use 1792x1344 on each monitor and constantly moving the mouse from one end to the other gets tiring :-).
6. Center the display on the pointer when using the mouse menu to switch magnification.
7. A way to quickly save and recall multiple settings for the current image. One example would add a section between the histogram and the settings. It has (left-to-right) a recall button, a dropdown with "---", "One", Two", etc., an increment button (increments the dropdown to the next saved), a decrement button, and a save button. Buttons are individually disabled when not applicable.
Don't you just love it when people come up with ludicrous "Great Ideas" for somebody else to work on :-)? Cheers!
I'd like to support the concept of pushing ACR towards being a complete image processing solution for photographers. I'm not talking about a saving money thing (I don't mind if it comes bundled with PS), I'm thinking about workflow and archiving. It would be a king-hit IMO. I really like the idea of staying in the linear data format as long as possible. To that end I would like to add to the above list:
1. Being able to simply store multiple processing runs with different processing values for individual images. To a large extent I already do this by manipulating xmp sidecars, having multiple sidecars per image, but building it in would probably be even better (for me keeping things as xmp data rather than saving the 5x larger tiff is enormously attractive).
2. Now something of a leap, what about linear layer masks to attach to raw images. This might seem mad but a linear mask of an image in most cases is closely equivalent to the image itself, it might be possible to store the mask as a series of standard commands also in the xmp sidecar (find edges, Gaussian blur X, saturation -100, contrast +80). So, in line with 1, from a data retrieval perspective, the mask becomes just another set of processing run data with just a few more instructions built in.
Put these two together and you could have the equivalent to a 300 Mb multilayer tiff stored as a 10Mb raw file with one or more 4 Kb sidecars. To push the point, this is not just archiving, it is workflow and file organisation.
3. Another step further would be to encourage / help plug-in makers to develop plugins at the linear / ACR level - I am particularly thinking of noise reduction and sharpening.
LOL, just a few ideas
Thomas, I would also like to see the camera model displayed there too. I shoot with three different camera models and have different calibration sets for all of them so that I can get the same 'look and feel' across the 3 different cameras. If I haven't checked which camera the image was taken on before opening the image in ACR, I have to close ACR go and check which camera was used and then open it up again.
Carol, <br /> <br />Hmm camera make and model is displayed on the very left in the ACR title bar. <br /> <br /> <a href="http://www.pixentral.com/show.php?picture=1AYnuEgBu6CsZFDepsdBPG0g5a1df30" /></a> <img alt="Picture hosted by Pixentral - http://pixentral.com" src="http://www.pixentral.com/hosted/1AYnuEgBu6CsZFDepsdBPG0g5a1df30_thumb.jpg" border="0" />
Your eyes are fine! Peripheral vision can play weird games with our brains.
I'm in the same boat using three camera bodies. When I saw your post my first reaction was: "exactly". Then. wait a minute, somehow I seem to know which camera I'm dealing with, I swear I've seen this displayed somewhere there.
But I had to go back and double check what was subconsciously in my field of view.
Missing the obvious is not that uncommon. where did I put my eyeglasses? I can't see them. ;)
Currently we have Camera vendor/make/model + image name and then (in brackets) the ISO, Shutter Speed, as shot Aperture, Lens with as shot focal length. Given that all of these are useful in determining which (if any) personalised settings for Noise CA correction, Vignetting and Calibration should be chosen then "I" think we're well covered.
I would like to save more than one custom settings for the Crop tool. Also,
once in the Custom pop-up dialog, to swap Width and Height.
An option to clear Straighten tool settings by clicking on its icon, not the
Crop tool icon.
Sticky tools or an option to select the default tool (my pref is for the
White Balance tool).
Precise cursors, instead of the current Normal.
A button or a shortcut to zero a slider. For example, Shift-clicking slider
sets value to zero.
One of the reasons I still prefer Nikon Capture to ACR is ACR calibration. I've used Bruce Fraser's book and the Fors script and neither produces as accurate a representation as Capture. I would like to see a calibration script or feature built into ACR that is a collaborative effort of Fraser, Fors and Knoll, that guides the user through calibration and the use of the Calibration tab.
ACR for dummies
I like to do shooting in RAW because it gives me maximum flexibility after the shot is done. BUT I am not able to get the same picture as if I use JPG and let the camera do the processing. The colors are washed out, the sharpening is not as good etc. After what I have read I am not the only one...
The solution: In addition to the ACR automatic settings, there should be another one making the picture look exactly like the JPG from the camera the picture comes from. I have a Canon 350D , I would like to have the Canon option and make my changes from that.
Add on 1: I would add the user interface from the camera regarding processing of the picture. On my 350D I have the different parameter sets controlling Contrast, Sharpness, Saturation and Color tone. I would like to control these from inside ACR and get the exact same results as with the DIGIC II processor on the camera.
Add on 2: I would like a new button: P&S style (Point & Shoot style) which makes heavier use of sharpening and colouring so I with SLRs easy can get the same picture look (but with better quality) as I am used to from my P&S camera.
I believe that if this was implemented in ACR 4 a lot more people would start using RAW; now it is to much hassle if you are not really into it. I am trying to learn using RAW myself now, and so far my pictures have not become better, but I like the extra control and I like the concept of archiving everything that was captured by the sensor.
Thanks in advance!
>In addition to the ACR automatic settings, there should be another one making the picture look exactly like the JPG from the camera the picture comes from.
You can play with the controls and then save the settings just the way you like them. To emulate Canon's in camera raw-to-JPEG conversion, just play with the sliders to generate an over-sharpened, over-contrasty, over-saturated image, and compress the low end of the curve in order to hide the noise in that range. That's what Canon does with its JPEGs. You can save them with whatever name appeals to you, including "Default".
One of the "curves" I have saved I just named "Let_it_be", because it essentially leaves everything flat. If I don't like ACR's interpretation of a RAW file, I just apply that "Let_it_be" settings and go from there.
Alternatively, if you like the Canon JPEG look, you could just shoot JPEGs and save a chunk of money in CF cards and storage space. :)
It is not ACR's goal to emulate either your in-camera JPEGs nor the conversions performed by your camera maker's software.
>On my 350D I have the different parameter sets controlling Contrast, Sharpness, Saturation
All those settings you adjust in your camera are irrelevant when you shoot RAW. They only apply to TIFFs and JPEGs.
No comment. The answer is implicit in the above.
> It is not ACR's goal to emulate either your in-camera JPEGs nor the conversions performed by your camera maker's software.
I shoot RAW because I like the extra control it affords me and the streamlined workflow in ACR. But, that does not mean that having the ability to emulate in-camera settings (curves, saturation, white balance, etc...) when I want it would not be a useful addition to my workflow.
I'm tired of people saying that ACR shouldn't do this. It should. It shouldn't be required for someone to use it, but it should be an option because it would help many people be more productive (such as gunder who requested this). As proof that this is not a black and white issue, people definitely find it useful that ACR attempts to support the in-camera white balance and, in fact, when that gets broken like it was with the Nikon D2X due to white balance encryption, people realize that it hurts their workflow not to have that option. I'd like similar options for in-camera curves, sharpness, contrast, saturation and other relevant settings that go into producing an in-camera JPEG. I'm not looking for an exact replica of the in-camera JPEG. That would be an impossible task since only the camera maker knows how the settings are really applied, but that doens't mean that trying to apply the other settings wouldn't be useful. In my opinion, it would.
It may be hard for Adobe. It may be a lot of work. Adobe may choose not to do it for whatever reason they have, but that doesn't mean it isn't a valid feature request. It would be useful to many and thus it is a valid feature request. For all those who don't want it, that's fine. You can campaign that Adobe spend it's time on other things. For those that think this would be useful and helpful, we can campaign for Adobe to spend some time on it. But, I'm a bit tired of reading that it's not a valid feature request. It is.
I never suggested ACR should do it by default. And, I have no idea why you like to produce such non-useful postings. I'm surprised Adobe lets you post here on their behalf. It's as if you are just angry at anyone who has a different point of view than you do.
As an example, some of the tone curve settings in my camera (including some of the automatic tone curve settings) can be very useful in some shooting settings (not all, but some). As it is, ACR makes me throw away that camera functionality and set it manually. I'd like ACR to have an option to pick that info up from the camera as a starting point if I so choose. ACR's default settings cannot emulate this camera functionality. I wouldn't use that in-camera functionality always, but I would use it sometimes.
>The functionality is there. All you have to do is learn how to use it.
Where would I find functionality in ACR that would apply in-camera settings for tone curves, saturation, sharpness, etc...?
In case I wasn't clear, I'm talking about the ability to make camera setting changes in the field during a shoot and have those changes be automatically applied as the initial image presentation in ACR before I make further adjustments.
> I kind of doubt that's going to happen.
That may be true and it's up to Adobe to decide that. Adobe has chosen to go the route of supporting some in-camera settings (like white balance). I'm merely pointing out (and agreeing with the original poster on this topic) that there would be some utility in transferring some of the other camera settings.
And, clearly Adobe is trying to turn the shoe onto the other foot by trying to get camera manufacturers to adopt DNG which would make supporting in-camera settings easier, less costly and probably more reliable.
The reason I stepped into this thread was because I was tired of seeing people get stepped on for asking for something that would be useful, just because it was hard or not likely to happen or not something that someone else wants. That's not how feature request threads should work. People should attempt to understand what it is that is being requested and why it's being requested and then allow it to be considered for prioritization along with all the other things being requested rather than just dismissing it.
I'll try to be constructive and point out what I perceived as a stomping, but it's probably best if we say our piece and move on to other topics so I'll probably go quiet on this topic after this and the excellent moderator we have here will probably clean some of the chatter up at some point.
First, Ramon's posting to Gunder said that he could set ACR itself to produce:
> over-sharpened, over-contrasty, over-saturated image, and compress the low end of the curve in order to hide the noise in that range
if he wanted to. That seemed like a slam and I took as an implication that he must be an idiot for wanting that in the first place. I decided to jump to his defense since I thought there was a real point to his request that wasn't getting listened to and/or understood.
Then the following line in a response to my initial message:
> But ACR can already emulate the over contrasty, over saturated, black levels stomped to the ground look that the in-camera JPEG processing gives you.
>But it's your choice if you want to do that much damage to your picture.
is the one that really felt like a stomping. I read it as, "if you're as dumb as you sound like you are by asking for this, go ahead and ruin your pictures".
I didn't see any attempt to understand why the poster thought the request might be useful and, in fact, both postings were just trying to convince us we were dumb for even asking.
Here's how I would have liked to have seen a response to Gunder's posting.
First of all Gunder, welcome to the forum and I'm glad you are trying out Adobe Camera RAW.
In the current state of things in ACR, you will probably have to do significant tweaking in ACR if you want to generate the same kind of pictures that Canon does with their JPEGs and you may need to learn quite a bit about ACR before you can really do that as well. Some of that tweaking, you could set as the default in ACR and some of it will have to be tweaked on each individual photo or at least on groups of photos. To date, the focus of development in ACR has been more about giving you control over these settings and making for an efficient workflow in setting them than it has been about automatically producing in-camera-like JPEGs.
I'd suggest one of the excellent books about ACR like Bruce Fraser's book "Real World Camera RAW with Adobe Photoshop CS2". It's an excellent book and after reading it you will really start to understand how the different ACR controls work, what they do and how they interact with each other. You may even be able to change the defaults in ACR to produce images closer to what you want without so much individual tweaking.
You may also want to experiment with shooting RAW+JPEG in your camera (setting your camera so it produces both if it supports that). That way you could selectively pick a few RAW images to play with while still using the JPEGs for many others. That's one way that some people get started with RAW.
Now, about your original feature request. I agree with you. A bunch more users would be able to use ACR if it was able to start out with a default "new user mode" that produced images similar to the in-camera JPEGs. I would have loved that myself when I first started. Adobe appears to be trying to move in that direction by both supporting white balance as an in-camera setting that works in ACR and by promoting the DNG RAW file format that, if camera makers would support it for a RAW format, would make it more practical for many more in-camera settings to be supported by ACR. Until either that happens or specific manufacturers agree to document more of their formats and algortithms, it will be difficult for Adobe to support many more in-camera settings. It would be useful and I hope it happens someday, but it doesn't look imminent to any of us onlookers because of the implementation complexity.
I hope that you are able to get successfully started with ACR because once you really learn how to take best advantage of the controls that it has, you can produce remarkable images. RAW will probably always require more learning and may always be a little more work, but should give you more of an ability to optimize your images as a reward for that extra work. I, myself, process a few hundred RAW photos a week on average and some weekend events I end up with 600-800 RAW photos. I now find it more efficient to process my photos as RAW than as JPEG because the workflow tools in ACR and the ability to make mass corrections/changes is so much easier in ACR than it is in the CS2 editor itself. But, it took me awhile to get that proficient. I started by hand tweaking each one in Elements, reading books on how to do it better and hanging out in various online forums with folks who were a lot more skilled than I.
Good luck getting started Gunder, and if you have any more questions about ACR, please don't hesitate to ask in the right forum here - that's what the forums are here for.
I sometimes detect a "closing of ranks" when someone requests something a bit out of the ordinary. It is as though the aim is to discourage the request instead of examining it to see if it has merit.
I suspect that if we look at the features in the current Photoshop, we would find that some of them were discouraged initially, and only much later were they properly examined and became mainstream.
In April 2002, in the newsgroup comp.graphics.apps.photoshop, there was a thread "Photoshop 7 has been released upon the planet!"
I said there that the lack of better 16-bit handling, including adjustment layers in 16-bit mode, probably meant that I wouldn't take PS 7. The response was overwhelmingly to try to convince me that the idea had no merit, no one wanted it, it was pointless without 16-bit output devices, etc.
Chris Cox said (24 April 2002): "our marketing department didn't think it was that big an issue (and so far, most of the users who have given us details on why they think they need the additional support have discovered that they didn't really need it)" and "So far, the highest end professionals haven't given us a good reason other than "making 16 bit workflow more consistent"", and "If 16 bit/channel OUTPUT devices existed - that would be a good reason".
I think it was simply an idea whose time had not yet come. When its time came, it became a "must have", and even Paint Shop Pro X has 16-bit support as far as I know.
Behind some of these feature requests is next year's "must have" struggling to get out. Perhaps badly expressed, perhaps expressed as a design rather than a requirement. I stopped tracking Photoshop releases in 2002, and unsubscribed to that newsgroup, because I felt that Adobe and those users were going in a different direction from where I wanted to go. It was only when I bought a digital camera that I decided that it was worth having another look at Photoshop, and upgraded to CS because it had what I wanted.
> I sometimes detect a "closing of ranks" when someone requests something a bit out of the ordinary.
only sometimes? :-)
that's an honest observation, but imho fair sport. a "little bit" of peer pressure helps people strengthen their ideas before formulating their thesis. outside of an insulated think-tank, brain storming session, or design process -- if one isn't comfortable enough to defend their proposition it rapidly falls back down to the bottom of the pickle barrel. we live in a world of competing priorities and only the most resilient of ideas put forth stand the scrutiny of time.
eye believe it twas back in sociology 101, where one of my profs use to drill her own observations into us:
1. "new ideas" which conflict with the norm are at first ridiculed.
2. if adopted by a critical mass of peers-- "they" become skeptically acknowledged.
3. finally, "they" become so commonplace that the same people which had at first ridiculed them now claim they were obvious to begin with.
it reminds me of the JPEG vs. RAW debates that went around the web. it was less than a couple of years back-- yet today no one would think to argue that JPEGs provide the same quality of output as RAW files.
>Here's how I would have liked to have seen a response to Gunder's posting.
hmmm ... by way of having access to some of the kernal folk--the nuclei at Adobe--it's my impression people default to believing these are "customer service" oriented forums rather than "user to user" forums.
eye actually prefer the "organic feel" of these discussions where people need to make their case by merit, rather than be encouraged by way of some welcome wagon. don't get me wrong, i also understand why your view may vary.
except for when Ian comes around with his big club-- these forums are pretty much self moderating and don't need a lot of rules. this "freespeak" rubs a lot of people the wrong way--but it also breeds some of the most creative discusions between peer groups. you will not find another ecosystem near as rich in "color management information" from as diverse an array of users--ANYWHERE. aside from photographers (novices and pros) there are graphic designers, software developers, creative directors, color theorists, production managers and print people --we're all here under one umbrella.
it's simply amazing! sometimes it's simply amusing!
we are too different to be alike. it's my feeling if we started structuring a facade which these moody, grumpy, innovative, short tempered and brilliantly creative people needed to conform to-- we'd lose a lot of the diverse talent in this ecosystem at the benefit of some very minor encouragement.
to paraphrase joni: "we'd pave paradise and put up a parking lot". :-)
nunatak, you say: "but imho fair sport. a "little bit" of peer pressure helps people strengthen their ideas before formulating their thesis".
I think there are two danger signs to look out for:
1. Is a critic trying to close down the discussion before it has even been opened up? Any significant idea is likely to need more than just one post to make it understandable. Sometimes it needs a joint effort to refine a thesis before it can be scrutinised properly.
2. More important, is the critic criticising the original statement, or a paraphrase of it? I am very familiar with people taking statements that I have carefully prepared, transforming them into something different, then attacking the latter. I tend nowadays to assume that if someone has to paraphrase a proposal in order to attack it, it is because the original proposal is hard to criticise.
(A refinement of that "sociology 101": at stage 3 the original critics claim the idea as their own! This is typical of politicians).
As Chris correctly points out, what jfriend00 is asking for is really a request aimed at camera manufacturers to provide their own proprietary algorithms and write the camera settings to the memory card, sort of in a sidecar file, so that those settings can be applied during the raw conversion.
One would assume that such a workflow is implied in the camera manufacturer's raw conversion software.
As such, I see no reason for a user who desires those results either not to shoot JPEGs in the first place or not to use the camera manufacturer's raw conversion software.
Whether jfriend00 wants to characterize the desire to have images that are over-sharpened, over-contrasty, over-saturated and compressed in the low end of the curve in order to hide the noise in that range or not as idiocy is entirely up to jfriend00 to decide. I made no such inference.
Incidentally, the reason I did not address you directly in my last post is that, quite honestly, I did not read your very long post in its entirety and was, therefore, forced to skip all of your subsequent posts. For that I must ask for your indulgence, as my poor health forces me to limit my efforts.
> I would love to see a "Relative" option for settings. If the "Relative" option is selected, when activated the settings would be added to the current image settings, rather than replacing them.
Can you describe more what you are looking for?
You can achieve the "relative" effect already by using adjustment layers. If you just make a new curve/levels/hue-sat/etc... adjustment layer, you get a relative effect with the new layer.
The whole idea is to have quick sets of related setting jumps to try different styles or slants in ACR. You could for example have a setting that increases saturation while reducing contrast and brightness, or viceversa, and quickly see the difference in the image.
Layers are a more formal and indeed finer instrument for the final image once you get into Photoshop. The ACR quick-tries are to get you in the ball park during the early development stage.
The ability to quickly save and recall settings and subsets is a real powerful tool within ACR. This would extend that, and is not a replacement for real work in PS with layers, as you suggest. That is indeed how I do my final image adjustments, and I always save with layers as a PSD.
First of all. Thank You Adobe (Thomas) for making ACR.
I use PhaseOne DigitalBacks and have C1PRO installed and I do not use C1 for my DSLR conversions since I find that ACR works better and are wonderfully integrated with PS and Bridge. But C1 have one feature that I miss in ACR. Custom camera profile support. If PhaseOne decides to have their backs deliver DNG files straight out of "camera", I could see myself using ACR instead of C1.
I would like to have the possibility to turn of ACRs profiles, to be able to generate my own in GMB ProfileMaker5, and then use that profile instead of ACRs.
Would that be possible in the future ?
Jörgen Nilsson, Portrait photographer.
> Echoing an earlier posting, I'd like to suggest a tool to assist straightening operations, either a grid or a drag-out ruler which would align to the crop window (not the overall image window).
Does the straighten tool that's already in CS2/ACR not work for you? I find that tool very, very useful and fast. If you have no crop already selected, it will make a rotated crop that makes the line you drag out straight. If you already have a crop, it will rotate the crop to straighten the line you drag out.