enblend: warning: images do not overlap; they will be combined without blending
enblend: note: usually this means that at least one of these images does not
enblend: note: belong to the set or the order of the images given at the
enblend: note: command line is wrong; sometimes passing option
enblend: note: "--pre-assemble" resolves the problem; in rare cases using
enblend: note: option "--levels=NUMBER" to force blending with a certain
enblend: note: NUMBER of levels can help, too
At the end, PTBatcherGUI output the following:
enblend: an exception occured
enblend:
Precondition violation!
separableConvolveX(): kernel longer than line
(/Users/max/Downloads/hugin-build-21/hugin-2021.0.0/mac/ExternalPrograms/repository/include/vigra/separableconvolution.hxx:1103)
enblend: info: remove invalid output image "_DSC0173 - _DSC0283.png"
I've also included a link to the entire status report and attached a screenshot of my settings under the Stitcher tab.
https://docs.google.com/document/d/1T1mln6FnDopkVkxYVMZ5sQim7zRd3A3kMadRDeyQUC8/edit?usp=sharing
Can anyone tell me why this is happening and what I'm doing wrong?
Much appreciated,
Alex
Can anyone tell me why this is happening and what I'm doing wrong?
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/165607a0-a06b-471f-8ac0-9ac84c81bed4n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/f8f6d0bf-4573-435b-a138-ac39899b7885n%40googlegroups.com.
in theory, TrX, TrY and TrZ can solve the problem, but in my case sometime it goes wrong and i don't know why.
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6490f7e6-67b3-4f91-b185-00b68ca2b393n%40googlegroups.com.
So I shot the image sequences with the camera attached to a handcart in a rigidly fixed position so there should be hardly any plane pitch or yaw. And for optimising, my process was the following:- Optimize for TrX only, which produced an average unit distance under 1 (can't remember exact figures off the top of my head)- Optimize for TrY and TrZ only, producing an average unit distance in the .4-5 range- Optimize for yaw, pitch and roll at which point the unit distance was around .2The resulting panorama looked great to my eyes but are these differences still to great?
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to a topic in the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hugin-ptx/UD75PbXwS60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/47e7f678-67c6-464e-8f5b-20f31d4b4e94n%40googlegroups.com.
Hmm ok, I'll go back and take a look. While I haven't gone through all 100 or so images in the panorama, I haven't seen any non-matching points in the control points I've looked at but I'll take a closer look.
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CALe0Q_%3DyDMz7EOMVS%2BNMLDiv5NyptCV9h2%2BdU5j9E%2BvDCCQm3w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CABqZK5dKq8OAuGFcTFm6WqwGX2FKWR1%2BS2qr7kFcB8iJr%2Buivw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ef7186f1-1f52-4634-90d8-99637df41818n%40googlegroups.com.
enblend: warning: unable to run Dijkstra optimizer
enblend: note: seam-line end point outside of cost-image
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to a topic in the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hugin-ptx/UD75PbXwS60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CALe0Q_nEJ%2BTUc_oXmsAWnneUL3TpFya8FH8QGUn7-cEm8%2Bb1sA%40mail.gmail.com.
I think cleaning the control points is what makes the difference for me.
I've also sometimes seen Hugin misread the focal length on an image. When that happens, I get weird results, and my process eventually hits a point where Hugin says that calculated values are invalid. But you would see that before getting to the actual stitching stage.
Helpful?
What is the cost-image? I'm wondering if both of you may, in one way or another, be pointing to the issue giving me problems. I was attempting to export stitches that were uncropped - that is to say, all of the edges of the panorama being visible - so that I could make decisions about cropping later, once I'd straightened the mosaic in a photo editing software like Gimp, but maybe doing that has been creating issues. I say that in part because some of the successful stitches I've made recently have come using Hugin in "simple" mode with a crop automatically applied.
Out of curiosity, have any of you had greater or less success depending on the file type you've used? I've experienced almost no success working with tiffs and pngs created off of the original raw files via Lightroom, but I'm getting more successful stitches with jpegs off of those same raw files. I should clarify that these successes and failures are coming while running tests on the same image set, DSC0175-DSC0235, just tiff vs png vs jpeg.
On Mon, Nov 7, 2022 at 6:03 AM John Fine <johnfi...@gmail.com> wrote:
On Sat, Nov 5, 2022 at 7:25 PM Alexander Drecun <alexande...@gmail.com> wrote:
enblend: warning: unable to run Dijkstra optimizer
enblend: note: seam-line end point outside of cost-image
I'm not sure I'm remembering correctly. If I am, this might help:I have had a lot of problems similar to that. I think they occured in panoramas with ragged edges.When I had not taken photos far enough beyond what I actually wanted, I had the problem that assembly of the panorama would tilt the outside edges of individual photos (not parallel to the panorama edge) so I had to either clip to exclude some of the content I wanted, or clip wider to include some empty space (make the edge of the final panorama ragged). The latter had the extra problem that I think matches what you described.I think you can avoid it by clipping tighter.
-- David W. Jones gnome...@gmail.com wandering the landscape of god http://dancingtreefrog.com My password is the last 8 digits of π.