Re: [hugin-ptx] Re: What are the keypoints to create 360 panorama ?

I would remove the '--linearmatch' parameter, as this prevents the last image being matched with the first image. (You could try '--multirow' instead, but this shouldn't be necessary) Possibly also removing the 'cpclean' command would help in this case, but I can't test from here. -- Bruno On

Re: [hugin-ptx] How line CPs really work (to level a panorama)

On Wed, 22 May 2024, 17:01 'ChameleonScales' wrote: > Please correct me where I'm wrong or confirm if I'm right. > > To my experience and reasoning, horizontal or vertical line CPs never > affect the relative positions of photos when optimizing. Only the > orientation of the panoramic sphere as a

Re: [hugin-ptx] Re: What are the keypoints to create 360 panorama ?

On Tue, 21 May 2024, 13:49 Wade Wang wrote: > > 'multirow' is what you want, it tries to match all the ends of > whatever chains are created after running a 'linearmatch'. Inspired by this, I find I can achieve my goal (matching only feature > points between adjacent images and the last image

Re: [hugin-ptx] Re: What are the keypoints to create 360 panorama ?

On Tue, 21 May 2024, 10:10 Wade Wang wrote: > 1.I find we can not use --multirow and --linearmatch simultaneously > because they are mutually exclusive, then can I achieve my goal (matching > only feature points between adjacent images and the last image matching the > first image) ? >

Re: [hugin-ptx] I am not a member, but I cannot quit receiving mail from the group

Done, you shouldn't get any more posts from the group - Bruno On Tue, 7 May 2024, 12:23 Bernard Lang, wrote: > Help please > I try to stop being sent email by the Google Groups "hugin and other free > panoramic software" group. > The only answer I received is that the group will not do anything

Re: [hugin-ptx] Re: Xpano

On Thu, 2 May 2024, 16:54 'T. Modes' wrote: > > This is "only" a GUI for the panorama functions in the OpenCV. library It > does not implement own panorama stitching algorithms. > In my simple tests the results were good for some projects, but for other > projects it works not so good. > There

Re: [hugin-ptx] Re: Stereo image alignment

On Wed, 17 Apr 2024, 20:33 Chris wrote: > OK. It wouldn't have occurred to me do this because there could be ten > files in the "glob". Would it just take the first 2, and assume that the > first one was the right-hand image and the second the left-hand? align_image_stack will align as many

Re: [hugin-ptx] Re: Stereo image alignment

On Wed, 17 Apr 2024, 07:13 Chris wrote: > T modes:"*No, you can also use placeholder like ? or *. "* > This is undocumented so far as I can see. > This is normal filename globbing. The ? and * characters are usually expanded into a list of files by the operating system. align_image_stack only

Re: [hugin-ptx] Disappearing posts

First posts from users stay in the moderation queue until they get approved (I'm a bit slow today as am at a theme park) - Bruno -- 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

Re: [hugin-ptx] What free software to stitch photos that exactly adjoin?

You could do this in Hugin, but it would be easier to use something like ImageMagick which has an 'append' function to do this - Bruno On Sun, 10 Mar 2024, 14:24 Joseph Elfelt wrote: > I wrote software that can take a series of screenshots that exactly > adjoin. Each screenshot is part of a

Re: [hugin-ptx] creating panoramas directly from RAW images

On Fri, 23 Feb 2024, 08:30 'kfj' via hugin and other free panoramic software wrote: > Okay, here goes: the code is online > > hugin developers, I can offer a patch against hugin master if you're > interested in trying it out. This looks like something

Re: [hugin-ptx] dark gradients and sharp edges in landscape panoramas

Hi Harald, this is a bug in enblend (which is used to join the individual remapped images). The workaround is to either use the built-in Hugin blender instead of enblend, or rearrange the order of photos in the project (drag them up and down in the photos tab) - Bruno On Tue, 16 Jan 2024, 12:42

Re: [hugin-ptx] Control points improvement proposal

I can't check the exact usage from here, but look for the 'multirow' option. This does a linear match (matching consecutive images), then matches the ends of each resulting disconnected chain together, then finally does a 'prearranged' match (with the hope that the previous steps have put

Re: [hugin-ptx] Stitching existing files together via Hugin

There is an old tutorial for 'flat scanned images'. Basically set the lens type and panorama type to 'rectilinear', use any number you like for photo angle of view (eg. 10), zero out any roll, pitch and yaw parameters, and optimise x, y and z for all images except the anchor. -- Bruno On Sat,

Re: [hugin-ptx] Combining small X-rays of circuit boards to make one complete image

Hi James, a multi-row stitch with 45 images shouldn't be a problem, this isn't a big project relatively. It isn't a 'normal' panorama where the camera has a fixed position and the photos only vary by rotation. Probably the rotation doesn't vary and the only thing that varies is the camera

Re: [hugin-ptx] Hugin 2022.0 Black blotches on final stitches

The black shadows are an enblend bug, they don't appear if you use the built-in Hugin blender (which is not as sophisticated as enblend, but is more stable) - Bruno -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message

Re: [hugin-ptx] Hugin 2023.0.0 released

Thanks Thomas! As usual there are preview fedora packages in the 'panorama' copr repository: https://copr.fedorainfracloud.org/coprs/bpostle/panorama/ Otherwise, users of the default hugin package in fedora 39 will get upgraded in a few days. -- Bruno On Sat, 11 Nov 2023 at 08:58, T. Modes

Re: [hugin-ptx] Hugin 2023.0 beta 1 released

I see this on fedora, this look a bit messed-up: $ pkg-config flann --libs -L/usr/lib64\;-llz4 -lflann -lflann_cpp On Sun, 24 Sept 2023 at 14:11, T. Modes wrote: > > it works here. lz4 is added to FLANN_LIBRARIES automatically by pgkconfig: > > from the Cache: >

Re: [hugin-ptx] Hugin 2023.0 beta 1 released

I'm not quite sure where to fix this, but flann-1.9.2 now has a dependency on lz4. So I needed to add "-llz4" to get hugin to build with this version of flann. -- Bruno On Sat, 23 Sept 2023 at 08:36, T. Modes wrote: > > today we are releasing beta 1 of Hugin 2023.0.0 > -- A list of

[hugin-ptx] libpano13-2.9.22 released

string 2023-06-22 17:54 +0200 tmodes(18ed65577fbc) * sys_ansi.c: ShowScript: Check if file exists before opening vi 2023-01-21 16:23 + Bruno Postle(778a20784e24) * man/Makefile, version.h: Bump version to 2.9.22 2023-01-21 16:11 + Bruno

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc2

Thanks Jeff, these look good to me but I'll defer to Thomas. Unless anyone has any objections, I'll release rc2 as libpano-2.9.22. -- Bruno On Wed, 16 Aug 2023 at 18:29, Jeff Welty wrote: > I didn't see any tags for rc2 in mercurial, so I made this patch which > gives changes I made against

Re: [hugin-ptx] Drone Pano Scripting - Cannot get rid of the Black Hole Sky

On Tue, 22 Aug 2023, 04:34 PanoSeek wrote: > > The closest I found was Bruno talking about the l-29 setting for enblend - > https://groups.google.com/g/hugin-ptx/c/aghpJeyIvQo/m/k6iOJVImjskJ - I > did attempt Bruno's solution, but got an error about couldn't do 29, could > only do 9 and some

Re: [hugin-ptx] Scripted Hugin Panos from Drone - Fighting the curvature of the earth?

On Tue, 22 Aug 2023, 03:58 PanoSeek wrote: > > After reading the latest thread about multi-row pano's, I have been > inspired to refine my hugin script I use to build 360 spheres from my DJI > Mini 2. I ran into an interesting artifact that I cannot get rid of - A > jagged line in the horizon. >

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc2

Thanks everyone for testing. Yes ideally fixes should be a mercurial merge request on sourceforge, but a diff/patch is nearly as good. A tarball is ok, but the first thing we would do is extract it to generate a diff - a diff has the advantage that you can see exactly what you are proposing to

[hugin-ptx] libpano13-2.9.22 release candidate rc2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 libpano13 is the PanoTools library for panoramic imaging. A libpano13-2.9.22 rc2 tarball has been uploaded to sourceforge, this is a release candidate for testing that may become the final release:

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

On Mon, 31 Jul 2023, 17:33 T. Modes wrote: > > I found a possibility to keep the ABI constant. All public functions keep > their signature and exist furthermore. But the critical functions have been > replace with a stub which prints only a message to stdout and does nothing > else. So the

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

The immediate need is to put out a bugfix release. If we bump the soname then it won't be a drop-in replacement, and Hugin will need to be rebuilt for all platforms etc.. These bugs are not relevant to Hugin users, but they are still security issues, so Linux distros will be looking to update

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

On Sat, 22 Jul 2023, 17:38 Robert Clausecker wrote: > > Failing that, bump the soname and make this a major or at least a minor > release so it's clear that this release has an ABI break. ABI breaks > in patch-level releases are not a good move. > I agree, if we are changing the ABI and soname,

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

these functions with no-op stubs to quieten the abi checkers. What do you think? -- Bruno On Sat, 22 Jul 2023, 13:36 Andreas Metzler, wrote: > On 2023-07-18 Bruno Postle wrote: > > libpano13 is the PanoTools library for panoramic imaging. > > > A libpano13-2.9.22 rc1 tarball

[hugin-ptx] libpano13-2.9.22 release candidate rc1

(18ed65577fbc) * sys_ansi.c: ShowScript: Check if file exists before opening vi 2023-01-21 16:23 + Bruno Postle(778a20784e24) * man/Makefile, version.h: Bump version to 2.9.22 2023-01-21 16:11 + Bruno Postle(da06997f4c2f) * ColourBrightness.c

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

The man page isn't very clear, enblend looks at the overlap size and sets the number of levels to mostly sample from the overlap area. If you set it to a large number of levels it will sample from much further beyond the overlap area - which is useful for smoothing out a sky. -- Bruno On Fri, 7

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

Enblend will adjust areas that are outside the overlap, -l 27 just tells it to use the maximum number of levels possible. Hugin can correct 'normal' radial vignetting, but these shots are not ideal for calibration. You would need to shoot a simple scene with about 50% overlap, get Hugin to

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

hanges over time and gets clouds a few minutes later. > > can i test that in command line and if so how should i add this to the > example? > enblend -o project.tif project.tif project0001.tif > > Op 05-Jul-23 om 22:27 schreef Bruno Postle: > > Are both photos take

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

Are both photos taken at the same time? I'm trying to figure-out the intent. If you just want an even blend across the sky, then you can increase the number of levels in the blend pyramid to the maximum. In the Stitcher tab, set enblend options to -l 27 -- Bruno On Wed, 5 Jul 2023, 21:05

Re: [hugin-ptx] Automatic train photography and stitching

Nice, see also Masakazu Matsumoto's work: https://github.com/vitroid/TrainScanner https://www.flickr.com/photos/vitroids/ On Wed, 3 May 2023, 09:05 Paul Womack, wrote: > This isn't hugin, but stitching more generally. And yet not generally, but > monumentally specific. > > And very cool. > >

Re: [hugin-ptx] Re: Vuze Camera 3D 360° VR. Parameters for import and stitching photo

So the camera takes two full panoramas that need to be stitched separately (though for stereo viewing they will need to be aligned with each other somehow). ie. all the left hand images (1, 3, 5 & 7) are stitched together, then all the right hand images (2, 4, 6 & 8) - Bruno On Fri, 3 Mar 2023,

Re: [hugin-ptx] Re: Vuze Camera 3D 360° VR. Parameters for import and stitching photo

Is this a stereo camera? It seems to be taking two sets of images - Bruno On Fri, 3 Mar 2023, 06:46 Francesco Sorrentino wrote: > The lenses are positioned to the sides (see attachment). I should try your > advice: take two shots, one of which is rotated 45 degrees, to give hugin > some

Re: [hugin-ptx] is "downscale final pano = 70% of max width" overriden by "calculate optimal size"?

On Sun, 22 Jan 2023, 18:38 T. Modes, wrote: > > The calculate optimal size button is using by default no additional > scaling factor. (So it ignores this setting. Except you hold the control > button.) > The downscale factor of 70 % is on the assistant tab in the preferences. > This indicates

Re: [hugin-ptx] is "downscale final pano = 70% of max width" overriden by "calculate optimal size"?

On Sun, 22 Jan 2023, 14:16 Fotis K wrote: > thank you Bruno, interesting information! i’m reading that the green > channel has more resolution - i wonder how this translates in my case: for > my workflow i’m batch developing the raw files of my camera into 16bit > tiffs that i then use as input

Re: [hugin-ptx] is "downscale final pano = 70% of max width" overriden by "calculate optimal size"?

On Sun, 22 Jan 2023, 10:30 Fotis K, wrote: > After all these years of using hugin I discovered that I never set the > option *downscale final pano* from 70% to 100% in the preferenecs. > > However I always click *calculate optimal size *right before the final > stitching. > This 'calculate

Re: [hugin-ptx] Hugin 2022.0.0 released

On Thu, 22 Dec 2022, 09:11 T. Modes wrote: > Thanks Bruno > >> >> - Fedora wxwidgets 3.2 still doesn't have Wayland support, so it is >> necessary to build Hugin with `-DUSE_GDKBACKEND_X11=ON` otherwise >> Hugin crashes on startup. >> > I'm a bit surprised on this. I was under the impression that

Re: [hugin-ptx] Hugin 2022.0.0 released

Thanks Thomas. 2022.0.0 will be in the next fedora 38 release. It is also available in the fedora panorama copr repository for all current fedora versions, enable this like so: `sudo dnf copr enable bpostle/panorama` A couple of notes: - Fedora wxwidgets 3.2 still doesn't have Wayland support,

Re: [hugin-ptx] Hugin to correct Iphone panorama fisheye distortion

This looks like a cylindrical panorama, ie. Set the projection of the input photo to cylindrical and the output panorama to rectilinear - Bruno On Mon, 21 Nov 2022, 06:10 Tony Denzer, wrote: > Hello, > Amateur-level question. > Can Hugin be used to correct (to make 'orthogonal') a single iphone

Re: [hugin-ptx] Re: Adjusting the yaw, pitch and roll of two equirectangular panorama in one view

Have you set the projection of both input images and the output panorama to equirectangular? On Thu, 17 Nov 2022, 13:34 DerekS, wrote: > Hi dkloi > > Interesting idea, that I been playing with at your suggestion. > > I loaded in the two panorama, and added control points, and the selected >

Re: [hugin-ptx] Unable to 'pip install hsi' (Hugin Scripting Interface)

I didn't know you could install hsi this way, but the error is because you don't have opencv2 header files on your system. On fedora these would be in the opencv-devel package. -- Bruno On Sun, 30 Oct 2022, 10:38 Thomas B., wrote: > Hello all, > > I have some Python scripts for automated

Re: [hugin-ptx] Calculate Optimal Size Shifting Control Point Distance

The control point error is reported in terms of pixels in the output panorama. So if 'calculate optimal size' changed your 3000x1500 panorama into a 3x15000 panorama then all the control point distances will be ten times bigger. The output will look the same but with higher resolution. You

Re: [hugin-ptx] Re: Stabilising/deshaking webcam timelapse footage

I just did a test and you don't need to modify nona-deshake to use TIFF input files. I created a set of images called: temp0001.tif, temp0002.tif etc... I created a Hugin project using just one of these images, set the crop and output projection, saved as template.pto Ran nona-deshake:

Re: [hugin-ptx] Re: Stabilising/deshaking webcam timelapse footage

ffmpeg can split a video into TIFF frames, just change the output format to webcam%08d.tif or similar. If you want nona-deshake to render to TIFF instead of JPEG, then you should change "$prefix%08d.jpg" on line 51 to "$prefix%08d.tif" and 'JPEG' on line 88 to 'TIFF'. -- Bruno On Thu, 6 Oct

Re: [hugin-ptx] enblend: encountered degenerate image/mask geometry; too high risk of defective seam line

You could try the internal Hugin blender. This doesn't have as many features as enblend, but it should be more stable with this sort of thing. Also, rearranging the order of photos in the Hugin Photos tab may help. enblend processes images in this order, so the seams will take a different shape.

Re: [hugin-ptx] Shooting Panoramas in Tight Spaces

Some notes I wrote on this eleven!! years ago: https://www.flickr.com/photos/brunopostle/5830006193/ Shooting from the same distance is useful, as is shooting perpendicular to the surface/wall. Though shooting from an oblique angle where necessary is ok, probably this would be better if this is

Re: [hugin-ptx] developed view of a cylindrical surface (timber carver)

This isn't a typical use for Hugin. But you might be able to produce a result by cropping out a narrow vertical strip from each photo and stitching these together. You can crop the photos by processing them in an image editor, or by adding masks in Hugin. I wouldn't expect the automatic control

Re: [hugin-ptx] Re: In Pano13 the tilt parameters TiX, TiY, TiZ and TiS?

On Wed, 10 Aug 2022, 23:58 johnfi...@gmail.com, wrote: > > > On Wednesday, August 10, 2022 at 5:15:33 PM UTC-4 bruno...@gmail.com > wrote: > >> On Wed, 10 Aug 2022, 22:07 johnfi...@gmail.com, <> wrote: >> >> These other parameters allow different planes. The basic use is for >> stitching a

Re: [hugin-ptx] Re: In Pano13 the tilt parameters TiX, TiY, TiZ and TiS?

On Wed, 10 Aug 2022, 22:07 johnfi...@gmail.com, <> wrote: > > I still hope this question gets a reply from someone who does know what > those parameters are intended for and what other tools might be using them. > 'Mosaic' XYZ control points are mapped onto a vertical plane that is directly in

Re: [hugin-ptx] Trapezoidal distorsion when stitching scanned images

Hi Pierre, I would first check that both the pitch and yaw of all your input photos is set to zero and that the output projection is set to rectilinear (not equirectangular). Some scanners can produce quite strong 'shear' distortion, like a parallelogram, if the head is not exactly perpendicular

Re: [hugin-ptx] Hugin Assistant tab changes

On Sat, 30 Jul 2022, 01:46 David W. Jones, wrote: > > Hey, Thomas and Bruno! > > On 7/29/22 09:17, Bruno Postle wrote: > > > The first lets you declare the lens type of your photos (if it can't be > > detected): > > Hmm. It seems complicated for the Assistant, whi

Re: [hugin-ptx] batch panorama with same params

Hi Maarten, you can use an existing Hugin PTO project as a template to stitch further panoramas that have the same arrangement of photos. On the command-line or in a script you can specify replacement input images: nona -o temp_ project.pto left/IMG_0001.jpg right/IMG_0001.jpg ..this will

Re: [hugin-ptx] Screenshots: "No or only partial information about field of view"

Hi Ray, this is an old tutorial, but the technique is the same, basically you can use whatever field of view you like within reason: https://hugin.sourceforge.io/tutorials/scans/ Also, there are easier ways to do this, in Firefox I can right-click a web page and save the entire thing as an image

Re: [hugin-ptx] Precise meaning of control point coordinates?

On Sun, 15 May 2022, 11:34 wrote: > > Imagine each pixel as a square in a very magnified image. I would expect > best behavior if that pixel's integer coordinates represented the center of > that pixel. But maybe some code would be simpler if the pixel's exact > coordinates represented the top

Re: [hugin-ptx] Using align_image_stack for focus stacking

align_image_stack works by identifying useful features (corners) in one photo, and then trying to find a similar collection of pixels in the next photo. It may be that it just isn't very good at catching focus variation. Also, and I haven't checked this, it may be matching all subsequent images

Re: [hugin-ptx] Determining lens distortion parameters from multiple panoramas

On Thu, 28 Apr 2022 at 15:57, Jeff Welty wrote: > On Thursday, April 28, 2022 at 2:33:53 AM UTC-7 Bruno Postle wrote: >> >> Lensfun and panorama tools have a slightly different lens model, so it >> isn't always possible to transfer parameters (I'm not sure if there is >&g

Re: [hugin-ptx] Determining lens distortion parameters from multiple panoramas

Lensfun and panorama tools have a slightly different lens model, so it isn't always possible to transfer parameters (I'm not sure if there is a converter, it wouldn't be difficult to write one if it doesn't exist). The idea of optimising a merged project to get more accurate lens parameters

Re: [hugin-ptx] Re: Default Settings

Hi Michael, it has been quite a while since I have done anything this complex in pto_var ot pano_modify, so I hope somebody else can answer your detailed questions. A couple of things I noticed: You are running cpclean immediately after running cpfind, but cpclean filters control points based on

Re: [hugin-ptx] Re: Default Settings

Generating templates like this is a good approach, and it works well in the GUI and on the command-line. Though I wasn't referring to the python API, the 'Executor' system is used by Hugin when aligning and stitching using the Assistant. It is configurable by editing these INI files. -- Bruno

Re: [hugin-ptx] Re: Default Settings

I'm not at a computer, so I can't point directly to functionality, but I seem to remember that the default Hugin Assistant has an angle of view threshold, below which it chooses rectilinear, and above which it chooses equirectangular. Regarding custom workflows that don't use these default

Re: [hugin-ptx] How to delete masks using command line ?

Masks in a Hugin PTO project are stored in lines of text that begin with the letter 'k'. So, make a copy of the file without any lines beginning with 'k' like this: grep -v '^k' project.pto > new_project.pto -- Bruno On Thu, 14 Apr 2022, 07:13 Noveguy, wrote: > Hi all, > > I need to mask

Re: [hugin-ptx] Create control points button in Photos tab

On Mon, 7 Mar 2022, 12:59 johnfine wrote: > > *1)* If you have only one image selected and the Settings is Vertical > lines, then you get the expected behavior (lines within just that > image). But if the Settings is not Vertical lines, you get the > surprising behavior that your selection of

Re: [hugin-ptx] where make install puts things

On Thu, 3 Mar 2022, 17:36 johnfine wrote: > > Are there options I should have used with CMake to get things to go to the > right place? Or is the place they went "right" and I should have done > something different with the other CMake to find things in that place. > > When I did a *make

Re: [hugin-ptx] Re: Vertical Hugin Panorama of Building has Discontinuity on sides

On Mon, 21 Feb 2022 at 11:46, johnfi...@gmail.com wrote: > On Monday, February 21, 2022 at 5:52:13 AM UTC-5 bruno...@gmail.com wrote: > >> >> The XYZ Translation parameters are initially hidden as they are not >> needed for normal usage, they are made available by selecting Menu -> >> Interface

Re: [hugin-ptx] Re: Vertical Hugin Panorama of Building has Discontinuity on sides

On Mon, 21 Feb 2022 at 02:31, scott092707 wrote: > > I actually did bring up the Optimizer Tab as before (since it solved the > last issue), but the only optimizations presented to me this time were > yaw/pitch/roll. > I'll try again tomorrow (?) and see where one can ADD parameters, and do > the

Re: [hugin-ptx] Problem with Hugin Panorama

Hi Scott, firstly this is primarily a mailing list, so anything you attach gets sent to 2000 mailboxes. Anyway it looks like your problem is that the two photos were not taken from the same position. Hugin assumes that you are stitching a panorama and maps the images as best as it can to a

Re: [hugin-ptx] Mask dialog, can't select just one when close together

On Thu, 10 Feb 2022 at 00:01, johnfi...@gmail.com wrote: > > When points are very close together in a mask, you can't select just one to > move. > > I understand having the points so close is not typical. But the code seems > to have been written anticipating points being that close together

Re: [hugin-ptx] Re: Removing magnifier hiding timer etc. from CPImageCtrl.cpp

On Thu, 3 Feb 2022 at 18:42, T. Modes wrote: > > Okay, this is now reproducible here. It is also a side effect of moving the > selection code from the mouse down to the mouse up handler. > I had to revert this change. I found no way to fix all these issue. > I tried the fix the issue with

Re: [hugin-ptx] Where is the choice to disable the fast preview window documented?

On Sun, 6 Feb 2022 at 23:24, johnfine2017 wrote: > > I eventually found out the method (hold ctrl while starting hugin) and then > found the place that is documented for re enabling fast preview window (it > brings up a dialog that lets you choose). But I didn't find any > documentation of

Re: [hugin-ptx] Re: Removing magnifier hiding timer etc. from CPImageCtrl.cpp

On Wed, 2 Feb 2022 at 16:38, T. Modes wrote: > > bruno...@gmail.com schrieb am Dienstag, 1. Februar 2022 um 23:20:14 UTC+1: >> >> On investigation, it looks like the magnifier doesn't appear when you click >> down on a control point, it only appears once you have dragged it away from >> the

Re: [hugin-ptx] Re: Removing magnifier hiding timer etc. from CPImageCtrl.cpp

On Tue, 1 Feb 2022, 17:53 johnfine wrote: > > I hope Bruno and others will answer your question, because I'm pretty sure > Bruno disliked the current magnifier hiding and would be more competent to > explain why and/or have more mainstream reasons. > I never really considered the possibility

Re: [hugin-ptx] Opinions on warping to fine tune the results of control point optimization?

On Tue, 1 Feb 2022 at 12:53, johnfine2017 wrote: > On Tuesday, February 1, 2022 at 6:56:17 AM UTC-5 bruno...@gmail.com wrote: > >> The remapping and stitching is performed as usual by the Hugin toolchain, >> ptomorph just manipulates the input images a bit to make them stitch better. >> > > By

Re: [hugin-ptx] Opinions on warping to fine tune the results of control point optimization?

On Mon, 31 Jan 2022 at 22:42, johnfi...@gmail.com wrote: > On Monday, January 31, 2022 at 5:06:20 PM UTC-5 bruno...@gmail.com wrote: > >> See the ptomorph proof of concept from ten(!) years ago here: >> https://groups.google.com/g/hugin-ptx/c/UripOuuYXCQ?pli=1 >> >> This works incredibly well,

Re: [hugin-ptx] malfunction in CPImageCtrl when the magnified image has over 2**27 pixels

Hi John, I'm just catching up on my email, do you have access to the Hugin repository yet? If not, then send me your sourceforge username. Note that sourceforge supports a fork/pull-request workflow (similar to github), so you can work on a separate personal repository just as easily as the main

Re: [hugin-ptx] Opinions on warping to fine tune the results of control point optimization?

See the ptomorph proof of concept from ten(!) years ago here: https://groups.google.com/g/hugin-ptx/c/UripOuuYXCQ?pli=1 This works incredibly well, with no need for low-priority control points, but I never pursued it, and it needs some thought regarding getting it to work with more than two

Re: [hugin-ptx] Control Point dialog features

On Sat, 22 Jan 2022 at 11:46, T. Modes wrote: >> >> Basically, the fix is to only centre the current control point in the >> viewports on mouseup, currently it centres on mousedown. > > Okay, now I see. I tested with zoom set to fit. There is was not obviously. > Tried to fix in repository.

Re: [hugin-ptx] Vertical panorama exposure issue

On Sat, 22 Jan 2022 at 18:24, johnfine2017 wrote: > There isn't actually a lot in the panorama above or below the middle image. > The top and bottom images overlap each other a lot in addition to each mostly > overlapping the middle. The original middle image isn't very distorted > (vertical

Re: [hugin-ptx] building hugin on fedora

On Sat, 22 Jan 2022 at 15:39, johnfine2017 wrote: > I got build instructions both from > https://wiki.panotools.org/Hugin_Compiling_Fedora > and from a recent post by Bruno suggesting > The list of things to install is very different between those two sources. > Is that first one obsolete?

Re: [hugin-ptx] Control Point dialog features

On Sat, 22 Jan 2022 at 01:17, johnfine wrote: > On Friday, January 21, 2022 at 7:20:51 PM UTC-5 bruno...@gmail.com wrote: > > Without a clear statement of the original intent, there is no way I would try > to fix the code for removing the magnifier to behave as intended and > predictably. I'm

Re: [hugin-ptx] Control Point dialog features

On Sat, 22 Jan 2022 at 08:57, T. Modes wrote: > bruno...@gmail.com schrieb am Samstag, 22. Januar 2022 um 01:20:51 UTC+1: >> >> When zoomed-in, if I go to drag a control point that is not in the >> centre of the viewport then the view jumps to centre the viewport on >> this location - but my mouse

Re: [hugin-ptx] Vertical panorama exposure issue

On Sat, 22 Jan 2022 at 00:16, johnfine2017 wrote: > > I still think that what I want for the main problem is to pre-shift the > exposure within each photo based on relative (within each image) vertical > position. I think I know which open source tool will make that fairly easy > (once I learn

Re: [hugin-ptx] Control Point dialog features

On Fri, 21 Jan 2022 at 18:34, johnfine2017 wrote: > > I want to make a bunch of changes to the control point dialog. > 1) Max resolution. 200% really isn't enough for me to place control points > easily. I don't know what puts me or my photos or my large high res displays > outside the usual

Re: [hugin-ptx] Vertical panorama exposure issue

On Fri, 21 Jan 2022 at 21:47, johnfine2017 wrote: > > I'm trying to assemble a specific vertical panorama, but also trying to learn > methods for assembling a vertical panorama. > > One major issue (that I'm furthest from figuring out on my own) is the > exposure issue: > Taken on a cell phone

Re: [hugin-ptx] Endless loop?

The optimiser can take a very long time with difficult projects. Is this with Hugin 2021.0? or an earlier version? This latest Hugin was released together with libpano13-2.9.21, which has had major changes to the optimiser. Can you attach a PTO project that shows the problem? (there is no need

Re: [hugin-ptx] Re: How to export panos to Google Maps?

On Tue, 4 Jan 2022, 13:33 Carlo, wrote: > > Stitched with Hugin and "reworked" with Gimp. There are no special > metadata in this file. > I uploaded this image 6000×3000 to my photos.google folder. > Note that Hugin adds the Google panorama metadata automatically whenever you stitch a project.

Re: [hugin-ptx] Re: How to export panos to Google Maps?

On Tue, 4 Jan 2022, 12:03 Carlo, wrote: > Can anyone see this one? > https://goo.gl/maps/xJxgPLeSrAdgLmQHA > I just published it with iPhone and the Street View app. > Works for me, launches in the Google maps app on Android - Bruno > -- A list of frequently asked questions is available at:

[hugin-ptx] libpano13-2.9.21 released

is equivalent to HG 906:2d4aeb9ca433 Here is the full ChangeLog since 2.9.20 for more details: 2021-12-13 17:25 +0100 tmodes(1f44b6e37e89) * panorama.h: Fixes big endian check for FreeBSD 2021-11-29 20:46 + Bruno Postle(cdd43e6c053c) * ChangeLog.hg

Re: [hugin-ptx] help for new user

On Mon, 27 Dec 2021, 18:38 dgjohnston, wrote: > > Bruno … thanks for your quick responses on this forum. It is very much > appreciated. > 1. Am I correct in saying that when hugin optimizes for translation that > the canvas always stays at 0,0,1 and then the x,y,z values basically move > the

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 15:43 johnfi...@gmail.com, wrote: > > On Monday, December 27, 2021 at 9:56:13 AM UTC-5 bruno...@gmail.com wrote: > >> all the images are projected is at a Z distance of 1. >> > > I'm taking that as the definition of the units X, Y and Z are all in. I > want to use some math

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 15:37 Donald Johnston, wrote: > Bruno, when hugin loads a number of photos does it base its initial Z > value for the output camera on the photo marked as the anchor? > And then optimize other Z values to that? > The xyz values for the viewpoint of the output panorama are

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 13:41 johnfi...@gmail.com, wrote: > " you will need to use all of these, but not all at once - this can > confuse the optimiser. " > > I want to understand that detail. Photos tab: Optimize Geometric: the > calculate button: > Does it start from zero when you click it or

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 13:24 johnfi...@gmail.com, wrote: > > X and Y should hold the major values BUT I don't yet understand what units > they are in: In the test I just ran, they must be quite big units because > a value of 0.1 is big. > The 'camera' for the output panorama is at 0,0,0 and the

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 12:47 Jon Schewe, wrote: > > When I specify recilinear as the output projection I get a warning from > Hugin "With a wide field of view, panoramas with rectilinear projection get > very stretched towards the edges. For a very wide panorama, try > equirectangular projection

Re: [hugin-ptx] Re: help for new user

On Mon, 27 Dec 2021, 00:33 Jon Schewe, wrote: > On Mon, 2021-12-27 at 00:20 +0000, Bruno Postle wrote: > > > For your document assembly project, you will need to use all of these, but > not all at once - this can confuse the optimiser. I suggest starting with > translation, th

Re: [hugin-ptx] Re: help for new user

On Sun, 26 Dec 2021, 23:57 Jon Schewe, wrote: > > Is there a good reference for what the following terms mean to Hugin? > Position > View > Translation > Barrel > Position is roll, pitch and yaw. View is the horizontal lens angle of view. Translation is xyz position of the camera. Barrel is the

Re: [hugin-ptx] Focus stacking together with panorama assembly

On Tue, 21 Dec 2021 at 23:40, john wrote: > > I will keep trying things. But from what I've tested so far, that idea > doesn't work (Align within stacks and combine each stack before combining the > results into a panorama.) > > A "similar" layout isn't nearly good enough. The layout would

  1   2   3   4   5   6   7   8   9   10   >