[hugin-ptx] Re: How to use geometry vs. feature based control points?
I'm doing a project where I'm building a motorized head which will save all the positions to a log file. I want to automate the entire process of creating a panorama in Hugin. So i'm basically doing exactly the same thing as Bruno. I want to use a log file to help Hugin to place photos in areas with no control points. It seems like Papy wizard can create such a file (xml) and APP can then use this. But APP is expensive and I would like to use Hugin. Would you set the y,p,r of all the photos and then run the optimizer, all in a script? What train of thought must I follow here :) On Feb 19, 1:58 am, Bruno Postle br...@postle.net wrote: On Fri 18-Feb-2011 at 10:54 -0500, Bill Sherman wrote: 1) I'm having trouble with the Move/Drag portion of the Preview (actually, to tell the truth, much of how to use the Preview window is a mystery to me). I just reran Hugin, using my sample images, and then go to the Move/Drag operation. At this point, I can move some of the images independently, but some stay stuck together -- and I want to move one relative to the others. The fast preview lets you drag connected image groups separately, a connected group is defined as any set that is connected by control points. 3) I noticed an image referred to in a post from yesterday an Overview sub window for the preview, but I do not see that in my version. Will this be in the next release? Will there be a new release soon? Here's the picture: -http://www.flickr.com/photos/36383814@N00/5451289889 Yes the overview will be in the next release, currently you need to build a snapshot from Mercurial to get it. The robot device does not directly communicate with any computer, so there is no log. However, it reports on the screen the angle between shots, so I could easily provide command line arguments of the MxN array, with both horizontal and vertical movement angles. And I'd be happy to help figure out the best procedure for this. What other ways do robots allow you to specify a sequence? Presumably you have an option to start at the top/bottom or left/right, or to specify the total angle rather than number of shots, or specify the total angle and angle between shots. -- Bruno -- 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] Stitching and enfusing a handheld panorama with several exposures
25.2.2011 8:24, Gnome Nomad kirjoitti: Markku Kolkka wrote: JiHO kirjoitti viestissään (lähetysaika torstai, 24. helmikuuta 2011): If I follow the steps exactly I do this: 1- import my images 2- in the Images tab, stack them in stacks of 3 (0, +2, -2) Don't use stacks with hand-held images. Hugin believes that images in a stack are pre-aligned perfectly. Hmm, I used Hugin to align a stack of hand-held images and used the Merge to HDR's Stacked HDR Images option to produce an EXR file. The point is that using the New stack button on the Images tab *prevents* Hugin from aligning images defined as a stack (unless you manually unlink them). I guess that your stack of images wasn't actually defined as a bracketed stack on the Images tab? -- Markku Kolkka markku.kol...@iki.fi -- 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 plugin interface - developers please liaise
Hi Kay, I also changed a few return codes in hpi to avoid potential confusion about which part produces an error. Is there some list, what each error code means? So we could add more meaningfull messages for users/new python developers, if the script or script interface fails. Currently they are only numbers, which does not say to much without looking into different places of the source. The changes are contained in a patch which I have put into my bazaar repo, hoping that it will go the way of it's predecessors, which have been integrated into the main repo by T. Modes. Commited. 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] 2011.0 and align_image_stack
Hi all, three weeks ago I added a new branch to the repository, with code contributed by Vladimir Nadvornik to align_image_stack. The code adds functionality for the alignment of stereo images, and should not change any previous functionality. Has any user of align_image_stack found unexpected changes in the behavior of align_image_stack in that branch? If there are no negative reports, I intend to merge the functionality into the default branch before branching out for the release cycle. I intend to branch 2011.0 out and issue the first beta release of the cycle probably on Sunday night. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: droplet failure on Windows
On February 24, 2011 07:26:59 am Tom Sharpless wrote: I meant I have not installed or learned Hg yet. If that's the obstacle and you have patched the tools please forward the patch and I'll apply it. If I can be of any help with Hg, feel free to ask questions. Yuv signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Broken Layout
Motivated by a ticket [0] on the tracker about numeric transform being 'broken' by the introduction of the new dragging functionality, I looked deeper into the matter. Turn out it was not broken, it was 'just' hidden outside of the viewport. While I normally work in full screen mode and am not aware of these issues, I have taken the steps of resizing all windows to their minimum size and trying to access app functionality. My conclusions: THE CURRENT LAYOUT OF HUGIN IS 'BROKEN'. We need decisions and consistency about the user interface layout. Here is what I would suggest: 1. Decide a minimum screen size at which the application is functional. 2. Decide a consistent way of paging the information that can't be fit in such minimum screen size - can be vertical scrolling, can be sub-tabbing, can be anything else we have not seen or tried yet. 3. Document the above decisions and enact them as project policies. 4. Implement the above decisions consistently across windows and tabs. Given the current hardware trends, I would suggest: 1. 800x480 minimum screen size 2. vertical scrolling within the tab (not so cool for mouse users, but look at tablets) Comments? Can we do this in the yet to be started 2011.0 release cycle, or do we have to ship another version of Hugin that becomes unaccessible at screen sizes below 1366x768? Yuv [0] https://bugs.launchpad.net/hugin/+bug/723696 signature.asc Description: This is a digitally signed message part.
[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: Broken Layout
Hi Yuv, THE CURRENT LAYOUT OF HUGIN IS 'BROKEN'. This affects mainly linux. On windows it working nice, even with minimum window size. Can we do this in the yet to be started 2011.0 release cycle, or do we have to ship another version of Hugin that becomes unaccessible at screen sizes below 1366x768? This applies also only to linux. On windows hugin is still usable with 800x600 screen size. So please not soo general statements. Given the current hardware trends, I would suggest: 1. 800x480 minimum screen size This is already set for windows and mac. The smaller size for linux seems to be related to Asus eeePC users. 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
Re: [hugin-ptx] Re: Broken Layout
While we are at it: Why can't one enter the numeric value and then just press Enter on the keyboard? Right now one has to press the button using the mouse. Thanks, Jan (on Ubuntu Linux) On Sat, Feb 26, 2011 at 4:28 PM, T. Modes thomas.mo...@gmx.de wrote: Hi Yuv, THE CURRENT LAYOUT OF HUGIN IS 'BROKEN'. This affects mainly linux. On windows it working nice, even with minimum window size. Can we do this in the yet to be started 2011.0 release cycle, or do we have to ship another version of Hugin that becomes unaccessible at screen sizes below 1366x768? This applies also only to linux. On windows hugin is still usable with 800x600 screen size. So please not soo general statements. Given the current hardware trends, I would suggest: 1. 800x480 minimum screen size This is already set for windows and mac. The smaller size for linux seems to be related to Asus eeePC users. 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 -- http://www.DIY-streetview.org -- 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 plugin interface - developers please liaise
On 26 Feb., 13:30, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, I also changed a few return codes in hpi to avoid potential confusion about which part produces an error. Is there some list, what each error code means? So we could add more meaningfull messages for users/new python developers, if the script or script interface fails. Currently they are only numbers, which does not say to much without looking into different places of the source. Thank you for the commit, Thomas. Really, none of the errors I worked on should occur under normal circumstances. But now, with the number, anyone can instantly locate them in the code to track down what went wrong. There is a pattern, though: - errors in the minus twenties come from hpi.cpp and indicate a problem in the interface - errors in the minus tens come from hpi.py and result from problems with the plugin - the plugin itself should return 0 if all is well or a small number on error If you want I can make a more detailed list, but I'd like to wait until we have decided how the plugin interface should be anchored in the main body of code. You may have read the remainder of my post, where I ask how this should be done, and I feel any formal specification at this point in time would be overkill. Once we've decided on the integration, a proper method to exchange messages, errors and data can be implemented. Kay -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] 2011.0 Artwork: voting starts now
Hi all, You will find at [0] images of the candidates for the splash screen / about menu of the upcoming Hugin 2011.0, as well as a link to vote for your favorite. Rules and the detailed description of the entries are at [1]. Voting is open now and will stay open during the beta phase of the release cycle. Voting will close a couple of days before the end of the beta phase and the splash screen will be integrated into the first release candidate. Entries are still accepted until the first beta release but late entrants acknowledge that voting has already started and accept that other entrants' artwork may have already received some votes. Yuv [0] http://www.photopla.net/hugin/2011.0.artwork.html [1] http://groups.google.com/group/hugin-ptx/t/2c24c7938309a241 signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Big list of suggestions
Hello, So I have several little things that I noticed, and that I think would help my workflow in using Hugin. I offer these not as complaints, but as ways that will increase my desire to continue using Hugin for my panorama projects. As an FYI, I've tested on a Fedora 11 w/ Hugin 2010.4.0 and a Fedora 14 system w/ Hugin 2010.5.0 from 2/22/2011 mercurial snapshot. I'll do my best to categorize the list since and make it more readable. -- Image list tab: - Some of the screenshots for show thumbnails in the image list. I think this is good, but I don't see them in the versions I'm using. - The text entry boxes in the Image Orientation area (which btw might better be called the Image Position area since it covers both orientation and location) are too small -- especially for negative numbers (ie. can't see the entire number). - Place the larger view of the selected image less far to the right (right now I have to make the Hugin window nearly full-screen just to see the image). Two quick ways to do this would be to: - move the Create control points button to be aligned with the Settings and Points per Overlap widgets: - shorted the size of the settings pull-down options list Bug: the selected image view doesn't redraw when the window size is changed. - Is there an argument I can pass to CPFind to increase the gamma that it uses when doing a comparison? Actually, I guess it might not truly need this since it has the raw numbers, but I did a test where I increased the gamma in all my images, and CPFind did a better job of finding matching points, so it would seem that a gamma argument could have value. -- Control points tab: - I would like the ability to set a gamma value for the entire image in the comparison image views. Actually, this request is broader than control points, I'd like to see it in the mask view and even on the selected image view on the Image tab. - Can there be a button to cancel a control point creation operation? There is an Add button, of course, when working with control points, I don't know how to get rid of a new control point that I don't want other than to Add it and then immediately Delete it. - Is there (or can there be) a way to create control points only between the two images shown? - Can the colors of the control point markers also be placed in a new column on the left of the point list? -- Preview window: - I'd like a preference to set the background color of the preview window to be something other than black. When working with nighttime featureless images, it can be hard to find them with a black background. - the Scale value of the Layout tab doesn't get set properly when going to another tab and then returning to Layout. - the sliders on the main preview window seem to be counter-intuitive (at least I have a difficult time using them). Perhaps this is because I'm been testing with super-high-res panorams rather than high FOV images) -- I have to move both sliders way to the right and the top to zoom in sufficiently to see anything. - I would like to be able to move/resize the overall view under the Preview and Layout tabs with the mouse (ie. not with the sliders). - Preview window (2010.5.0 version): Bug: the image toggle boxes are only big enough to see one digit of the image number. - I can't raise the overall Panorama Preview window to be on top of the Overview window (when that window is torn off from the main window). - The grid checkbox on the Ovewview window controls the display of the grid in the primary preview window - I don't know how to adjust the scale of the images in the overview window (they seem too big in my project). - Selecting the Thoby projection from the pull-down menu in the Projection tab went off to do the calculations and three days later had not completed (yes, I didn't get back to my home computer for three days and found it still calculating). So, a way to interrupt/cancel this would be good -- as well as fixing what is probably a bug. --- Of course, those are mostly orthogonal to my original issue (which I haven't created a good solution yet) of doing an alignment based on the robotically generated positions of each image capture. But looking to when I'll be using Hugin more regularly, these issues will be most helpful. I hope that list isn't too overwhelming! Thanks, Bill -- Bill Sherman Sr. Technology Advisor Advanced Visualization Lab Pervasive Technology Inst Indiana University
Re: [hugin-ptx] Stitching and enfusing a handheld panorama with several exposures
Markku Kolkka wrote: 25.2.2011 8:24, Gnome Nomad kirjoitti: Markku Kolkka wrote: JiHO kirjoitti viestissään (lähetysaika torstai, 24. helmikuuta 2011): If I follow the steps exactly I do this: 1- import my images 2- in the Images tab, stack them in stacks of 3 (0, +2, -2) Don't use stacks with hand-held images. Hugin believes that images in a stack are pre-aligned perfectly. Hmm, I used Hugin to align a stack of hand-held images and used the Merge to HDR's Stacked HDR Images option to produce an EXR file. The point is that using the New stack button on the Images tab *prevents* Hugin from aligning images defined as a stack (unless you manually unlink them). I guess that your stack of images wasn't actually defined as a bracketed stack on the Images tab? I'm still using an old version of Hugin that doesn't appear to support what you call a stack, so things could be very different from what a newer version can do. -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god 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] 2011.0 Release Plan
Hi all, I have just entered the 2011.0 Release Plan into Launchpad [0] and documented release planning [1]. The intention is to make the plan as predictable as possible so that contributors can plan for their own contributions (e.g. translations and bug fixes) and distributors can plan for the binary builds. Like with the last release cycle, it would be great if binary releases follow on the heels of the tarball releases. Feedback to the plan is welcome. I have set the final release well out in the future. It will depend amongst others also on the final release of Libpano 2.9.18 and other factors that are not fully predictable at the moment. As usual, the release will happen when it is ready and the provided time estimates are just an indication and are not guaranteed. Let's get it rolling! Yuv [0] https://launchpad.net/hugin/2011.0 [1] http://wiki.panotools.org/Development_of_Open_Source_tools#Release_Plan signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: How to use geometry vs. feature based control points?
On Sat 26-Feb-2011 at 00:29 -0800, Martin Terblanche wrote: I'm doing a project where I'm building a motorized head which will save all the positions to a log file. I want to automate the entire process of creating a panorama in Hugin. So i'm basically doing exactly the same thing as Bruno. I want to use a log file to help Hugin to place photos in areas with no control points. It seems like Papy wizard can create such a file (xml) and APP can then use this. But APP is expensive and I would like to use Hugin. Papywizard is open source, so it would be a good choice for controlling your panoramic head. Would you set the y,p,r of all the photos and then run the optimizer, all in a script? What train of thought must I follow here :) Unfortunately (as mentioned elsewhere in this thread) you can place the photos according to a log file, but photos move around as soon as you optimise, so you lose any benefit of aligning them beforehand. -- Bruno -- 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 plugin interface - developers please liaise
On Fri 25-Feb-2011 at 08:33 -0800, kfj wrote: Yet again, I ask: developers, liaise. Please don't expect of me to do it all. I'm not a GUI person, really, and I've spent a great deal of effort getting the backend right. Maybe someone else could look at the goodies I've stacked up and think of a clever way of enabling people to use them? Sorry, I haven't had time to look into this. I think initially the python interface would be useful even if it presents as a menu of functions that don't take any parameters. i.e. it can be merged more-or-less in the state it is in. Then there is an issue I'd like to have considered by the group: the hsi python module could be considered a library, since it can do hugin- ish stuff outside hugin, probably linking in a few shared libraries, but if it was linked statically, not even that. A lot of hugin's code is GPLed. Is there a problem with that? Please use 'GPL version 2 or later', this makes it easier to ship with Hugin. Are you concerned about how this effects the license of potential 3rd party plugins? And one more thing: I'd like to see a discussion about a perspective for merging the python_scripting branch back into the mainstream. Thomas and I have made a good effort to parametrize everything in cmake and make the scripting capability a compile-time option. The intersections with other code are minimal and well #ifdeffed. I would like to see the current Hugin 'trunk' move to a 2011.0.0 release branch as soon as possible. So the python interface should then be merged so that it goes into the next release after that. -- Bruno -- 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] 2011.0 Release Plan
On Sat 26-Feb-2011 at 17:11 -0500, Yuval Levy wrote: Feedback to the plan is welcome. I have set the final release well out in the future. It will depend amongst others also on the final release of Libpano 2.9.18 and other factors that are not fully predictable at the moment. If necessary libpano13-2.9.18_beta1 could be relabeled as 'final' if we need it for a Hugin release (since it seems to be ok). It would be nice to merge the new libpano13 test suite, but this needs some work. As far as Hugin is concerned, the current cpfind is so much better than anything we had before that I'd almost recommend people use a snapshot rather than 2010.4.0. -- Bruno -- 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] Hugin gives me an error and doesn't make me the panorama.
The error is that one: === *** Panorama makefile generated by Hugin *** === System information === Software: System Software Overview: System Version: Mac OS X 10.6.2 (10C2234) Kernel Version: Darwin 10.2.0 Boot Volume: Macintosh HD Boot Mode: Normal Computer Name: iMac de FRANCESC User Name: FRANCESC-MARIA (FARMAR) Secure Virtual Memory: Not Enabled 64-bit Kernel and Extensions: No Time since boot: 11:06 Hardware: Hardware Overview: Model Name: iMac Model Identifier: iMac10,1 Processor Name: Intel Core 2 Duo Processor Speed: 3,06 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 3 MB Memory: 4 GB Bus Speed: 1,07 GHz Boot ROM Version: IM101.00CC.B00 SMC Version (system): 1.52f9 Serial Number (system): WQ9501XA5PC Hardware UUID: 267E5620-2938-580D-9D12-1F2356FBC87B Disc usage Filesystem Size Used Avail Capacity Mounted on /dev/disk0s2 465Gi 373Gi 93Gi80%/ devfs 110Ki 110Ki0Bi 100%/dev map -hosts 0Bi0Bi0Bi 100%/net map auto_home0Bi0Bi0Bi 100%/home /dev/disk1s1 3.8Gi 21Mi 3.7Gi 1%/Volumes/EOS_DIGITAL /dev/disk2s2 218Mi 196Mi 22Mi90%/Volumes/hugin- mac-2010.4.0 === Output options === Hugin Version: 2010.4.0 built by Harry van der Wolf Project file: /var/folders/di/diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/ huginpto_tGIP4b Output prefix: -Users-FARMAR-Desktop-IMG_1501-IMG_1503 Projection: Rectilinear (0) Field of view: 84 x 47 Canvas dimensions: 8030 x 3924 Crop area: (0,0) - (8030,3924) Output exposure value: 15.19 Selected outputs Normal panorama * Blended panorama === Input images === Number of images in project file: 3 Number of active images: 3 Image 0: /Users/FARMAR/Desktop/IMG_1501.JPG Image 0: Size 5184x3456, Exposure: 15.19 Image 1: /Users/FARMAR/Desktop/IMG_1502.JPG Image 1: Size 5184x3456, Exposure: 15.20 Image 2: /Users/FARMAR/Desktop/IMG_1503.JPG Image 2: Size 5184x3456, Exposure: 15.16 === Testing programs === Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 0 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 1 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 2 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/enblend --compression=NONE - f8030x3924 -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503.tif -Users- FARMAR-Desktop-IMG_1501-IMG_1503.tif -Users-FARMAR-Desktop- IMG_1501-IMG_15030001.tif -Users-FARMAR-Desktop-IMG_1501- IMG_15030002.tif enblend: unknown option -U Try enblend --help for more information. gnumake: *** [-Users-FARMAR-Desktop-IMG_1501-IMG_1503.tif] Error 1 I use mac OSX snow leopard... do you know what I should do for repair it? Thank you. -- 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] Big list of suggestions
On Sat 26-Feb-2011 at 13:35 -0500, William Sherman wrote: So I have several little things that I noticed, and that I think would help my workflow in using Hugin. I offer these not as complaints, but as ways that will increase my desire to continue using Hugin for my panorama projects. Hi Bill, thanks these are some useful bug reports and should be added as bugs in the tracker (though search to make sure they don't already exist first). Some comments below: - Some of the screenshots for show thumbnails in the image list. Can you point to these? it could be you are seeing a file browser window or the Add Images dialog which shows thumbnails (depending on OS). - Is there an argument I can pass to CPFind to increase the gamma that it uses when doing a comparison? Potentially the existing camera response parameters in the cpfind input file could be used to map the images to linear space for matching (this would be similar to gamma correction), but without some testing I'm not sure how useful this would be. Control points tab: - I would like the ability to set a gamma value for the entire image in the comparison image views. Actually, this request is broader than control points, I'd like to see it in the mask view and even on the selected image view on the Image tab. Hugin needs to be changed to display photos properly using colour profiles, this would be something related to that. - Is there (or can there be) a way to create control points only between the two images shown? You can select two or more photos in the Images tab and generate points for just those photos. - the sliders on the main preview window seem to be counter-intuitive (at least I have a difficult time using them). Basically, the preview window doesn't have any zoom functionality. The sliders are changing the field of view of the output panorama canvas, which is not quite the same thing. There is a feature request in the tracker somewhere for zooming. - I can't raise the overall Panorama Preview window to be on top of the Overview window (when that window is torn off from the main window). It is an over-view, I think this is intentional. -- Bruno -- 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] Hugin gives me an error and doesn't make me the panorama.
Looks like you've given the name of the output file as -Users-FARMAR-Desktop-IMG_1501-IMG_1503 It mustn't start with a '-', try removing that. Tim On 27 February 2011 00:34, Frank Al 9fra...@gmail.com wrote: The error is that one: === *** Panorama makefile generated by Hugin *** === System information === Software: System Software Overview: System Version: Mac OS X 10.6.2 (10C2234) Kernel Version: Darwin 10.2.0 Boot Volume: Macintosh HD Boot Mode: Normal Computer Name: iMac de FRANCESC User Name: FRANCESC-MARIA (FARMAR) Secure Virtual Memory: Not Enabled 64-bit Kernel and Extensions: No Time since boot: 11:06 Hardware: Hardware Overview: Model Name: iMac Model Identifier: iMac10,1 Processor Name: Intel Core 2 Duo Processor Speed: 3,06 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 3 MB Memory: 4 GB Bus Speed: 1,07 GHz Boot ROM Version: IM101.00CC.B00 SMC Version (system): 1.52f9 Serial Number (system): WQ9501XA5PC Hardware UUID: 267E5620-2938-580D-9D12-1F2356FBC87B Disc usage Filesystem Size Used Avail Capacity Mounted on /dev/disk0s2 465Gi 373Gi 93Gi80%/ devfs 110Ki 110Ki0Bi 100%/dev map -hosts 0Bi0Bi0Bi 100%/net map auto_home0Bi0Bi0Bi 100%/home /dev/disk1s1 3.8Gi 21Mi 3.7Gi 1%/Volumes/EOS_DIGITAL /dev/disk2s2 218Mi 196Mi 22Mi90%/Volumes/hugin- mac-2010.4.0 === Output options === Hugin Version: 2010.4.0 built by Harry van der Wolf Project file: /var/folders/di/diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/ huginpto_tGIP4b Output prefix: -Users-FARMAR-Desktop-IMG_1501-IMG_1503 Projection: Rectilinear (0) Field of view: 84 x 47 Canvas dimensions: 8030 x 3924 Crop area: (0,0) - (8030,3924) Output exposure value: 15.19 Selected outputs Normal panorama * Blended panorama === Input images === Number of images in project file: 3 Number of active images: 3 Image 0: /Users/FARMAR/Desktop/IMG_1501.JPG Image 0: Size 5184x3456, Exposure: 15.19 Image 1: /Users/FARMAR/Desktop/IMG_1502.JPG Image 1: Size 5184x3456, Exposure: 15.20 Image 2: /Users/FARMAR/Desktop/IMG_1503.JPG Image 2: Size 5184x3456, Exposure: 15.16 === Testing programs === Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 0 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 1 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503 -i 2 /var/folders/di/ diDkgh2lHxm4eC9KTZktCk+++TI/-Tmp-/huginpto_tGIP4b /Applications/Hugin/Hugin.app/Contents/Resources/ HuginStitchProject.app/Contents/MacOS/enblend --compression=NONE - f8030x3924 -o -Users-FARMAR-Desktop-IMG_1501-IMG_1503.tif -Users- FARMAR-Desktop-IMG_1501-IMG_1503.tif -Users-FARMAR-Desktop- IMG_1501-IMG_15030001.tif -Users-FARMAR-Desktop-IMG_1501- IMG_15030002.tif enblend: unknown option -U Try enblend --help for more information. gnumake: *** [-Users-FARMAR-Desktop-IMG_1501-IMG_1503.tif] Error 1 I use mac OSX snow leopard... do you know what I should do for repair it? Thank you. -- 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
Re: [hugin-ptx] Hugin gives me an error and doesn't make me the panorama.
Frank Al schrieb am 27.02.11 00:34: The error is that one: [...] enblend: unknown option -U Try enblend --help for more information. gnumake: *** [-Users-FARMAR-Desktop-IMG_1501-IMG_1503.tif] Error 1 I use mac OSX snow leopard... do you know what I should do for repair it? It's a bug: The default file name for your output image is confusing enblend: the suggested name starts with '-U...' which is interpreted later on as a command, not as a file name. So when you trigger the stitching process all you need to do is type a different (or shorten the suggested) file name in the dialog. Hugin somehow wants to use the whole path for the file name and at least on Mac OS exchanges all '/' with '-'. That's basically a good behaviour but OTOH a '-' at the start should be avoided. Hope that helps, Carl -- 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] Big list of suggestions
Hi, On February 26, 2011 01:35:53 pm William Sherman wrote: So I have several little things that I noticed thank you for taking the time to note down your observation, well explained, categorized, and mostly pertinent. -- Image list tab: - Some of the screenshots for show thumbnails in the image list. I think this is good, but I don't see them in the versions I'm using. Do you mean a thumbnail for every line in the list? or the thumbnail for the selected image? I see the thumbnail for the selected image. - The text entry boxes in the Image Orientation area (which btw might better be called the Image Position area since it covers both orientation and location) are too small -- especially for negative numbers (ie. can't see the entire number). Done. Please check if it needs even larger field size. - Place the larger view of the selected image less far to the right (right now I have to make the Hugin window nearly full-screen just to see the image). Two quick ways to do this would be to: - move the Create control points button to be aligned with the Settings and Points per Overlap widgets: Done. - shorted the size of the settings pull-down options list If I am not mistaken the length of that pull-down list is determined by the string entered in the preferences, which in turn is user-changeable. The default names are long / descriptive. Bug: the selected image view doesn't redraw when the window size is changed. Please file in the tracker. - Is there an argument I can pass to CPFind to increase the gamma that it uses when doing a comparison? Not that I know of. Please file feature request in the tracker. -- Control points tab: - I would like the ability to set a gamma value for the entire image in the comparison image views. Please file feature request in the tracker. - Can there be a button to cancel a control point creation operation? hit the Delete button. Works at any stage of the creation. Tested on the most recent snapshot a few minutes ago, Kubuntu 10.4 LTS. - Is there (or can there be) a way to create control points only between the two images shown? This is actually in the Images tab. CTRL-click on the images in the list and hit the button to generate CPs only between the selected images (the one you asked me to move). - Can the colors of the control point markers also be placed in a new column on the left of the point list? Please file a feature request in the tracker. -- Preview window: - I'd like a preference to set the background color of the preview window to be something other than black.When working with nighttime featureless images, it can be hard to find them with a black background. Make sense. Please file a feature request in the tracker. - the Scale value of the Layout tab doesn't get set properly when going to another tab and then returning to Layout. Please file a bug report in the tracker. I could see it as well: the images are drawn to default scale rather than to the selected scale in the slider. - the sliders on the main preview window seem to be counter-intuitive The slider set the field of view of the panorama. I suspect you are using them as a zoom function. Use the mouse wheel in a 2010.5 snapshot instead. - I would like to be able to move/resize the overall view under the Preview and Layout tabs with the mouse (ie. not with the sliders). Why, if I may ask? And how would you like the mouse to behave? - Preview window (2010.5.0 version): Bug: the image toggle boxes are only big enough to see one digit of the image number. This is already in the bug tracker IIRC. - I can't raise the overall Panorama Preview window to be on top of the Overview window (when that window is torn off from the main window). Why would you want to do so? note that you can show/hide the overview with the button next to the list of the displayed images. - The grid checkbox on the Ovewview window controls the display of the grid in the primary preview window Indeed it does. Where would you put this control? - I don't know how to adjust the scale of the images in the overview window (they seem too big in my project). There should not be a need to scale the images in the overview window. That's their size, shape, position in relation to the panosphere. If they seem to big, the project is not properly aligned / optimized. - Selecting the Thoby projection from the pull-down menu in the Projection tab went off to do the calculations and three days later had not completed (yes, I didn't get back to my home computer for three days and found it still calculating). So,
