My Autopano Pro forum

i'll try again to upload a file

You probably have to zoom in!



thanks

Henrik

PS: it really helps when I read the error messages when trying to upload :-)

Last edited by tived (2008-07-26 14:44:47)

First thing that comes to mind are bad sectors on your disk. Run a full disk scan, preferably offline (boot from another disk if you have another OS on another disk, or boot from a live cd), once thats done try opening that .pano again (no need to restitch) and try rendering it again.

tived wrote:

How do I move a topic to another part of the forum.Henrik

I guess only a forum admin can do this. You did several panos yesterday/today. Can you see such lines on every one or only this panorama ?

marco-pano wrote:

tived wrote:

How do I move a topic to another part of the forum.Henrik

I guess only a forum admin can do this. You did several panos yesterday/today. Can you see such lines on every one or only this panorama ?

Hi Macro-pano,

no only this one so far.

thanks

You can get that effect from transient disk errors, not necessarily bad sectors that will show up in chkdsk.

tived wrote:

... I do not change my focal lenght it shows several different focal lengths in AAP and also shutter speeds, even though everything has been set to Manual... regards. Henrik

Surprising As you have Bridge, I guess you have PS. Did you check the EXIF data with PS to see if focal / aperture / speed are correct, compared to what you know or what say your Canon software (maybe DPP) ?

The camera doesn't report the true focal lenth-its only an approximation.  APP will guess a better length.  Its not unusual to have each image be a slightly different length, especially if you handhold or if your pano head is a bit off.

The shutter speed is problematic.  I recomend checking the EXIF for the shutter speeds, and verify that you were in manual mode, not Aperture Priority.

Last edited by hankkarl (2008-07-28 17:07:03)

How is any of this relevant to his problem that some parts of the rendered pano (NOT source images, since if they were corrupt the lines would not be so ideally straight) are corrupt?

Hello everyone,

thanks very much for chipping in here to solve my problem - I am trying to empty disks to re-format them, to see if this will change anything, needed to do some housekeeping anyway.

I see the change in various setting in the layer editor

I will try to post an image

thanks

Henrik

marco-pano wrote:

...(and I don't believe in random errors because of neutrino, of what ever else )

Silent data corruption is real and demonstrable: http://storagemojo.com/2007/09/19/cerns … -research/

I've had 3 image files (2 TIFF files and 1 Kodak RAW file) on 2 Lacie external 500GB "Big Drives" affected by silent data corruption. I know this because I verify my back-ups several times a year by comparing with the original data. Of course, I no longer use those Lacie drives.

The visual effect is a line or rectangle, one more pixels high and spanning the entire width of the image, containing obviously wrong data in one or more channels.

It's also possible for a file to become corrupted when it is saved, without any error messages, and you won't know there is a problem until you try to open it again. That's why, when using Photoshop, I always save two copies of very important images.

When you say it has happened again, what exactly has happened again?

If you render a pano and it has lines across it, and then you render the same pano again under a different filename, and the two rendered panos have the same lines, then the problem is probably not a disk drive.

If you render the same pano several times and get different lines across the rendered files, or especially if you get the lines in images from other applications such as Photoshop, then it is fairly likely you have a bad disk. If disk diagnostics don't reveal any specific problems, I would recommend you replace the disk, or use it only as a scratch/temporary disk.

In the meantime, look at every image that you render in APP or save from any other application, and if it looks good, back it up promptly. You should have at least two back-ups of all important files. That way, you can compare the back-up with the original, and if any file shows a difference, you have a 3rd file to use to decide which one is correct if it's not visually obvious.

Also consider using a back-up program such as EMC Retrospect that allows you to verify the integrity of the contents of a back-up. But keep in mind that backing up a file that's already corrupted doesn't do any good.

marco-pano wrote:

hankkarl wrote:

The camera doesn't report the true focal lenth-its only an approximation.  APP will guess a better length.

Camera reports what it knows to be focal length in EXIF data (true length, not equivalent35mm). APP can report focal length on 2 places : 1) in the detection group, before detection ; 2) in the Layer editor, after detection (then focal may differ, maybe more if you activate "advanced lens distortion" that it's not so much advised for rectilinear lenses).

Henrik, can you explain more on where you see APP changing focal ? I agree with Hankkarl, check also where speed information are changed from EXIF to APP.

The camera reports an approximation of the actual focal length.  A zoom lens has an infinite number of focal lengths, but may only report 5 or 6 different ones.  So if the lens reports 51mm, the actual focal length may be somewhere near there.  In the OPs case, 53.xx is pretty close to the reported length, but APP guesses a better length.

In the case of a circular or spherical pano, its easy for APP to calculate (not guess) the correct length.

The different focal lengths can be explained by a pano head that is a hair off, or by a handheld pano, or just some bad CPs.

Last edited by hankkarl (2008-07-29 17:52:26)