|
What's your favorite image editing feature? Link: 02/12/2006 01:12 PM 18
comments
I've got a quick question for 'yall: what's your favorite image editing feature? Doesn't matter which app (Photoshop, Painter (woo!), MS Paint, MacDraw, etc..) just what it is and why. If you have more than one let me know that as well! (Layer support and filters don't count, because that's sorta like 'duh' :) |
links:
search
people
kirstin
andy brent buzz byron chris daniel dave ejalbert jeff b jeff j joe jonathan luis mike m mike p rogue amoebas rogue sheep |
|
Copyright © 2001-2006 August Mueller
|
For some reason, Photoshop has this feature and Illustrator doesn't. Rubber-band is a feature of the pen tool that shows you what the path will look like after you click to set the anchor point, before you click to set the anchor point. This live preview is sorely missing from Illustrator, even though there's no reason not to have it. (Do they think it's too CPU-intensive or something? Ask the Photoshop team!)
Lineform has this feature, as well it should. Once you've tasted rubber-band, there is no doing without it.
The other feature I would suggest is Core Image, with a twist: Add the ability to apply a Core Image filter within a selection or path. It'd be work (you'd have to rasterize that area of the image, then apply filter, and of course it'd be for display only in a special Core Image type of layer), but it'd be yummy. I'd use this for blurring out sections of screenshots (e.g. people's email addresses or IM handles).
Non-destructive editing is a very good general goal. You could probably think of even more cool features if you headed in that direction.
I did, however, fall deeply in love with MacDraw and still mourn its loss. I switched late to Adobe Illustrator, but have since stopped doing so much technical style drawing (used to be for games and the like). I don't mix much vector and pixel style so much - pixel is messing with images, vector is technical drawing. I'm pretty plain that way I guess.
I was born to crop.
Cropping with feedback on the exact image size is very handy.
As is Photoshops canvas dimensions dialog that allows you to shift the image based on how you resize the canvas.
Simple but very handy functionality.
That gave me another idea: Customizable origin. At the very least, top-left or bottom-left; I don't believe that anybody needs to go to Photoshop's extreme of having an origin at any random point. Bottom-left would be handy for me to study numbers to plug into my PostScript source files, besides also being useful for Carbon and AppKit programmers to mock up views and then later turn their mock-ups into real code/nibs. The rest of the world can use top-left.
Can you tell that I think a lot about what features I want in a graphics program? :)
Since you disqualified layers (harumph), I'll have to go with levels. I am starting to get comfortable with the much more powerful curves feature, but levels is the one effect that I at least try out on every single photo I edit. Brightness/contrast has its uses, but is a sucker's game for the most part.
Having just discovered Photoshop's ability to refine selections through addition, subtraction, and intersection, I am very excited about it, but that feature will never see the kind of use that levels does.
--mkb
Extremely useful.
Photoshop's curves tool is the most important and powerful color adjustment tool in the application. When an image is switched to L*a*b* color mode, curves adjustment layers combined with masks allow very fine control of color balance and contrast.
Anyway, I should add that the curves tool is a lot easier to use when a histogram is simultaneously visible. And also, stick to 16 bits/channel mode for L*a*b*, because in 8bit/channel mode, L*a*b* has such a high dynamic range that some amount of detail will probably be lost. Fortunately, with RAW images, they start out with 16 bits/channel.
There's no need for them if your app can do paths (as Photoshop can): everything that selections do today can be easily transferred to paths (presuming that you have rectangular-path and freehand-path tools). And paths are persistent and mutable, unlike selections, which are transient, and therefore can't be mutated after they've been put to their purpose.
Consider the case of running a filter in Photoshop using a selection. Once you've done it, saved, and quit the app, you can't go back and run the same filter over some other part of the image; you can only run the filter anew, which breaks things like Gaussian Blur, and various lens-effect filters such as Core Image's Kaleidoscope.
Now consider a persistent filter layer constrained to a path and masked with an alpha channel. At any time, you can go back and add segments, remove segments, add or delete whole subpaths, reverse subpaths (= Invert Selection), and the effect of the filter is updated accordingly. Even if you save, close, quit, shut down, and move to a Himalayan summit for ten years.
Non-destructive editing is the way of the future. You heard it here first. :)
And by the way, there's no need to restrain it to filters. You could do plain fills, gradient fills, strokes — all the basic vector-app requirements. It would then be a hybrid, and with a good Mac-like UI on it, it would be a very powerful one.
Yes, we need filter layers masked with alpha channels. No, we don't need it all to use paths. My alpha channel mask can use 8 or 16 bits of transparency. This is way more powerful than any path is going to ever be. I can use the paintbrush tool to add or subtract transparency with fine control. Without very serious filesize and processor overhead, that's not going to be adequately replaced with paths.
Empty clipping paths do not clip (more precisely, they are of infinite bounds), so if you do not set a clipping path, it will not clip, and only the alpha channel will have any effect.