Re: [hugin-ptx] Re: Default Settings
Should anyone be interested, this is a script developed for stitching (mosaic) images in a folder prior to tidying up rotation, fine-tuning CPs, adjusting FoV and stitching in Hugin. #!/bin/bash pto_gen -p 0 -f 40.7 -c 200,5560,133,3707 -o project.pto *.tif cpfind --multirow --fullscale --sieve1width 12 --sieve1height 8 --sieve2width 4 --sieve2height 4 --sieve2size 1 -o project_cp.pto project.pto pto_var --set=r=90 --opt=TrX,TrY -o project_XY.pto project_cp.pto autooptimiser -n -o project_XY.pto project_XY.pto pto_var --opt=y,y0,p,p0,TrZ -o project_ypZ.pto project_XY.pto autooptimiser -n -o project_ypZ.pto project_ypZ.pto pto_var --opt=y,y0,p,p0,TrX,TrY,TrZ -o project_ypXYZ.pto project_ypZ.pto autooptimiser -n -o project_ypXYZ.pto project_ypXYZ.pto cpclean --fast -o project_clean.pto project_cp.pto pto_var --opt=y,y0,p,p0,TrX,TrY,TrZ -o project_ypXYZ.pto project_ypXYZ.pto autooptimiser -n -o project_ypXYZ.pto project_ypXYZ.pto pano_modify --projection=0 --fov=AUTO -o finished.pto project_ypXYZ.pto On Friday, 29 April 2022 at 13:05:52 UTC+1 Michael Perry wrote: > Thank you, that works simply and perfectly > > > On Thursday, 28 April 2022 at 16:30:21 UTC+1 T. Modes wrote: > >> michae...@mac.com schrieb am Donnerstag, 28. April 2022 um 12:23:49 >> UTC+2: >> >>> pto_var: can anyone tell me whether there is a way to specify, for >>> example, optimising yaw of all images including the anchor without having >>> to specify each image? >>> >>> Thus, some sort of: >>> --opt=yALL >>> rather than >>> --opt=y0,y1,y2,y3,y4… >>> >> >> Assuming anchor is first image (image index 0): >> pto_var --opt=y,y0 >> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/86d945cd-fa6a-4119-bfaa-80d43451cd9dn%40googlegroups.com.
[hugin-ptx] Re: Control Point Bias
Thank you Florian; I can see a logic in your statement. However, I still think there is something odd with this. It may be a particular result of working with mosaic stitching in very controlled conditions; the images making up my panoramas are laid out on a regular grid and my control points are often repeated between multiple images. My "errors" always tend to be the control points towards the edges, those which are only in two images. My best CPs are always those towards the centre of any four images. This is because, I believe, the optimisation prioritises points equally across the panorama/mosaic. However, if one set of points is repeated many times, the model will tend to exaggerate the correctness of those points over the equally important points at the edge. I think your weighting feature in Hugin++ could be very helpful. On Friday, 6 May 2022 at 18:14:44 UTC+1 Florian Königstein wrote: > Since every control point connects only two images, it's normal and > reasonable that you have more CPs in the intersection of 4 images. Every CP > generates constraints on the relative position of two images. > > In Hugin++ you could set weights for control points. However, this should > in most cases only be necessary when you have "good" CPs and "bad" CPs > (e.g. due to moving objects) and you have no other choice but keeping some > of the "bad" CPs. Then you can assign higher weights for good CPs and/or > lower weights for bad CPs. > michae...@mac.com schrieb am Freitag, 29. April 2022 um 14:54:49 UTC+2: > >> Is there not a bias in the way Hugin optimises; that control points at >> the intersection of four images will be weighted three more times than >> those at the intersection of the pair of images above or below? The larger >> error in control points always tend to be the furthest from the centre. >> >> Without manually adding control points away from the 4-way intersection >> (or removing those in the centre), is there some way to compensate for this >> with cpfind or autooptimiser? >> >> (Hoping the attached image posts) >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/00f4f2e9-8eb8-46c1-9433-3ee363670591n%40googlegroups.com.
[hugin-ptx] Control Point Bias
Is there not a bias in the way Hugin optimises; that control points at the intersection of four images will be weighted three more times than those at the intersection of the pair of images above or below? The larger error in control points always tend to be the furthest from the centre. Without manually adding control points away from the 4-way intersection (or removing those in the centre), is there some way to compensate for this with cpfind or autooptimiser? (Hoping the attached image posts) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ddaa8581-edd2-4a29-b399-60e5e9d9732en%40googlegroups.com.
Re: [hugin-ptx] Re: Default Settings
Thank you, that works simply and perfectly On Thursday, 28 April 2022 at 16:30:21 UTC+1 T. Modes wrote: > michae...@mac.com schrieb am Donnerstag, 28. April 2022 um 12:23:49 UTC+2: > >> pto_var: can anyone tell me whether there is a way to specify, for >> example, optimising yaw of all images including the anchor without having >> to specify each image? >> >> Thus, some sort of: >> --opt=yALL >> rather than >> --opt=y0,y1,y2,y3,y4… >> > > Assuming anchor is first image (image index 0): > pto_var --opt=y,y0 > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/bfdfe96c-2b46-467c-848c-d93423634509n%40googlegroups.com.
Re: [hugin-ptx] Re: Default Settings
pto_var: can anyone tell me whether there is a way to specify, for example, optimising yaw of all images including the anchor without having to specify each image? Thus, some sort of: --opt=yALL rather than --opt=y0,y1,y2,y3,y4… On Thursday, 28 April 2022 at 10:39:12 UTC+1 Michael Perry wrote: > Bruno, thank you for replying and so quickly. > > cpclean - I shall move this, optimise and re-optimise as you suggest. > > vignetting - I believe I do not need to optimise exposure as I am shooting > in controlled lighting (it does not change). In practice I use a raking > light; so I don't want anything to happen to exposure until I get to > Photoshop where I can apply a neutral gradient to correct it. > > mosaic drag - yes, it resets on opening Hugin, it's not stored in the .pto > nor, sadly, in the plist. I suppose it is hard-wired in the programme > somehow. > > I wonder if future incarnations of Hugin could include preferences for the > Optimiser (orientation parameters) and Fast Panorama Preview (mosaic drag > and projections) > > On Wednesday, 27 April 2022 at 23:12:41 UTC+1 bruno...@gmail.com wrote: > >> 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 how well they optimise, so you should >> run it after optimisation, or at least after you have set all your >> optimisation parameters. Then usually you would run optimisation again >> after running cpclean. >> >> Although fixing barrel distortion in an external tool should be fine, >> you might want to let Hugin optimise vignetting if you are also >> optimising exposure, Hugin uses the exposure distribution caused by >> the vignetting to calculate the camera response curve. >> >> I don't think Hugin settings like mosaic drag mode are stored in the >> PTO file, in which case it wouldn't be possible to set this on the >> command-line. >> >> -- >> Bruno >> >> On Wed, 27 Apr 2022 at 19:30, 'Michael Perry' wrote: >> >> > I am converting my workflow to the command line. I have a problem with >> pto_var and a question about pano_modify, I wonder if you can advise me. >> > >> > BACKGROUND >> > >> > I am stitching a mosaic of images of a painting. The photographs have >> been shot with a camera mounted on a gimbal that is itself suspended on an >> X-Y frame. The biggest difference between one image and the next is its X-Y >> position. In theory they should all have the same pitch and yaw as the >> camera moves little on its gimbal. There is some slight Z to account for as >> the frame is not perfectly parallel to the painting. The images have to be >> rotated some 90 degrees. >> > >> > The images have been pre-processed for lens distortion and vignetting >> with Capture One, so I am ignoring lens parameters. >> > >> > COMMAND LINE >> > >> > I have been using the following commands to build the .pto file. I have >> annotated them in case it is useful for other people >> > >> > pto_gen -p 0 -f 40.7 -o project.pto *.tif >> > >> > (create the project with all files in folder, rectilinear projection >> and a 50mm lens (FOV = 40.7) >> > >> > cpfind --multirow --fullscale -o project_cp.pto project.pto >> > >> > (find control points in a mosaic, full-scale probably not necessary for >> me) >> > >> > cpclean -o project_clean.pto project_cp.pto >> > >> > (clean control points) >> > >> > pto_var --set=r=90 --opt=TrX,TrY -o project_XY.pto project_clean.pto >> > >> > (set X-Y variables of all images EXCEPT anchor, for optimisation) >> > >> > autooptimiser -n -o project_XY.pto project_XY.pto >> > >> > (optimise images for X and Y) >> > >> > pto_var --opt=y,p,TrZ -o project_ypZ.pto project_XY.pto >> > >> > (set pitch, yaw and Z of all images EXCEPT anchor) >> > >> > This is where I have the problem, I need to select the yaw and pitch of >> the anchor image for optimisation with all the rest. I can not see how to >> do that easily. >> > >> > POSSIBLE SOLUTION >> > >> > pto_var --opt=y0,p0,y1,p1,TrZ -o project_ypXYZ.pto project_ypZ.pto >> > >> > (set pitch, y
Re: [hugin-ptx] Re: Default Settings
Bruno, thank you for replying and so quickly. cpclean - I shall move this, optimise and re-optimise as you suggest. vignetting - I believe I do not need to optimise exposure as I am shooting in controlled lighting (it does not change). In practice I use a raking light; so I don't want anything to happen to exposure until I get to Photoshop where I can apply a neutral gradient to correct it. mosaic drag - yes, it resets on opening Hugin, it's not stored in the .pto nor, sadly, in the plist. I suppose it is hard-wired in the programme somehow. I wonder if future incarnations of Hugin could include preferences for the Optimiser (orientation parameters) and Fast Panorama Preview (mosaic drag and projections) On Wednesday, 27 April 2022 at 23:12:41 UTC+1 bruno...@gmail.com wrote: > 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 how well they optimise, so you should > run it after optimisation, or at least after you have set all your > optimisation parameters. Then usually you would run optimisation again > after running cpclean. > > Although fixing barrel distortion in an external tool should be fine, > you might want to let Hugin optimise vignetting if you are also > optimising exposure, Hugin uses the exposure distribution caused by > the vignetting to calculate the camera response curve. > > I don't think Hugin settings like mosaic drag mode are stored in the > PTO file, in which case it wouldn't be possible to set this on the > command-line. > > -- > Bruno > > On Wed, 27 Apr 2022 at 19:30, 'Michael Perry' wrote: > > > I am converting my workflow to the command line. I have a problem with > pto_var and a question about pano_modify, I wonder if you can advise me. > > > > BACKGROUND > > > > I am stitching a mosaic of images of a painting. The photographs have > been shot with a camera mounted on a gimbal that is itself suspended on an > X-Y frame. The biggest difference between one image and the next is its X-Y > position. In theory they should all have the same pitch and yaw as the > camera moves little on its gimbal. There is some slight Z to account for as > the frame is not perfectly parallel to the painting. The images have to be > rotated some 90 degrees. > > > > The images have been pre-processed for lens distortion and vignetting > with Capture One, so I am ignoring lens parameters. > > > > COMMAND LINE > > > > I have been using the following commands to build the .pto file. I have > annotated them in case it is useful for other people > > > > pto_gen -p 0 -f 40.7 -o project.pto *.tif > > > > (create the project with all files in folder, rectilinear projection and > a 50mm lens (FOV = 40.7) > > > > cpfind --multirow --fullscale -o project_cp.pto project.pto > > > > (find control points in a mosaic, full-scale probably not necessary for > me) > > > > cpclean -o project_clean.pto project_cp.pto > > > > (clean control points) > > > > pto_var --set=r=90 --opt=TrX,TrY -o project_XY.pto project_clean.pto > > > > (set X-Y variables of all images EXCEPT anchor, for optimisation) > > > > autooptimiser -n -o project_XY.pto project_XY.pto > > > > (optimise images for X and Y) > > > > pto_var --opt=y,p,TrZ -o project_ypZ.pto project_XY.pto > > > > (set pitch, yaw and Z of all images EXCEPT anchor) > > > > This is where I have the problem, I need to select the yaw and pitch of > the anchor image for optimisation with all the rest. I can not see how to > do that easily. > > > > POSSIBLE SOLUTION > > > > pto_var --opt=y0,p0,y1,p1,TrZ -o project_ypXYZ.pto project_ypZ.pto > > > > (set pitch, yaw and Z of all images INCLUDING anchor) > > > > It is possible to select the anchor if each image is individually > selected. HOWEVER when large mosaics are stitched it makes for clumsy code. > > > > EXTRA QUESTION > > > > pano_modify --projection=0 --fov=AUTO -o finished.pto project_ypXYZ.pto > > > > (Set projection to Rectilinear, fit image to screen) > > > > I finalise the image in Fast Panorama preview having set Projection to > Rectilinear and fitted the image to the screen. It would be helpful if I > could also set the Drag Mode to Mosaic in the Move/Drag tab and the > Overview Mode to Mosaic Plane. Is there some code that might effect this? > > > > Hoping you will find these inter
Re: [hugin-ptx] Re: Default Settings
Dear Bruno I am converting my workflow to the command line. I have a problem with pto_var and a question about pano_modify, I wonder if you can advise me. BACKGROUND I am stitching a mosaic of images of a painting. The photographs have been shot with a camera mounted on a gimbal that is itself suspended on an X-Y frame. The biggest difference between one image and the next is its X-Y position. In theory they should all have the same pitch and yaw as the camera moves little on its gimbal. There is some slight Z to account for as the frame is not perfectly parallel to the painting. The images have to be rotated some 90 degrees. The images have been pre-processed for lens distortion and vignetting with Capture One, so I am ignoring lens parameters. COMMAND LINE I have been using the following commands to build the .pto file. I have annotated them in case it is useful for other people pto_gen -p 0 -f 40.7 -o project.pto *.tif (create the project with all files in folder, rectilinear projection and a 50mm lens (FOV = 40.7) cpfind --multirow --fullscale -o project_cp.pto project.pto (find control points in a mosaic, full-scale probably not necessary for me) cpclean -o project_clean.pto project_cp.pto (clean control points) pto_var --set=r=90 --opt=TrX,TrY -o project_XY.pto project_clean.pto (set X-Y variables of all images EXCEPT anchor, for optimisation) autooptimiser -n -o project_XY.pto project_XY.pto (optimise images for X and Y) pto_var --opt=y,p,TrZ -o project_ypZ.pto project_XY.pto (set pitch, yaw and Z of all images EXCEPT anchor) This is where I have the problem, I need to select the yaw and pitch of the anchor image for optimisation with all the rest. I can not see how to do that easily. POSSIBLE SOLUTION pto_var --opt=y0,p0,y1,p1,TrZ -o project_ypXYZ.pto project_ypZ.pto (set pitch, yaw and Z of all images INCLUDING anchor) It is possible to select the anchor if each image is individually selected. HOWEVER when large mosaics are stitched it makes for clumsy code. EXTRA QUESTION pano_modify --projection=0 --fov=AUTO -o finished.pto project_ypXYZ.pto (Set projection to Rectilinear, fit image to screen) I finalise the image in Fast Panorama preview having set Projection to Rectilinear and fitted the image to the screen. It would be helpful if I could also set the Drag Mode to Mosaic in the Move/Drag tab and the Overview Mode to Mosaic Plane. Is there some code that might effect this? Hoping you will find these interesting problems. Michael On Tuesday, 26 April 2022 at 15:34:22 UTC+1 Michael Perry wrote: > Oh! How exciting. I had not come across this Executor system - I will > search for it. Thank you > > > On Friday, 15 April 2022 at 18:05:13 UTC+1 bruno...@gmail.com wrote: > >> 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 >> >> On Fri, 15 Apr 2022, 13:54 'Michael Perry' via hugin and other free >> panoramic software, wrote: >> >>> Bruno, thank you - However, I suspect that the Python Plugin Interface >>> (which I believe is what I would need to do that) does not work with the >>> OSX version of Hugin. I can not find it in my Preferences menus nor an >>> angle of view threshold. I think instead that I will create a library of >>> .pto files (1 x 2 frames , 2 x 2 frames, 2 x 3 frames, 3 x 3 frames and so >>> on) where I would just need to substitute the filenames of my >>> images, preset an XY optimisation, and then find control points, and then >>> optimise pitch, yaw and Z. >>> >>> >>> On Thursday, 14 April 2022 at 14:39:21 UTC+1 bruno...@gmail.com wrote: >>> >> 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 Assistant >>>> settings (again, I can't point to this off the top of my head), there are >>>> a >>>> series of Hugin 'executor' configurations that you can use instead. These >>>> are in an easy-to-edit INI format, so you are encouraged to modify, create >>>> and share. I haven't played with them since they were first introduced, it >>>> would be really useful if you could try this method and describe your >>>> success or failur
Re: [hugin-ptx] Create control points button in Photos tab
"I seem to remember that you can select more than one photo and it will generate points just for that set" Yes, this is also a useful way of adding a bias to an optimisation I think - by adding in extra links for the less well correlated images, countering the success of the better matches. Also, sometimes, Hugin fails to find control points in large arrays. Selecting subsets of images in the photos tab is a good way to force find these control points. On Monday, 7 March 2022 at 20:34:52 UTC bruno...@gmail.com wrote: > 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 one image is ignored and you get >> more CPs connecting everything to everything. >> > > I can't check right now, and I've only ever used this button to create > control points for all images, but I seem to remember that you can select > more than one photo and it will generate points just for that set. > > Also it is worth checking to see if the equivalent button in the fast > preview does something more like what you are expecting. > > -- > 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 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/61c53b70-af35-453b-8f78-62211d0ea225n%40googlegroups.com.
Re: [hugin-ptx] Re: Default Settings
Oh! How exciting. I had not come across this Executor system - I will search for it. Thank you On Friday, 15 April 2022 at 18:05:13 UTC+1 bruno...@gmail.com wrote: > 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 > > On Fri, 15 Apr 2022, 13:54 'Michael Perry' via hugin and other free > panoramic software, wrote: > >> Bruno, thank you - However, I suspect that the Python Plugin Interface >> (which I believe is what I would need to do that) does not work with the >> OSX version of Hugin. I can not find it in my Preferences menus nor an >> angle of view threshold. I think instead that I will create a library of >> .pto files (1 x 2 frames , 2 x 2 frames, 2 x 3 frames, 3 x 3 frames and so >> on) where I would just need to substitute the filenames of my >> images, preset an XY optimisation, and then find control points, and then >> optimise pitch, yaw and Z. >> >> >> On Thursday, 14 April 2022 at 14:39:21 UTC+1 bruno...@gmail.com wrote: >> > 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 Assistant >>> settings (again, I can't point to this off the top of my head), there are a >>> series of Hugin 'executor' configurations that you can use instead. These >>> are in an easy-to-edit INI format, so you are encouraged to modify, create >>> and share. I haven't played with them since they were first introduced, it >>> would be really useful if you could try this method and describe your >>> success or failure here, as they are an underused resource that more people >>> would use if they were aware. >>> >>> On Thu, 14 Apr 2022, 11:58 'Michael Perry' via hugin and other free >>> panoramic software, wrote: >>> >>>> Is there a way to get the Hugin 2019.2.0 to use Rectilinear Projection >>>> as its default projection rather than Equirectangular? >>>> >>>> On Thursday, 25 February 2021 at 13:00:58 UTC Michael Perry wrote: >>>> >>>>> I wonder if there is anyone in the forum who has a view about this? >>>>> >>>>> On Saturday, 22 August 2020 at 15:31:54 UTC+1 Michael Perry wrote: >>>>> >>>>>> Can anyone advise me how to change the default settings for y, p, r, >>>>>> X, Y, projection (to and move/drag (to mosaic) >>>>>> Also, is there some way that I can restrict the clustering of control >>>>>> points - reducing the number of points created in similar locations - >>>>>> I'd >>>>>> rather have 5 well-spaced control points per overlap than 25 control >>>>>> points >>>>>> >>>>>> thank you >>>>>> >>>>>> On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote: >>>>>> >>>>>>> I use Hugin to stitch mosaics. I find the best procedure is to >>>>>>> optimise for X and Y before y, p and r. I have to select Custom >>>>>>> parameters >>>>>>> to be able to do this, then after de-selecting yaw, pitch and roll in >>>>>>> the >>>>>>> Optimiser tab, I select the X and Y variables columns in their place. >>>>>>> >>>>>>> Is there a way to change the default settings for Hugin so that, on >>>>>>> opening the application: >>>>>>> a) Custom parameters is always selected in Photos tab and X and Y >>>>>>> columns are selected in the Custom tab? >>>>>>> b) Similarly, is there a way to change the default projection from >>>>>>> Equirectangular to Rectilinear? >>>>>>> >>>>>>> Thank you for your thoughts >>>>>>> >>>>>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/daa30aa3-9cd5-4d99-be19-7ddeab079560n%40googlegroups.com.
Re: [hugin-ptx] Re: Default Settings
Bruno, thank you - However, I suspect that the Python Plugin Interface (which I believe is what I would need to do that) does not work with the OSX version of Hugin. I can not find it in my Preferences menus nor an angle of view threshold. I think instead that I will create a library of .pto files (1 x 2 frames , 2 x 2 frames, 2 x 3 frames, 3 x 3 frames and so on) where I would just need to substitute the filenames of my images, preset an XY optimisation, and then find control points, and then optimise pitch, yaw and Z. -- Michael On Thursday, 14 April 2022 at 14:39:21 UTC+1 bruno...@gmail.com wrote: > 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 Assistant settings > (again, I can't point to this off the top of my head), there are a series > of Hugin 'executor' configurations that you can use instead. These are in > an easy-to-edit INI format, so you are encouraged to modify, create and > share. I haven't played with them since they were first introduced, it > would be really useful if you could try this method and describe your > success or failure here, as they are an underused resource that more people > would use if they were aware. > > -- > Bruno > > > On Thu, 14 Apr 2022, 11:58 'Michael Perry' via hugin and other free > panoramic software, wrote: > >> Is there a way to get the Hugin 2019.2.0 to use Rectilinear Projection as >> its default projection rather than Equirectangular? >> >> On Thursday, 25 February 2021 at 13:00:58 UTC Michael Perry wrote: >> >>> I wonder if there is anyone in the forum who has a view about this? >>> >>> On Saturday, 22 August 2020 at 15:31:54 UTC+1 Michael Perry wrote: >>> >>>> Can anyone advise me how to change the default settings for y, p, r, X, >>>> Y, projection (to and move/drag (to mosaic) >>>> Also, is there some way that I can restrict the clustering of control >>>> points - reducing the number of points created in similar locations - I'd >>>> rather have 5 well-spaced control points per overlap than 25 control points >>>> >>>> thank you >>>> >>>> On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote: >>>> >>>>> I use Hugin to stitch mosaics. I find the best procedure is to >>>>> optimise for X and Y before y, p and r. I have to select Custom >>>>> parameters >>>>> to be able to do this, then after de-selecting yaw, pitch and roll in the >>>>> Optimiser tab, I select the X and Y variables columns in their place. >>>>> >>>>> Is there a way to change the default settings for Hugin so that, on >>>>> opening the application: >>>>> a) Custom parameters is always selected in Photos tab and X and Y >>>>> columns are selected in the Custom tab? >>>>> b) Similarly, is there a way to change the default projection from >>>>> Equirectangular to Rectilinear? >>>>> >>>>> Thank you for your thoughts >>>>> >>>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/f2cbe1b1-0405-466d-88e0-2cbd2bab38c5n%40googlegroups.com.
[hugin-ptx] Re: Default Settings
Is there a way to get the Hugin 2019.2.0 to use Rectilinear Projection as its default projection rather than Equirectangular? On Thursday, 25 February 2021 at 13:00:58 UTC Michael Perry wrote: > I wonder if there is anyone in the forum who has a view about this? > > > On Saturday, 22 August 2020 at 15:31:54 UTC+1 Michael Perry wrote: > >> Can anyone advise me how to change the default settings for y, p, r, X, >> Y, projection (to and move/drag (to mosaic) >> Also, is there some way that I can restrict the clustering of control >> points - reducing the number of points created in similar locations - I'd >> rather have 5 well-spaced control points per overlap than 25 control points >> >> thank you >> >> On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote: >> >>> I use Hugin to stitch mosaics. I find the best procedure is to optimise >>> for X and Y before y, p and r. I have to select Custom parameters to be >>> able to do this, then after de-selecting yaw, pitch and roll in the >>> Optimiser tab, I select the X and Y variables columns in their place. >>> >>> Is there a way to change the default settings for Hugin so that, on >>> opening the application: >>> a) Custom parameters is always selected in Photos tab and X and Y >>> columns are selected in the Custom tab? >>> b) Similarly, is there a way to change the default projection from >>> Equirectangular to Rectilinear? >>> >>> Thank you for your thoughts >>> >>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/eea4b896-c667-4418-a6c6-2410a47959c4n%40googlegroups.com.
[hugin-ptx] Re: Default Settings
I wonder if there is anyone in the forum who has a view about this? On Saturday, 22 August 2020 at 15:31:54 UTC+1 Michael Perry wrote: > Can anyone advise me how to change the default settings for y, p, r, X, Y, > projection (to and move/drag (to mosaic) > Also, is there some way that I can restrict the clustering of control > points - reducing the number of points created in similar locations - I'd > rather have 5 well-spaced control points per overlap than 25 control points > > thank you > > On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote: > >> I use Hugin to stitch mosaics. I find the best procedure is to optimise >> for X and Y before y, p and r. I have to select Custom parameters to be >> able to do this, then after de-selecting yaw, pitch and roll in the >> Optimiser tab, I select the X and Y variables columns in their place. >> >> Is there a way to change the default settings for Hugin so that, on >> opening the application: >> a) Custom parameters is always selected in Photos tab and X and Y columns >> are selected in the Custom tab? >> b) Similarly, is there a way to change the default projection from >> Equirectangular to Rectilinear? >> >> Thank you for your thoughts >> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/e3c72a67-54b7-492d-be53-ecfc1c4ec62en%40googlegroups.com.
[hugin-ptx] Re: Default Settings
Can anyone advise me how to change the default settings for y, p, r, X, Y, projection (to and move/drag (to mosaic) Also, is there some way that I can restrict the clustering of control points - reducing the number of points created in similar locations - I'd rather have 5 well-spaced control points per overlap than 25 control points thank you On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote: > I use Hugin to stitch mosaics. I find the best procedure is to optimise > for X and Y before y, p and r. I have to select Custom parameters to be > able to do this, then after de-selecting yaw, pitch and roll in the > Optimiser tab, I select the X and Y variables columns in their place. > > Is there a way to change the default settings for Hugin so that, on > opening the application: > a) Custom parameters is always selected in Photos tab and X and Y columns > are selected in the Custom tab? > b) Similarly, is there a way to change the default projection from > Equirectangular to Rectilinear? > > Thank you for your thoughts > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/49c75b3f-01e3-476a-836d-eb785bc3c761n%40googlegroups.com.
[hugin-ptx] Default Settings
I use Hugin to stitch mosaics. I find the best procedure is to optimise for X and Y before y, p and r. I have to select Custom parameters to be able to do this, then after de-selecting yaw, pitch and roll in the Optimiser tab, I select the X and Y variables columns in their place. Is there a way to change the default settings for Hugin so that, on opening the application: a) Custom parameters is always selected in Photos tab and X and Y columns are selected in the Custom tab? b) Similarly, is there a way to change the default projection from Equirectangular to Rectilinear? Thank you for your thoughts -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/b9901d4d-59c6-4398-a386-fe9373f239ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Weird-looking Fast Preview window
Me too on OSX 10.7.5. Quite irregular, though I will pay more attention next time On Thursday, November 6, 2014 5:55:42 PM UTC, Frederic Da Vitoria wrote: 2014-11-06 18:34 GMT+01:00 John Muccigrosso jmuc...@gmail.com javascript:: Hugin 2014 RC4 on a MacBook Pro running OS X 10.9.5 with Intel HD Graphics 3000 512 MB Not always, but often I get weird previews in the Fast Preview window. See the attached. The stitching will go just fine, but of course I can't use any of the functions in Fast Preview. Any help? I sometimes get this too on Windows. I may be wrong, but I recently managed to get the preview correctly by just closing Hugin and then loading it again. But I think (I did not pay much attention) that sometimes this did not work. -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/24f76704-cb11-4ad7-b291-92441b3075ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Mosaics
Terry, Bruno Thank you for your comments. I am using Hugin 2014.0.0-RC4. On a typical 4-shot stitch (2 x 2 tiles) Optimising in XYZ, I get maximum error of 2.2 Adding in y,p,r reduces error to 0.75 Changing Hfov from 50 to 10 reduces maximum error from 0.75 to 0.16 In another case, changing Hfov from 50 to 10 reduces maximum error from 0.8 to 0.15 Maybe I am being over-greedy for optimisation but when I see hand held examples delivering maximum control point distances below 1.0, I think the copy stand should be able to get much better results. On Thursday, October 16, 2014 10:50:28 PM UTC+1, Tduell wrote: Hello Michael, On Fri, 17 Oct 2014 04:35:46 +1100, Michael Perry michae...@mac.com javascript: wrote: 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. I haven't tried to stitch shots from a copy stand as you describe, so this is a bit of guess. I would think that you should be optimising all your translation parameters (X,Y,Z). When the camera slides in X and Y the Z value will probably alter, although only a very small amount. Stitching images from a flat scanner is a close approximation to your case, as you're using a calibrated lens. For scanned images I get good results optimising positions and translations. If I also optimise view I don't see hfov vary very much. Try optimising positions and translation (y,p,r,X,Y,Z). Which version of hugin are you using? 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/55091299-500e-4107-84d2-2ba61499d37c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] 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+unsubscr...@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.
[hugin-ptx] 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+unsubscr...@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.
[hugin-ptx] cpfind
For me, cpfind is incredibly accurate at identifying control points with paintings and photographs. Today I have tried to stitch some maps. The control point selection was not at all accurate. Worse, when I manually chose control points, hugin informed me that my point were not correlated. Has anyone else suffered this image with diagrams? What was the solution? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ab5aa0f7-b36e-45df-8ac9-ea9a6eeb4473%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] cpfind
On Friday, December 6, 2013 1:44:15 AM UTC, Tduell wrote: Hello Michael, On Fri, 06 Dec 2013 12:07:15 +1100, Michael Perry michae...@mac.comjavascript: wrote: For me, cpfind is incredibly accurate at identifying control points with paintings and photographs. Today I have tried to stitch some maps. The control point selection was not at all accurate. Worse, when I manually chose control points, hugin informed me that my point were not correlated. Has anyone else suffered this image with diagrams? What was the solution? I have stitched maps in the past, and seem to recall that maps tend to have a lot of identical symbols and line work, which can confuse the control point detector. If you haven't already done so, I would suggest trying to manually fine tune the control points to improve accuracy. If that doesn't help then there may some other problem and it might be necessary to have a look a pair of your images that are giving you trouble. See how go with fine tuning and let's know how you get on. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/b26d8652-cab0-4edc-a53c-a04fe8632f62%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] cpfind
Thank you for being so prompt with your thoughts. Hugin (cpfind and cpfind pre aligned) were making many non-matches - such as the T of Tumulus with the second U of Tumulus. Really surprising after the magic of spot accurate matching of hundreds of photographs of paintings. I think my problem is, perhaps, in the overlaps. I was trying to use a 15-20% overlap, using 35-40% has made all the difference. I also restarted. Hmm. I will try to replicate the problem when I have some more time. Fine Tuning: I find fine tuning both effective and elegant but it was not the issue here - my errors were huge. thanks again though Michael On Friday, December 6, 2013 1:44:15 AM UTC, Tduell wrote: Hello Michael, On Fri, 06 Dec 2013 12:07:15 +1100, Michael Perry michae...@mac.comjavascript: wrote: For me, cpfind is incredibly accurate at identifying control points with paintings and photographs. Today I have tried to stitch some maps. The control point selection was not at all accurate. Worse, when I manually chose control points, hugin informed me that my point were not correlated. Has anyone else suffered this image with diagrams? What was the solution? I have stitched maps in the past, and seem to recall that maps tend to have a lot of identical symbols and line work, which can confuse the control point detector. If you haven't already done so, I would suggest trying to manually fine tune the control points to improve accuracy. If that doesn't help then there may some other problem and it might be necessary to have a look a pair of your images that are giving you trouble. See how go with fine tuning and let's know how you get on. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/803218b4-172d-4aa0-992f-4820ae5f7c83%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] A couple of questions
Why does the flat-scanned stitching tutorial state that You need to stop Hugin from assuming that all the pictures were taken with the same camera? What is the reason for that - it can take a long time changing the notional lens on each image http://hugin.sourceforge.net/tutorials/scans/en.shtml I have an issue with the way that Hugin calculates focal length: I have a full frame sensor and the EXIF tab of the Stitcher shows the correct focal length of 50mm. But at the bottom of that screen, under lens type, my lens is shown as 38.601mm with a focal length multiplier of 1x. How did that get calculated? Any thoughts would be 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/43f36968-6ce5-4349-a7f2-6779ccca3798%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
