Hi Chris, thanks for taking the time to further inform us on the abilities of your product. It can be a very rewarding experience for both end users and software developers when they have frank discussions concerning each of their respective issues and needs. Keep in mind that I am just a end user with no programming knowledge (apart from Basic on the Atari when I was a kid <g>) and the closest I have come is using custom convolution filters, let alone filter facotory or more serious plug creation.
Firstly - I think your company should seriously consider a demo version of the plugs of some sort (time limited, watermarked, pixel limited, preview only etc). Many users need to get a feel for things in person to see if the plug is for them - reviews and vendor information are not enough. I guess that I am not in the direct target market for your product - but prepress often has similar concerns as photographers. Another factor is that the more advanced a user is, the less they feel the need for third party add on's - when they know how to exploit Photoshop's numerous abilities. That being said, when a utility is found that meets or exceeds expectations, then the user is very happy with the purchase and is often a good word of mouth advocate.
There is a lot to go over, so I will respond in small chunks to each of your replies to my original musings.
Quote:
There are a number of things that we did in Optipix that I need to point out.
2. We thought we did a pretty good job with Blend Exposures. If you convert both images to 16-bits first and do the blend, you can then do a useful curves or levels adjustment, because your precision has been maintained. |
Yes, this is a nice feature - although not unique to your product it is nice that you offer the ability to merge multiple high bit files, which many photographers like using.
I am not sure what your point is on moving an original 8 bpc file to 16 bpc before averaging...as no new valid data is generated - unless the averaging process yields a better result when performing in/on high bit data.
Are you saying that 8 > 16 bpc > Blend Exposure yields a better result than 8 bpc > Blend Exposures? How about a true high bit file that does contain valid extra data? If the false high bit file is better due to the calculations done in high bit, then having true extra data should be a significant improvement again.
90% of my work is presented as CMYK 8 bpc data direct off a high end Crossfield PMT drum scanner - and all of my edits are performed in/on 8 bpc data...All of my edits seem useful to me! <g> I think the supierior 8 bpc data off the drum beats any 16 bpc data off a CCD flatbed, when it comes down to useful edits...but I could be wrong.
Even if I moved the data up from 8 to a false 16 bpc - can your product work with CMYK files? If you have to convert from CMYK to RGB to use the plugs - then I would think that any concern over bit depth would be misplaced.
Is the better result visible to the human eye as an improvement to the appearance of the image (that is worth the extra time/effort), or is the benefit only indicated in the histogram? And if the effect can be seen at 1:1 size on the monitor - will it be seen on final common print output to inkjet or press?
Some users care about the data, others may only be concerned with the final visual results and may not care about extra precision behind the scenes - if it can't be directly billed to the client (high bits do take extra time and graphics is not a hobby for all users). Most clients only care about how their image reproduces, not how many levels or useful bits it has (although some who purchase data do care about these factors).
Quote:
| [4. Auto Contrast. Without loosing some bits by switching to L*a*b, doing an autolevels, and coming back (incidently something you cannot do in 16-bits per channel) how do you propose to do this in Photoshop without screwing up the color balance? The build-in Autolevels does each channel separately causing all manner of color problems. |
For 8 bpc images, an adjustment layer set to luminosity blend or a fade command to luminosity mode would be the preferred edit if not working the separate channels in normal mode to gain colour and contrast. Although not the same as L of LAB, this luminosity average blend and it's opposite (color [hue+sat]) can often do similar things to LAB and HSB modes without the very minor visual penalties of some mode changes (which may or may not be common).
Photoshop offers a basic auto contrast option - which affects the levels/curves differently to auto levels/curves - although it is not doing a luminosity blend (you can add a luminosity blend/fade to the auto contrast command). Are you familiar with luminosity/color blends and the contrast and the new level/curve options of Photoshop 7?
As for high bit images - I agree that Photoshop's current inability to layer 16 bpc data makes the use of luminosity blends a dead issue.
Quote:
| [5. Nudge. I find it very useful to have +/- 1/3 shifts programmed in on the function keys. "Fade the move tool?" Go for it. it is very useful to record a specific move distance into an action. I made this tool for myself. It seemed like a natural to include in the package. |
Not sure here Chris - unless you can defy the basics of raster graphics, the nudge plug will be using some sort of averaging technique to simulate the sub pixel location of the new pixel location. I once had some custom filter kernels for this, but I have lost them (David Biedny had them on offer on the dead PhotoshopCentral site years ago).
Unless I am mistaken, using the offset filter or the move tool and nudge keys to *fade* a single pixel movement would provide a similar result - although the underlying maths may be different.
I am interested in why you recommend 1/3 increments - I would have thought that even increments would have been better, such as 1/4 or 1/2 pixel steps?
Quote:
[6. Edge Enhancement. Y'all missed the boat on this. We're not doing an Unsharp Mask (which is technically a Laplacian of the Gaussian). We're doing a Difference of Gaussians which lets you do a bandpass, not simply amplify the frequencies right below the HF cutoff. In addition, by letting you pick either the light or the dark edges (a way-cool thing to do with portraits) you can get the advantages of sharpening detail without making nasty halos around them.
It really does make a difference. We're not just blowing smoke. |
OK. This is why I wanted to play with KPT Convolver, but there is no demo. For serious exploration, you need quick interactive feedback via a GUI control, which the custom filter does not offer. Thank you for offering some basic DOG txt files in your free custom filter, as this will let me explore this concept to see how it differs from USM. Your product adds my requested GUI component to the DOG operation, which is great.
As for the split light/dark halo concept - this is nice to see. Many higher end scanners offer many sharpening options such as both smoothing and sharpening - as mentined above. They also offer the ability to control the % of dark or light halo intensity. It seems that your product offers only on/off for dark/light halos? It would be a major benefit to have sliders to control the application of dark/light haloing. Often you want the dark halo at 100% but need the lighter halo reduced in intensity, but not absent.
All of this can be done in Photoshop with layers or fades, but not on high bit files, although they can still be sharpened.
Quote:
| [7. Safe Sharpen is here because it works in 16-bits. Yes, it is similar to the L*a*b processing that you describe (with some attention to chroma noise), but you can do it without loosing any precision in your images?. |
For 8 bpc data this can all be done without loosing any precision via a mode transform using blending modes/fades (math may be different, but the visual results are usually close). If you mean can it be done on high bit data, then again - no, not with Photoshops current limitations on layering/blending...although with history states there are some possibilities...
Quote:
[The whole point of Optipix is to preserve and optimize the content of your pictures. I want to save every last little bit so you have more options down the road in your processing. If you're doing even a few steps of processing to your image, 8-bits per channel isn't going to cut it.
(end rant)
-Chris Russ |
OK - I agree in theory and concept, but the real world results are usually lacking and contradict the theory. I will try to use high bits in acquire (scanner, camera)...but for edits in Photoshop things are not so clear cut.
My situation demands a practical mindset. Time is very limited and there are a large amount of images to process. Most useage of the images is one off for offset press on good matte or glossy stock. If the final printed results do not justify the extra time and hassles that high bit data or workflows add - then it is hard to implement thier use.
I would not have a job if I missed magazine press deadlines because my edits took twice as long becuase I was working with high bit data instead of regular bit data, when the images often do not show the great benefit at the end of the day when the final prints are on the stands. When processing power and editing software allow full flexible use of high bit data in real time with no hits to productivity, then I have no problems with this workflow concept. Until then, high bit edits are more of an interesting theory than standard practice.
I would have to say that my edits *do* cut it, even though they are on 8 bpc data - but this is a subjective rating after all. <g>
Thank you for the exchange Chris, I have enjoyed the exchange and gained some deeper knowledge on image processing, I also hope that you can gain something from my 'in the trenches' perspective too.
P.S. I do not consider this a rant at all, these are deep and serious topics that are not easy to comment on without boring the author, let alone the audience.
Sincerely and respectfully,
Stephen Marsh.