Hello,
it also works the other way round. Sometimes a glitch or bug from deep
inside enblend rears its head, and a minute change of the output crop
can make all the difference between fail and success. With your approach
of blend first then crop this workaround chance would not be available.
Great idea, but if the output ends up being different (especially from the
preview) then all that saved processing time gets lost by me having to
fiddle-with and re-do the stitching. Or worse, as in this case, no output
image at all.
On Saturday, January 23, 2021 at 9:39:41 AM UTC-5 T. Modes
talk2...@gmail.com schrieb am Samstag, 23. Januar 2021 um 13:32:41 UTC+1:
> Hi there,
>
> But does the program not stitch the images together, and THEN crop the
> final image ?
>
>>
>>
No. It process only the pixels in the crop area. Why should it process many
pixels first and then crop them
Hi there,
But does the program not stitch the images together, and THEN crop the
final image ? I am not cropping the original images, i am cropping the
final stitched result.
thanks for the reply
On Friday, January 22, 2021 at 10:23:16 AM UTC-5 T. Modes wrote:
> Hi,
> talk2...@gmail.com schr
Hi,
talk2...@gmail.com schrieb am Montag, 11. Januar 2021 um 14:17:29 UTC+1:
> Hello - The Assistant created a perfect stitch of 3 photos, but I wanted
> more than the auto-crop. However, when I changed the crop size (to
> anything outside of autocrop) the saved file has stitching errors (eg. a
