 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
On a large panorama im trying to stitch, Im having a little problem with stability. As you can see in the attatched image, although the image initially appears to have stitched well, the final psb file, when opened to edit had a number of corrupted horizontal lines of pixels across it in various places. Has anyone come across this before and/or have any suggested solutions?
APG 2.6.3, Win7Pro64Bit
Offline
I have seen something like it. See the images below.
It was a pain in the ass and I had to do a lot of thinking before I found the explanation. First (ofcourse) I thought it was APG. But before throwing accusations against Kolor I explored other options.
It was disk error !
I have a RAID of 4 SSD's on a LSI controller and there was a hardware error. After a low level format the problem disappeared.
I don't know if this is the source of your problem, but you should check it out.
leifs
Offline
I did think it was probably a hardware fault but thought id check here first as there's alot of hardware to check. That particular render performed read and/or write on every disk. Ive started a new render missing out one of the disks and work from there to find the fault.
Interesting that formatting was sufficient to remove the error
Offline
Ive run memcheck and removed one bad stick of ram, Ive also formatted my SSD scratch disk and run the render several times avoiding each possible disk and im still getting issues. Ive got a 4Gigapixel image which has stitched ok but the 20Gigapixel image is still comming out plastered in corruption, any other ideas?
Offline
small update. I rendered the 20 gigapixel image at 1 gigapixel to see if the corruption was still present, and it came out clean, so i rendered at 85% giving 15 gigapixels and that too came out clean so i will use that for now. However such a result does throw the source of error back into question
Offline
We did have only a few time this kind of report and every time, it was a hardware issue. THe fact that you don't have it with smaller version does work with this hypothesis : you just didn't use as much cache as with the full version and so didn't reach the hardware sector that has issue.
Offline