[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
On Thursday, 28 February 2019 14:44:52 UTC+1, Abrimaal wrote: > > "Add images" already opens Windows explorer, a second Explorer window will > only take space on the screen and it will not follow the current work > folder. The "Open file" and "Save file" look much like Windows Explorer (they use the same view components) but it's not the same thing. The dialogs are basically aimed at opening of saving files (hence their name), and because Windows, do indeed offer some of the functionality that the full blown Explorer does. This is however not the same in every operating system (for Linux it depends on your desktop environment). Surely an external Explorer window takes up some space, but if you have that, you don't need the "Add images" thing either. You can just drag images from Explorer onto Hugin. I'm not sure what you mean by "doesn't follow the current work folder". I started to write a command line script to get filenames from .pto files, > to be interpreted as images, but as I see, it will certainly fail. Command > line is tough for multiple file operations and loops (and extremely slow) > (and I don't know any other language). > The initial goal is only to get filenames from .pto files and load these > images to Hugin. All the parameters may be added later. > Doesn't the merge functionality that was mentioned by T. Modes in this thread do what you want? > Why it is so important to me: I have already photographed almost the whole > town in panoramas, from 3 to 20 photos. Then gradually merge one pano with > another, to create a street, then a street with another street and so on... > Intriguing! Can you share some results? Sound like you are creating multi-viewpoint panorama's, (i.e., one long strip showing an entire street), no? -- 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/f4a66f1c-8728-4a0f-be7f-aa07bad7d6b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
What prevents you from just using Windows Explorer to find your .pto between the images? I still don't see how this is Hugin's problem. You're basically "abusing" the Load Images button just to see the image previews so you can find the .pto file you want to work on, from what I gather. Didn't check (no Hugin on my current machine) but can't you just show all files in the Open .pto dialog (whatever the name) if you really want to stay within Hugin? I'd really suggest just using Windows Explorer though, that's what it exists for. On Tuesday, 26 February 2019 03:11:35 UTC+1, Abrimaal wrote: > > >But this DOES NOT turn a PTO magically into an image, so it cannot be > opened as an image, because it isn't an image. > Yes, I know. I use Load images button to preview how the panorama looks. > (right click -> open in a default viewer) > The .pto file is saved just before the panorama in the same folder. > If the panorama requires corrections, then right click .pto -> Send to -> > Hugin. > Now it became impossible. When there are a few hundreds partial images in > a folder, it is not easy to find the proper .pto file from the standard > menu File -> Open. > > On Monday, February 25, 2019 at 10:51:32 PM UTC+1, Bart van Andel wrote: >> >> Abrimaal wrote: >>> >>> It does not work in the 2019 beta 2 version, because the filter "All >>> files" has been changed to "All images". >>> >> >> Sorry, apparently I missed this. BTW I think 2018 version had both >> >> >>> I typed: >>> * >>> "*" >>> *.* >>> "*.*" >>> in the filename field. >>> .pto files are among the images, but not accessible. >>> >> >> Just * works for me to show all files. But this DOES NOT turn a PTO >> magically into an image, so it cannot be opened as an image, because it >> isn't an image. >> > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to 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/00370011-3084-47fe-a8e1-29c27445bd4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
Abrimaal wrote: > > It does not work in the 2019 beta 2 version, because the filter "All > files" has been changed to "All images". > Sorry, apparently I missed this. BTW I think 2018 version had both > I typed: > * > "*" > *.* > "*.*" > in the filename field. > .pto files are among the images, but not accessible. > Just * works for me to show all files. But this DOES NOT turn a PTO magically into an image, so it cannot be opened as an image, because it isn't an image. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to 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/774bf62d-23b5-4b67-bbdd-c82d74a48161%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Installed hugin now what?
@Abrimaal: > > Although the default installation folder in Windows is "C:\Program Files", > it is not recommended to install any third party software on C:, except > drivers, codecs, fonts and other shared files. > Files on C: are often protected by Windows in various ways, > Better to install software on a different hard drive or partition. The > user can access all files, the system is more efficient and easier to > manage. > This is not generally true. "C:\Program Files\" and its 32 bit equivalent "C:\Program Files (x86)\" are perfectly valid places to install software. In fact, certain software may fail to function if you change the default location (yes, that's bad design, but still true). Hugin has been running from the default location on my machines for years and this never caused any problem. Please don't spread FUD like this. -- 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/de5f9fa2-27cc-451c-a08d-1d35170549db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
> > @Bart > Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: >> >> What you're asking is (correct me if I'm wrong) the ability to import >> images from one project into another one. That is currently not supported >> without scripting I think. Still not the same as treating the PTO as an >> image though. >> > This is already possible (without scripting): in panorame editor: > File>Merge project > Thanks, didn't know! I haven't had a use for this yet though, so that may be why I never noticed. -- 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/5141f1da-fb9b-4365-a953-6a6c6e9bc382%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
This is not a bug. You're trying to load a .PTO file as if it were an image, which it is not. To take your .doc example: you can also not expect any image editor to just open a Word document because it may contain an image. Same with opening a Zip file, or any other file with some image data embedded. It just doesn't work like that. What you're asking is (correct me if I'm wrong) the ability to import images from one project into another one. That is currently not supported without scripting I think. Still not the same as treating the PTO as an image though. On Monday, 4 February 2019 15:48:33 UTC+1, Abrimaal wrote: > > [image: hugin-could-not-decode-image-from-pto-file.png] > While loading images from a .pto file, this error message is displayed. > The images have not been moved, not renamed, the are still in the same > folder as the .pto file. > The filenames and paths to images stored in the .pto file did not change. > > > -- 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/68312e6c-8ab6-46ea-abfd-7bec25760573%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Hugin is purely and simply unusable for panorama stiching
On Saturday, May 17, 2014 12:28:38 PM UTC+2, Harry van der Wolf wrote: Well, I could start with saying that it works for me as it really does. I'm on Linux. [...] To comment on my own it works for me: This is the most annoying answer a help desk can give when someone whith a problem asks for assistance. I agree that it is an annoying answer, absolutely, and none that will help. The problem is, we are not a real help desk. We can neither stay on the phone and walk a user through a number of (standardized) steps, nor walk into their office and start troubleshooting for ourselves. Since we do not have access to other users' machines, troubleshooting is quite hard if the problem does not occur on your own machine. Hugin mostly works for me too, apart from some (known) quirks (like make.exe crashes on 2014.0 RC1, if I remember it right), and I am not terribly familiar with the code base, nor do I have a build environment installed for Windows. If I were to work on Hugin, it would be on Linux most likely, simply because setting up a build environment is a whole lot easier there. In fact I regularly pull the sources and compile Hugin for Linux already. Things would be quite different if I were paid to support Hugin for Windows, but since I only have so much spare time (and other things and interests with more priority), I don't feel much of an urge to start hunting for hard-to-reproduce bugs (on my system anyway) on the Windows version of Hugin. A simple truth. Inconvenient for people who only want to use the software, not develop it, but it's simply how it works. And to refer to ITIL: if one person has an issue it is an incident. If many users have an issue it is a problem. I'm afraid we have a problem. Yes. But again, non-reproducibility and lack of installed build environment prevents me from diving into this. -- 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/1c71ba7c-90e9-4b23-bf60-688ca90978a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Hugin is purely and simply unusable for panorama stiching
Jeff, On Thursday, May 15, 2014 2:12:34 PM UTC+2, Jeff W wrote: The only reason I've entered this discussion at all is that following Hugues' admittedly not-terribly-helpful post, the universal response from the community was what we might call the Apple playbook: blame the user. You didn't take time to get to know the software. You must not understand what's going on. You're holding it wrong. You're not computer savvy enough. You are just part of the point and shoot crowd that wants a one click solution. You should be using Linux instead of Windoze. Etc. By universal response I assume you are referring to the responses in this specific thread, which started by a rather hostile message basically calling crap on everything Hugin is about. That's arguably not the best way to get any help at all. There are numerous threads pointing out various (far too many) problems of Hugin on various kinds of systems. Most of them were written in a much more relaxed tone, resulting in a completely different kind of discussion from the one in this here thread. You'll agree with me that nice questions deserve nice answers, whereas questions asked like the developers produced nothing but an executable pile of steaming shit deserve to be flushed down the toilet, or at the very least may expect some less subtle responses. Consider this example. You are helping out in a shop which gives away refurbished electronics equipment to people who cannot afford it. Of course you are doing this without compensation, and only if you have spare time left after your busy everyday job and other activities. Someone enters the shop, carrying with him a faulty hard drive. Which complaint would you prefer: - This hard drive is utter shit, I tried to connect it to my computer once and it didn't work!, or - Something is wrong with this device, my computer does not recognize it somehow. The light is blinking and the drive seems to be spinning, but no matter what USB port I try, my OS cannot see it. I guess the answer is obvious. Maybe you'd still try to help out a rude customer, but with a lot less willingness than when helping a polite customer. I agree with you however that Hugin severely lacks in stability and speed, and that the UI and workflow could use improvement. Long time user here, not very happy yet with the current state of the (new) UI, but I know enough about the program to work around most annoyances most of the time. However, considering almost everything is done in the spare time of a pretty diverse group of contributors, without an architecture overseeing things or a lot of code review, I don't think it's a bad product at all. Supporting the subtleties of several different kinds of OS (Linux, iOS, Windows, all in several flavors) isn't a straightforward task. Many libraries are involved, some of which require (or have required in the past) adaptation specific for Hugin. Not an easy thing to maintain. In the end, it's a complex product, far from perfect, but still a hell of an accomplishment. And I'm usually very happy with the results it produces, especially considering I shoot almost everything hand-held with auto exposure. -- Bart -- 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/9299daca-8168-4eb6-a2ce-ee8d5032b47f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Hugin.exe doesn´t work...
Hi Erdmann, Which version of Hugin did you install? I.e., version number, 32 or 64 bit, with/without Python support, using the installer or by unzipping a 7Z file? When does this error occur? Have you tried a different version? FYI, I'm using Windows 7 x64 as well, and apart from the occasional quirk, Hugin (64 bit, pretty much any version) usually does the job quite well on my machine. This kind of error message dump may be helpful when the failing program is attached to a debugger, but without that, it's pretty hard to guess what is going wrong exactly. I mean, ntdll.dll seems like something from the Windows core. I have no idea what could trigger this from Hugin. Kind regards, Bart On Monday, May 12, 2014 2:35:08 PM UTC+2, erdman...@googlemail.com wrote: High together, hugin-2013-Version doesn´t work under Windows 7 - 64-Bit. I can open the program, but it doesn´t work. This ist the Windwos-System-Report. Name der fehlerhaften Anwendung: hugin.exe, Version: 0.0.0.0, Zeitstempel: 0x523cb338 Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7601.18247, Zeitstempel: 0x521eaf24 Ausnahmecode: 0xc374 Fehleroffset: 0x000c4102 ID des fehlerhaften Prozesses: 0x61c Startzeit der fehlerhaften Anwendung: 0x01cf6db68b6a8910 Pfad der fehlerhaften Anwendung: C:\Program Files\Hugin\bin\hugin.exe Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll Berichtskennung: e4806c98-d9a9-11e3-b5da-404e57434401 Can anybody help? *Erdmann * -- 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/0c44f80a-2d11-4004-ad11-472db32ce366%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Panini-general broken in 64-bit builds
Additional information: - Hugin fails on Linux as well (hg tip, also libpano13 tip); - For me, it fails with tops=60, but succeeds with top=-100. Seems like a sign thing to me. I've been digging around in the source code a bit but it's huge so I haven't been able to pinpoint the problem yet. Gotta go now, I'll probably do some more digging later. Cheers, Bart On Sunday, April 27, 2014 6:53:02 PM UTC+2, Bart van Andel wrote: I'm experiencing the same issues with panini general in recent builds. I'm trying to use the tops parameter but it seems to be ignored completely. However, I've tried running the very same project using a number of Hugin versions, and they are all failing, both 32 and 64 bit. After a number of runs I saw that I had forgotten to delete the generate project.mk file, which contains references to the paths for every tool being used, but after deleting this file the results are still the same: tops parameter not applied. I could see in the progress window that the intended version of nona was being used. Versions tested (all on Windows 7, 64 bit): - 2014.0.0-beta1 x32 (installer, Python version) - 2014.0.0-beta1 x64 (installer, Python version) - 2013.0.0 x32 (7z, non-Python version) - 2012.0.0 x32 (7z, non-Python version) - 2011.4.0 x32 (7z, non-Python version) - 2010.4.0 x32 (7z, non-Python version), this one even fails to call make.exe, even after Load defaults for every preferences page. I haven't bothered to check out why this is happening. Note that in all cases, the GL preview shows the correct projection. Some versions of nona (or maybe all, haven't watched everything) complained about the projection not being GPU-compatible, so it switched to CPU remapping. Disabling GPU processing alltogether does not change anything. What version are you using to stitch your panini-general images, Tom? On Monday, August 19, 2013 2:22:09 AM UTC+2, Tom Sharpless wrote: Recent 64-bit Windows builds of Hugin don't apply the panini-general squeeze settings tops and bots while stitching, although they do display squeezed images in the preview window (I have tried 2010.4, 2011.4, and 2012.0) The 32-bit builds seem to apply tops and bots correctly. I suspect this is a word size issue somewhere in nona; but it might be in libpano. I rely on Hugin's panini-general for making architectural prints, and many of the images I work with nowadays are too big for the 32-bit version. I'm not currently set up to build Hugin at 64 bits, so I would really appreciate it if the Hugin team could fix this. -- Tom -- 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/33a3c414-d9ab-4c25-bf69-065c098f9568%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Panini-general broken in 64-bit builds
I'm experiencing the same issues with panini general in recent builds. I'm trying to use the tops parameter but it seems to be ignored completely. However, I've tried running the very same project using a number of Hugin versions, and they are all failing, both 32 and 64 bit. After a number of runs I saw that I had forgotten to delete the generate project.mk file, which contains references to the paths for every tool being used, but after deleting this file the results are still the same: tops parameter not applied. I could see in the progress window that the intended version of nona was being used. Versions tested (all on Windows 7, 64 bit): - 2014.0.0-beta1 x32 (installer, Python version) - 2014.0.0-beta1 x64 (installer, Python version) - 2013.0.0 x32 (7z, non-Python version) - 2012.0.0 x32 (7z, non-Python version) - 2011.4.0 x32 (7z, non-Python version), this one even fails to call make.exe, even after Load defaults for every preferences page. I haven't bothered to check out why this is happening. Note that in all cases, the GL preview shows the correct projection. Some versions of nona (or maybe all, haven't watched everything) complained about the projection not being GPU-compatible, so it switched to CPU remapping. Disabling GPU processing alltogether does not change anything. What version are you using to stitch your panini-general images, Tom? On Monday, August 19, 2013 2:22:09 AM UTC+2, Tom Sharpless wrote: Recent 64-bit Windows builds of Hugin don't apply the panini-general squeeze settings tops and bots while stitching, although they do display squeezed images in the preview window (I have tried 2010.4, 2011.4, and 2012.0) The 32-bit builds seem to apply tops and bots correctly. I suspect this is a word size issue somewhere in nona; but it might be in libpano. I rely on Hugin's panini-general for making architectural prints, and many of the images I work with nowadays are too big for the 32-bit version. I'm not currently set up to build Hugin at 64 bits, so I would really appreciate it if the Hugin team could fix this. -- Tom -- 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/810657fb-086e-4185-ae62-cf79d454d926%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Panini-general broken in 64-bit builds
I'm experiencing the same issues with panini general in recent builds. I'm trying to use the tops parameter but it seems to be ignored completely. However, I've tried running the very same project using a number of Hugin versions, and they are all failing, both 32 and 64 bit. After a number of runs I saw that I had forgotten to delete the generate project.mk file, which contains references to the paths for every tool being used, but after deleting this file the results are still the same: tops parameter not applied. I could see in the progress window that the intended version of nona was being used. Versions tested (all on Windows 7, 64 bit): - 2014.0.0-beta1 x32 (installer, Python version) - 2014.0.0-beta1 x64 (installer, Python version) - 2013.0.0 x32 (7z, non-Python version) - 2012.0.0 x32 (7z, non-Python version) - 2011.4.0 x32 (7z, non-Python version) - 2010.4.0 x32 (7z, non-Python version), this one even fails to call make.exe, even after Load defaults for every preferences page. I haven't bothered to check out why this is happening. Note that in all cases, the GL preview shows the correct projection. Some versions of nona (or maybe all, haven't watched everything) complained about the projection not being GPU-compatible, so it switched to CPU remapping. Disabling GPU processing alltogether does not change anything. What version are you using to stitch your panini-general images, Tom? On Monday, August 19, 2013 2:22:09 AM UTC+2, Tom Sharpless wrote: Recent 64-bit Windows builds of Hugin don't apply the panini-general squeeze settings tops and bots while stitching, although they do display squeezed images in the preview window (I have tried 2010.4, 2011.4, and 2012.0) The 32-bit builds seem to apply tops and bots correctly. I suspect this is a word size issue somewhere in nona; but it might be in libpano. I rely on Hugin's panini-general for making architectural prints, and many of the images I work with nowadays are too big for the 32-bit version. I'm not currently set up to build Hugin at 64 bits, so I would really appreciate it if the Hugin team could fix this. -- Tom -- 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/acb16032-9e46-4c23-8cce-8c68f8fa5f9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Hugin is purely and simply unusable for panorama stiching
That's weird. I can stitch whatever I want with this same Hugin program and the results usually come out pretty nicely. Must be me doing something wrong? On Monday, March 24, 2014 6:08:34 PM UTC+1, Hugues D wrote: Hi, I just downloaded and installed Hugin. I then loaded 15 pictures I have stiched very easily with the free Microsoft ICE giving great results but some stiching errors. I thought that Hugin would be a better tool. Conclusion : Hugin is not even capable of finding two common points between 2 pictures in my set of 15. This is ridiculous and unusable. -- 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/0916798c-447e-41c9-9a41-3818dd68777e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: enfuse 4.1rc2 random segfaults with openmp compiled
On Tuesday, November 27, 2012 11:47:01 AM UTC+1, rew wrote: On the other hand, programs like enfuse are deterministic. They should yield exactly the same output given the same input. This means that intermittent problems are a hint that your hardware is broken. This is not necessarily true for multi-threaded programs, like the OpenMP enabled version of enblend. Example: worker thread A may finish before thread B in one run of the program, or later in another run (depending on e.g. the load of the CPU the thread is run on). Now, if the results of both worker threads are merged in a wrong way, this may result in unexpected behavior, but not necessarily always on the same input. Or both threads may for instance use the same variable for both read and write, without making a local copy first. Such an (implementation) error is easy to overlook. The chances of such an error are way higher than the chance of hardware failure. -- Bart -- 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
[hugin-ptx] Re: Hugin 2012.0beta1 released
Thanks again Matthew! Just installed the Python enabled x64 version and ran a panorama with it on Win7. Not much of a panorama, but it worked as expected (didn't even reset the settings). Haven't fiddled with any Python stuff yet so I can't comment on that. On Tuesday, July 31, 2012 5:07:53 AM UTC+2, Matthew Petroff wrote: Windows binaries for Hugin 2012.0.0-beta1 are now available. Unfortunately, they are not on SourceForge since the files I have uploaded don't seem to appear for some reason. For the Python enabled builds, one needs a preexisting Python 3.2 installation. -- Bart -- 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
[hugin-ptx] Re: Why WIGINWIS (What I Get Is Not What I See)?
What version of Hugin? On what machine? We need a bit more detail to check what went wrong. Could you repeat the process and if it fails again, tell us *exactly* how you got there? Because this is a very unlikely result if you *only* pressed the Stitch button on the stitching tab after checking the alignment in the fast preview. Please provide a zip with your project file and (scaled down) images as well if possible. -- Bart On Monday, July 9, 2012 8:01:51 AM UTC+2, ecs1749 wrote: I've done several 360-180 pictures where the picture looks great in fast pre-view mode but looks horrible after I stitch them together. What is causing that? See photos attached. -- 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
[hugin-ptx] Re: Looking for a new OSX Hugin builder
Well. Even though I don't own a Mac and have never used Hugin on a Mac, I'd like to give Harry a big thumbs up for maintaining the OSX build all this time. Harry, great job! Houdoe :) Bart On Saturday, June 30, 2012 6:39:56 PM UTC+2, DaveN wrote: Does this mean Hugin for Mac is dead? Nobody else is thanking you and I don't have the expertise to build it on my own based on what you describe. Dave On Jun 27, 9:30 pm, DaveN tahoedave...@yahoo.com wrote: Thanks Harry for all your work to date. I don't have any Xcode experience so I can't pickup where you are leaving off and it sounds very complicated. Good luck to you in your future endeavors. I do hope someone picks up on the Mac side of things. Dave On Jun 25, 11:07 am, Harry van der Wolf hvdw...@gmail.com wrote: Hi, I'm moving away from Mac OS X and back to Linux: I just bought a new laptop and put it on Ubuntu. I started using Linux in 1993 (when it was really only a kernel and a gcc predecessor and few curses based programs) and since 2003 I completely switched to linux apart from video editing. I switched to Mac OSX in 2006 when I was given a macbook and now I switch back to (Ubuntu) linux. I won't throw my MacBook Pro out of the window as my wife will keep using it as long as it will function, but I will move away. (Reasons and rant far below in this mail) With regard to Hugin: The XCode project has grown to a complex thing to maintain due to more and more dependencies and Apple's weird gcc/openmp strategy . Having maintained it now for 5 years for me most changes seem like small steps, unless some GSOC chunk moves in. For a newcomer I assume it's overwhelming. What I will do in the coming time in the XCode project (next to trying to keep up with the current developments): - Move from wxwidgets Carbon to wxwidgets Cocoa as carbon is going to be abandoned and it isn 64bit anyway. This is already implemented in the gui-overhaul branch be it experiemental. - Create several targets: -- a simple non-openmp target group which will build Hugin and which should be the most simple approach for a starting builder -- a openmp target group for the more experienced, daring builder (patch here, patch there, patch everywhere). -- trying to build a python enabled target. - Build a scripted portable Hugin bundle from the command line. *But the most important line in this email:* In a very near future I will ask others to step in as builders. Feel free to volunteer now :) One more with regard to Hugin: Lately more and more dependencies crept in. Next to that: Due to Apple's own curious strategy with regard to apple-gcc support and development, the openMP stuff really becomes a patched thing and hard to maintain over OS X versions (think of the enblend issues on Lion, which is now solved fortunately). Non openmp stuff needs to be compiled with gcc 4.2 or gcc 4.3 and openmp stuff can only be compiled with gcc 4.6.x (and not officially from Apple) to be able to run on Lion and up: This Lion OpenMP issue is an open bug for over a year now and still not solved by Apple and it can only be solved with the non-official patched 4.6 gcc. Probably it's Apple strategy to do nothing in this case: They want you to develop on Lion (buy it) for Lion (end users buy it). This patched non-apple gcc 4.6 fails to compile over 90% of the non-openmp stuff on non-Lion systems. === Below you will find my reasons for switching back to linux, which you may skip completely as it is not really relevant for the main reason of this mail: requesting new builders. Main reason: Video editing is for me the most important part. That doesn't mean that it is what I use my macbook most for. The hardware: I can afford a MacBook pro, that's not the issue. I simply don't want to anymore. The cheapest 15 MacBrook Pro costs 1750 Euros. A comparable notebook w.r.t. perfomance (and performance only) costs 750-900 Euros: That notebook misses the Apple MacbookPro superthin, slick design which actually makes the Apple MBP noisier (or more often noisy) as it can't dissipate it's heat well enough compared to an ugly ventilation slides covered laptop, not all pc notebook have the phantastic discrete video card a MacBook pro has, a pc laptop misses builtin bluetooth (mostly) and it has a (slightly) inferior keyboard and slightly inferior display. Also: The cheaper notebooks come with more memory and bigger harddisks and some of them have a discrete graphics card as well be it not as superb as Apple's. So with Apple: yes, you get very good quality (business ruggedness instead of consumer plastic) and yes, you
[hugin-ptx] Re: Cpfind should accept filenames and wildcards
If you like you could also create a little batch script to create your command line. The following script just creates a set of filenames based on a wildcard. The wildcard has been hard coded here, but I assume you know a bit about scripting already so you could easily modify this to your needs. @echo off setlocal enabledelayedexpansion set wildcard=* set files= echo Generating a list of files using wildcard: %wildcard% for %%f in (%wildcard%) do ( rem For full path, use %%~ff rem For just filename and extension, use %%~nxf rem For plain use, use %%f set file=%%f rem Check for spaces and escape if necessary if not !file!==!file: =_! ( set file=!file! ) rem Add file to our list of files set files=!files! !file! ) echo Done. echo. echo List: echo %files% echo. Good luck with your giant set of photos! What kind of your are we walking about? -- Bart On Monday, June 25, 2012 2:47:41 AM UTC+2, John Eklund wrote: In short: I strongly suggest making Cpfind accept filenames and wildcards to make it usable for scripting. Elaborated: For the last few years I've been on-off working on a big panorama project where over 60.000 individual images of mine are to be stitched into a couple of hundred panormas for a virtual tour. With this huge amount of material, a streamlined workflow becomes crucial. I have developed a tightly slimmed workflow where I develop several panoramas in parallel through my processing pipeline. I work mostly in the command prompt through batch scripts and avoid the Hugin GUI for the most part. My control point generator of choice has always been Alexandre Jenny's great old Autopano 1.03, which wins out over Autopano-SIFT in ease of use (Autopano-SIFT does not interpret wildcards, which makes usage a pain on Windows systems where the shell does not expand them for me). After upgrading my system, I've found that Autopano crashes on Windows 7 and I'm suddenly out of control point generator. The introduction of CPFind in the Hugin package is even worse from a batch-usage standpoint as it inconceivably expects a complete pre-made project file as input which would force me to handle every panorama in the GUI. As most of my images are preprocessed (including a stacking utility I developed myself), EXIF information is usually not preserved. This has never meant any trouble as Autopano doesn't need it anyway (thus I'd venture to say no control point generator or panorama stitcher should ever need it). Now having to manually add images and enter bogus lens parameters in Hugin to make CPFind work seems ridiculous. I'd wholeheartedly suggest adding an alternative method of calling CPFind by supplying images and making it process wildcards. I'm currently unsure how to get past this setback. I guess until CPfind is fixed, either I'll have to adjust to using Autopano-SIFT (and spend most of my time editing endless command lines of filenames), change to Linux or install Windows XP on a virtual machine just to get good old Autopano to work again. Any suggestions? Best regards John Eklund, Sweden -- 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
[hugin-ptx] Re: Error messages when loading pictures
Hi Mark, Just to make sure, do the complete paths of the images (e.g. /home/yourname/somepath/img0001.tif) contain any of these characters? I'm asking because the file name in this case would be just img0001.tif, but if the rest of the path contains an invalid character, this error may show up. By the way, the reason these characters are marked invalid is because make (used by Hugin to assemble the panorama) and possibly other tools in the tool chain have issues with them. -- Bart On Saturday, June 16, 2012 1:48:22 AM UTC+2, Mark wrote: Hello. Have been happily using Hugin for some months and all of a sudden, every time I try to import images to start a new panorama I get an error message saying I have invalid characters like $#@!= in the file name and to rename it. There are no such such characters in the file names and even when I rename them, the same thing happens. I was trying to load photos taken in portrait orientation but it appears to be affecting all of them now regardless. Mac OSX 10.6.8 Hugin 2011..4.0 -- 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
[hugin-ptx] Re: Memory allocation issue still not resolved w 64 bit version
Dear ecs1749, Please reply to the message your response is referring to, or learn to quote. In your messages (which I'm replying to right now) you say this setting and this procedure but it's unclear what you are referring to. This makes it hard for anyone to understand what you're talking about. -- Bart On Wednesday, May 30, 2012 5:35:11 PM UTC+2, ecs1749 wrote: Yes, this procedure solves the problem. I loaded 128 photos with this setting and it went through. On Wednesday, May 30, 2012 7:58:55 AM UTC-7, ecs1749 wrote: I am able to go a lot further with this setting. I am pushing to see how many photos I can process - right now it's processing 32 no problem. On Sunday, May 27, 2012 11:28:09 AM UTC-7, ecs1749 wrote: I downloaded the 64 bit version for Windows 7 and tried to load photos at full resolutions (width 4948) . Can only load 4 photos before running into the dreadful An error happened while loading image : caught exception: bad allocation. I have plenty of free memory - according to the Task Manager. -- 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
Re: [hugin-ptx] Memory allocation issue still not resolved w 64 bit version
It would help if you provide a *detailed* description of when things go wrong instead of just saying Hugin crashes. Which version, which OS, 32 or 64 bit, amount of RAM, *specific error message*, all of those may matter. Moreover, giving incorrect information (which you did, I guess not purposefully but nonetheless) can steer your fellow group members in the wrong direction. Being precise can save everyone some time - and a little frustration. Please keep that in mind. Also, I asked which program crashed a couple replies back. Please do read answers carefully when people are offering you a hand. We are all volunteers here. Could you try to see which image the cp generators are crashing on exactly? If you find it, you may want to post it somewhere so we can have a look at it. Maybe one of your images is broken which may cause all kinds of unexpected behavior. -- Bart On Tuesday, May 29, 2012 6:02:36 PM UTC+2, ecs1749 wrote: Yes, I have done both and still fails. Incidentally, the failure is not when loading the images. It's when detecting control points. I've tried changing detectors and they all fail the same fashion (some sooner than others). On Tuesday, May 29, 2012 12:09:06 AM UTC-7, Stefan wrote: On 27.05.2012 20:28, ecs1749 wrote: I downloaded the 64 bit version for Windows 7 and tried to load photos at full resolutions (width 4948) . Can only load 4 photos before running into the dreadful An error happened while loading image : caught exception: bad allocation. I have plenty of free memory - according to the Task Manager. Have you tried to increase the image cache memory setting in the Hugin Preferences dialog? Are you sure you have enough free disk space in your TEMP directory? With kind regards Stefan Peter -- In theory there is no difference between theory and practice. In practice there is. -- 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
[hugin-ptx] Memory allocation issue still not resolved w 64 bit version
How much memory is Hugin using when the error occurs? Are you talking about loading images inside Hugin itself or during stitching? In other words which program is failing? -- Bart -- 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
[hugin-ptx] Memory allocation issue still not resolved w 64 bit version
How much memory is Hugin using when the error occurs? Are you talking about loading images inside Hugin itself or during stitching? In other words which program is failing? -- Bart -- 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
[hugin-ptx] Re: Panorama Viewer For Android
Hi Jorge, I'm not sure why you haven't thought of this, but Flickr really is a good source if you need images to experiment with, for instance by searching for equirectangular (these are spherical images) [0]. Equirectangular images can be converted to cubic faces using e.g. Panotools Script [1]. For instructions see [2] (which mentions an older version but it still works the same). Good luck and be sure to post back whenever you have a viewable result. [0] http://www.flickr.com/search/?q=equirectangular [1] http://search.cpan.org/~bpostle/Panotools-Script-0.26/ [2] http://vinayhacks.blogspot.com/2010/11/converting-equirectangular-panorama-to.html -- Bart On Wednesday, May 16, 2012 4:05:25 AM UTC+2, Jorge Luis Iten Júnior wrote: Hi all, Like I told you before, I am working at a panorama viewer for Android. What I need now, is just a repository or web site where I can found the images to project. I need cubic and spherycal images. On 22 mar, 12:47, luca vascon luca.vas...@gmail.com wrote: Good! Open Source too? Il giorno 21 marzo 2012 22:44, Jorge Luis Iten Júnior jorgei...@gmail.comha scritto: It's gonna be free, it is my final paper in the university. On Wed, Mar 21, 2012 at 5:18 PM, kfj _...@yahoo.com wrote: On 20 Mrz., 14:54, Jorge Luis Iten Júnior jorgei...@gmail.com wrote: The intetion is to devolop a viewer with Android SDK 2.3.3 and OpenGL ES 1.0. So, is it going to be free software or commercial? Kay [snip] -- Luca Vascon. www.nuovostudio.itwww.officinepanottiche.com -- 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
Re: [hugin-ptx] Re: GUI overhaul
What about easy, medium, hard? Now we still have to find a way to implement fatality ;-) Without kidding: I think guided, standard and expert mode are pretty nice. Guided being assistant only, basically (except maybe from some basic viewpoint selection using the preview window). -- Bart On Thursday, May 10, 2012 5:37:38 PM UTC+2, zarl wrote: Jim Watters schrieb am 10.05.12 17:29: On 2012-05-09 5:05 PM, Bruno Postle wrote: On Wed 09-May-2012 at 09:12 -0700, Thomas Modes wrote: In the fast preview I started to hide controls in the beginner mode: currently only the mosaic drag controls are hidden for beginner. Which control do you think can be confusing for beginner? These can also be hidden in beginner mode. I'm in two minds about the beginner/advanced toggle, but I agree that the mosaic mode should be invisible to new users. Looking at the preview, maybe everything else is actually useful to beginners. I believe simple is a better term than beginner. How about standard and advanced modes? Looking forward to see and try out a build with this interface overhaul. Carl Beginner mode, is using wizards that do everything for you. The Assistant tab. Simple mode, is using a cleaner interface that hides all the advanced features that are hardly used. Advanced mode, is having every possible control available. We just need to define what a simple stitch is and what is not necessary to accomplish it. -- 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
[hugin-ptx] Re: Windows 7 64bit: Hugin 2011.4.0 64 works only first time and then don't works
Hi Niki, There are a couple things which can mess up the alignment. First, since you're using (ultra) wide angle lenses, it's important that you have set the correct lens type for your projects. Most likely you'd have to select fisheye. Next thing, how did you generate the control points? Did you check whether they are actually valid? A couple wrong control points can seriously mess up the alignment, so make sure they are right. Also, what are you aligning? Just 'positions, starting from anchor'? Or are you trying to optimize everything at once? It's usually better to start with just positions (or positions and view), and add options to optimize if the alignment is not correct. By the way I'm using the same version, also on Win7 x64, with mostly the standard options, without any serious issues. -- Bart On Monday, May 7, 2012 2:20:38 PM UTC+2, Niki wrote: Hi all,first time here and i hope to find a solution to my problem. I tried many version,many uninstalls and reinstalls,registry cleaning,different prefences...but the results is always the same,untill yesterday: i reinstalled Hugin after a long period without (for frustation and keep calm...) and at the begin it worked! Only 2 projects,3 photos each one,equirectangulars,made with a 18mm and 8mm...created points,optimized and aligned...all worked. But after that NO WAY,don't works,different projects and the same who worked ,nothing to do. The problem is always in the align process: hugin freezes. AND if the preview works,is a disaster,poligons,triangles,squares...and the planisphere is worst. I tried to improve the dedicated memory,from 256Mb to 2048Mb (i have 6GB) but nothing. Activated GPU...nothing. I have a i7 2,8GHz processor ,6GB 1600MhZ ram,the motherboard is a Asus P6T V2 deluxe, the HDD for OS is a Velociraptor 1rpm,plus 3HDD 1TB each one,the GPU is a GeForce GTX560Ti...more than 1500€ of PC. In past i used Hugin with WinXp Sp3 and NO PROBLEMS... What the hell i have to try? Changing version? Changing compatibility? Tring a 32bit version is the same... -- 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
[hugin-ptx] Re: Not able to run panomatic
You forgot the file extensions. E.g. if your image is called Mall_1.tiff, specify Mall_1.tiff, not just Mall_1. Also make sure you execute your command line from the directory where the images reside, or you'll need to specify the correct paths to the images instead of just the file names. PS: next time just paste the text here instead of a cropped screenshot please. On a side node: WTF#1: it appears you're having 2 output streams intertwined in your console (ContractViolation something, and the Panomatic output). How on earth did this happen? -- Bart On Thursday, May 3, 2012 7:49:43 AM UTC+2, Prashanth wrote: https://lh4.googleusercontent.com/-95afnfPI6sM/T6Ib5kCHRiI/AB8/Os5dCKJYmLE/s1600/pan.png Hi guys i have a project Mall_1-Mall_10.pto and images named Mall_1,Mall,2.Mall_10 . When i run the following command panomatic -o Mall_1-Mall-10.pto Mall_1...Mall_10 I'm getting the exception as the one posted in the pic above. Can anybody tell what i'm doing wrong? -- 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
[hugin-ptx] Re: multiblend 0.3beta - now with pseudowrapping for 360 degree panoramas
Hi David, I think I may have seen it, and meant to reply one day, but then I forgot... No problem :) Anyway, I will look into adding your MCE support for the next version - thanks for those. Since the project has been renamed to MXE instead of MCE we'd probably better call it by its proper name MXE from now on. Just curious, why is -lz necessary in the build script? Both libjpeg and libtiff make use of zlib functions. Normally you'd expect the compiler to add this -lz automatically when the build system was properly configured and you include -ljpeg of -ltiff. Unfortunately at least on my system this seems not to be the case, resulting in lots of errors like undefined reference to _inflate. Adding -lz manually resolves this (and adding it twice won't hurt the compiler). This may have to do with an incomplete pkg-config file in libtiff or libjpeg which may or may not have been fixed (note that my MXE system isn't entirely up-to-date, I'll check this later). I will add seam saving/loading soon as well, but I will use TGA as it is easily compressed (although PNG may be even better). TGA may be nice compression wise, but I don't think this format is as widely known as TIFF or PNG, so I'd opt for using the latter. Note that this is pretty straightforward when using (for example) the freeimage library (as opposed to using functions from libtiff or libjpeg directly). Cheers, Bart There may also be some disk caching features added, although the biggest problem at the moment is heap fragmentation (and this may actually be the cause of Evgeny's problems, rather than running out of memory). David On Thursday, April 19, 2012 9:26:08 AM UTC+1, Bart van Andel wrote: Hi David, Have you missed the contributions I posted earlier [0] (probably) or are you just ignoring it (unlikely)? [0] https://groups.google.com/d/msg/hugin-ptx/JPiViZQ-Ycw/4ygfvPVq4hgJ -- Bart -- 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
Re: [hugin-ptx] merge enblend and multiblend code?
On Monday, April 30, 2012 9:13:42 AM UTC+2, Monkey wrote: I did try multi-threading it in a couple of places, but maybe it was doing it wrong because it didn't make it any quicker. That was with native Windows multithreading - unfortunately Microsoft don't want you to use OpenMP with Visual C++ Express, which is the only option now multiblend is multi-platform. Fortunately, cross-compiling using MXE is pretty easy as I've shown in another thread [0, 1]. I haven't actually tried compiling anything with OpenMP enabled using this approach, but I don't think it should be too much of a hassle. And there's a great support community there so if I need help all I need to do is ask. [0] https://groups.google.com/forum/?fromgroups#!topic/hugin-ptx/-3-i9ynuCig [1] https://groups.google.com/d/msg/hugin-ptx/JPiViZQ-Ycw/4ygfvPVq4hgJ Besides which, the seaming algorithm can't be multithreaded (at least not easily), and that and image loading are usually the two slowest parts. David On Monday, April 30, 2012 7:24:32 AM UTC+1, GnomeNomad wrote: Thanks, I thought it was multi-threaded. On 04/28/2012 11:41 PM, Monkey wrote: The same benefit it has on any system - it's quicker (but not better) than Enblend :). The multi in multiblend doesn't have anything to do with multicore processing - it's (currently) single-threaded. On Sunday, April 29, 2012 1:26:16 AM UTC+1, GnomeNomad wrote: What benefit does multiblend have on uniprocessor systems? -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god http://www.clanjones.org/david/ http://dancing-treefrog.deviantart.com/ http://www.cafepress.com/otherend/ -- 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
[hugin-ptx] Re: multiblend 0.3beta - now with pseudowrapping for 360 degree panoramas
Hi David, Have you missed the contributions I posted earlier [0] (probably) or are you just ignoring it (unlikely)? [0] https://groups.google.com/d/msg/hugin-ptx/JPiViZQ-Ycw/4ygfvPVq4hgJ -- Bart On Tuesday, March 27, 2012 1:01:56 AM UTC+2, Monkey wrote: Hi all, Previous discussion: http://groups.google.com/group/hugin-ptx/browse_thread/thread/b08211b2659a7eab There's a new beta (I say beta; I probably really mean alpha) of multiblend available at http://horman.net/multiblend I've implemented a feature I'm calling pseudowrapping to blend around the left/right borders for 360 degree panoramas, a much- requested feature. There are no command-line switches to access this; pseudowrapping is enabled any time multiblend is run with only a single uncropped TIFF (such as that already created by a normal multiblend run) as its input. This is really only a stepping-stone to a properly integrated wrapping solution - it can't be called straight out of Hugin, for example, because it only wraps a previously blended panorama. Questions, comments, and complaints please :) David -- 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
Re: [hugin-ptx] Re: iterations of cpfind gives back different number of points (matches)
On Wednesday, February 8, 2012 2:25:51 PM UTC+1, Harry van der Wolf wrote: Only one calculation delivered one match less (floating point accuracy?) Floating point accuracy will be exactly the same for consecutive runs (unless your processor is physically broken), so this cannot be the issue. I haven't looked at the algorithms used (or the source code at all), but if RANSAC (random sampling consensus) is used, the differences can be caused by different seeds for the randomizer. Note that in this case it isn't really a bug, although it may seem strange. RANSAC needs randomization. The results would be the same every time if the random values used by RANSAC were more or less static (e.g. same initial seed instead of based on the computer clock) which would solve this apparent issue. But this is a mere guess. -- Bart -- 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
[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes
Hey everybody, I've downloaded the source files to try and see if I could compile it for my own purposes. Attached is a modified version (source code) with a number of changes compared to David's current version: - The software can now be cross-compiled on a Linux system targeting Win32, using mingw-cross-env (MCE) http://mingw-cross-env.nongnu.org/. This took some effort, because this compiling environment is slightly different from both native Linux and WIN32, e.g. it doesn't come with a memalign-implementation, so I had to import one (not my own code). - Source code structure has been restructured slightly: all source code has been moved into a src/ directory. - Build script provided (build.sh), capable of building natively, or using MCE, both in release and debug flavors. Binaries will be placed in bin/ directory. - Code reformatted. Mixed spaces and tabs were being used, now the code more or less follows the Linux standard with the exception that longer lines were kept. GNU indent was used for this (indent.sh script provided). - Most importantly, I needed to be able to provide my own seam masks instead of having multiblend compute one for me. So I've implemented a function to load a PGM mask file. This file should use gray values [0..n-1] corresponding to images 0 to n-1, and have dimensions equal to the input span (may need --nocrop argument to prevent multiblend from modifying the output size; in my case it did). However a function to unstretch palettes from [0..255] back to [0..n-1] has also been implemented (--loadseams-unstretch). - Mask saving (already present) is now a command line argument (--saveseams). This file can be edited and used again as an input mask. In this case, --loadseams-unstretch is required because the current implementation of saving the seams stretches the palette. - I suppose the other functions for saving intermediate files (pyramid for example) could be exposed similarly, but I haven't implemented that (yet). - NB: the default behavior hasn't been changed. - NB: this is a work in progress, therefore, YMMV when using it. Code is tested only through the cross-compile build and works fine for me. If anyone is interested I can post the binaries to this list or some other place. Compiling natively on Linux works fine too, but I haven't actually blended anything with it (it does run though). Compiling natively on Windows hasn't been tested. Comments welcome! @Monkey: Feel free to put this file on your site! What about putting the source code on github for example? -- 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 multiblend-v0.2-bart.7z Description: application/7z-compressed
[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes
Oh, by the way, when installing mingw-cross-env, it is not required to build the whole system (which takes ages). After unpacking the .tar.gz archive or hg cloneing the system, a mere make tiff jpeg should do. This will automatically build the dependencies required for libtiff and libjpeg (e.g. the compiler itself). -- Bart -- 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
[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes
Although this is slightly off topic, I feel I should mention it. On Monday, January 16, 2012 6:05:15 PM UTC+1, Monkey wrote: I've updated the download archive now - I haven't changed the version number as the fix doesn't change multiblend's functionality. Please do update version numbers if the contents of the file have changed. There may be various reasons why this should be done, but one in particular that I know of is this: There exists a cross compiler environment named Mingw-cross-env [0], which relies on the file name for versioning. Part of the script is an update procedure which checks if newer files are available. Obviously this will fail if the filename hasn't changed. Moreover, it includes a hash based check to see if the downloaded file is indeed the file we are looking for (a basic sanity check). And this part will fail if the *contents* of the file with the same file name have changed. Although this is mostly important for libs, I guess it's good practice to apply this reasoning to other packages as well. This statement is not only applicable to multiblend, it also affects any other package. I believe Hugin itself doesn't suffer from this as version numbers are properly used in file names on sourceforge (note: behavior not recently tested). [0] http://mingw-cross-env.nongnu.org/ -- Bart -- 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
[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Windows only)
Sounds interesting and I'd like to try it, but unfortunately my virus scanner popped up a warning while attempting to download the file. Has the file been tempered with? [image: Avira] Warning In order not to compromise your security, this page will not be accessed A virus or unwanted program was found in the HTTP data of the requested page. *Requested URL:*http://horman.net/multiblend/multiblend0.1.zip*Information:*Is the TR/Crypt.XPACK.Gen Trojan Generated by Web Protection 12.01.06.17, AVE 8.2.8.14, VDF 7.11.20.66 -- 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
Re: [hugin-ptx] How to force CP detection order?
On Saturday, October 22, 2011 1:13:47 AM UTC+2, Bruno Postle wrote:
On Fri 21-Oct-2011 at 11:43 -0700, McFly wrote:
Hi,
I bumped into a problem trying to stitch a panorama with hfov 360° (in
fact
about 4x360° :) )
Starting with the next photo after 360°, hugin detects the same objects as
in the first photo, so the resulting panorama will be 360° with 4
layers.
This is normal but I'd like the panorama to continue beyond 360° (to show
evolution of the objects and scenery in time -if you were wondering why)
A panoramic scene isn't a simple flat strip that you can stretch out
beyond 360°.
I suggest you treat this as four 'layers', stitch them separately,
and stick them together in an image editor later. You can do this
with a single Hugin project by turning the photos on and off
individually in the preview before stitching.
... Or you can keep them in one project (such that similar features get a
perfect overlay), and stitch this project file several times, with different
images enabled/disabled. You can do so in the Fast Preview window. I suggest
you keep an overlap between each of the 360 degree panos, e.g.:
- select (enable) the images you'd like to show up on the leftmost part, and
stitch;
- enable the next set of images, but keep a small overlap with the previous
ones (e.g., you only move 270 degrees);
- iterate until at the end.
- merge the files using either an image editor, or using command line tools.
For Smartblend the last step would be something like this:
smartblend -o final.tiff pano1.tiff -x {offset for pano2} pano2.tiff -x
{offset for pano3} pano3.tiff ...
Make sure to post your result here! :)
--
Bart
--
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
[hugin-ptx] Re: Creating an HDR panorama
http://wiki.panotools.org/A_simple_approach_to_HDR-blending -- 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
[hugin-ptx] Re: Smartblend wrapper not in the Windows install packages.
To get things started, I already posted a patch (which updates the old ISS installer scripts instead of the new NSIS ones, my bad, but probably still contains a nice starting point) [0]. And here's the LP link: [1] [0] https://groups.google.com/d/msg/hugin-ptx/E6EC4PCV2fE/7ymv4_kfaBgJ [1] https://bugs.launchpad.net/hugin/+bug/788990 -- Bart -- 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
[hugin-ptx] Re: Is the panosphere preview looking at the outside of the sphere?
On Friday, May 27, 2011 9:53:46 PM UTC+2, kfj wrote: On 27 Mai, 21:39, Milan Knížek knizek...@volny.cz wrote: Anybody filed it as a bug/feature request? (I have not found anything on launchpad.) The flipped left / right sides are really confusing. I haven't. Please go ahead and do it. I'm not convinced by Yuval's lone voice earlier in this thread telling me that looking at the outside of the panosphere was natural. Sorry for not replying earlier, but I also think that looking at the panosphere from the outside is the right thing to do. Normally the camera is inside the sphere, looking at the outside. That's the normal panorama view. The spherical view is kind of a god mode allowing a meta view on the whole world, thus, from the outside. If it's confusing, flipping the x coordinate should be quite a trivial option (that is: checkbox and/or preference) to add. I wouldn't go for forcing either the current view (which is mathematically the most sound) or the proposed reversed view where every image is flipped in the x direction so it doesn't look mirrored. -- Bart -- 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
[hugin-ptx] Re: enblend
You need to modify your .hg/hgrc to read like this (between the lines) -- [paths] default = ssh://*sf-username*@hugin.hg.sourceforge.net/hgroot/hugin/hugin [ui] username = *Full Name em...@provider.com* -- Replace sf-username with your sourceforge username, and fill in the details of the username field. Now when calling `hg push` you will be asked for your sourceforge password and you should be good to go (if you have push permission). -- Bart -- 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
Re: [hugin-ptx] Re: enblend
You don't actually need to make a fresh checkout when changing the path in the .hg/hgrc file. I had similar issues before pushing the smartblend-fix [0] and the only thing I had to modify was this config file. No fresh checkout. Saves you a bit of waiting next time something similar is needed :) [0] https://groups.google.com/forum/#!topic/hugin-ptx/ekK0pNTLogc -- Bart On Thursday, May 26, 2011 11:03:53 AM UTC+2, kornel wrote: Am Donnerstag, 26. Mai 2011 schrieb Bart van Andel: You need to modify your .hg/hgrc to read like this (between the lines) -- [paths] default = ssh://*sf-username*@ hugin.hg.sourceforge.net/hgroot/hugin/hugin Seeing this 'ssh' protocol for hugin, I tried to clone from the the ssh-enblend-repository. Making changes, comitting. Push was OK!! You don't actually need to make a fresh checkout when changing the path in the .hg/hgrc file. I had similar issues before pushing the smartblend-fix [0] and the only thing I had to modify was this config file. No fresh checkout. Saves you a bit of waiting next time something similar is needed :) So you have directed me to the right cause, thanks. You're welcome! [0] https://groups.google.com/forum/#!topic/hugin-ptx/ekK0pNTLogc -- Bart -- 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
Re: [hugin-ptx] Smartblend wrapper doesn't work in Hugin 2011.0 RC1
I've committed a fix, see the LP bug report. It had to do with the additional '--' argument separator which is apparently new in this Hugin release. Smartblend tries to load this as an image but of course it does not exist. By the way, the upside down issue does not concern TIFF images on my machine. I suspect you're using JPG output, Henk? I remember this being an known issue with Smartblend and JPG. -- Bart -- 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
[hugin-ptx] Re: Smartblend Wrapper Fixed - 2011.0.0_RC2 will follow
On Tuesday, May 24, 2011 9:40:00 PM UTC+2, Henk Tijdink wrote:
Have downloaded the new wrapper and it works now with 2011.0RC1.
I have done some testing with the old wrapper with 2011Beta 2 and 3
too and then the old wrapper still worked.
The change has come between Beta 3 and RC1.
I hadn't noticed this behavior with older versions either. The only purpose
of the wrapper is actually to reformat or get rid of parameters that are
hardcoded into Hugin. A nicer way would actually to be able to drop or
modify those hardcoded values. New parameters aren't automatically
understood by the wrapper, which is why it stopped working with this
release.
The wrapper is not in an install package for windows. You have to
download it separately as you have to do with smartblend.
With Hugin is probably nothing wrong, but only the wrapper has to be
adapted to a new extension in Hugin.
But it should be nice if the wrapper and instructions for it is in the
install package, so you can copy it to your smartblend folder.
Agreed. I don't have a Windows build environment setup, so I can't test it,
but the attached patch may solve this. It modifies1 and adds 1
CMakeLists.txt files, and changes to the Inno Setup (pre)release scripts are
made accordingly. Can someone with a working Windows build env test this?
(Allard, are you reading this?)
--
Bart
--
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
diff -r f00957574874 platforms/windows/CMakeLists.txt
--- a/platforms/windows/CMakeLists.txt Tue May 24 21:57:34 2011 +0200
+++ b/platforms/windows/CMakeLists.txt Wed May 25 01:21:47 2011 +0200
@@ -1,4 +1,5 @@
ADD_SUBDIRECTORY(droplets)
ADD_SUBDIRECTORY(installer)
-ADD_SUBDIRECTORY(huginsetup)
\ No newline at end of file
+ADD_SUBDIRECTORY(huginsetup)
+ADD_SUBDIRECTORY(smartblend-wrapper)
\ No newline at end of file
diff -r f00957574874 platforms/windows/installer/hugin_prerelease.iss
--- a/platforms/windows/installer/hugin_prerelease.iss Tue May 24 21:57:34 2011 +0200
+++ b/platforms/windows/installer/hugin_prerelease.iss Wed May 25 01:21:47 2011 +0200
@@ -1,6 +1,7 @@
; Hugin InnoSetup Installer File
; (C) 2008 Yuval Levy, licensed under GPL V2
; Minor adaptations 2009-2010 by Allard Katan
+; Smartblend-wrapper added 2011 by Bart van Andel
; if possible, let the Make process edit AppVerName to have a proper, automated SVN numbering
; make sure that the Make process copies this file from platforms/windows/msi to INSTALL/
; and that it also copes the files win_installer_readme.txt and win_release_notes.txt to INSTALL/
@@ -69,7 +70,7 @@
; Name: ap_c; Description: Autopano-SIFT-C (Patent issues in the USA!); Types: autopanoSIFT full custom
Name: matchpoint; Description: Matchpoint (EXPERIMENTAL control point generator); Types: full custom
Name: panotools; Description: Panotools Command Line Tools; Types: default full custom
-
+Name: smartblend; Description: Smartblend-wrapper; Types: default full custom
; not necessary (if the directory is not empty) but clean
[Dirs]
@@ -146,6 +147,9 @@
Source: FILES\bin\PTBatcher.exe; DestDir: {app}\bin; Components: core; Flags: overwritereadonly
Source: FILES\bin\PTBatcherGUI.exe; DestDir: {app}\bin; Components: core; Flags: overwritereadonly
+; smartblend wrapper
+Source: FILES\bin\smartblend-hugin.bat; DestDir: {app}\bin; Components: smartblend; Flags: overwritereadonly
+
; install redirect URL to welcome page
Source: url.txt; DestDir: {app}; DestName: test.url; Flags: deleteafterinstall; Attribs: hidden
@@ -155,6 +159,7 @@
Source: FILES\doc\enblend\*; DestDir: {app}\doc\enblend; Components: enblend; Flags: overwritereadonly recursesubdirs
Source: FILES\doc\hugin\*; DestDir: {app}\doc\hugin; Components: core; Flags: overwritereadonly recursesubdirs
Source: FILES\doc\panotools\*; DestDir: {app}\doc\panotools; Components: panotools; Flags: overwritereadonly recursesubdirs
+Source: FILES\doc\smartblend\*; DestDir: {app}\doc\smartblend; Components: smartblend; Flags: overwritereadonly recursesubdirs
; autopano docs
;Source: FILES\doc\autopano-sift-C\*; DestDir: {app}\doc\autopano-sift-C; Components: ap_c; Flags: overwritereadonly recursesubdirs
; hugin's UI and languages
diff -r f00957574874 platforms/windows/installer/hugin_release.iss
--- a/platforms/windows/installer/hugin_release.iss Tue May 24 21:57:34 2011 +0200
+++ b/platforms/windows/installer/hugin_release.iss Wed May 25 01:21:47 2011 +0200
@@ -1,6 +1,7 @@
; Hugin InnoSetup Installer File
; (C) 2008 Yuval Levy, licensed under GPL V2
; Minor adaptations 2009-2010 by Allard Katan
+; Smartblend
[hugin-ptx] Re: panorama making software for droid
It's not a Hugin- or Panotools-related app, so I don't think we can answer this properly. Why don't you just try it and report back here? It seems to be free (at least for the non-Pro version). -- Bart -- 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
Re: [hugin-ptx] Re: Finding control points for many images
On Thursday, May 19, 2011 9:53:41 PM UTC+2, GnomeNomad wrote: Jeffrey Martin wrote: one could argue that it is more user friendly to try to join the first and last image of the sequence (assuming a full circle) or that it is more user friendly not to try to join them (assuming only a partial tour of the horizon). the most popular use-case should be the default. there is no way for cpfind to know or guess if the sequence covers a full circle without trying to match them. I think it should try by default. in my experience (but i'm biased towards 360's admittedly) most panos people try to stitch are 360 images. I've never even tried to shoot one, let alone stitch one. So I wouldn't make it the default. But what's being said about adding this convenience feature sounds good and workable to me. I don't see any harm in having cpfind to *try* to match the first and last image. If it finds a connection, voila, probably it was indeed a 360 degree pano. If it doesn't find any matches, then probably it wasn't. How big are the changes of a false positive (e.g. it connects the images where it shouldn't)? Or a false negative (it doesn't where it should)? My guess is that in most cases it will work. So even though I don't often shoot a 360 (I've only done maybe 4 of them) I opt to try finding a 360 by default. The small extra cost of computation I don't mind. -- Bart -- 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
[hugin-ptx] Re: Need some help | Hugin Speed test tab for automated hardware evaluation
Hi Dip, I'm sorry but I fail to see the importance of these preliminary results. You did not provide detailed enough info about the used equipment to see what the results mean. My guess is that the Atom equipped computer contains far less memory than the Core one, and obviously it has less processing power. Some observations: - The CPU usage graphs look pretty similar when stretched to 100% of the total time used (so each device takes 100%) instead of time in seconds. - This is also valid for the memory write graph (what is read/secs? KB/s? Read operations per second?) - About the same is true for the memory graphs, although of course the Core uses more memory than the Atom. Is this total amount of memory used by the whole system or just by Hugin? I'm asking because (max mem) - (min mem) is about 200MB for both devices. And please use MB instead of kB on the vertical axis, this makes it more readable. - Because the Atom has less memory *and* less speed it can't read all the images at once but spreads it out over more time than the Core. This is all pretty logical and I don't see what information your tests have provided that we couldn't know by simple reasoning. Furthermore, the notion that Calculating/finding the bottlenecks and tuning expensive algorithms to boost this performance should be valued contribution to hugin community. always makes sense, it does not need a speed test. Tuning algorithms (especially memory intensive ones, where not all data will fit in RAM) for optimal performance and memory usage is a nice aim, but I don't think that's what you propose to do yourself. At least your proposal doesn't mention it. I've taken a look at the schedule in your proposal too and don't get me wrong, but you're taking a lot of time to create a working XML parser/builder. I hope you're aware that there are libraries available which will do this task for you without you having to worry about implementation details, right? For instance, PHP has SimpleXML and also XmlReader/XmlWriter which are very easy to use and definitely don't need 2 months work. Last point: why would I want a tab to evaluate Hugin speed? I can see a point in a menu item for this, but something as permanently visible as a tab does not make sense to me. Overall I think your proposal definitely needs some work. I hope you didn't think this reply is too discouraging, I'm just trying to see the actual point in this. -- Bart -- 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
Re: [hugin-ptx] Re: Need some help | Hugin Speed test tab for automated hardware evaluation
On Tuesday, April 19, 2011 6:19:27 PM UTC+2, rew wrote: On Tue, Apr 19, 2011 at 04:49:54AM -0700, Bart van Andel wrote: always makes sense, it does not need a speed test. Tuning algorithms (especially memory intensive ones, where not all data will fit in RAM) for optimal performance and memory usage is a nice aim, but I don't think that's what you propose to do yourself. At least your proposal doesn't mention it. The does not need a speed test part is something I strongly disagree with. Way too many people optimize what they percieve as being a bottleneck and end up optimizing the wrong thing. Sure, I'm not questioning that. You have to find out what can be optimized. Benchmarking may be a tool for that (I'm not saying it's useless), but a thorough understanding of the procedures and algorithms in use is probably even more important. Now specific for hugin. What performance bottlenecks do we expect? == Finding control points. == Finding control points is usually a two-step process. First distinitive points are searched. Next these are matched against the distinctive points in all the other images. Recent updates to Hugin have already helped optimizing this by allowing the user to specify other search strategies (e.g. only adjacent pairs A-B, B-C etc), but I guess you already knew that. - Memory bottleneck? This is a process that requires each image (or even a scaled-down version of the image) in memory to find distinctive points. After that there are just a few (in computer terms) points that need attention, so very little memory requirements afer the images are processed. It requires every image to be processed to find feature points (defined by a descriptor like SIFT, SURF, or what our own cpfind produces). This can be done for each image separately. The second step does the actual matching, keeping only points which are found in (at least) one image pair. The old generatekeys/autopano combo did exactly this. More recent approaches combine this into 1 program, but as far as I know, none of them require all the images to be present in memory at the same time. Note that total memory used != (size of program) + (size of image) + (keypoint datastructure). While processing the image, multiple copies of the same image, at different resolutions (image pyramid), using a few different image processing operators (e.g. derivative, DOG etc) may be required, depending on the feature point extraction algorithm. - CPU bottleneck? Possible. The old finding matches step was horribly slow for larger stitches. A factor of 10 performance increase can be achieved by searching for matches between adjacent images first, then optimizing the layout and then recheck the matches between images that are now seen to (almost) overlap. As I said before we already have that. May be a candidate for even more optimization, but I think it does quite a nice job already, at least when some information is available, e.g. images are pre-aligned, or the user knows that the images are taken in a certain pattern, e.g. left-to right. == optimizing the layout == This is currently implemented as a multi-dimensional upgrade of newton-raphson (it has a name, which I've forgotten). This is very efficient at converging on a solution. Performing benchmarks should show that this is not worth the trouble of optimizing: it already takes little memory and little CPU time. As the algorithm is already much better than simple strategies like hill-climbing, there is probably little to be gained by optimizing this step. I can't comment on this one, I wouldn't know. == displaying intermediate results == For a user to see what the result is going to look like and if the results are usable, a quick preview of the resulting panorama is neccesary. - memory In theory numimages * numpixels_per_image of pixels are involved. This can be a large number. More precisely: the sum of the pixel counts of all images. Hugin does not require all images to have equal dimensions. In practice the display is only on the order of 2 Mpixels. This is a very small number for a computer. A modern computer can easily handle 120Mpixels per second. (60 fps at 2Mpixel). Just curious: on what info is this based? I all depends on what you mean by handle. Simply outputting 120Mpixels/s (at 32bpp, this would be 480MB/s) directly to the screen is a bit different from doing computations for each pixel and *then* outputting it to the screen. Of course modern GPUs are way faster at handling most pixel related operations than CPU, hence the improved usability of the fast preview compared to the old preview. If each of my images is going to show as a 100x100pixel image (10kpixels), it is wasteful to process the 10Mpixel camera image each time. In practise I see huge amounts of memory being used. In theory - CPU In practice hugin is slow in this step. Benchmarks are needed to see where
Re: [hugin-ptx] Re: [REVIEW] Pushing Hugin changes to VIGRA upstream
Nice work! I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! There are still a few packages missing in the cross-compiling system I'm using (mingw-cross-env [0]), I'd have to check which ones, but I hope that in the end I'll be able to do a full cross-compile. This will make the process of releasing Windows binaries even easier (at least for me). Note that I *really don't* have that much spare time, so it may take a while. Of course anyone interested may take a look as well, we're talking open source here :) [0] http://mingw-cross-env.nongnu.org/ -- Bart -- 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
[hugin-ptx] Re: OT: the future of enfuse/enblend
Well, I didn't exactly study the verbose output, but some time ago, I sent Michael Norel (the author of Smartblend) a message, asking about SB going open source. This was a follow-up on an email sent earlier and discussed briefly here [0]. Maybe the email and reply are interesting to the group, so here they are: -me (9 Feb 2011)- Hello Michael, It's been almost 2 years since we were last in touch. I imagine you have been very busy. Is there any news on the Smartblend sources and/or any further development? Out of curiosity: what other projects are you involved in? Anything image-related? I found out that you used to have a website about Smartblend, but it has been turned into one of these annoyingly useless search page sites by some domain scraper, unfortunately. Hope to hear from you soon. Best regards, Bart van Andel -Michael Norel (10 Feb 2011)- Hello. Still no development and no plans for SB and no news. But anyone still can contribute to ENBLEND project or related. There a re many good algorithms to use for blending in public domain. psychovisual error + kolmogorov min cut + ENBLEND + subpixel acuracy and pyramid with alpha channel = smartblend Last years my work is Computer Vision , Real Time SFM , Augmented Reality. So i spend my time for very intresting things, more complex than smartblend. Thanks. --- Sorry for not posting this sooner, I kind of forgot about it until I read Jeffrey's post. [0] https://groups.google.com/forum/#!topic/hugin-ptx/5oRw_6uVsoI -- Bart -- 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
Re: [hugin-ptx] Re: [REVIEW] Pushing Hugin changes to VIGRA upstream
Hi Stefan, On Thursday, March 31, 2011 10:15:31 PM UTC+2, Stefan wrote: Am 31.03.2011 18:06, schrieb Bart van Andel: I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! I had a look at his, too. However, without being able to actually use the resulting binaries due to my lack of a windows license and my lack of interest to get one, I figured that I won't be able to support this kind of port. On the other side, if I had a windows license and would be willing to create panos on this platform, wouldn't it be more natural to use the (available) free MS development tools for porting? I understand your situation, but from my point of view, compiling under Linux is usually a bliss. I like the way things can be automated using the shell in Linux. And this mingw-cross-env thing really takes away a lot of pain. For instance, I can build the required libs (minus some that I still need to add) using a single make command. The system will automatically download the sources for me, including dependencies, and build everything into static libs. The only thing left to do then is to compile Hugin (and Enblend, APSCpp, ...) itself, using cmake and some cross-compiling settings. Pretty easy. I'm using a virtual machine to do this. On the other hand, using the MS path requires many more steps. A whole lot of packages need to be compiled separately. Just take a look at [0] to see what I mean. Ok, if your initial setup is done (building dependencies), building and rebuilding Hugin is not a problem, except when some dependency needs a rebuild... To me, the Linux approach is much simpler. And if the workflow has been setup correctly, Hugin can be built on a (native) Linux machine, QA tested by a few Windows pre-testers, and then distributed. I think that hugin needs to attract some more windows users being able to fend for their OS themselves. Providing binaries that are not tested by the producer and that can not be properly supported, therefore, does not help. I agree about quality assurance. Distributing non-tested binaries is not a good thing. But this kind of testing has to be done for native Windows builds (built on a Windows machine I mean) as well, and depending on the builder, this will happen or not. Sorry, just my 2 cents. No apologies required, your points are valid. [0] http://wiki.panotools.org/Hugin_SDK_(MSVC_2010) -- Bart -- 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
Re: [hugin-ptx] Re: [REVIEW] Pushing Hugin changes to VIGRA upstream
On Friday, April 1, 2011 1:08:29 AM UTC+2, Bruno Postle wrote: Regarding fixing the Hugin sources, there is no need to remove the Hugin copy of the library from the sources if it is possible to build with the system library as an option. Is there a valid point in keeping a local copy of a library if the official one works? If you mean keeping the local copy until the changes are in a release version of Vigra, I can understand, but otherwise? -- Bart -- 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
Re: [hugin-ptx] Bug
Probably related: out of curiosity I've played around a bit with a test makefile to try different special characters in target names. I've added the resulting test.mk as an attachment to bug Stitching fails with '' character in path [0]. [0] https://bugs.launchpad.net/hugin/+bug/679353 -- Bart -- 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
[hugin-ptx] Re: how should hugin interact with plugins?
On Friday, March 11, 2011 5:01:48 PM UTC+1, kfj wrote: On 11 Mrz., 11:40, Bart van Andel bavan...@gmail.com wrote: When plugins report a display name and a short description as well, this can also be shown in this dialogue. If the plugin does not report any options, it can be run directly without asking anything. Note that this needn't be restricted to Python plugins. I don't quite understand what you mean by 'report a display name', can you clarify? By 'display name' I mean just a name to display (e.g.) in the menu structure. This means you can name the file e.g. kfjGBlur.py, but the display name 'gaussian blur', as an example. I'm not familiar with Python syntax, but the interface may look like this: getPluginName : string getPluginDescription : string getPluginParams : arrayname, type, min, max, default, whatever Name is what you'd need in the menu, description maybe on mouse over, and params are used to display the GUI (in case we decide on doing so). Min/max may not always apply, in the case of an enumaration type, it may report the options for a drop down list, or radio button list. -- Bart -- 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
Re: [hugin-ptx] Re: hugin has become unusable for me
You're not insane, but this really isn't a bug. There's no photometric optimization going on here, Hugin is just handling exposure like it should. When it reads EV 12 in a source image, but the output image is set to 15 EV, it correctly applies a curve to the brightness value of the input image to get it to match with the selected output EV. What you want is to bypass this correct behavior, which can indeed be accomplished by setting every EV to the same value. Any value will do, 0 is just as right as 12, or PI, or whatever you like. So, instead of filing a bug report, you should file a feature request for a checkbox (or another means of setting) to bypass EV computations for the stitching phase. I hope this will clear up some misunderstandings about the way Hugin (correctly) handles EV. -- Bart -- 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
[hugin-ptx] Re: Call for Nominations: Dedication of 2011.0
On Wednesday, March 2, 2011 6:50:50 PM UTC+1, kfj wrote: On 2 Mrz., 18:34, harry van der Wolf hvd...@gmail.com wrote: Personally I don't like the concept of dedicating a piece of software or an OS project to anyone or anything at all. Me too, I thought it was a one-time occasion as well. Therefore I would like to raise the question if we as OS community would like to dedicate Hugin, both as software and as project, to someone or something. My vote is against it. I'm also against dedications. I vote against as well. -- Bart -- 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
Re: [hugin-ptx] How should the 'Grey picker' work?
On Wednesday, March 2, 2011 4:50:40 PM UTC+1, paisajesenvenezuela wrote: whoa i mustve been using a really old version of hugin now what does this gray picker do? Not necessarily, it's a brand new feature. The gray picker can be used to correct the white balance of an image semi-automatically. You need to select a point which contains what should be a neutral gray, but may be (e.g.) a bit reddish in the image. Hugin will then compute the right white balance values which will correct this (e.g.) reddish shade into neutral gray. Quite handy. -- Bart -- 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
[hugin-ptx] Re: 2nd Panini Video demo
Nice showcase! It's also nice to hear your voice for a change, this will make reading your posts here a bit more lively in my head from now on :) -- Bart -- 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
[hugin-ptx] Re: Undeletable artifacts
Hmm you're on WinXP right? I may have posted a Vista/7-specific version of cacls. There have been a number of commands which provide ACL-related functionality. You need to replace 'xcacls' with just 'cacls' [0], my mistake. Alternatively, you can use the Windows Explorer GUI to check file rights, by right-clicking the affected files, choosing 'Properties', and browse the 'Security' tab. BTW: I don't have XP at hand anymore, so some names may be wrong. -- Bart [0] http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cacls.mspx?mfr=true -- 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
[hugin-ptx] Re: enblend help,
What error? If I try my solution, I get a perfectly valid .jpg file out of it. No warnings or errors at all. I'm on Windows 7 x64, using Enblend 4.0 (from Hugin 2010.4.0-beta2 x32 build). I hope you agree with me that the info you are providing is pretty brief. You haven't provided which OS you are using, which version of Enblend, i.e. nothing at all except a command line. You need to provide at least some details, or we can't help you. -- Bart -- 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
[hugin-ptx] Re: Undeletable artifacts
Are the files still undeletable after a reboot? If not, there might be an issue with the files never being closed by the application. I can't imagine why this would happen, but it is a possibility. A workaround might be to use unlocker [0], in this case. If this is not the case, another possibility may be that somehow the files are saved such that you don't have rights to delete the file. Could you open a command prompt (cmd.exe), browse to the directory mentioned where the intermediate files are stored (cd /d Z:\Artefacts\Imagery\Photo\Calendric\2011\02\24 if that's where the files are stored), and run xcacls on the temporary file (e.g. xcacls 2011-02-24.tif)? This shows the access control list (ACL) associated with the file. Could you post the results here? By the way, I'm not sure but this last log line strikes me as abnormal? Maybe someone else can comment on this? enblend: input image 2011-02-240002.tif does not have an alpha channel -- Bart [0] http://unlocker.emptyloop.com/ -- 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
[hugin-ptx] Re: Hugin Timeline on Launchpad complete
Big thumbs up! Impressive indeed! -- Bart -- 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
[hugin-ptx] Re: ANN: Hugin-2010.4.0_rc1 released
Hi Matthew, On Friday, December 24, 2010 5:15:46 AM UTC+1, Matthew Petroff wrote: Windows binaries for Hugin 2010.4.0-rc1 are now available: 32-bit (no installer): http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4_beta/Hugin_2010.4.0-rc1_32bit_Windows.7z/download 64-bit (no installer): http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4_beta/Hugin_2010.4.0-rc1_64bit_Windows.7z/download 32-bit Installer: http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4_beta/HuginSetup_2010.4.0-rc1_32bit_Windows.exe/download 64-bit Installer: http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4_beta/HuginSetup_2010.4.0-rc1_64bit_Windows.exe/download Thanks for being such a fast binary contributor once again (and big thanks to all other contributors as well of course)! Are your '2010.4.0-rc1' files supposed to be in the '2010.4_beta' location? I know, it's merely a cosmetic issue, but I'd expect them to be located in a '2010.4.0_rc1' directory instead. -- Bart -- 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
[hugin-ptx] Re: ANN: Hugin-2010.4.0_rc1 released
Hi Terry, On Windows, the OpenGL functionality is provided by the graphics card driver, if I'm not mistaken. The generic drivers that ship with (the quite old) Windows XP don't offer a lot of OpenGL. You should try to get a more specific (and up-to-date) driver. Depending on the virtual device offered by the virtual machine, this may or may not be available. Updating drivers has helped me in the past (for Pannini that was, which also requires more OpenGL than the generic driver offers). -- Bart -- 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
[hugin-ptx] Re: Hugins CPFind not finding any CPs at all?
Well, your images might be wrong, for instance. Without any reference, we can't really tell what's going on, let alone troubleshoot it. So could you post a couple of the affected images somewhere? (or alternatively just attach them to a message to this group). Preferably also attach a failing .pto project file with those images loaded. Let's see if we can help from there. -- Bart -- 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
[hugin-ptx] Re: Rounded Perspective correction
I think you are looking for this? ;) http://www.youtube.com/watch?v=w5HY2xMCldI -- Bart -- 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
[hugin-ptx] Re: Idea for horizontal/vertical lines
Excellent idea! The way adding lines works has bothered ever since I started using it, it just didn't bother me enough to file a request I guess (or it didn't cross my mind). But now we're at it: we'd need 3 tools actually. Besides horizontal lines (lines at the equator) and vertical lines (lines perpendicular to the equator) there is a third type of line, referred to as add new line in the control point interface. This is a general type of line, IIRC this just means a straight line in any direction (maybe someone has a better definition?). I've used it in a couple occasions, maybe only with rectilinear output, I don't remember. Anyway, it should definitely not be forgotten, if this feature request is accepted and implemented. By the way, I believe we had someone working on line detection in the past (GSOC project)? Has this resulted in anything but a dead branch? I remember uploading some test images but I don't think I ever read anything about results... -- Bart On 7 dec, 21:20, Lukáš Jirkovský l.jirkov...@gmail.com wrote: Today I've found an interesting idea for RawTherapee project [0] and I think hugin could make use of a similar tool to the tool proposed on Rawtherapees forum. Long story short. Currently there is only one way how to specify horizontal or vertical lines. For defining either of them you need to manually specify control points. This is not very user friendly and it can take a lot of time. The idea is to allow drawing the lines in fast preview window. There would be two new tools in Fast Preview window - draw vertical line and draw horizontal line. User then would just draw the line over the image and hugin would automatically add control points defining line here. [0]http://rawtherapee.com/forum/viewtopic.php?p=17063#17063 -- 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
[hugin-ptx] Re: that was fast!
On 24 nov, 18:27, Harry van der Wolf hvdw...@gmail.com wrote: [snip] I fully agree with Kornel (and Gerry and Rew and Paul). I have been out of the air for 3 days and I might be a little late now with my response, so I'll keep it short. Yuval has been a contributor to this project for many, many years. With regard to self appointed leader: He indeed has taken the lead on multiple occasions when so many others didn't, and he did lead us further along the road (please don't think I will start a new religion). Most of us in the community are very grateful he did take the lead. I am for sure. Being a leader is something else than a self appointed leader. To finish this: I'm grateful in general that we have so many volunteer (keep that in mind) contributors that help this project progress further. Harry +1. Cheers for Yuv! -- Bart -- 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
[hugin-ptx] Re: that was fast!
On Nov 25, 12:28 am, michael crane mick.cr...@gmail.com wrote: On Wed, November 24, 2010 9:31 pm, Bart van Andel wrote: Please just freeze the thing and make it work without the evangelical grief. We're talking open source. To paraphrase Yuv: if there's an itch, scratch it yourself. Or just be patient and wait until someone else has found the time and interest to fix things. Noone is forced to hurry up here (or actually do anything), and unconstructive whining won't help. what is unconstructive about suggesting that there are enough features and make those work before fsking about on other things please explain Ok you sound way more reasonable if you put it that way. We can't read your mind, you know. Freeze and make it work sounds way different to me than shouldn't we best first fix (most of) the bugs in current features before adding new ones. YMMV of course, but the latter is not how I interpreted your first post. -- Bart -- 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
[hugin-ptx] Re: Claiming an SF account in LP
Yes. Well this is quite strange. Actually in the advanced search page there is a field for reporter. I am able to find myself there using the built-in search facility. The page shows my sf account name (@users.sf.net) but it also says that no account using this name/ email can be found. However there *does* exist 1 bug with me as reporter, and I have tracked it down. Weird. LP Bug? not sure that I understand your description, but it sounds more like a misunderstanding than a Bug. LP has an icon next to the user / account name. Is it grayed out? no account using this name means no *LP* account using this name. The moment you'll claim this as your account, the icon will be colored and there will be an LP account using this name (or this name will be gone and will be merged with the name of the LP account you've merged into). I think the reason why searching for reporter does not work is because it search for an LP handle, not for an SF handle, and the imported SF personalities probably have some cryptic string as handle (which is different from the visible name) to avoid duplicates. Ok, I'll clarify. 1. go to https://bugs.launchpad.net/hugin 2. enter advanced search 3. click choose next to the reporter field 4. enter SF handle, e.g. blabla...@users.sf.net 5. click the search icon 6. select the appropriate result by clicking it (if any) 7. the reporter field is now filled with a value, e.g. blablabla 8. now, hit the search button (or enter in any field) You'd expect some results to show up, of maybe nothing at all, but I got this error below the reporter field: There's no person with the name or email address 'blablabla'. So, first it finds me, than it doesn't find me. This is not expected behavior, is it? Or is it the result of the Hugin import from SF, where handles are only partly copied? It reeks of a bug to me. -- Bart -- 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
[hugin-ptx] Re: Claiming an SF account in LP
On 23 nov, 20:45, Yuval Levy goo...@levy.ch wrote: On November 23, 2010 07:55:08 am Bart van Andel wrote: 4. enter SF handle, e.g. blabla...@users.sf.net finds nearly nothing here. when I enter only @users.sourceforge.net it finds i-root-42 (which I guess was generated by the import process and the i stands for import) My account is really someth...@users.sf.net, not @users.sourceforge.net, but if I just use @users.sf.net (without anything in front of the @), it does not find me. Ah, you know, it's not that much of a problem. I know how to work around the issue, which is by finding my own bug report. There's no person with the name or email address 'blablabla'. I get blablabla into the reporter field as well, and I see the error you mean. My guess is that the error message means that there is no LP account by that name. I guess. So, first it finds me, than it doesn't find me. This is not expected behavior, is it? Or is it the result of the Hugin import from SF, where handles are only partly copied? It reeks of a bug to me. I have not been even able to find you. If this bugs you, you can file a bug report with LP, but for that you'll need an account :) Hehheh. Indeed :) -- Bart -- 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
[hugin-ptx] Re: male hugin skinnable
If you want this so badly, why not just install something like Windowblinds [0]? Or, if you're on Linux (guess not) there are enough ways to customize lookfeel already. For Hugin this has absolutely no priority. Would you ask Adobe to do the same thing for Photoshop? I guess you won't. [0] http://www.windowblinds.net -- Bart On 10 nov, 07:42, Lukáš Jirkovský l.jirkov...@gmail.com wrote: On 10 November 2010 03:55, john doe guerrerodelu...@gmail.com wrote: upssorry for the typo instead of male i meand make... On Tue, Nov 9, 2010 at 9:55 PM, paisajesenvenezuela guerrerodelu...@gmail.com wrote: hey how about adding an option to make hugin skinnable??that is let the user chance the appearance of the programs windows?? -- 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. 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 OH NO! Never ever ever ever ever do this. I don't understand why some people want every application look completely different from the rest of desktop. just my 2 cents. -- 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
[hugin-ptx] Re: some mailing list admin, displaying the membership list
On 7 nov, 01:01, michael crane mick.cr...@gmail.com wrote: On 6 November 2010 23:24, Bruno Postle br...@postle.net wrote: I'd like to change a googlegroups setting so that members can see the members list. This page doesn't include email addresses, just usernames. ok with me I'm alright with it too. -- 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
[hugin-ptx] Re: hugin and video stitching
Well, since all mentioned applications are open source, why don't you go ahead and start mashing up a nice program? Or do you think this will be too much work or too hard? /irony I'm not here to discourage anyone, but seriously, this suggestion is very far from a simple / easy / straightforward task. The availability of source code to start with does not make much difference: being able to open a video stream and extract frames does not imply that stitching them automatically (into what?) is done with a few lines of code. But if you want to give it a shot, go ahead of course. Oh and by the way, krpano is NOT a video stitching program. It is merely a program which can display panoramic video (ok, warping it in real time), which is already in panoramic format (e.g. stitched from multiple videos in a pre-processing step or taken with a panoramic camera system directly). -- Bart On 1 nov, 23:48, Tom Sparks tom_a_spa...@yahoo.com.au wrote: --- On Sat, 30/10/10, paisajesenvenezuela guerrerodelu...@gmail.com wrote: has any of the hugin creators though about using FFMPEG, OPENCV and LIBPANO to make user open, read, write video files and to be able to stitch theM?? VLC is made with QT, and uses FFMPEG, so if any of the coders need some sample code to work on, they could use VLC and FFMPEG to start.. I would like to see a real-time video stitch/warping program like krpano but not flash based tom -- 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
[hugin-ptx] Re: IMPORTANT: GoogleGroup Changes
Just deleted the files I had uploaded. I have a backup of these files in case anyone ever needs them (not very likely). Thanks for bringing this to our attention, Yuv! -- Bart -- 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
[hugin-ptx] Re: hugin eats up to 12Gb of RAM and freezes system
Hi, Could you try to replace step 8 by the following: 8a) Go to Stitcher tab 8b) Set Panorama Canvas Size to some sensible values 8c) Hit Stitch now! This will circumvent the behavior you have encountered where the panorama canvas size is somehow computed as an absurdly large value. By the way your PTO file looks quite normal: the p line indicates a width of 6160 and a height of 3617, which might indeed indicate that you have bumped into a bug since the program is clearly going nuts about size later on (see Andreas Metzler's reply). But the above steps will help you circumvent this erratic behavior. -- Bart On 10 okt, 16:43, Mateusz mateusz.ka...@gmail.com wrote: 1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: Mateusz mateusz.ka...@gmail.com wrote: Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto [...] When I open this pto file and use Stitch Now nona works without problem. I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. thanks cu andreas -- 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
[hugin-ptx] Re: hugin eats up to 12Gb of RAM and freezes system
Your assumptions are wrong: it's not Hugin which is using up all your memory, it's either Nona, or more likely, Enblend. These are the external programs which are used by Hugin to create the warped images and to merge them together into a panorama. Hugin itself doesn't use that much memory with the amount of images you have fed into it. So unless it's a bug, I suspect you are trying to stitch the panorama at an enormous resolution. Please check the output size at the stitcher tab and report back. -- Bart On 9 okt, 09:25, Mateusz mateusz.ka...@gmail.com wrote: Hi, I was trying to work with images directly from my camera. Each image is of size 10mb. Hugin resized them when loading (21 images). I selected only 6 for panorama. After Create Panorama with CPU my system total freezed and I had to do hard reboot, with GPU I managed to to some extend kill hugin and find out that it takes 4Gb of RAM and 8Gb of swap. I think algorithm should not load into memory all images at once, thats wrong for me. It should free the memory after working of selected pair of images, especially if the images are large. The time cost loading image from hard-disk and freeing memory is incomparable to how sever problem it triggers when all images are loaded at once. Please fix the algorithm or feed it with fewer pictures at once. -- 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
[hugin-ptx] Re: Windows hugin-2010.2.0_rc1 Build
On 5 okt, 15:34, davidefa goo...@davidefabbri.net wrote: - a windows build of autopano-sift-c 2.5.1 can be found at the following address:http://www.sendspace.com/file/0mgb8o( from this post:http://old.nabble.com/Hugin-2009.4.0-Win-XP-autopano-sift-c-2.5.2-bug... ) Indeed. That's where I uploaded it once I had found it in one of the older Hugin installers a while ago. I'm quite surprised that it's actually still available, but maybe I had chosed this site for that reason, can't remember. Probably not the easiest location for your installer since to my knowledge you can't use a direct file url, so you'll need to copy it somewhere else. This was an easy location, since I lack private web space. -- Bart -- 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
[hugin-ptx] Re: building hugin 2010.2.0 with minGW
On 24 sep, 04:17, Yuval Levy goo...@levy.ch wrote: On September 23, 2010 10:03:32 am kfj wrote: Having finally managed to build libpano and collateral software using minGW and msys, [...] AFAIK yours is the only recent success at building anything related to Hugin with MinGW. More power to you. Does building libpano13 using the mingw-cross-env cross building environment [0] count? I've successfully built APSC for Windows from a Ubuntu virtual machine last week. This required only very little manual intervention: libpano13: - enable PPM support for MINGW target, to prevent linker errors later on. This should probably go into Makefile.am, but I edited the already generated Makefile.in instead, which was faster. Is there a reason why PPM support was disabled in the first place? - sys_win.h includes WINDOWSX.H (all uppercase), but the file is called windowsx.h (all lowercase) when using mingw-cross-env. Not sure if this is specific to mingw-cross-env. - some tweaks specific to mingw-cross-env for file naming and usage of tools, handled by mingw-cross-env. APSC: - manually edited the order of inclusion of libraries, since I couldn't get (the cross build) GCC to work with the automatically generated, but improper order. I don't know of any way to correct the order using CMake? Of is there a GCC option I missed to instruct the linker to search for symbols in all libs provided on the command line? The PPM tweak for libpano13 is on its way into the mingw-cross-env sources and will work with the current libpano13 release, the other tweaks were already included. Probably it should be fixed in libpano13 itself though, and maybe also the uppercase/lowercase fix, is it's not mingw-cross-env specific. [0] http://mingw-cross-env.nongnu.org/#packages -- Bart -- 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
[hugin-ptx] Re: smarter undo/redo
I just read your patch, to see if I could spot a bug (without
compiling, as an exercise), and I think I've found one. Can't compile
it myself now because I haven't currently set up a building
environment, but here goes:
Line 175 currently reads:
+while ( (commands[nextCmd]-getName()==change active
images) (nextCmd commands.size()) ) {
This should be:
+while ( (nextCmd commands.size() (commands[nextCmd]-
getName()==change active images)) ) {
You were reading the name of a command which may not exist when at the
very end of the queue,
--
Bart
On 21 sep, 23:38, Yuval Levy goo...@levy.ch wrote:
Hi all
Hugin keeps track of all operations done on the panorama. Great for undo.
It also stores the toggling of an image visibility status. Personally I find
this unnecessary: when I move forth and back over the history of the project
I am interested in before and after, not visible and invisible. I end up
clicking multiple times to get through an undo/redo cycle if in between I
toggled visibility (e.g. to influence the set of CPs used by the optimizer).
In an attempt to work around the issue by simulating the multiple clicks, I
produced the attached patch. It's not perfect yet, and has segfaulted on me
on redo. It's fairly simple. I look forward for critique and feedback of
the patch and I hope to fix the segfault soon.
Yuv
selective.undo.patch
7KWeergevenDownloaden
signature.asc
1 KWeergevenDownloaden
--
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
[hugin-ptx] Re: smarter undo/redo
On 22 sep, 19:02, Yuval Levy goo...@levy.ch wrote: On September 22, 2010 05:43:19 am Bart van Andel wrote: I just read your patch, to see if I could spot a bug Thank you, Bart! You spotted right. With your fix it no longer segfaults on my tests. Ok great! Exercise completed successfully :-) I like the idea of your patch by the way. It's neat. A more complicated version could auto-undo when you first hide a picture and then immediately show it again, without doing anything in between. Or even group all successive hide/show actions and remove combined hide/show actions (as netto this would be the same as doing nothing to the image). This should be done when the first non-hide/ show-action is performed. But that is just an optimization step which probably only makes sense if such history steps would take up lots of memory, which I guess they don't. -- Bart -- 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
[hugin-ptx] GSoC 2010 results
Please, no thread hijacking. This appears entirely irrelevant to the original thread, so unless I'm wrong, start your own thread. -- Bart On 21 sep, 14:00, PhG t...@ediphi.org wrote: hi, the previous 2010.1.0 svn build worked fine under my win2k SP4. the 2010.2.0 x32 build raises a not a valid win32 application error, the same msg as with the x64 version. and the 2 versions are really different (8MB - 12 MB). it seems a compilation option was inadequate for win2k strangely, it's ok with Win XP SP3 (http://thepanz.netsons.org/post/hugin-2010-2-0_beta2-installer/commen... -1#comment-24) cheers, Philippe -- 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
[hugin-ptx] Re: How to reduce the size of the final panorama ? Fast previews ?
On 17 sep, 17:59, WaterWolf waterw...@gmail.com wrote: When you say output size and pixel width and height are you referring to the Panorama Canvas Size in the sticher tab? How do these fields work? I tried changing them but whenever I pressed the Create Panorama button they seemed to be reset to some automatically calculated values. You should be able to set the desired output width and height in the Stitcher tab, under Panorama Canvas Size. To create the panorama using these settings, you can use the Stitch now! button on the same tab. I don't know what the Create Panorama button on the Assistant tab is supposed to do, besides creating the panorama. It may be programmed to first automatically guess the panorama output size (based on the input files and the other output options), in which case the values you've entered will indeed be overwritten. Anyway normally you wouldn't need to resize the input images before feeding them into Hugin. The rendering process takes care of resizing for you when writing the intermediate files which are fed to Enblend, or whatever blending program you're using. -- Bart -- 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
[hugin-ptx] Re: Multi-row pano layout?
What control point detector did you use? You can check which one is default in the preferences. 30 images should not pose a problem really. As far as I understand, APSCpp and Panomatic follow a different approach when it comes to matching images. Panomatic tries to match every pair of images separately, while APSCpp collects all control points in one big tree and matches all images at once, at least the more recent versions by Tom Sharpless. Correct? Anyway 30 images isn't really that big a number, so they should both be able to cope with that. BTW I'm using Panomatic most of the times, and sometimes when I first start up Hugin (on a Windows restart) Panomatic crashes when run. If I then restart Hugin and try again, it works correctly. Not sure if it's a bug or a configuration problem, but could it be you're experiencing the same thing? -- Bart On 20 aug, 23:53, Joel B cincoden...@gmail.com wrote: Bart: I tried the Align button, and Hugin eventually froze and became nonrespondent, and I think crashed - I was guessing because of the sheer number of unmatched pairs it was trying to match. I didn't know the Layout mode had made it into preview though - thanks, I'll have to check that out. T. Modes: That sounds very promising! I didn't have that option, but I was running 2009.04. I found builds from lemur with more recent versions, and I'll try those options out. Thanks! On Aug 19, 10:30 pm, T. Modes thomas.mo...@gmx.de wrote: On 19 Aug., 19:17, Joel B cincoden...@gmail.com wrote: I've been working with some multi-row panos, similar to the ones on the multi-row tutorial, actually:http://hugin.sourceforge.net/tutorials/multi-row/en.shtml And when I hit the align button, it seems to try to find points in *every* pair of images. In my case, however, I'm doing a 360-degree, two-row panorama, that has 30 or so images, not just the 8 in the demo - so instead of 36 possible pairs of which about a third will be used, it has to match more than 450 possible matches. Is there a way to arrange the images and tell it which ones it should try to match up? Ideal would be an interface similar to a combination of the first and last pictures in the multi-row tutorial, actually, where I could drag the photos around, overlapping them, to specify which photos overlap visually, and have Align just try those pairs. This can be achieved by using a multi-row control point detector setting. seehttp://wiki.panotools.org/Hugin_Preferences#Control_Point_Detectors andhttp://wiki.panotools.org/Hugin_Parameters_for_Control_Point_Detector... If you want to use it with the assistant tab, you need to set the multi-row detector as default. Thomas -- 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
[hugin-ptx] Re: Multi-row pano layout?
Have you already tried the Align button on the Assistant tab, after loading the images? Or the Create control points button on the Images tab, followed by some optimizing on the Optimizer tab (e.g. Position (incremental, starting from anchor) followed by Position, view and barrel)? In most cases this should do the trick with the current Hugin. Don't be afraid to experiment a bit, and if you get strange output, you can examine the links Hugin found between the images using the Layout mode in the Fast Preview. Sometimes it will find false positives, if features are similar enough, and you'll have to filter those out yourself. Unless it's in the clouds, where Celeste comes into play and may do all the dirty work. Or am I stating the obvious now? -- Bart On 19 aug, 19:17, Joel B cincoden...@gmail.com wrote: I've been working with some multi-row panos, similar to the ones on the multi-row tutorial, actually:http://hugin.sourceforge.net/tutorials/multi-row/en.shtml And when I hit the align button, it seems to try to find points in *every* pair of images. In my case, however, I'm doing a 360-degree, two-row panorama, that has 30 or so images, not just the 8 in the demo - so instead of 36 possible pairs of which about a third will be used, it has to match more than 450 possible matches. Is there a way to arrange the images and tell it which ones it should try to match up? Ideal would be an interface similar to a combination of the first and last pictures in the multi-row tutorial, actually, where I could drag the photos around, overlapping them, to specify which photos overlap visually, and have Align just try those pairs. As-is I've been specifying the matchings manually (as in the two- photos tutorial), but this is very time-consuming and inefficient. If there isn't a way to do this, any idea on how hard it would be to implement such an interface? And where would I start in such things? I'm willing to work on implementing such a thing, but don't know if there's already something similar, or where I would start in making one if there isn't. Thoughts? -- 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
[hugin-ptx] Re: Looking for help fixing distortion in panoramic photos
I don't want to ruin your enthousiasm, but this thread is about a completely different topic. Please don't hijack threads, just open a new thread when starting a new topic. -- Bart On 17 aug, 19:29, Joergen Geerds jgee...@gmail.com wrote: I have started to play with the triplane projection. Is there a way in hugin to modify the corners of the projection? right now it looks like it's projecting 90+ deg / 90 deg / 90+ deg. would it even make sense to adjust the break points? joergen -- 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
[hugin-ptx] Re: Looking for help fixing distortion in panoramic photos
Read the opening post and agree with me that the problem you describe is of a rather different nature. Your problem is about finding the right settings for the tri-plane projection, which I wouldn't call a distortion problem. Both problems ask for a completely different solution. It's probably a matter of definition, but to me, it looks like apples and pears: both are fruits and they look a bit alike, but they're not quite the same. Anyway it would help if you could provide a screenshot of what your problem looks like (best in a new thread). For the Hugin community, a picture often says more than a thousand words ;-) -- Bart On 17 aug, 21:37, Joergen Geerds jgee...@gmail.com wrote: On Aug 17, 3:15 pm, Bart van Andel bavanan...@gmail.com wrote: I don't want to ruin your enthousiasm, but this thread is about a completely different topic. Please don't hijack threads, just open a new thread when starting a new topic. oh, sorry, I thought it would fit perfectly under Looking for help fixing distortion in panoramic photos since I am trying to fix the distortion that happens in the wrong place in a panoramic photo. joergen -- 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
[hugin-ptx] Re: Looking for help fixing distortion in panoramic photos
On 29 jul, 22:29, sani...@ymail.com sani...@ymail.com wrote: Could you guys clarify for me what is causing the curving? What could I do differently without adding seams to my image? As far as I can see from the tinypic image, the horizon isn't level. You can tell because the far ends of the building do not point straight up in the image, while would in the real world. Try adding some vertical control points [0] and reoptimize the image. Don't get confused by a curve in the image strip: probably your panoramic head wasn't exactly level but slightly off-horizon. [0] http://wiki.panotools.org/Vertical_control_points -- Bart -- 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
[hugin-ptx] Re: Hugin Mercurial Repo - Please Test and Help
Hey Yuv, Thanks for all your effort! I must say to me the HG web viewer looks a lot cleaner than the SVN web viewer. One interesting thing I noticed: the latest entry in the changes table shows in the future convert-repo update tags default tip Didn't know HG has supernatural powers :) Does this have to do with timezone settings or incorrect server time? I'm currently at CET summertime (GMT+2), it's 0:19 here while the latest change shows 0:31 +. Or is the job still running? Looking forward to experiment with the HG repo! -- Bart On 16 mei, 22:43, Yuv goo...@levy.ch wrote: On May 16, 4:01 pm, Yuv goo...@levy.ch wrote: I'll get back later with a status update. SVN write permission have been revoked to everybody except Bruno (the Hugin website with its automated update still runs off SVN, we'll need to bring that process up to date to do the same with Hg, as done for the Enblend website) and myself (to add the last bits of information about the migration once the migration is done). Updating permissions on Sourceforge is ... suboptimal (understatement) and slow, but at last it is done. Whoever had SVN write access now has Hg write access. I am currently pushing the new repo to Sourceforge. I am using the `hg push` command which is much slower than simply rsyncing all the files, but it is also cleaner. It will take some time. Once this is done, I'll edit the repo's .hgrc file for email notifications and other stuff. Also, after the repo is updated, everybody will have read access to it via the web athttp://hugin.hg.sourceforge.net/hgweb/hugin/hugin/ Read-only access, for everybody building Hugin from the repo: `hg pullhttp://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin` Everybody who had write access to SVN now has write access to Hg. Pull/ push from/to the following URL: ssh://USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin replace USERNAME with your Sourceforge user name. I don't know how long the push operation will still need, nor if it will be successful. If you're in a hurry, check out the above linked web URL. I'm going out for a job now. Will be back in 2-3 hours to continue the migration. If everything went as expected, by then the new Hg repo is up and running and available for use. When I will be back I will set up email notification and other details. Yuv -- 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 athttp://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. 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
[hugin-ptx] Re: Using phone cameras and Hugin
On 24 apr, 11:14, aws357 wong@gmail.com wrote: Google docs link to pictures I've taken. When I use a value of 37mm, hugins return me some funky results... I tried using Panomatic as the control point finder, and the result isn't that bad. I optimized Position, Translation, View, Barrel at once, and then selected Center, and Straighten from the preview window. I've uploaded the .pto to [0]. Stitched, cropped and blended image (using Smartblend) can be found at [1] However... Nothing is moving Not true. *You* were moving. There is quite a lot of parallax error between the images. Compare the images of the open door for instance and notice that things behind the door are shifted quite a distance. Since Hugin cannot reconstruct a complete 3D scene, this *will* cause trouble. It's a good thing we have pretty intelligent blend tools, see my result, where you can hardly spot errors (the door post has some for instance). though I admit perhaps I'm not making it easy for the software to find control points... Panomatic didn't have any difficulties. I didn't even process the generated control points any further (no refining, no removing of odd points). By the way, I used Zoran's 2010.1.0.5063 Windows build. -- Bart [0] http://groups.google.com/group/hugin-ptx/web/2010-04-24.pto [1] http://groups.google.com/group/hugin-ptx/web/2010-04-24-sb.jpg -- 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
[hugin-ptx] Re: (Patch-plugin practice) Enfuse and Enblend Gimp Plugins - Gsoc
Hi, I don't want to sound rude, but how exactly can we see your coding skills from these source files? From what I see: - You have successfully set up a build environment to build plugins for GIMP. - You can make a hello world plugin for GIMP, which is basically taken literally from [0] with only a few textual changes. - You can change 0 into height/4, 0 into width/5 and width into width - width/5. Another example taken from [1]. - You cannot create the right diff. The diff you made transforms your file back into the original, so it can't be used to take the original file and transform it into yours. - Where are the credits for the original author? I'm sorry but you haven't convinced me yet. I know I'm not mentoring (nor have I contributed a lot of code) but I don't think this shows the level we need for a GSOC project. Maybe you have something else to show? [0] http://developer.gimp.org/writing-a-plug-in/1/hello.c [1] http://developer.gimp.org/writing-a-plug-in/3/myblur3.c -- Bart On 20 apr, 01:03, Elle Yan elle.yan...@gmail.com wrote: Hi, Sorry for the late reply. I just got a chance to organize some source code files. I will have plenty of time in the summer (from May). Thank you very much for all suggestions of getting involved in open source development. It is really helpful. I am excited to contribute to Hugin and open source community. I learned quite a lot about open source before, but think taking some good actions from now is good. This Gsoc project will be a wonderful opportunity for me to start. I have uploaded some source code in Hugin Google Groups: http://groups.google.com/group/hugin-ptx/web/Sample%20source%20code.zip or, the Sample source code.zip file at:http://groups.google.com/group/hugin-ptx/files?upload=1 I also uploaded another zip file, Hugin patch-screenshots.zip, in the same directory. That is my patch work to support the application of Hugin Gsoc project, Enfuse and Enblend Gimp Plugins. I have write a description for those files in the first email. I have shared source code before, and I agree that it is really great to give back. Thank you. Elle. On Thu, Apr 15, 2010 at 9:12 AM, Yuval Levy goo...@levy.ch wrote: I should be packing boxes and the computer should be already in one of them. so concise and to the point: On April 15, 2010 01:24:13 am Elle Yan wrote: I should have asked how to send a patch. or read the messages on this mailing list. I think it was Antoine that asked. Learning from other peoples questions and answers is an important skill in Open Source. Since everyone in the mailing list can see the email addresses of the senders, why are they private information? everybody can see my phone number in the phone book but it is still private information and an unsolicited call on it without permission is not a good thing. ... maybe you can explain why I didn't notice you in this community before? I just started to communicate in the community recently. Before, when I reviewed the code base, and found very useful sources, I made use of them, e.g. spline.cpp. OpenSource 101: FEEDBACK. Saying Thank You when making use of the code. can you share some links to code you committed in the repository of the mentioned projects? I am happy to share some. I did not often commit to the repository of large software though. I don't expect you to have commit right to the repository of large software. OpenSource 102: Contribution starts with communication. Usually forwarding the changes to a maintainer (somebody with access to the repository); or publishing a patch somewhere. Subsequently the maintainer may or may not accept the patch. If the patch is accepted, it leaves a trace in a commit and most maintainers will credit the contributor in the commit log. For an example, see [0]. Usually, I code for the software out of my own interest or goal. For example, I code within the code base, to make and change some features as I needed. Or, I use their routines or libraries. It is not the formal commit. OpenSource 103: it is common for people to code out of their own interest. It's called scratch your itches. The spirit of Open Source is that when you make changes you publish them for the next person in your same situation. Sometimes this spirit is enshrined, to different extent, in the more or less permissive licenses. For smaller software, I did have many commits. It is open source projects locally in two universities. They do not currently have commit info on line publicly. Do they have the source code published in other form, e.g. a tarball? OpenSource 104: Giving back to the general public is key to be a good Open Source citizen. In the days prior to the internet, these were off line tools such as CDs, books, or other media. However, I have many written source code for projects mentioned.
[hugin-ptx] Re: (Patch-plugin practice) Enfuse and Enblend Gimp Plugins - Gsoc
Hi, I'm sorry, this is just for the crop/blur example. I missed your other file, which is definitely more impressive. Again, sorry. Best, Bart On 20 apr, 13:21, Bart van Andel bavanan...@gmail.com wrote: Hi, I don't want to sound rude, -- 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
[hugin-ptx] Re: SVN repository conversion - Important for past contributors
Hi Yuv, Since sourceforge mail allows forwarding email to your own specified email address (I think this is the default when an email address has been supplied) I'm perfectly fine with the sourceforge.net address. In fact I prefer it this way, since it allows me to change the forward address whenever I like. Thanks for asking and (as always) all your efforts! -- Bart -- 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
[hugin-ptx] Re: Simplest panohead ever? (was: Pano Head)
I always like to keep things as simple as possible. My minimalist solution might look childish but works great for my setup. This is brilliant! Simple is good! I *have* to find myself some second hand Meccano to build a similar setup :) -- Bart -- 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 To unsubscribe from this group, send email to hugin-ptx+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[hugin-ptx] Re: triple me
Most obvious way: mask out the area you don't want from the images. With the most recent builds, you can do this very easily using the Mask tab. You can create positive masks (areas you want to see in the output, will automatically mask out the same area in other images) and negative masks (areas you don't want to see). If this isn't enough help, just post another question. And of course, showcase your output here :) -- Bart On 12 mrt, 22:48, Thomas Steiner finbref.2...@gmail.com wrote: Hi, I'd like to make a panorama with mulitple copies of myself - so to say the opposite of deghosting. I make some panorama pictures with me at different positions. I load them, crop them in hugin's crop tool, create control points (BTW: ctrl-pts are searched by autopano-SIFT-C everywhere, not only on the uncropped part - why?) and then I stitch them. You find a screenshot of the preview and the stitched result attached. One copy is lost, probably by enblend due to some background shaddows - how can I avoid this? Thank you very much for your help and hints, Thomas PS: Why is the usage of the crop in the crop tab so different from the crop in the fast-preview? I like the latter much better... IMG_6240-42m.jpg 205KWeergevenDownloaden crop-1.jpg 227KWeergevenDownloaden -- 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
[hugin-ptx] Re: GLpreview and projections
On 11 mrt, 16:45, Simon Oosthoek soml...@xs4all.nl wrote: Simon Oosthoek wrote: Bruno Postle wrote: On Wed 10-Mar-2010 at 12:50 +0100, Simon Oosthoek wrote: When I changed the projection, some projections altered the FoV in such a way that the output got totally distorted. Switching back to something sensible didn't always reset the FoV to sensible values. Wouldn't it make sense to review these functions and prevent unsensible values to be set, unless confirmed by the user? There have been a few changes recently to make this better, but probably Hugin does the wrong thing in a number of situations. There are hundreds of combinations of projections, a bug report where people could add examples that don't work well would be useful. When I have some time, I'll see what I can do, (@anyone) feel free to start an issue on this, I may not have time soon... I managed to do it now anyway ;-)https://sourceforge.net/tracker/?func=detailaid=2968662group_id=775... Meanwhile, wouldn't it be a good idea to put a prominent UNDO feature on the windows/tabs that allow you to change aspects that have effect on the FoV? the more I think about it, the more I think this is really a bug and UNDO is not the right way to fix it. The projections shouldn't fundamentally change properties like FoV, unless I don't understand something (I'm not into the mathematics of making panorama projections!) Well, a rectangular projection can only display images with 180 degrees field of view (and 120 degrees for practical use), so for this projection, the FOV field needs to be modified. This is a mathematical restriction, so it can't be circumvented. I guess you didn't realize this? This is exactly what Hugin will do when you switch from a Panini projection with a large FOV (180) to rectangular. Nothing strange about that really. -- Bart -- 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
[hugin-ptx] Re: Towards a non-patented control point detector
The name of Hugin itself comes from Norse mythology [0] (Huginn and Muninn [1], which stand for thought and memory respectively, are the ravens who tell Odin how the earth is doing). I think it may be a nice idea to steal another name there. So... what about Loki? According to its Wikipedia article [2], Loki assists the gods, and sometimes causes problems for them. Loki is a shape shifter and in separate incidents he appears in the form of a salmon and a mare.. Certainly a feature detector assists our precious Hugin, and certainly this sometimes will cause problems (bad matches etc.). I don't know about the internal working but it might do some shape shifting too. Anyway afterwards the images (shapes) will be shifted based on the feature points found. Besides that, Loki sounds a bit like localize, which is what it does, it localizes points which will be used to connect the images. Of course we could also add a cheesy backronym [3] like Locally Oriented Keypoint Indexer (depending on what it actually does under the hood this might or might not be correct), or Localizer of Orientation independent Keypoints of Interest. Anyone with a cheese-o- matic can think of even nicer backronyms, if you tune the machine correctly. ;-) [0] http://en.wikipedia.org/wiki/Norse_mythology [1] http://en.wikipedia.org/wiki/Huginn_and_Muninn [2] http://en.wikipedia.org/wiki/Loki [3] http://en.wikipedia.org/wiki/Backronym -- Bart -- 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
[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01
Hi, Hmm this had to do with quotes in filenames, which it should now handle properly. Get the just updated version here: http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/platforms/windows/smartblend-wrapper/smartblend-hugin.bat?revision=5050 -- Bart On 4 mrt, 15:35, Trev trevs.mail...@googlemail.com wrote: Hi I am new here so I had better introduce myself! My name is Trevor, I live in the UK and have only been using Hugin for two months. It's a great piece of software and I would like the thank everyone who has put the time in. I also experience the inverted jpeg. Yesterday I downloaded a newer version of Hugin for Windows (Pre-Release 2010.1.0.5046 built by zoran zoric) and I get the following error: C:/Users/User/Downloads/Hugin5023/bin/Smartblend/smartblend- hugin.bat --compression NONE -f4608x1935 -o test.tif test.tif [smartblend-wrapper] Skipping compression argument and its parameter: --compression NONE [smartblend-wrapper] Skipping crop argument: -f4608x1935 [smartblend-wrapper] Output file: test.tif The syntax of the command is incorrect. make: *** [test.tif] Error 255 I have tried using a panorama that previously worked OK and get the same result. It looks as if one of the parameters might have changed or I am doing something silly!! regards Trevor The version of Smartblend is 1.2.5.0 dated 25/03/2007 On Mar 2, 2:02 pm, Henk Tijdink h.tijd...@gmail.com wrote: Hello Bart The ouput file now has the EXIF info. As I understand from your previous answer there is no compression available due to parameter stripping , needed for enblend to work. Can live with it and compress it later. The only strange thing is that a JPEG output is upside down. Have other people that experience too? Kind regards Henk Tijdink On 24 feb, 00:11, Bart van Andel bavanan...@gmail.com wrote: Whoops, I had mixed up two versions of the batch file on my harddrive and uploaded the wrong one (which was still an update, but incomplete), fixed that. Sorry Bruno, you'll need to merge again I guess... -- Bart On 23 feb, 23:30, Bart van Andel bavanan...@gmail.com wrote: I just committed a new version, which can be found at [0]. Tested with Hugin 2009.04 official build, but it should be version independent. It will work with Hugin as long as Hugin does not the command line arguments currently supplied to enblend/smartblend. The wrapper currently strips -f and --compression, gets the output from -o and leaves everything else alone. The readme also got an update to reflect the changes. By the way it's okay to include the wrapper and accompanying readme in a future Hugin package, so users won't have to go search for the wrapper in the svn repos themselves. I have no experience with building such packages myself though. [0]http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/platforms/w... -- Bart -- 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
[hugin-ptx] Re: Towards a non-patented control point detector
On 3 mrt, 00:03, Daniel Reetz danre...@gmail.com wrote: On Tue, Mar 2, 2010 at 6:04 AM, Bruno Postle brunopos...@googlemail.com wrote: On 1 March 2010 18:36, Aron H aron.hel...@gmail.com wrote: perhaps 'daisy_geoblur' might be better. What do you think, Pablo? 'daisy' is good, I like 'daisychain', 'daisypicker' or 'upsydaisy' (hmm, I've been watching too much children's television). You know, it might be useful to call it something more informative than illustrative. Daisy is good, but I'd never search for Daisy if I was searching for a non-patented control point detector. However you'd search for Hugin if you were to find a panorama creation tool... I don't think this is a strong argument. Why not use a nice name like Daisy and add a short description, (like Hugin has: panorama photo stitcher)? You'd still be able to find it that way. And to end users such a name is more friendly too. Well, that's my opinion. And what about when another patent free feature detector is build? You'd end up with confusion if you only use a descriptive name, or you'd have to resort to full descriptive names like scientific papers often do (ugly!). Remember qtpfsgui? I definitely wouldn't vote for that one. If this were my project, I would seriously call it Patent Free Feature Detector. And in this perfect world, everyone would use it because it would be so plain and obvious and clear... and Google-able. That is, if you know your panorama-creation program should detect features in the source images. It's only obvious once you know what you should be looking for. -- Bart -- 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
[hugin-ptx] Re: Hugin 2010.1 svn5031: autopano-sift-c finds VERY few keypoints
Autopano-SIFT-C 2.5.2 23July2009 is known to be broken and should not be used or included in the installer. You need to use 2.5.1 instead, which I've recently uploaded for convenience [0]. In the output you included in your message it says hfov 180, but this can't be correct if I examine your example photo. Are you sure Hugin imported the picture correctly? E.g. on the images tab, what does the hfov value say? [0] http://www.sendspace.com/file/0mgb8o -- Bart On 1 mrt, 13:18, Andres andres.l...@gmail.com wrote: First - Hugin is a great program and has allowed me to do things I previously couldn't do (automate). Now, the problem, as stated, is that autopano-sift-c finds very few keypoints and subsequent image alignment fails. For example, on same image the autopano-sift-c in Hugin 0.7 finds 5921 keypoints, but the latest bundle 2010.1 svn5031 finds only 2 keypoints. What could be wrong? 0.7: APSCpp, enhanced Autopano-sift-c Filename example.jpg width 2288 height 1712 reduce size to 1600 x 1197 5921 keypoints found 2010.1 svn5031: APSCpp, enhanced autopano-sift-c version 2.5.2 23July2009 Default fisheye lens type is equal-area. Focal length will be computed from hfov. Stereographic projection enabled for hfov = 65.0 degrees. Filename example.jpg rectilinear width 2288 height 1712 hfov 180 reduce to 1600 x 1197 (Scale 1.4300)... convert to stereographic projection ... find keypoints ... 2 keypoints found The image itself is here:http://www.hot.ee/lux44/example.jpg Regards -- 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
[hugin-ptx] Re: Hugin 2010.1 svn5031 for download
Please use 2.5.1 instead, which I've uploaded to [0] for convenience [0] = http://www.sendspace.com/file/0mgb8o -- Bart -- 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
