Re: [hugin-ptx] Multi-row panorama
I downloaded these files and I've found that the image stacks message only pops up when adding the eighteenth image to the list of imported images. It appears not to matter which image is the eighteenth - it can even be a duplicate of one of the already selected photos. I retried after converting the images to jpgs - same behaviour. I also retried after reducing the image sizes to 50% with the same results. I recently stitched a multi row pano having more than 30 images without any issues. I am on Win10. B On Tuesday, August 22, 2023 at 12:36:45 PM UTC+10 Donald Johnston wrote: > Greg, thanks for the additional information. The images in this set are > well suited to the quick run though using the Fast Pano Preview because of > the randomness of the rocks, trees, and water. It’s hard to detect any > minor discrepancies like one would with images of manmade structures. With > those the iterative process that David covered works well to get the best > alignment. > > I don’t know why David’s version of Hugin wasn’t able to find connections > between so many images. He used 2022.0 and I’m using 2022.1 (listed as > pre-release). > > 1. Another reason that Hugin might be coming up with the “image stacks” is > the difference in shutter speed of the images … they run from 1/125 s to > 1/500 s (but I don’t know what Hugin is basing its decision on). > Stanley … I’ve seen many suggestions that pano images be taken in manual > mode with the settings base on the brightest part of the image. Also, > keeping the white balance fixed might help the colour tinting that shows up. > > 2. After Align, I get a mean error of 5.5 pix with max 38.6. > > I received the same colour tint issues that showed in David’s stitched > image. The top-right corner has a green tinge. > > Don J. > > > On Aug 21, 2023, at 6:27 PM, Greg 'groggy' Lehey > wrote: > > > > On Sunday, 20 August 2023 at 6:34:23 -0400, Stanley Green wrote: > >> If the link is still active, you can try to get the images directly: > >> > >> > https://wetransfer.com/downloads/c5b1b40878f4f80c5b68af6a6767392b20230817102250/51d164ee951b6c084af7ed1d0d27730e20230817102250/2ee2fd >  > > > > Thanks for that. > > > > I'm confused. A week ago I wrote: > > > > On Tuesday, 15 August 2023 at 11:02:08 +1000, Greg 'groggy' Lehey wrote: > >> > >> My suggestion: use the Align tab on the Fast Panorama Preview. > > > > Specifically, > > > > 1. Load the files from the "Load Images" tab in the Fast Panorama > > Preview. > > 2. Select "Align" from the Fast Panorama Preview. > > 3. Select "Create Panorama" from the Fast Panorama Preview. > > > > And that's all. > > > > In a little more detail for this specific panorama: > > > > 1. Loading the files produced the popup > > > > Hugin has image stacks detected in the added images and will > > assign corresponding stack numbers to the images. Should the > > position of images in each stack be linked? > > > > That's incorrect. There are no image stacks here, so you should > > answer No. I've almost never seen this message, and I suspect it > > comes here because of the overlap between images. 30% should be > > enough. This will give you fewer images and will greatly reduce > > the stitching time. > > > > 2. Aligning the images gave me an image with mean error 3.8 pixels, > > maximum 28.4. Potentially you could improve on this with more > > attention to the position of the entrance pupil, but part of it > > will be due to the water, which doesn't stay the same from one > > image to the next. You could tune the control points, but in this > > case I don't think you need to: I don't see any inconsistencies in > > the finished panorama. > > > > 3. "Create Panorama" offers you a choice of stitching options, > > defaulting to "exposure corrected, low dynamic range". That's the > > one. > > > > But that's all. In particular, I don't understand the problems that > > David W. Jones had, but then I don't understand the complexity either. > > I also didn't see the colour discrepancies that he mentions. > > > > So: the final image is at > > http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817 > > I have also put the .pto file at > > > http://www.lemis.com/grog/Day/20230817/GF_6-panels_-3-Rows-0-GF_6-panels_-3-Rows-17.pto > > This will not be directly applicable, because I have removed the > > spaces from the file names you provided. > > > > Click on the image up to three times to increase the size up to the > > original (about 113 MP). Also let me know if you want this image > > removed after we're done. > > > > Greg > > -- > > Sent from my desktop computer. > > Finger groo...@gmail.com for PGP public key. > > See complete headers for address and phone numbers. > > This message is digitally signed. If your Microsoft mail program > > reports problems, please read http://lemis.com/broken-MUA.php > > > > -- > > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ > > --
Re: [hugin-ptx] Hugin Assistant tab changes
What I suspected - thanks On Monday, August 1, 2022 at 12:01:04 AM UTC+10 T. Modes wrote: > smib schrieb am Sonntag, 31. Juli 2022 um 12:55:49 UTC+2: > >> Thomas >> Visual Studio 12 2013 >> > > That's really old. Sorry, but there is no official support for a nearly 10 > year old compiler. > > -- 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/b370c7f3-8c6c-4dea-9d4f-8aa25d6d1f56n%40googlegroups.com.
Re: [hugin-ptx] Hugin Assistant tab changes
Thomas Visual Studio 12 2013 Brian On Sunday, July 31, 2022 at 6:16:21 PM UTC+10 T. Modes wrote: > Hi, > > I added also the display of more help texts for the menu items in the > status bar. This should give more information about the selected > assistant/output. > > @Brian > smib schrieb am Sonntag, 31. Juli 2022 um 08:06:17 UTC+2: > >> Hi, >> Just tried to compile this latest version (win10 64 bit) using an older >> version of MSVC and get: >> > How old is "older"? It compiles fine with MSVC2022. > Trying to fix in repository. But the support for older compilers will be > limited because of my limited resources. > > Thomas > -- 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/a248dcb2-c175-48d2-a9f5-6fa0d727e43en%40googlegroups.com.
Re: [hugin-ptx] Hugin Assistant tab changes
Hi,
Just tried to compile this latest version (win10 64 bit) using an older
version of MSVC and get:
Error56error C2039: 'max' : is not a member of 'std'
E:\PHOTOGRAPHIC\HuginDLL\Hugin\src\hugin1\hugin\SplitButton.cpp213
1hugin
and
Error57error C3861: 'max': identifier not found
E:\PHOTOGRAPHIC\HuginDLL\Hugin\src\hugin1\hugin\SplitButton.cpp213
1hugin
Brian
On Saturday, July 30, 2022 at 7:06:43 PM UTC+10 bruno...@gmail.com wrote:
> 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, which I think of as the
> > "beginners" tool. Would a beginner even know what the different lens
> > types mean?
>
> The previous Assistant tab had a drop down for lens type, plus focal
> length and crop factor, all in the space next to the first button.
> This was exposing deep photo techno stuff to first-time users that in
> reality would be auto-detected (if the focal length can't be detected
> in the EXIF metadata, you still get a pop-up asking for it as before).
>
> With the split button, the lens type options appear only if you click
> on the pull down arrow - and the first item is labelled as default, so
> I *hope* anyone exploring these will be gently made aware only that
> there are other possibilities.
>
> > > The second lets you run different alignment strategies.
> >
> > I like the wording of the options on the dropdown. They make functional
> > sense - user knows they have scanned images or have a dual-lens camera.
> > Although why are there two "Scanned images" entries - one plain, one
> > with TrXYZ? Would a beginner know what the difference is?
>
> The problem is that: although using the XYZ mosaic parameters to
> stitch scans is conceptually the right way to do it (because sometimes
> your 'scans' are from a mounted camera or microscope and need lens
> correction); the simple way of doing it that abuses the lens d&e
> parameters is more stable and works perfectly for flat-bed scanners.
>
> You can read the labels as 'scanned images' and 'scanned images using
> cryptic other stuff', which is about right.
>
> What I like about this new framework is you can try it, undo, try
> something else etc... Before, these assistant scripts were difficult
> to find.
>
> > > The third split menu gives various ways of stitching the final
> panorama.
> >
> > This dropdown list definitely drops out of the beginner category!
> >
> > What does the "Zero-noise output" do?
>
> It is a photo technique where you shoot bracketed exposures and
> reconstruct a normal (non HDR) image that uses the lowest noise data
> for the dark areas of the image. It gives spookily high quality
> results, especially if you are printing. You need a tripod and a
> static scene, so it isn't an everyday technique:
> http://www.guillermoluijk.com/article/nonoise/index_en.htm
>
> > Does hovering over a number/button have a tooltip that explains things?
>
> The buttons have the same tooltips as before ("Load a series of
> images"), there are no tooltips for the individual menu entries.
>
> --
> 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/7933aa81-b7e5-46f4-a50e-c901e05963c8n%40googlegroups.com.
Re: [hugin-ptx] Hugin++ : fast geometrical optimization and other features
I have tried to run the Windows executable but it is reporting a missing Vcruntime140D.dll. I believe that this is a debug dll and that you may not have distributed the release version.. Brian On Sunday, August 15, 2021 at 4:11:26 AM UTC+10 gunter.ko...@gmail.com wrote: > On Ms windows there normally is no good way of telling where libraries are > installed. > > > Am 14. August 2021 18:41:13 MESZ schrieb "Florian Königstein" < > niets...@gmail.com>: >> >> I have build Hugin and Hugin++ on Windows also with vcpkg. There I have >> the vcpkg directory in the root-directory >> of Hugin++. >> I use the CMake Gui instead of the command line version. As far as I >> remember WxWidgets was also not found although it >> was installed via vcpkg. I entered the paths to WxWidgets manually in >> CMake Gui, and so it worked. It was necessary >> to enter the paths of other libraries manually, too. Maybe I made >> something "sub-optimal" so that the libraries could >> not be found automatically. >> >> Florian >> >> kornel schrieb am Samstag, 14. August 2021 um 18:10:01 UTC+2: >> >>> Am Sat, 14 Aug 2021 15:24:29 + >>> schrieb "'ChameleonScales' via hugin and other free panoramic software" >>> : >>> >>> > line 112 in ./CMakeLists.txt (the one at the root), freshly downloaded >>> from >>> > https://sourceforge.net/projects/huginplusplus/ : >>> > >>> > > include( vcpkg/scripts/buildsystems/vcpkg.cmake ) >>> > >>> > We're talking about vcpkg, right? >>> > >>> >>> Probably my fail. I am using hugin, not huginplusplus. >>> >>> Kornel >>> >> -- 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/5f6dfe65-ff74-491e-893f-e6229a9d10een%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay, Forgot to say that the icon file is included in the files copied to the Lux directory during installation. You may have to copy this to somewhere else and modify the icon location in the script to point to this new location Brian On Monday, May 31, 2021 at 8:47:35 PM UTC+10 smib wrote: > Hi Kay, > Sorry about missing file, here is another link (hope its both files this > time) > https://www.dropbox.com/sh/ggztv234kfqe437/AADhRXvrgSzcnKozUgoFGtQ-a?dl=0 > Brian > > On Monday, May 31, 2021 at 8:00:20 PM UTC+10 kfj wrote: > >> Am 31.05.21 um 10:08 schrieb smib: >> >> > Never played with the Registry before - steep learning curve. My >> current >> > installer (and INNO script) can be downloaded from: >> > https://www.dropbox.com/s/rp5py97hxh1j8gx/Lux%20setup.iss?dl=0 >> >> The download is just the .iss script. Thanks for your contribution! >> >> > If associated, Lux can be selected by right clicking an appropriate >> > file --open with-> choose another app. I have not worked out yet how >> to >> > add it to the basic open with list during installation. >> >> I'm not sure if this is possible, I just thought it might be... sorry if >> I've sent you on a wild goose chase. >> >> > As the installer changes the registry I suggest that you create a >> > restore point before you start. >> >> Thanks for the warning. >> >> > As the program files are changing, I think that you should have the >> > installer and distribute. I think that it is obvious what needs to >> > change in the script to use access the main program files. >> >> Am I understanding you correctly: you would like me to take it over from >> here and use the inno script myself to create the installer when I build >> new versions? >> >> > Also I think >> > that 'ini' is not a good file extension to use as so many other >> > programs use it for various purposes >> >> May be best to use the '.lux' extension for the ini files lux can >> process. I think this is not a common extension, and it could be >> associated with lux without messing things up for other programs. And if >> a user passes a file with .ini extension on the command line, lux can >> still open it. >> >> > PS Don't have privileges to contact you off line >> >> Ooops.. I thought everyone could just reply to a specific person on the >> list. Here, I see your email address as the sender (using thunderbird), >> and I can reply just to you or to the group. >> >> If you want to reply to me off-list, just use the gmail account which is >> given in all my source code. Alternatively, you can also create an issue >> at bitbucket (you don't have to be a member there), just go to >> >> https://bitbucket.org/kfj/pv/issues >> >> and start a new one. >> >> Kay >> > -- 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/377256d3-f9d4-4657-9dbf-d82edbeb52bbn%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay, Sorry about missing file, here is another link (hope its both files this time) https://www.dropbox.com/sh/ggztv234kfqe437/AADhRXvrgSzcnKozUgoFGtQ-a?dl=0 Brian On Monday, May 31, 2021 at 8:00:20 PM UTC+10 kfj wrote: > Am 31.05.21 um 10:08 schrieb smib: > > > Never played with the Registry before - steep learning curve. My current > > installer (and INNO script) can be downloaded from: > > https://www.dropbox.com/s/rp5py97hxh1j8gx/Lux%20setup.iss?dl=0 > > The download is just the .iss script. Thanks for your contribution! > > > If associated, Lux can be selected by right clicking an appropriate > > file --open with-> choose another app. I have not worked out yet how to > > add it to the basic open with list during installation. > > I'm not sure if this is possible, I just thought it might be... sorry if > I've sent you on a wild goose chase. > > > As the installer changes the registry I suggest that you create a > > restore point before you start. > > Thanks for the warning. > > > As the program files are changing, I think that you should have the > > installer and distribute. I think that it is obvious what needs to > > change in the script to use access the main program files. > > Am I understanding you correctly: you would like me to take it over from > here and use the inno script myself to create the installer when I build > new versions? > > > Also I think > > that 'ini' is not a good file extension to use as so many other > > programs use it for various purposes > > May be best to use the '.lux' extension for the ini files lux can > process. I think this is not a common extension, and it could be > associated with lux without messing things up for other programs. And if > a user passes a file with .ini extension on the command line, lux can > still open it. > > > PS Don't have privileges to contact you off line > > Ooops.. I thought everyone could just reply to a specific person on the > list. Here, I see your email address as the sender (using thunderbird), > and I can reply just to you or to the group. > > If you want to reply to me off-list, just use the gmail account which is > given in all my source code. Alternatively, you can also create an issue > at bitbucket (you don't have to be a member there), just go to > > https://bitbucket.org/kfj/pv/issues > > and start a new one. > > Kay > -- 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/e1c23321-c423-48c2-adc7-4d2174ed0ffcn%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay,
Never played with the Registry before - steep learning curve. My current
installer (and INNO script) can be downloaded from:
https://www.dropbox.com/s/rp5py97hxh1j8gx/Lux%20setup.iss?dl=0
If associated, Lux can be selected by right clicking an appropriate file
--open with-> choose another app. I have not worked out yet how to add it
to the basic open with list during installation.
As the installer changes the registry I suggest that you create a restore
point before you start.
As the program files are changing, I think that you should have the
installer and distribute. I think that it is obvious what needs to change
in the script to use access the main program files. Also I think that
'ini' is not a good file extension to use as so many other programs use it
for various purposes
Brian
PS Don't have privileges to contact you off line
On Friday, May 28, 2021 at 5:01:25 PM UTC+10 kfj wrote:
> Am 28.05.21 um 03:55 schrieb smib:
>
> > Sorted out icons.
>
> Good.
>
> > What mimes (other than pto files) did you have in mind?
>
> I'd let the installer offer to make lux the standard viewer for common
> image files (.jpg, .tif, .png) and also for .exr files. Here on my
> systems I have it as standard program to open PTO files as well - I tend
> to look at the PTOs more often than edit them with hugin - and also for
> the .ini extension, which is a bit debatable, but lux accepts ini files
> as image input, e.g. for cubemaps or to 'wrap' .exr files with metadata.
> But that would also offer other ini files used by the system to be
> opened by lux. I may have to change the extension, or add a shebang,
> what do you think?
>
> All of this should be optional, and the user should have to explicitly
> make the choice for any of the mime options. I don't know if you can
> also make mime associations which only show up in the context menu
> ('open with') without changing the default application - if so, I'd
> offer lux in the context menu for all the mime types given above.
>
> BTW - can you offer different types of install? Like, 'regular' install
> to the system's binary folder vs. user-only install without admin
> privileges? That would be nice to have as well.
>
> Looking forward to your installer! Lux 1.0.9 will come out soon, I only
> did a few bug fixes since 1.0.8e, and when we're both ready your
> installer can be distributed via bitbucket downloads - unless you want
> to distribute it yourself.
>
> Kay
>
--
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/efc3cc65-4205-4d20-8013-1f4fbd6875f3n%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay, Sorted out icons. What mimes (other than pto files) did you have in mind? Brian On Friday, May 28, 2021 at 9:06:33 AM UTC+10 smib wrote: > Thanks - got it > Brian > > On Thursday, May 27, 2021 at 11:55:09 PM UTC+10 hvd...@gmail.com wrote: > >> This PV.icns is actually a MacOS package containing 5 or 6 icons for the >> several screen resolutions to use on. >> On MacOS you can simply open the package, select one of the icons and >> export is as png (or jpg). >> I will have a look. >> Otherwise you can use the original svg and convert it to png or ico. >> >> Harry >> >> Op do 27 mei 2021 om 10:02 schreef 'Kay F. Jahnke' via hugin and other >> free panoramic software : >> >>> Am 27.05.21 um 09:55 schrieb Brian Ims: >>> > Hi Kay, >>> > I'll have a go but here is some of my ignorance showing - where do I >>> > find the scripts folder with the icons?. I have looked in bitbucket >>> but >>> > cannot see anything that resembles an icon >>> >>> Try this one: >>> >>> https://bitbucket.org/kfj/pv/src/master/scripts/PV.icns >>> >>> I'm not sure about the format - I managed to get windows to accept it as >>> the source for an icon, even though I believe it's a mac format. If you >>> can't get it to work, ask again and I'll try and find a different format! >>> >>> Kay >>> >>> -- >>> A list of frequently asked questions is available at: >>> http://wiki.panotools.org/Hugin_FAQ >>> >> --- >>> >> You received this message because you are subscribed to the Google Groups >>> "hugin and other free panoramic software" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to hugin-ptx+...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/hugin-ptx/27749d91-b9dd-1028-a1ce-61a153804d36%40yahoo.com >>> . >>> >> -- 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/7eb83385-5500-40f7-a91b-f3bafc115617n%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Thanks - got it Brian On Thursday, May 27, 2021 at 11:55:09 PM UTC+10 hvd...@gmail.com wrote: > This PV.icns is actually a MacOS package containing 5 or 6 icons for the > several screen resolutions to use on. > On MacOS you can simply open the package, select one of the icons and > export is as png (or jpg). > I will have a look. > Otherwise you can use the original svg and convert it to png or ico. > > Harry > > Op do 27 mei 2021 om 10:02 schreef 'Kay F. Jahnke' via hugin and other > free panoramic software : > >> Am 27.05.21 um 09:55 schrieb Brian Ims: >> > Hi Kay, >> > I'll have a go but here is some of my ignorance showing - where do I >> > find the scripts folder with the icons?. I have looked in bitbucket but >> > cannot see anything that resembles an icon >> >> Try this one: >> >> https://bitbucket.org/kfj/pv/src/master/scripts/PV.icns >> >> I'm not sure about the format - I managed to get windows to accept it as >> the source for an icon, even though I believe it's a mac format. If you >> can't get it to work, ask again and I'll try and find a different format! >> >> Kay >> >> -- >> A list of frequently asked questions is available at: >> http://wiki.panotools.org/Hugin_FAQ >> > --- >> > You received this message because you are subscribed to the Google Groups >> "hugin and other free panoramic software" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to hugin-ptx+...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/hugin-ptx/27749d91-b9dd-1028-a1ce-61a153804d36%40yahoo.com >> . >> > -- 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/600381fb-ca2c-4175-9539-8820a6eda60an%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay, Link for the installer and the script file used (as generated by the wizard) is: https://www.dropbox.com/sh/ggztv234kfqe437/AADhRXvrgSzcnKozUgoFGtQ-a?dl=0 Brian On Wednesday, May 26, 2021 at 4:39:49 PM UTC+10 kfj wrote: > Am 26.05.21 um 03:38 schrieb smib: > > > I am not a serious programmer but I thought I would try to create a > > Windows installer. > > Nice one! > > You got the idea - you needn't be a 'serious programmer' to help the > project along. In the FOSS world it's 'scratch your own itch', and if > you'd like to see a Windows installer and know how to make one, there > you go. And if you like what you did you can share it. > > > I used Inno Setup (https://jrsoftware.org/) > > I looked at their home page, and it looks good. Their license seems to > be compatible, and I'd have no problem mentioning that their software is > used to make a lux installer. > > > After > > about 5 mins work (including download and install time) I came up with a > > working install program. The creation wizard provides many options most > > of which I left as default. Could be the way to go! > > My experience is that the most important step is to find a viable path > in the first place. Fleshing things out later is nice-to-have. I'd like > to have a look at the installer you made, can you share it? You could > either upload it to some cloud place where I can pick it up, or attach > it to an email and send it off-list. > > I'd be happy to have some help with the windows installer, so if you > feel like working on it a bit to make it nice for everyone to use, you'd > be very welcome. If not, that's also fine, then I'll just keep your > suggestion as an option to find a good way to build an installer. > > I had the idea to use CMake's packaging capabilities to produce a > windows installer, which would fit in well with the lux project, because > it now uses CMake for building. CMake uses cpack, a component which > builds installers for various platforms. lux' CMakeLists.txt already has > some content to 'feed' package building, and it's already used to make > linux packages, so starting afresh with a different package building > system may be more work, and duplicate effort which was already put into > the CMakeLists.txt for lux, but so far the effort put into packaging > wasn't very large - I think it's about the minimum necessary to get a > package together at all. Have a look at what cpack offers: > > https://cmake.org/cmake/help/latest/manual/cpack.1.html > > They provide several builders for windows, but there does not seem to be > one to target inno setup, here's an example: > > https://cmake.org/cmake/help/latest/cpack_gen/nsis.html > > I haven't tried any of this, but it looks like another viable route to a > windows installer. But it does also rely on external tools, so going via > CMake/cpack would just be a matter of convenience. > > So, thanks again for your interest and effort! And let me have a look at > what you made! > > Kay > -- 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/a24748ab-4c5b-4bec-9840-ba83ed60c588n%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Kay I am not a serious programmer but I thought I would try to create a Windows installer. I used Inno Setup (https://jrsoftware.org/) After about 5 mins work (including download and install time) I came up with a working install program. The creation wizard provides many options most of which I left as default. Could be the way to go! Brian -- 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/80b50b38-edf1-4684-8e46-e8969d72863fn%40googlegroups.com.
Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv
Hi Kay, Are you planning to provide another windows build? At the moment I am having problems building but this is due to my lack of knowledge Brian On Monday, March 29, 2021 at 8:59:03 PM UTC+11 kfj wrote: > There is new functionality in lux: I call it 'snap-to-stitch'. > > After a few weeks of development, I have gained enough confidence in my > implementation of the multilevel blending code to try and use it > automatically when a PTO is displayed. Here is the logic: > > Per default, lux switches to 'high quality rendering' if there is no > activity: neither ongoing user input, nor any background jobs, and no > jobs pending in any of the queues. Until recently, 'hq rendering' would > display the 'live view' of a PTO file, just with better interpolation. > Now what happens is that a stitch or exposure fusion of the current view > is produced in the background and displayed once it's ready. > > For 'ranked blending' - the default, used for panoramas - this may be > hard to notice, but if the live view showed 'hard' borders between the > images, with the switch to the blended result these borders should > simply 'disappear' after a while. For 'hdr blending' the switch is much > more noticeable, because due to the exposure fusion the intensity values > change a good deal - blown-out highlights darken and become visible, and > dark areas receive fill light. > > The snapshot logic remains the same: 'E' produces a snapshot of the live > view, 'U' an exposure fusion and 'P' a panorama. As I have explained in > my last post, the default for the 'source-like' snapshots, done with > 'Shift+E', 'Shift+U' and 'Shift+P' is now to produce a rendition > according to the p-line in the PTO. > > So trying out the new functionality is simple, especially for panoramas: > just load a PTO with a panorama and see the boundaries between the > images disappear after some time. Play with it: zoom in and out, look at > other places. Once the viewer is at rest, the 'snap-to-stitch' should > happen after some time. If you don't like the new mode, you can easily > switch it off by pressing F12 or clicking on 'IDLE HQ'. For exposure > fusions, you have to invoke lux with --blending=hdr to see the effect. > > Of course, all of this is CPU- and memory-intensive, so if you use it > with large panoramas, the background task may take long, and - as ever - > you may run into memory problems, so you may want to consider adding > --build_pyramids=no and possibly even --facet_squash=1 to your command > line to lower RAM consumption. The idea is not to use lux' PTO-viewing > capabilities to actually *look at* PTOs for any length of time - if you > want to do that, stitch/fuse to a single output file and view that > instead. What's intended is to give you a tool to inspect what the > blended/fused output will look like before you actually commit to > stitch/fuse. > > And, again, a word of warning: lux' understanding of PTO files is > limited to source image projection, position, Ev, lens and vignetting > correction - and now the projection, shape, fov and crop from the p-line > for source-like snapshots. Don't be disappointed or surprised if other > stuff from the PTO file is simply ignored. And be aware of the fact that > this is new code and not yet well-tested. Start with something simple > and work your way up. > > Kay > > -- 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/afffd29d-0a96-41c2-b486-82182952b211n%40googlegroups.com.
Re: [hugin-ptx] Re: Color bug with verdandi
I can confirm that with a recent Windows build (post the April changes to Verdandi), I get similar stitching lines as Stéphane with 2 image panos. They are not visible using Enblend. Brian > -- 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/e2847de1-8ace-4bb4-a7e6-35629cc9d0cc%40googlegroups.com.
[hugin-ptx] Re: woa: NO control points added?
> > I am not sure what version of Python has been used in the build but I have > found the same issue in my own build using Python 2.7. Interestingly when I > first got a 64 bit win 8 box I copied across the 32 bit version of Hugin > that I had (and where WOA worked) . Hugin ran fine but WOA no longer worked! > I can run WOA from the command line using woa.py ain.pto -c 1.0 -g cpfind -m 0 -o aout.pto -b woa -s 0.25 -verbose -t 0.01 >out.txt where ain.pto is the basic pto file generated by Hugin and aout.pto is the new pto file created using WOA To my little brain it appears that there has been a change in the way that Win8/10 handles the WOA script from within Hugin Cheers -- 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/e63f4c53-6826-4aad-8023-aa82fe9c3abc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Problem with Windows build of current repository version
Thomas: Just built version 7402 and problems appear to be solved On Sunday, May 22, 2016 at 8:47:09 PM UTC+10, smib wrote: > Forgot to add Windows 10.1 and Hugin not on C drive. The build procedure > for all attempts was identical > -- 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/4fac77c5-e7d9-4d9d-8b05-1490f8cdd49e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Problem with Windows build of current repository version
Forgot to add Windows 10.1 and Hugin not on C drive. The build procedure for all attempts was identical -- 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/1898e5d4-1a7e-4a8e-b414-d2ae5935b1d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Problem with Windows build of current repository version
Hi, I finally managed to get a Win 64 bit version of the 2016 release working (following steps given on the Wiki page),. Being brave I then tried the latest repository version (7400). Compiled Ok but CPfind returned zero control points. Autopano - sift -c returned a believable number of points but after optimising (appropriate values reported) both the fast and full preview windows only show the pictures in the 'layout screen' positions. Back tracking it appears that the last working (Windows) version was 7366 Hope this helps in finding the problem Brian -- 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/076fbd31-fb03-4671-9c63-dc979653ac11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: 2015 beta 2 and windows build problem
Hi Harry, Forgot to say MSVC2013 express Brian > -- 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/69a9b29d-1957-46ce-b608-b88a6f5f106b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] 2015 beta 2 and windows build problem
Hi, Trying to build a 32 bit win 8.1 version with wxwidets 3.0.2/ vigra 1.10.0 boost 1.57.0 and the 2015 beta 2 code I managed to get past my earlier issue (see thread on 2015 beta 1) - the cmake name vigra_config_hxx needs to point to configVersion.hxx not config.hxx - and are now getting more than 1000 errors of the form: - Error 1 error C2146: syntax error : missing ';' before identifier 'wxSTD_FRAME_ICON' E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 48 1 huginbasewx - Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 48 1 huginbasewx - Error 3 error C2146: syntax error : missing ';' before identifier 'wxSTD_MDIPARENTFRAME_ICON' E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 49 1 huginbasewx - Error 4 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 49 1 huginbasewx - Error 5 error C2146: syntax error : missing ';' before identifier 'wxSTD_MDICHILDFRAME_ICON' E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 50 1 huginbasewx - Error 6 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 50 1 huginbasewx - Error 7 error C2146: syntax error : missing ';' before identifier 'wxDEFAULT_FRAME_ICON' E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 51 1 huginbasewx - Error 8 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 51 1 huginbasewx - Error 29 error C2061: syntax error : identifier 'HANDLE' E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 193 1 huginbasewx - Error 30 error C2833: 'operator HANDLE' is not a recognized operator or type E:\Photographic\Huginbase\wxWidgets-3.0.2\include\wx\msw\private.h 196 1 huginbasewx - I am not knowledgeable enough to work out what is going on. Searching suggests that it could anyone of a number of causes including a missing ';' somewhere before the error is reported, incorrectly typed or spelt variable name, missing file etc etc Is this a bug or is it me? Cheers Brian -- 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/3e72f956-b464-45c3-9b69-b9d4161a0bab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Compilation error
I decided to look at the features being added to the latest repository version rev 6690. Compiling a Win 32 bit version with MSVC2010 gave the following error: error C2668: 'sqrt' : ambiguous call to overloaded function E:\Photographic\Huginbase\hugin\src\hugin1\hugin\ImageVariableDialog.cpp line 508 Revs before 6670 compile and run ok Brian -- 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/9d0bd652-3368-4bf8-9cd0-f3e6a4da427d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Problem with Tortoise HG?
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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/b1117517-229d-425c-b971-754aaf1dfa6e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] Problem with Tortoise HG?
I've just tried synchronising and Tortoise is reporting that the last update/change was 8 weeks ago. I do not believe thsi is correct. Is there something wrong preventing the latest changes from being pulled? (Windowes XP 32 bit). Creating a cloned directory does not make any difference Cheers -- 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/187bd9b0-3dba-419e-ac46-b91cd6efac15%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] Re: Small errors, Projection formula and Preview
Getting a little further. Message is now basically: > examining image pair (0, 1) > > overlap area: 11736755.252809558 pixels > > overlap ratio: 0.729671189939638 > > overlap area: 11524660.939996947 pixels > > overlap ratio: 0.7164853386310013 > > setting subpano width to 7278 > > creating warped overlap images with woa_base.pto > > cp detection: cpfind ['--fullscale', '--sieve2size', '5', '--ransacmode', > 'hom', '-o', 'woa_warped.pto', '_woa_warped.pto'] > > CPG found 80 CPs > > matching pair (0, 1) failed with TypeError: "float() argument must be a > string or a number" > > stack traceback > The suggetsed mod works with Python2.7 Brian On Friday, 17 May 2013 20:10:49 UTC+10, kfj wrote: > > > On Wednesday, May 15, 2013 12:39:15 PM UTC+2, smib wrote: > > matching pair (1, 2) failed with TypeError: "can't use a string >> pattern on a bytes-like object" >> > > Okay. Figured it out. The key is this last message, can't use a string... > > The problem is due to the use of python 3. I hadn't tested woa under > python 3, and obviously noone else has, either. So an error could stay > undetected: to analyze tiffdump's output, the output is matched with > regular expressions to filter out the bits which interest us. There, the re > search patterns are given as string literals. This is fine in python 2.x, > but python 3.x expects byte literals. Now this is easy to fix and doesn't > break it for python 2.X either, because the relevant literal modifier, a > prefixed 'b', is simply ignored in python 2.x. I'd ask you to midify woa.py > in lines 237 and 238. The current version is > > fieldname = re.match ( r'[^\(]+' , t ) . group(0) . strip() > fieldcontent = re.match ( r'([^<]+<)([^>]+)' , t ) > > please insert the additional 'b' so that the lines read > > fieldname = re.match ( br'[^\(]+' , t ) . group(0) . strip() > fieldcontent = re.match ( br'([^<]+<)([^>]+)' , t ) > > this should fix the problem. If it does, please let me know so that I can > send in a patch. If it doesn't , well..., let me know too, but I hope this > is it ;-) > > Kay > >> >> >> Cheers >> >> On May 10, 7:30 pm, kfj <_...@yahoo.com> wrote: >> > On Thursday, May 9, 2013 12:13:03 PM UTC+2, smib wrote: >> > >> > > Hi Kay >> > >> > > I've noticed the same issue with my win 32 bit build using MSVC2010 >> from >> > > last weekend. Woa works fine from the command line and from an >> earlier >> > > build (built with MSVC2008). The 'limit to 5 points' script works >> from my >> > > recent build but the woa script returns -1 after calling Nona and >> then >> > > CPfind. From what I can see woa has not changed so i guess that there >> must >> > > be a recent code change somewhere that is conflicting >> > >> > Interesting. The next thing in line from calling the cpg is calling >> > tiffdump, in order to get the information about the cropping in the >> cropped >> > TIFF which nona produces - this might be where things go awry. Would >> you be >> > so kind and run woa from the command line with --verbose to make it >> more >> > chatty, capture all console output and post that? It might give me more >> of >> > a clue where things go wrong, particularly if the problem raises an >> > exception and I can see from the stack trace where it tripped. >> > >> > Of course there's always the possibility of an incompatible change in >> > hugin's API... I don't think anyone cares overly much about breaking >> the >> > very few extant python plugins. The python interface itself adapts to >> every >> > new version of the API automatically, but when an 'old' plugin tries to >> > call what it could safely call when it was written, and what is called >> has >> > changed in the meantime, it may well fail. That's why Yuv coded an API >> > version check into the system, which resulted in all plugins being >> disabled >> > in a previous release, because noone had minded the mechanism and >> checked >> > and updated them when they were found compatible... I guess it will >> take a >> > 'killer plugin' which everyone wants to make the pl
[hugin-ptx] Re: Small errors, Projection formula and Preview
Hi Kay Command line output as requested checking for availability of tiffdump checking for availability of nona checking for availability of cpfind main: parameters used for this run: ceiling: 1.0 exclude: [] focus: None images: [] margin: 0 output: xout.pto scale: 0.25 stop:None thresh: 0.01 prolific True ptofile: b.pto verbose: True found 3 images in panorama image 0: C:\SLR Photos\Europe 2006-7\England + Germany\IMGP0823.JPG image 1: C:\SLR Photos\Europe 2006-7\England + Germany\IMGP0824.JPG image 2: C:\SLR Photos\Europe 2006-7\England + Germany\IMGP0825.JPG processing image set [0, 1, 2] examining image pair (0, 1) overlap area: 3946190.434895714 pixels overlap ratio: 0.6559492079281439 overlap area: 3943129.262840057 pixels overlap ratio: 0.6554403694880414 setting subpano width to 4722 creating warped overlap images with woa_000_001.pto nona returned 0, output: b'woa_000_001.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'b'woa_000_0010001.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'cp detection: cpfind ['--fullscale', '--sieve2size', '5', '--ransacmode', 'hom', '-o', 'woa_000_001_warped.pto', '_woa_000_001_warped.pto'] CPG found 122 CPs matching pair (0, 1) failed with TypeError: "can't use a string pattern on a bytes-like object" stack traceback: examining image pair (0, 2) overlap area: 2098998.746581664 pixels overlap ratio: 0.3489027171844521 overlap area: 2084369.3272030938 pixels overlap ratio: 0.3464709652930675 setting subpano width to 4722 creating warped overlap images with woa_000_002.pto nona returned 0, output: b'woa_000_002.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'b'woa_000_0020001.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'cp detection: cpfind ['--fullscale', '--sieve2size', '5', '--ransacmode', 'hom', '-o', 'woa_000_002_warped.pto', '_woa_000_002_warped.pto'] CPG found 110 CPs matching pair (0, 2) failed with TypeError: "can't use a string pattern on a bytes-like object" stack traceback: examining image pair (1, 2) overlap area: 3263912.034864002 pixels overlap ratio: 0.5425385696250004 overlap area: 3262644.4793947963 pixels overlap ratio: 0.5423278722398265 setting subpano width to 4722 creating warped overlap images with woa_001_002.pto nona returned 0, output: b'woa_001_002.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'b'woa_001_0020001.tif: LZW compression is not available to due to Unisys patent enforcement.\r\n'cp detection: cpfind ['--fullscale', '--sieve2size', '5', '--ransacmode', 'hom', '-o', 'woa_001_002_warped.pto', '_woa_001_002_warped.pto'] CPG found 108 CPs matching pair (1, 2) failed with TypeError: "can't use a string pattern on a bytes-like object" stack traceback: Cheers On May 10, 7:30 pm, kfj <_...@yahoo.com> wrote: > On Thursday, May 9, 2013 12:13:03 PM UTC+2, smib wrote: > > > Hi Kay > > > I've noticed the same issue with my win 32 bit build using MSVC2010 from > > last weekend. Woa works fine from the command line and from an earlier > > build (built with MSVC2008). The 'limit to 5 points' script works from my > > recent build but the woa script returns -1 after calling Nona and then > > CPfind. From what I can see woa has not changed so i guess that there must > > be a recent code change somewhere that is conflicting > > Interesting. The next thing in line from calling the cpg is calling > tiffdump, in order to get the information about the cropping in the cropped > TIFF which nona produces - this might be where things go awry. Would you be > so kind and run woa from the command line with --verbose to make it more > chatty, capture all console output and post that? It might give me more of > a clue where things go wrong, particularly if the problem raises an > exception and I can see from the stack trace where it tripped. > > Of course there's always the possibility of an incompatible change in > hugin's API... I don't think anyone cares overly much about breaking the > very few extant python plugins. The python interface itself adapts to every > new version of the API automatically, but when an 'old' plugin tries to > call what it could safely call when it was written, and what is called has > changed in the meantime, it may well fail. That's why Yuv coded an API > version check into the system, which resulted in all plugins being disabled > in a previous release, b
Re: [hugin-ptx] Re: Small errors, Projection formula and Preview
Hi Kay I've noticed the same issue with my win 32 bit build using MSVC2010 from last weekend. Woa works fine from the command line and from an earlier build (built with MSVC2008). The 'limit to 5 points' script works from my recent build but the woa script returns -1 after calling Nona and then CPfind. From what I can see woa has not changed so i guess that there must be a recent code change somewhere that is conflicting Cheers Brian On Thursday, 9 May 2013 05:18:32 UTC+10, kfj wrote: > > > On Monday, May 6, 2013 9:55:41 PM UTC+2, Giancarlo Todone wrote: >> >> >> -1 means that the call to the plugin interface has failed. Can you call >>> any of the other plugins? And can you run woa from the command line? What >>> system and what version of hugin are you using? >>> >> Right now i'm on Windows 8 x64 but I'm using Hugin 2012.0.0 x86 because >> x64 version gives problems on UI (some missing controls). I tried 2012 and >> 2013 beta x86/x64 normal/hsi with same results: all of the scripts return >> -1. >> I tried calling "python woa.py" in the scripts folder: it complains about >> lack of hsi include. Didn't experiment further (but will with my >> Ubuntu10.04 install) >> > > Well, lack of hsi means that you don't have a hugin built with python > support. If you build yourself, you can get the python interface by > building with these cmake flags > > -DBUILD_HSI:BOOL=ON -DSWIG_EXECUTABLE=/usr/bin/swig2.0 > > It should at any rate be much easier getting it to run on > Linux. Just follow the wiki: > > http://wiki.panotools.org/Hugin_Compiling_Ubuntu > > Once you have built hugin with the python interface, you can > test easily whether you've succeeded by just opening a python > session and typing > > import hsi > > at the python prompt. If that succeeds, you should be fine. > Why the Windows build you have allows you to call a plugin when > the python interface isn't there, I don't know. > > Kay > > > > > > > > -- -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx --- 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. For more options, visit https://groups.google.com/groups/opt_out.
