Spencer Egart | 22 Oct 22:48 2014
Picon

Hugin appears to be non-deterministic?

I'm stitching images via script, and have noticed that every time I run it I get a slightly different final pano.  I'm making sure to delete any old intermediate .pto files beforehand, so it's not that.

Are any of the tools in Hugin (autooptimiser, cpfind, etc.) based on random/non-deterministic algorithms?  If so is there a way to seed the RNG or in some other way ensure reproducible results? 

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/7999ad49-23ff-44a8-8ce5-1aad32ccc3ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
John Muccigrosso | 21 Oct 15:34 2014
Picon

Manipulating masks on a Mac - bugs?

Some of the mouse commands that are listed in the manual are difficult for Mac users, since we don't generally have 3-button mice and a control-click is the same as a right click (we'll leave the trackpad out of it).

That said, I was working on a mask and found some inconsistencies with what the manual says, and just some oddities. Are these actual bugs or has the manual simply not been updated? I'm happy to create a screencast to show them, if that would help.
  1. A right-drag inside a mask does what the manual says and moves it. (Control-click and drag acts the same, as expected.) So the hint about command being the same as control on the Mac is wrong here. The only issue I found is that sometimes it takes a second for Hugin to register the click and select the entire mask.
  2. OTOH, command-clicking on a line creates a new point there, just as control-clicking is said to for other OSes.
  3. When I click on an existing point, Hugin will sometimes select not just that point, but also an adjacent one or more. Why?
  4. When I click near the mask, Hugin will select 1 or more points. They look like the closest n points to where I'm clicking, but how is it deciding what n is? This looks like Hugin treats a click near the mask as if it were actually on the mask. Note that unlike #3, the points do not have to be adjacent to each other, but apparently near to the click location.
  5. Similar to #4, if I command-click somewhere off a line, Hugin will create a new point, but not necessarily in the nearest line segment. How is it deciding where to make the new point? I can actually get pretty far away from the mask and have this happen.
  6. Drawing a marquee around a point will sometimes select adjacent points as well, just like clicking does. This is somewhat dependent on the size of the marquee: a small one confined to an area just around a point will select only that point, but if the marquee is big and approaches other points - even if it doesn't include them - then more than one point will be selected.
  7. If I drag a point selection (of one or more points) a short distance away from its original location, it will snap back. But if I drag it further, it will stay where I put it. What's happening there? Is there some minimum change that Hugin needs? (If so, that's not very helpful for tweaking masks.)
Any help appreciated. I'm happy to file these as bugs, but not if I just need to RTFM (whatever manual that is).

Thanks.

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5ef5789e-572d-439b-9647-41758bf2a8e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
John Muccigrosso | 21 Oct 15:12 2014
Picon

Questions about masks/cropping

Was working on a pano today and needed to do some masking, which got me thinking:

1. There was some talk about this in the original announcement of this functionality, but do I have it right that Hugin clips the mask to the image boundaries, even if the mask looks like it goes outside them?

2. Similarly, does the optimization know about the masks? Does it ignore control points within cropped areas? Or are the effects of the masks and cropping just limited to the final image?

TIA.

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/98fb02b7-dfbe-4d67-9e7a-b13d8d11005f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
paul womack | 21 Oct 12:43 2014
Picon

Making 1 image fit another?

In an almost vestigial instance of optimisation, I would like
to "mate" a pair or photographs. Both are near square, but
are not as high quality as I would wish.

In order to preserve the most quality possible, I would like
to keep one of  the images (that happens to carry more important
subject matter) untransformed, and get hugin to calculate and apply
transforms only to the second image.

It's easy to persuade hugin to transform them BOTH
so the transformed PAIR are a mutual match, but how
to I persuade hugin to come up with a transform
for one image (presumably the anchor) which is a pixel
perfect no-op (such that I'll actually use the original :-) and
the second (transformed) image can be matched to it?

  BugBear

--

-- 
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/544638EC.5030203%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.

Ryan Molden | 21 Oct 06:51 2014
Picon

Hugin 2014.0.0.6951a0bde18c AVs trying to save panoramas

Hello, I recently upgraded to 2014.0.0.6951a0bde18c to get past the annoying message box warning popup on Widows when various program's used by Hugin encountered unrecognized EXIF metadata. That bug is fixed, yay, but now there is a much worse one. Every time I try to save a successfully stitched pano I see this:

"C:\Program: Interrupt/Exception caught (code = 0xc0000005, addr = 0x000007F7B81DC15F)

And it fails to save anything. The last program that appears to have run is nona, so I assume that is the one A/Ving. Is this a known issue? I earlier thought it was only in stitching TIFFs (as those are the only type I had tried), but tonight I tried simple JPGs, same issue.

Ryan

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5fcd46e3-bc97-4b7b-bb3b-4b79e0e8c286%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Terry Duell | 21 Oct 00:53 2014
Picon
Picon

Enblend-4.1.3 Fedora src.rpm here

Hello All,

For anyone who wants it, you will find a Fedora src.rpm of the last stable  
release of enblend (4.1.3) here...

<https://www.dropbox.com/s/im19c6ykd5xn335/enblend-4.1.3-1.fc20.src.rpm?dl=0>

Please let me know if you have any problems with it.

Cheers,
-- 
Regards,
Terry Duell

--

-- 
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/op.xn1wjyvors0ygh%40localhost.
For more options, visit https://groups.google.com/d/optout.

John Muccigrosso | 20 Oct 00:06 2014
Picon

Interface comments: The Fast Preview Window

I find a few things about the Fast Preview window confusing:

1. It's the same things as Simple mode. I think I see that the functions you want in it are nearly all the ones you want in Simple mode (you don't need to add photos when you're using it simply as Preview), but still, why is it identical? I guess this pertains to the Assistant tab, which doesn't seem necessary when you're not working in Simple mode.

2. It takes over the whole screen (on my Mac anyway) and so it isn't clear that it's a new window, instead of a replacement view for the other one. The old Preview window is a smaller window and so it's clear what has happened.

3. It has no close button, nor does it respond to the keyboard equivalent for closing. I can close it using the usual widget (red button in the "traffic light" in upper left corner), but this is odd behavior, especially since when I'm using it as the Fast Preview and not simple mode, I want to close it so that I can return to the main window. I realize that I can just go back to the main window by using the keyboard command for that (command-`) and just leave it open, but that is not nearly the behavior that you expect less expert users to know about, and it's weird to have to do it anyway when I expect to close the Preview window when I'm done with it.

So am I missing something important about this window, or is this one of those unresolved UI things.

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ea7e3150-496b-453f-9cee-5eac96646dd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mike Sopalla | 18 Oct 21:02 2014
Picon

Final output panorama is smaller than the original; keeping the resolution 100% relative to original?

Hello all,

When I process the panorama I usually save the pto file and open it with the hugin_stitch_project.exe because the batch processor is broken (I'm on XP SP3).
The question I have is what command line command can I type to tell the stitcher, I guess enblend to output the final panorama at the same resolution as the original. I know that the
resolution must be smaller because when I open the panorama in GIMP and try overlapping part of the panorama with an image (used for making the panorama) I find the scale has changed.


Mike

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/fdb91f0e-7d21-4071-bc40-b313a876c4af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Brandon | 16 Oct 21:18 2014

What kind of lens does hugin call a Rokinon 8mm?

I have a new fish eye lens and I do not know what to tell hugin it is.

It is a dead lens, so it does not have any exif data for hugin to look at so I need to put it in by hand. The lens is a

Rokinon HD8M-C 8mm f/3.5 HD Fisheye Lens with Removeable Hood for Canon DSLR 8-8mm, Fixed-Non-Zoom Lens

http://www.amazon.com/gp/product/B008X1C4IY/ref=oh_aui_detailpage_o03_s01?ie=UTF8&psc=1


The part that has me stumped is it a normal lens, circular fish eye, a full frame fish eye or something else? I am using it on a cannon rebel t5 if that makes any difference. It has a focal multiplier of 1.585x


--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/a57a4223-1b84-462b-af6d-0178aadb7981%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Michael Perry | 16 Oct 19:41 2014
Picon

Mosaics with a Copy Stand

I stitch mosaics using Hugin. My camera is mounted to a copy stand and can slide in both X and Y and uses a (calibrated) Macro lens about 40cm above the artwork. 

I am convinced that I am not using the right optimisation processes in Hugin. The workflow is:

•  Optimise in x and y to get all the images in roughly the right place and spot cpfind Control Point errors (if any)
•  Optimise in all of y,p,r,x,y and v to bring down the errors

As the HFoV approaches some (arbitrarily) small value, optimisation is complete. That just seems a bit wrong.

•  Surely I should have a constant yaw, pitch and roll? One that is applied to all of the images (including the anchor image). After all the camera only moves in X and Y and the artwork is fixed.
•  Should I be using the Plane Yaw and Plane Pitch tools - but how?
•  Is the importance of the HFoV in achieving optimisation a reflection of panotools origins as a panorama tool?

Any thoughts would be much appreciated.



--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c3033d87-8a26-4b6d-9c02-44fac8280134%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Michael Perry | 16 Oct 19:35 2014
Picon

Mosaics

I stitch mosaics using Hugin. My camera is mounted to a copy stand and can slide in both X and Y and uses a (calibrated) Macro lens about 40cm above the copy artwork. 

I am convinced that I am not using the right optimisation processes in Hugin. The workflow is:

•  optimise in x and y to get all the images in roughly the right place and spot cpfind Control Point errors (if any)
•  optimise in all of y,p,r,x,y and v to bring down the errors

As the HFoV approaches some (arbitrarily) small value, optimisation is complete. That just seems a bit wrong.

•  Is it a reflection of panotools origins as a panorama tool?
•  Should I be using the Plane Yaw and Plane Pitch tools 

--
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+unsubscribe <at> googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/7b75d931-f2f5-4122-88e2-553078dc95ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gmane