[hugin-ptx] libpano
I have committed the changes to support tilt of the camera in PToptimizer and PTmender. See the ChangeLog for details. the new parameters are: Tx, Ty, Tz, and Ts (for scale). --dmg -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . --~--~-~--~~~---~--~~ 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: Tilt transformation...
Nice work guys! 2009/9/9 D M German d...@uvic.ca Now, the real question for hugin developers: can somebody create a branch of hugin that supports these new parameters during the optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale? So trying to mentally picture these parameters in my head to understand how optimization should be done. When assembling a mosaic camera position imagine subject beeing a plane Xs-Ys with Zs constant, and camera moved across a paralell plane X-Y (with Z=0). What would these parameter represent? *shearX,shearY = camera position in the camera plane, this would be different for each picture taken * tiltX,Y,Z. rotation around the camera node (shearX,shearY), also different for each picture * tiltScale, I guess this afect scaling of the picture... ( how does this relate to current FOV or an imaginary shearZ parameter?) Am I on the right track? Cheers /O --~--~-~--~~~---~--~~ 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: strangely calling antipano-sift-c
Thank you Seb Bart so much, So this is how it works and what is happening, now I can understand. I do mean autopano-sift-c, it is a funny mistake. your information helps a lot, Best Regards Elvis --~--~-~--~~~---~--~~ 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: Tilt transformation...
When assembling a mosaic camera position imagine subject beeing a plane Xs-Ys with Zs constant, and camera moved across a paralell plane X-Y (with Z=0). What would these parameter represent? * shearX,shearY = camera position in the camera plane, this would be different for each picture taken * tiltX,Y,Z. rotation around the camera node (shearX,shearY), also different for each picture * tiltScale, I guess this afect scaling of the picture... ( how does this relate to current FOV or an imaginary shearZ parameter?) to be honest, I am not sure how much they will help for a mosaic. The model for panos in libpano is still spherical. But it is a matter of trying. scale scales the tilt operations only. It actually scales the view point from which the photo was originally taken. I actually think that libpano needs a plain, simple, scaling option. If you look at the PDF I sent, the scale is a factor by which the field of view of the lens is multiplied in those computations. As I said, I am not sure what use it might have. But the feature is there now. Perhaps for mosaic mode we need to redesign the libpano internal model. we'll see. --dmg --~--~-~--~~~---~--~~ 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: Tilt transformation...
On Wed, Sep 9, 2009 at 23:03, D M German d...@uvic.ca wrote: I have the inverse transformations done. they are described here: http://turingmachine.org/~dmg/temp/tiltEq.pdf I am struggling with the inverse ones. If anybody wants to help, I'll be grateful. This is the only roadblock to have an alpha version of it. Looking at the formulas, I have the impression that the inverse transformation should not be complicated - but this probably means I missed something. The inverse operation of V' = Mx My Mz V is V = Mz- My- Mx- V' (1) with Mx- defined as Mx but with a -theta instead of theta (rotation around an axis can be undone by rotating by the opposite amount). You just have to be careful with the order of the unrotations. V' is known up to a multiplicative constant, and is proportional to (x'/d ; y'/d; 1). So we find V up to a multiplicative constant by the inverse operation (1) above, and x0 and y0 are obtained by: x0 = V0 * d / V2 y0 = V1 * d / V2 Does this make sense? S --~--~-~--~~~---~--~~ 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] Tilt transformations....
Hi, I was reading stuff about tilt transformations and was wondering if it would help me build a fitting pano for a bunch of pictures I took. If it doesn't... this might serve as a hint as to what may be useful and developed in the future The situation - I took a bunch of pictures from about 450-500m above the Dutch landscape. In fact the first picture was around 500m and the last around 450. There was some wind, so there is also considerable positional shift between the first and the last image. The goal To build a panorama that doesn't have visible artefacts. This is currently not possible with Hugin. At least I couldn't manage. The Trick - If we assume that all pixels that I shot are in one plane (which is a good approximation of the Dutch landscape), a hugin-like optimization step will find the position and direction of the camera relative to the plane. This is similar to what Google does from the areal images they took. But their task is much easier as they usually take photographs mostly straight down. From the pixels in the plane, we can project again to a panoramic projection that is nice to view. This is in a way similar to what google earth does. The problem is that if I get the plane as a temporary image, it will be inifite in size because we included the horizon in the pictures. And I would like the horizon and the sky above to be in the final image, which doesn't get projected on the plane. The questions - Is this already possible to stitch with current hugin/panotools? Would the tilt/shift stuff be neccesary? Does the current tilt/shift stuff help in this situation? Roger. -- ** r.e.wo...@bitwizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** **Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. - Adapted from lxrbot FAQ --~--~-~--~~~---~--~~ 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: Tilt transformation...
Here are examples of the use: This photo was not remapped: But this one was: http://turingmachine.org/~dmg/temp/floorInput.jpg and this is the output, merged (difference mode): http://turingmachine.org/~dmg/temp/merged.jpg It was optimized using: # specify variables that should be optimized v Tx1 Ty1 Ts1 g1 t1 p1 r1 y1 using 17 control points in intersections of lines of floor. And remapped using: o f0 r-99.5957 p-0.992759 y-3.69248 v94.6652 a0.00 b0.00 c0.00 g-726.252355 t558.903060 Tx54.770184 Ty-45.457790 Tz18.993815 Ts2.536055 d0.00 e0.00 u10 +buf As you can see, the transformation works. and the output: http://turingmachine.org/~dmg/temp/floorOutput.jpg and this is a photo of the same place taken: http://turingmachine.org/~dmg/temp/floor.jpg In this case, there is a tiltX of 32 degrees, and a tiltZ of -11 and a shear of -125 pixels. I have also added 3 parameters to the parser: Tx, Ty, and Tz, which are angles to rotate in degrees; and Ts, which is a scaling factor. I have the inverse transformations done. they are described here: http://turingmachine.org/~dmg/temp/tiltEq.pdf I am struggling with the inverse ones. If anybody wants to help, I'll be grateful. This is the only roadblock to have an alpha version of it. Now, the real question for hugin developers: can somebody create a branch of hugin that supports these new parameters during the optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale? I haven't committed my code but will do soon. in its current state the optimizer nor the cropping works (we need the forward transform for that). -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . -- --dmg --- Daniel M. German http://turingmachine.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: Tilt transformations....
All that is necessary is there, but it needs some manual work until hugin is modified. You need to edit the script before the optimization. then export the script to remap the photos using PTmender. BTW, hugin developers, any chance you can implement using a script to edit the script before optimizing? --dmg On Thu, Sep 10, 2009 at 2:07 AM, Rogier Wolff rew-googlegro...@bitwizard.nl wrote: Hi, I was reading stuff about tilt transformations and was wondering if it would help me build a fitting pano for a bunch of pictures I took. If it doesn't... this might serve as a hint as to what may be useful and developed in the future The situation - I took a bunch of pictures from about 450-500m above the Dutch landscape. In fact the first picture was around 500m and the last around 450. There was some wind, so there is also considerable positional shift between the first and the last image. The goal To build a panorama that doesn't have visible artefacts. This is currently not possible with Hugin. At least I couldn't manage. The Trick - If we assume that all pixels that I shot are in one plane (which is a good approximation of the Dutch landscape), a hugin-like optimization step will find the position and direction of the camera relative to the plane. This is similar to what Google does from the areal images they took. But their task is much easier as they usually take photographs mostly straight down. From the pixels in the plane, we can project again to a panoramic projection that is nice to view. This is in a way similar to what google earth does. The problem is that if I get the plane as a temporary image, it will be inifite in size because we included the horizon in the pictures. And I would like the horizon and the sky above to be in the final image, which doesn't get projected on the plane. The questions - Is this already possible to stitch with current hugin/panotools? Would the tilt/shift stuff be neccesary? Does the current tilt/shift stuff help in this situation? Roger. -- ** r.e.wo...@bitwizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. - Adapted from lxrbot FAQ -- --dmg --- Daniel M. German http://turingmachine.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: [OSX] hugin-mac-2009.2-Beta3 for download
Harry van der Wolf wrote: 2009/9/9 Carl von Einem c...@einem.net nona crashed almost instantly on my G5 / OSX 10.4.11 Thanks for testing. In the bug ticket you specify that nona with GPU immediately crashes. I assume that nona wthout GPU usage does work correctly? Harry Yes it worked great without using the GPU option, I just commented on my bug report and posted a link to the stitched test panorama: http://einem.net/berge/2009/090825-schachen-pavillon/ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: [PanoTools-devel] Tilt transformation...
On Thu 10-Sep-2009 at 02:11 -0700, Daniel M. German wrote: But this one was: http://turingmachine.org/~dmg/temp/floorInput.jpg and this is the output, merged (difference mode): http://turingmachine.org/~dmg/temp/merged.jpg That is a 404 error, this looks like the right link: http://turingmachine.org/~dmg/temp/floorMerged.jpg Very impressive. Will it be possible to take the Tx, Ty, Tz Ts parameters and calculate a cartesian x, y z vector between the two camera points? -- 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] Re: Mailing List(s)
Bart van Andel wrote: [...] I rather think that we will have one separated list for notifications (tracker and commits), and one separated list for talk (which can very well be hugin-ptx if the users tolerate more dev talk). As a user with an interest in coding and algorithms, I'm pretty happy with the way the hugin-ptx list is working right now, but the approach mentioned above seems fair. Since I'm reading all the list messages through the Google Groups interface [0], everything gets grouped properly already, and a few extra messages to read or decline won't hurt. As a simple user I like the hugin-ptx list the way it is now. Though much of the dev talk is above me it gives me a good idea of the way things are going and whether I should be thinking of upgrading, the sorts of problems I could come across in using whichever version of hugin - so I'm not completely thrown when they turn up - and a feel for the way hugin works, which helps in using it. Eliminating the stuff I don't want to read is really not a problem. Doug --~--~-~--~~~---~--~~ 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] Error when trying to stitch large panoramas
Hello, I am using hugin Version 2009.1.0.4175. I am attempting to stitch together a panorama with 39 images 12 megapixels each. I am using Windows 2000 SP5 with 1 GB RAM and 4 GB virtual memory. I have an error I have attempted to solve and have searched the mailing list for a solution. When I attempt the automatic alignment procedure, I get the following error in a dialog box: Could not execute command: autopano-sift-c.exe --maxmatches 20 C: \DOCUME~1\ADMINI~1\LOCALS~1\Temp\ap_80B.tmp F:\hugin \pano33\IMG_1458.JPG F:\hugin\pano33\IMG_1459.JPG etc... and all 39 images are listed. Please let me know if this bug has been encountered and what the fix is. Thanks for your patience, profdc9 --~--~-~--~~~---~--~~ 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: cleaning up the Hugin-Libpano link
T. Modes wrote: It works on windows, but you have removed the progress windows of the optimiser oups, sorry. I'll try to fix this today. 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Updated extended enfuse and enblend documentation
2009/9/9 Yuval Levy goo...@levy.ch:
and IMO the wrong way to go about the issue. Wiki format only makes
sense if you want the pages to be editable in the Wiki. Good luck
syncing with the official documentation if you do.
it's clear that there should be one source of documentation or it
could get silly.
I'm fiddling about with the texi, info files largely because I've no
idea till yesterday how they are done.
Can somebody explain what @ref{Figure:photographic-workflow} is ? in
workflow.texi
some programs ( texi2html, texi2dvi, texi2pdf, dvipng expect a txt
file, some a pdf, some a ps, some a jpg.
which causes an error.
I made .pdf .jpg , ps from the .fig file and they seem happy with that
but what is supposed to happen ?
regards
mick
--~--~-~--~~~---~--~~
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 when trying to stitch large panoramas
On Sep 10, 2:46 pm, profdc9 prof...@gmail.com wrote: SNIP Could not execute command: autopano-sift-c.exe --maxmatches 20 C: \DOCUME~1\ADMINI~1\LOCALS~1\Temp\ap_80B.tmp F:\hugin \pano33\IMG_1458.JPG F:\hugin\pano33\IMG_1459.JPG etc... and all 39 images are listed. Well, it's a bug in windoze command line length. It can't be helped. You could drop the number of images you're trying to align. But, you can change the way you're calling autopano-sift by using this arguments: --maxmatches %p %o %s. Notice the %p instead of %i. This way you're giving apsc the whole project file, instead of individual image names. You also get some other bonuses by calling it like that, as it enables feature classification in conformal space. Also consider upgrading Hugin from here: http://hugin.huikeshoven.org/ Newer versions have a nice interface for multiple CP generators. PS: consider upgrading you ram (3-4gb), it's dirt cheap nowdays and you'll get a 10-fold increase when you get to the blending part. --~--~-~--~~~---~--~~ 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: Changing [OSX] hugin-mac AutoCP parameters is possible.
Hello Harry, I thought OS X users should know that they could change the plug-in parameters. Your idea to save multiple parameter versions for the same plug-in type is a great idea. If it were me creating the Hugin interface I would not have the parameter settings accessible only in Peferences. I'd have the setting available in the context where it is used. In other words the parameters would be visible and easily changed with a double click on their representation. One way to do this would be to have the Peference pane openable to the settings location upon that double click. That same concept could be applied througout Hugin where applicable. I don't know how the different os packages are created. It seems to me that one can code the parameter less plugin concept without needing to change the current the OS X plug-in structure. Hugin knows all about these plug-in files. It can easily read each plug-in's argument line, report it in Peferences and then alter the argument if needed. Allan On Tue, Sep 8, 2009 at 12:20 AM, Harry van der Wolf hvdw...@gmail.comwrote: 2009/9/8 AKS-Gmail-IMAP aksei...@gmail.com Harry van der Wolf wrote regarding the plug-in method for AutoCP matchers used in the OS X implementation: The disadvantage of Ippei's implementation is that you can't change parameters which you can with Thomas solution. Ah but Harry you can change easily the parameters for the OS X AutoCPs. In each of the OS X AutoCP packages is an XML property list plist file called Info.plist. OS X will open that file using the Property List Editor. Using the editor you may change the HginAutoCPArgs key to be anything you want. You may even keep the plist open after saving the change so to quickly change the arguments for the next AutoCP run. Allan Hi Allan, Thanks for your reply. I know that you can do that as I myself created a couple of them after the first release by Ippei. The same plist editor also gives you the chance to change the name displayed inside hugin. So you can copy them, change the parameters and displayed name and you have a new plugin The problem is that many users simply don't know where these plugins are or how to open them. I want to look into the option where we have parameter less plugins that can be selected and configured from the new Preferences panel. That leaves you with only one plugin per AutoCP creator, but you can call it many times based on the settings. Harry --~--~-~--~~~---~--~~ 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: [PanoTools-devel] Tilt transformation...
Awesome. This will be quite useful (specially for some nadir shot that I badly took and invested quite some time to redo). I'm always impressed by the power of this software, and where it is going. nick On Thu, Sep 10, 2009 at 6:15 AM, Bruno Postle br...@postle.net wrote: On Thu 10-Sep-2009 at 02:11 -0700, Daniel M. German wrote: But this one was: http://turingmachine.org/~dmg/temp/floorInput.jpg and this is the output, merged (difference mode): http://turingmachine.org/~dmg/temp/merged.jpg That is a 404 error, this looks like the right link: http://turingmachine.org/~dmg/temp/floorMerged.jpg Very impressive. Will it be possible to take the Tx, Ty, Tz Ts parameters and calculate a cartesian x, y z vector between the two camera points? -- 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] Re: Error when trying to stitch large panoramas
Could not execute command: autopano-sift-c.exe --maxmatches 20 C: \DOCUME~1\ADMINI~1\LOCALS~1\Temp\ap_80B.tmp F:\hugin \pano33\IMG_1458.JPG F:\hugin\pano33\IMG_1459.JPG etc... and all 39 images are listed. Well, it's a bug in windoze command line length. It can't be helped. You could drop the number of images you're trying to align. I don't think it's the command line length with only 39 images. I think the correct path to autopano-sift-c.exe is missing. Go under preferences, CP generators, then select autopano-sift-c and choose edit. Then select the correct path to autopano-sift-c.exe (look in the folder where you installed hugin, e.g. c:\Program Files\Hugin \bin\autopano-sift-c.exe). Then it should work. Also consider upgrading Hugin from here:http://hugin.huikeshoven.org/ Newer versions have a nice interface for multiple CP generators. Rev 4175 has yet the new interface with multiple CP generators. Maybe the installer is not yet updated to the new interface. 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: Updated extended enfuse and enblend documentation
I know nothing about Texinfo but that looks very much like QuarkXPress
ASCII/XPress Tags I usually work with. That's basically content as
plain ascii text files together with formatting instructions which start
with a '@'. Cool :-)
Carl
michael crane wrote:
2009/9/9 Yuval Levy goo...@levy.ch:
Can somebody explain what @ref{Figure:photographic-workflow} is ? in
workflow.texi
--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation
from the texinfo.pdf on page 225:
@ref{node, [entry], [node-title], [info-file], [manual]}
Make a plain reference that does not start with any special text.
Follow command with a punctuation mark. Only the first argument
is mandatory. See Section 8.6 [...@ref], page 70.
and...
8.6 @ref
@ref is nearly the same as @xref except that it does not generate
a ‘See’ in the printed output, just the reference itself. This
makes it useful as the last part of a sentence. (...)
Carl von Einem wrote:
I know nothing about Texinfo but that looks very much like QuarkXPress
ASCII/XPress Tags I usually work with. That's basically content as
plain ascii text files together with formatting instructions which start
with a '@'. Cool :-)
Carl
michael crane wrote:
2009/9/9 Yuval Levy goo...@levy.ch:
Can somebody explain what @ref{Figure:photographic-workflow} is ? in
workflow.texi
--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation
2009/9/10 Carl von Einem c...@einem.net
from the texinfo.pdf on page 225:
@ref{node, [entry], [node-title], [info-file], [manual]}
Make a plain reference that does not start with any special text.
Follow command with a punctuation mark. Only the first argument
is mandatory. See Section 8.6 [...@ref], page 70.
and...
8.6 @ref
@ref is nearly the same as @xref except that it does not generate
a ‘See’ in the printed output, just the reference itself. This
makes it useful as the last part of a sentence. (...)
Carl von Einem wrote:
I know nothing about Texinfo but that looks very much like QuarkXPress
ASCII/XPress Tags I usually work with. That's basically content as
plain ascii text files together with formatting instructions which start
with a '@'. Cool :-)
Carl
michael crane wrote:
2009/9/9 Yuval Levy goo...@levy.ch:
Can somebody explain what @ref{Figure:photographic-workflow} is ? in
workflow.texi
Or to put it simple : @ref{Figure:photographic-workflow} refers to a figure
which is an eps file called photographic-workflow.eps. You will find this
photographic-workflow.eps in the same directory (in this pathless case)
as the texi file.
Harry
--~--~-~--~~~---~--~~
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: cleaning up the Hugin-Libpano link
Yuval Levy wrote: T. Modes wrote: It works on windows, but you have removed the progress windows of the optimiser oups, sorry. I'll try to fix this today. DONE. tr...@rev4361 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Windows Hugin SDK and documentation
Hi Ryan and other Windows developers I'm moving this piece of information to the main mailing list. Ryan Sleevi wrote: -Original Message- From: Yuval Levy Sent: Tuesday, September 08, 2009 8:34 AM To: kornel.be...@berlin.de Cc: Harry van der Wolf; Christoph Spiel; ryan+hugin; bst; Thomas.Modes; Andrew Mihal; Lukáš Jirkovský; Bruno Postle; Pablo d'Angelo; Pascal Spörri Subject: Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list] SNIP OK, so we may create something working on more then one platform. reminds me that I did not yet even try on Windows. I'm stuck with not being able to build lcms-1.18a inside the Hugin SDK (which has 1.17). Yuv, check the .diff file uploaded to the Wiki for building the Windows SDK. It's just a one line change for lcms (1.18). The trick for lcms-1.18 is that you *only* need to build the lcms project, not the entire solution. lcms (the project) doesn't depend on the TIFF or JPEG libraries, so it should have no trouble building. Thanks, Ryan - this did the trick. I was going to add this bit of information, as well as document the lack of OpenMP support in the Express Editions of MSVC, to the page documenting the [Hugin SDK]. Then I realized that I was going to raise a conflict again: There is a major inconsistency in the document which stems from the definition of Hugin SDK. When writing up the document, Guido defined Hugin SDK as the minimal stable binaries and headers needed to build and run Hugin. To me it must be more than that. And to Ryan obviously too: lcms is not needed to build the Hugin binary. Hence it is documented as 64-bit Only. But as I found out, it concerns 32-bit as well. The logical consequence would be to first define what the Hugin SDK really is; then to update the documentation and distributed binaries accordingly. Ad's releases are to me the proof that the current SDK does not work. It becomes stale quickly as upstream tools and libraries evolve. Worse: it leaves people like Ad dependent on the next binary SDK instead of giving them the tools and knowledge to update their SDK. The [Hugin SDK] Wiki page should make people like Ad independent. Hence my suggestion: 1. The [Hugin SDK] will document how to build each and every package upstream, including further upstream dependencies (e.g. Hugin depends on enblend; and enblend depends on lcms; hence both should be documented), for both 32 and 64 bit. 2. Distribute the SDK in two forms: one large archive containing everything (almost like the current one). It will become outdated, but here comes the second distribution: archives of individual packages. This way the faster evolving packages can be updated/distributed more often. To achieve this, I suggest to expand on the current structure of the [Hugin SDK]. Add/document the missing packages (currently if I try to build enblend according to [build] instructions, I miss some bits). For each package, note if it is: - FIX: has not been changing for years and is unlikely to change any time soon (e.g. GetText) - STABLE: evolves regularly and is worth updating to the latest stable, but is not critical (e.g. Boost) - DYNAMIC: evolves continuously and is worth updating continuously (e.g. ExifTool) - DEV: is critical to bleeding edge Hugin functionality, and it is worth following it in between releases when making test builds (e.g. libpano or Enblend and Enfuse) Currently there is too much confusion. There are four pages documenting Windows builds. I would suggest integrating the information about the [patches] into the [Hugin SDK] documentation; and extracting the relevant information from the [incomplete] page. In the end, there should be just two pages: one guiding the complete newbie through a simple [build] of the DEV packages (that's Hugin, Autopano-SIFT-C, Enfuse-Enblend, Libpano) with pre-built SDK binaries; and one documenting how to build the *whole* [Hugin SDK] from scratch. Yuv [Hugin SDK] http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29 [build] http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK [patches] http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29_Patches [incomplete] http://wiki.panotools.org/Hugin_Compiling_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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: [OSX] hugin-mac-2009.2-Beta3 for download
Carl von Einem wrote: Yes it worked great without using the GPU option excellent. this means that it is no show stopper. thanks Carl 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Error when trying to stitch large panoramas
T. Modes wrote: Could not execute command: autopano-sift-c.exe --maxmatches 20 C: \DOCUME~1\ADMINI~1\LOCALS~1\Temp\ap_80B.tmp F:\hugin \pano33\IMG_1458.JPG F:\hugin\pano33\IMG_1459.JPG etc... and all 39 images are listed. Well, it's a bug in windoze command line length. It can't be helped. You could drop the number of images you're trying to align. I don't think it's the command line length with only 39 images. I think the correct path to autopano-sift-c.exe is missing. Go under preferences, CP generators, then select autopano-sift-c and choose edit. Then select the correct path to autopano-sift-c.exe (look in the folder where you installed hugin, e.g. c:\Program Files\Hugin \bin\autopano-sift-c.exe). Then it should work. Also consider upgrading Hugin from here:http://hugin.huikeshoven.org/ Newer versions have a nice interface for multiple CP generators. Rev 4175 has yet the new interface with multiple CP generators. Maybe the installer is not yet updated to the new interface. it is likely the installer (depending on what the user ticks it writes configurations into the registry). now that the settings are properly taken care of by the new interface, it should be changed, in the .iss files. Ad did build rev 4175 from trunk and his build process is right. The Hugin binary is pretty much up to date (although using a more recent build won't hurt). May be that the SDK still has an older version of autopano-sift-C. 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Windows Hugin SDK and documentation
Or we can go the easier route (for end users) that I've been pursuing: An automatable that handles it all for you ;-) With the basic pre-requisite of 1) Sources for packages 2) The patches from me (already applied, but nothing to say we can't automate that in the future) 3) MSVC Express Edition 4) Windows SDK (6.1 or 7) It digs in and builds each part of the SDK - Debug Release, 32-bit and 64-bit. I'm currently using batch files as the means, but after working with the CMake-ification of Enblend/Enfuse, I think there is enough capability (by means of the external commands) that for the non-CMake'd portions (eg: Everything *BUT* enblend/enfuse), we can call the appropriate tools (eg: configure.bat for STLport, bjam for boost, vcbuild for the various .sln based projects, etc). With my batch file setup, I've got it automatically building everything through enblend-enfuse hands-free. Using the four basic requirements above, I can kick it off, and step back and I've got all the enblend-enfuse binaries. At that point, the distribution of the SDK needs merely concern itself with the maintenance of 1) The patches - Which tend to fix path resolution issues relative to the SDK for .sln projects and add 64-bit configurations 2) The CMake configuration script - Which is used really just to find the various packages, determine if they're built yet or not, and if not, build them using the packages appropriate build mechanism. This seems a much more realistic and reasonable scenario for getting people started, and also resolves potential issues where, for example, a user might want to alternative between statically and dynamically linking the MSVC runtime (Legal concerns, performance concerns, functionality, who knows) and issues w/ versions (eg: 2008 v 2008 SP1 v 2010 at some point) Thoughts? -Original Message- From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf Of Yuval Levy Sent: Thursday, September 10, 2009 12:16 PM To: hugin-ptx@googlegroups.com Subject: [hugin-ptx] Windows Hugin SDK and documentation Hi Ryan and other Windows developers I'm moving this piece of information to the main mailing list. Ryan Sleevi wrote: -Original Message- From: Yuval Levy Sent: Tuesday, September 08, 2009 8:34 AM To: kornel.be...@berlin.de Cc: Harry van der Wolf; Christoph Spiel; ryan+hugin; bst; Thomas.Modes; Andrew Mihal; Lukáš Jirkovský; Bruno Postle; Pablo d'Angelo; Pascal Spörri Subject: Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list] SNIP OK, so we may create something working on more then one platform. reminds me that I did not yet even try on Windows. I'm stuck with not being able to build lcms-1.18a inside the Hugin SDK (which has 1.17). Yuv, check the .diff file uploaded to the Wiki for building the Windows SDK. It's just a one line change for lcms (1.18). The trick for lcms-1.18 is that you *only* need to build the lcms project, not the entire solution. lcms (the project) doesn't depend on the TIFF or JPEG libraries, so it should have no trouble building. Thanks, Ryan - this did the trick. I was going to add this bit of information, as well as document the lack of OpenMP support in the Express Editions of MSVC, to the page documenting the [Hugin SDK]. Then I realized that I was going to raise a conflict again: There is a major inconsistency in the document which stems from the definition of Hugin SDK. When writing up the document, Guido defined Hugin SDK as the minimal stable binaries and headers needed to build and run Hugin. To me it must be more than that. And to Ryan obviously too: lcms is not needed to build the Hugin binary. Hence it is documented as 64-bit Only. But as I found out, it concerns 32-bit as well. The logical consequence would be to first define what the Hugin SDK really is; then to update the documentation and distributed binaries accordingly. Ad's releases are to me the proof that the current SDK does not work. It becomes stale quickly as upstream tools and libraries evolve. Worse: it leaves people like Ad dependent on the next binary SDK instead of giving them the tools and knowledge to update their SDK. The [Hugin SDK] Wiki page should make people like Ad independent. Hence my suggestion: 1. The [Hugin SDK] will document how to build each and every package upstream, including further upstream dependencies (e.g. Hugin depends on enblend; and enblend depends on lcms; hence both should be documented), for both 32 and 64 bit. 2. Distribute the SDK in two forms: one large archive containing everything (almost like the current one). It will become outdated, but here comes the second distribution: archives of individual packages. This way the faster evolving packages can be updated/distributed more often. To achieve this, I suggest to expand on the current structure of the
[hugin-ptx] optimization of calculations in PTmender
Hi everybody, For those using (or wanting to use PTmender). for the sake of maintainability I have used only matrix multiplications right now. I am going to wait until we are sure about their correctness before I expand them. By the way, in the process of hacking the stack, I discovered that, if a parameter is present in the 'o' line, an operation in the stack is created, even if the parameter is zero, which is a penalty on speed. Hugin outputs many parameters, even if zero. Removing them will speed up operations a bit. --dmg -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . --~--~-~--~~~---~--~~ 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: Tilt transformation...
I committed my changes here: http://panotools.svn.sourceforge.net/viewvc/panotools/branches/libpano_gsoc2009_mosaic/ On Wed, Sep 9, 2009 at 11:27 PM, Yuval Levy goo...@levy.ch wrote: dmg wrote: Hello, I am confused. Would one not be able to continue development in the same branch that Dev made the initial changes in? Why is another branch needed? I apologize if I am missing something obvious. Gerry are you talking libpano or hugin? Dev never committed anything to http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2009_mosaic/ :-( 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Updated extended enfuse and enblend documentation
2009/9/10 Harry van der Wolf hvdw...@gmail.com:
Or to put it simple : @ref{Figure:photographic-workflow} refers to a figure
which is an eps file called photographic-workflow.eps. You will find this
photographic-workflow.eps in the same directory (in this pathless case)
as the texi file.
there is only the .fig file there. other programs seem to expect a jpg or a pdf.
where does it say that it is an .eps.
What program is meant to view the .texi file directly in all it's
composed glory ?
I've installed so many now I'm not sure what's going on.
regards
mick
--~--~-~--~~~---~--~~
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: Tilt transformation...
Thanks Dev for your work. BTW, this is now integrated into libpano HEAD. On Thu, Sep 10, 2009 at 11:53 AM, dev g dev.gh...@gmail.com wrote: I committed my changes here: http://panotools.svn.sourceforge.net/viewvc/panotools/branches/libpano_gsoc2009_mosaic/ On Wed, Sep 9, 2009 at 11:27 PM, Yuval Levy goo...@levy.ch wrote: dmg wrote: Hello, I am confused. Would one not be able to continue development in the same branch that Dev made the initial changes in? Why is another branch needed? I apologize if I am missing something obvious. Gerry are you talking libpano or hugin? Dev never committed anything to http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2009_mosaic/ :-( Yuv -- --dmg --- Daniel M. German http://turingmachine.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: libpano
D M German wrote: I have committed the changes to support tilt of the camera in PToptimizer and PTmender. See the ChangeLog for details. the new parameters are: Tx, Ty, Tz, and Ts (for scale). thank you for this! 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: libpano
I have committed the changes to support tilt of the camera in PToptimizer and PTmender. See the ChangeLog for details. the new parameters are: Tx, Ty, Tz, and Ts (for scale). thank you for this! Yuv the accolades should go primarily to Dev Gosh and Google. Dev did the hard work. I just integrated. --dmg --~--~-~--~~~---~--~~ 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 SDK and documentation
Ryan Sleevi wrote: Or we can go the easier route (for end users) that I've been pursuing: An automatable that handles it all for you ;-) makes sense - just make sure that it is documented well enough so that: a) a monkey like me can build the automatable from scratch b) *when* things evolve and change, a slightly more expert hand can fix it when I work on the project, I try to make myself redundant by documenting what I do and trying to pass on the knowledge to what will be our next generation of maintainers long after I'm gone. 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 at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Tilt transformations....
Hi Daniel, in the optimiser tab there is a checkbox in the bottom [] edit script before optimising I often use it to optimise the shear parameters of my scanned images. That works but I'd prefer a solution for both shift boxes where I could choose from a list of other available parameters using drop down lists. dmg wrote: BTW, hugin developers, any chance you can implement using a script to edit the script before optimizing? Another idea about the optimiser tab: the yaw box normally has one value that is in a different tab marked as anchor. I think that special anchor frame should be easily identifiable by either using a bBOLD/b font or some colour. That anchor should also not be selected when clicking the 'select' button (correct naming should be 'select all' btw). If the user checks that frame directly it's his own fault... Carl ps. What's the correct term for longer (floating) texts that are available when the mouse pointer stays on some part of the gui for a longer time? In this case they should show the file name of the frame instead just e.g. '3(-136,240)'. --~--~-~--~~~---~--~~ 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: Tilt transformations....
What's the correct term for longer (floating) texts that are available when the mouse pointer stays on some part of the gui for a longer time? In this case they should show the file name of the frame instead just e.g. '3(-136,240)'. Hey Carl, the term is tooltip. DR --~--~-~--~~~---~--~~ 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: Updated extended enfuse and enblend documentation
Harry van der Wolf wrote:
2009/9/10 Carl von Einem c...@einem.net mailto:c...@einem.net
from the texinfo.pdf on page 225:
(...)
michael crane wrote:
2009/9/9 Yuval Levy goo...@levy.ch mailto:goo...@levy.ch:
Can somebody explain what @ref{Figure:photographic-workflow} is ? in
workflow.texi
Or to put it simple : @ref{Figure:photographic-workflow} refers to a
figure which is an eps file called photographic-workflow.eps. You will
find this photographic-workflow.eps in the same directory (in this
pathless case) as the texi file.
Harry
That was too simple ;-)
I haven't worked out that .eps part I must admit, and texi is really
interesting!
--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation
2009/9/10 michael crane mick.cr...@gmail.com
2009/9/10 Harry van der Wolf hvdw...@gmail.com:
Or to put it simple : @ref{Figure:photographic-workflow} refers to a
figure
which is an eps file called photographic-workflow.eps. You will find
this
photographic-workflow.eps in the same directory (in this pathless
case)
as the texi file.
there is only the .fig file there. other programs seem to expect a jpg or a
pdf.
where does it say that it is an .eps.
Sorry. I didn't pay attention well enough. You are working with the source
of the documentation and not with the generated documentation when you build
enblend.
What program is meant to view the .texi file directly in all it's
composed glory ?
I've installed so many now I'm not sure what's going on.
regards
mick
As far as I know texi is only the text formatting ascii file which you edit
in a ascii editor like vi(m). You must first convert it to texinfo (makeinfo
file.texi) or to pdf (texi2pdf file.texi) or to html (texi2html) or to
whaever format.
I suppose you already read http://en.wikipedia.org/wiki/Texinfo.
At that stage I looked at texi to xml and xml to wiki as there are
converters for that, but none is really sufficient.
Also texi to html to wiki as there are also converters for that but none
really sufficient.
I'm sorry I can't help. I could only give some explanations.
I hope you find something useful.
Harry
--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation
2009/9/10 Carl von Einem c...@einem.net
Harry van der Wolf wrote:
2009/9/10 Carl von Einem c...@einem.net mailto:c...@einem.net
from the texinfo.pdf on page 225:
(...)
michael crane wrote:
2009/9/9 Yuval Levy goo...@levy.ch mailto:goo...@levy.ch:
Can somebody explain what @ref{Figure:photographic-workflow} is ?
in
workflow.texi
Or to put it simple : @ref{Figure:photographic-workflow} refers to a
figure which is an eps file called photographic-workflow.eps. You will
find this photographic-workflow.eps in the same directory (in this
pathless case) as the texi file.
Harry
That was too simple ;-)
I haven't worked out that .eps part I must admit, and texi is really
interesting!
Yes, you are right. I was mistaken. I thought Mick was working on the
genreated documentation, not on the source document data.
Harry
--~--~-~--~~~---~--~~
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: Tilt transformations....
blush... (Thanks!) Daniel Reetz wrote: What's the correct term for longer (floating) texts that are available when the mouse pointer stays on some part of the gui for a longer time? In this case they should show the file name of the frame instead just e.g. '3(-136,240)'. Hey Carl, the term is tooltip. DR --~--~-~--~~~---~--~~ 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: Updated extended enfuse and enblend documentation
2009/9/10 Harry van der Wolf hvdw...@gmail.com: 2009/9/10 Carl von Einem c...@einem.net Yes, you are right. I was mistaken. I thought Mick was working on the genreated documentation, not on the source document data. 'working' is the wrong expression. rag in teeth ? gnawing on bone ? so what is the way to view the document in all it's composed glory ? man shows some of it info shows some of it perldoc shows some of it but I forget the syntax ? mick --~--~-~--~~~---~--~~ 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] Enblend 4.0 messes image
Hi all I tried enblend 4 as described on the wiki, in Linux Ubuntu 9.04 x86_64. With a standard equirectangular panorama, I get the following strange result: http://farm4.static.flickr.com/3530/3907886322_4280aa77f6_b.jpg This is a reduced version of the 1x5000 original. When I create the image at a smaller resolution, the strange errors go away. I've tried with OpenMP disabled at compilation, and with the image cache enabled. And when I use enblend 3.2, even at full resolution, it works and produces this: http://www.flickr.com/photos/sbprzd/3907902566/ The command line used is: enblend --compression=LZW -o out.tif -w -l 15 in*.tif The issue can be seen in the masks, using the option --save-mask: http://farm3.static.flickr.com/2450/3908003514_f269b493b3_o.jpg The mask in the bottom left corner (mask number 7) seems to be wrong. Here are the different component images, before blending. Mask number 7 would go between image 7 and all the previous ones. http://farm4.static.flickr.com/3101/3908003530_cb9bde9e3d_b.jpg Does anyone have a clue how to solve this? I've gone back to enblend 3.2 for the moment... Cheers, Seb --~--~-~--~~~---~--~~ 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 4.0 messes image
On Sep 10, 11:21 pm, Seb Perez-D sbprzd+...@gmail.com wrote: I tried enblend 4 as described on the wiki, in Linux Ubuntu 9.04 x86_64. With a standard equirectangular panorama, I get the following strange result:http://farm4.static.flickr.com/3530/3907886322_4280aa77f6_b.jpg This is a reduced version of the 1x5000 original. This is a known problem http://sourceforge.net/tracker/?func=detailaid=2855277group_id=123407atid=696409 /Chris --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
