![]() |
|
|
|
|
|
||||||||||
|
| User list | You are not logged in.
I was wondering, is there any meaning in producing 16-bit panoramas (from the APP setting) from 8-bit files?
Does the algorithm actually produce more tonal information, so that a 16-bit output has meaning when feeding APP with usual 8-bit photos?
Thanks
Offline
kharvatis wrote:
Does the algorithm actually produce more tonal information, so that a 16-bit output has meaning when feeding APP with usual 8-bit photos?
Autopano uses more than 8 bits for its color and brightness adjustments as illustratred there: http://www.autopano.net/wiki-en/action/ … rightness.
My user opinion:
If the same exposure setting was used for all 8-bit source images in a panorama, I doubt a 16-bit result file being actually very useful (but opinions may vary.)
On the contrary, the larger the exposure differences between source images, the more a 16-bit output file should be preferable if you intend to post-process the resulting pano in an other application and intend to use tools like Curve, shadows/highlights adjustments, etc.
Before deciding to use a 16-bit output file, these three steps are to be followed:
1) Select LDR mode.
2) Watch how automatic anchors were set by Autopano and possibly adjust them.
3) Use the pano editor Levels tool before rendering, as explained there: http://www.autopano.net/wiki-en/action/ … ss#Levels.
These three steps will ensure the full bit-depth (either 8-bit or 16-bit) will be actually used by the resulting file...
Last edited by GURL (2010-03-20 09:11:07)
Offline
kharvatis wrote:
Do you have an opinion on whether it's worth feeding APP with 16-bit TIFFs?
Yes - it is. But they should be "real" 16bit - which means that the camera-file should be photographed as RAW and processed/saved as 16bit TIFF.
In that case - and only then - APP/APG has a greater range to work with . . . which provides smoother curves/color-corrections and rendered as 16bit TIFF it gives
better quality for being printed or processed in Photoshop for composings or so.
best, Klaus
Online
Thank you klausesser. I an professional, and it's been quite a while since I have switched to RAW. My goal is usually fine art/hi res printing.
So, new problems arise when color profiles and bit depth come to play (especially since APP is not color managed yet).
For example, if I feed APP with ProPhoto 16-bit files, and get an (untagged) 16-bit panorama, is it just ok to tag it back to Prophoto?
Offline
kharvatis wrote:
Thank you klausesser. I an professional, and it's been quite a while since I have switched to RAW. My goal is usually fine art/hi res printing.
So, new problems arise when color profiles and bit depth come to play (especially since APP is not color managed yet).
For example, if I feed APP with ProPhoto 16-bit files, and get an (untagged) 16-bit panorama, is it just ok to tag it back to Prophoto?
Working with profiles is better afterwards when preparing the images for being printed.
Don´t use profiled images to feed a stitcher - any stitcher.
Save your renderings as 16bit TIFFs or as PS and export them to Photoshop to edit them for print.
best, Klaus
Online
I think kharvatis means he uses the ProPhoto color space, and then creates a 16 bit pano. Then he imports it back into PS and tags it (sets the colorspace, not converts the colorspace) to ProPhoto.
AFIK, that's the way you have to do it.
Offline
Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
|
CHOOSING KOLOR Why choose Kolor? Which solution to choose? Download a trial Where can I buy? Education |
SOFTWARE Autopano Pro Autopano Giga Panotour Panotour Pro XnView |
ACCESSORIES Training DVD Panobook PROJECTS Paris 26 Gigapixels Yosemite 17 Gigapixels |
COMMUNITY Forums Blog |
COMPANY About Kolor Corporate blog Resellers Contact |
PRESS Press center Press review TOOLS My account |
