Sharing knowledge around Autopano
You are not logged in.
I've processed one to two hundred panos now and have some observations about the program hanging during the generation of the projection.
I am processing adobe.dng files. My system is a Mac 10.5x and there are 3 to 18 images in each pano. All are three-image, exposure bracketed, sets. The settings are autocrop, autoexpose, and save and close. Autolevels is off. Number of points varies from the default to 200. I begin by moving sets for each group from the lightroom display to the autopano display. After moving 1 to a few dozen sets, I click the detect all button.
I define a hang as occurring when the detect process moves from the left panal to the right where the projection preview is displayed. If the busy bar extends about 1/8th inch from the beginning then stops progressing for two to three minutes (or as long as several hours in one case), I assume it has hung (especially for three images) and click the red abort button on the left panel which removes that group. But clicking the red abort button on the right panel does nothing and I have to force quit.
The only constant is that any set that fails can be processed using autopano 1.4.2.
Usually the hang involves a group of three exposure bracketed images. Failure has occurred with two sets of three bracketed images. Sometimes when I go back and try the group, by itself, it works. Sometimes the only way I can complete the detection process is to use 1.4.2. Once, I combined two sets of three bracketed images that had each failed and moved them as one group and the software returned two panos, as it should have done initially.
I hope this detail helps, because I like the look of 1.9.0 better than 1.4.2
Offline
Just try to remember that APP is not able yet to read the .xmp file made by ACR conversion containing your adjustments, neither for Dng files… If you want to have your corrections taken into account… eg CA or exposure or color balance, you better have to save your corrected files in tiff… 8 or 16 bits per pixels…
This is right now not a bug, but a non developed feature.
I'm sure that the kolor team will work on that soon… Even if this is not a "major priority"…
Offline
I think that the reading of .XMP file made by ACR is way beyond our possibility. I don't want to code everything that has been done in ACR in autopano ... That would be crazy ( one solution might to call ACR from autopano ... never though of that ! ).
Offline
So why does the hang not occur with 1.4.2?
Offline
I use 16 bit tiffs for my work. You have more control over the image, processing your own RAW files. As your camera gets updated, so does the interpretation of its data. I use nikon, which chooses to hide proprietary data. So I develop RAW images with which ever version of capture they are using now. It helps the images quite a bit in terms of sharpness and color.
Offline
Remember that 1.9 is really a early early alpha.
Offline