https://wiki.panotools.org/api.php?action=feedcontributions&user=Klaus&feedformat=atomPanoTools.org Wiki - User contributions [en]2024-03-29T01:16:00ZUser contributionsMediaWiki 1.35.3https://wiki.panotools.org/index.php?title=User:Klaus/Improving_Hugin&diff=11640User:Klaus/Improving Hugin2009-07-23T15:57:49Z<p>Klaus: reply - no offense taken at all</p>
<hr />
<div>* include antialiasing interpolators<br />
* add a r^4 term to the a*r^3+b*r^2+c*r+d distortion correction (because the r^4 term like b*r^2 has correct symmetry whereas a and c terms are largely unphysical)<br />
: Why that? The formula applies to the radius of the image, which means it is always symmetrical. a and c terms work great to correct for special types of distortion ([[Wavy distortion|wavy one]] f.e.) <small>--[[User:Erik Krause|Erik Krause]] 22:07, 21 July 2009 (UTC)</small><br />
::Yes, it does work to some extend, but it is phenomenology only.<br />
::Mathematically, assuming the lense mapping function to be holomorphic is rather close to reality, without a singularity at r=0. Less stringent, but along the same line is the symmetry argument that flipping the sign, r -> -r, and adding 180 degrees to the angle, ought to give you the same output values. Polar coordinates need special treatment at r=0, but for the sake of reasoning one can go to (x,y) cartesian coordinates. Terms for a and c require sqrt(x^2+y^2), sqrt() has a singularity at 0 but the lense does not, so a<>0 and c<>0 introduce a behaviour the lense does not have.<br />
::A few days ago we were discussing the equivalence of different camera models on the hugin-ptx list. One has to compare them to (a*r^3+b*r^2+c*r+d)*r and one finds only odd powers of r in these. There must be a reason (but such heuristic argument I would not buy standalone).<br />
::And there is a practical issue. Of course we are talking of effects at the pixel level, but I did some tests last weekend and found that the (a,b,c) parameter set for my camera lense actually varies if I choose the placement of my Control Points in different ways. Imagine, you were to follow measurement prescription 1 and find a focal length of 50mm, then you follow measurement prescription 2 and find a focal length of 45mm. Exaggerated and simplified analogy, yes, but that is the situation I could confirm with my lense for the (a,b,c) parameter set.<br />
::In practice, I remember a stitch with one lone CP in a corner, which was misaligned by 3 pixels. Finding the sharpness ok, Finetune working fine, CA not spoiling either I now do put this to the deficiency of the (a,b,c) parametrisation in panotools. -- [[User:Klaus|Klaus]] 14:01, 22 July 2009 (UTC)<br />
::: Sorry, I misunderstood. However, distortion doesn't necessarily need to by rotational symmetric anyway, as shown on [http://www.stoske.de/digicam/Artikel/verzeichnung.html], hence one radial model might be as bad as the other. The panotools model seems one of the most widely used - probably hundreds of thousands of panoramas where stitched using it, and my impression was that Prof. [[Helmut Dersch|Dersch]] choose it deliberately - which doesn't mean of course that it can't be enhanced... <small>--[[User:Erik Krause|Erik Krause]] 19:01, 22 July 2009 (UTC)</small><br />
:::: Recently on hugin-ptx in the thread "What is optimized FOV really?" we discussed lense models and how to compare Bouguet camera model with Dersch/panotools model. Bouguet does introduce non-rotationally-symmetric terms indeed. Choosing three polynomial coefficients is not too stupid, it is only with deeper mathematical insight that one understands why the even coefficients tend to become zero when one uses "enough" polynomial coefficients. And I do remember that at the time Dersch got hassled not because his model was bad quality, but because others had their inferior software protected by dubious patents. -- [[User:Klaus|Klaus]] 15:57, 23 July 2009 (UTC)<br />
* allow simultaneous use of both flatfield polynomial and dustmap file<br />
* <s>implement orthographic projection (benefits from antialiasing interpolators)</s> <small>implemented in Hugin 0.8.0 [[User:Klaus|Klaus]] 16:51, 21 July 2009 (UTC)</small><br />
--[[User:Klaus|Klaus]] 14:30, 29 May 2008 (CEST)</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Improving_Hugin&diff=11636User:Klaus/Improving Hugin2009-07-22T14:01:09Z<p>Klaus: medium short answer</p>
<hr />
<div>* include antialiasing interpolators<br />
* add a r^4 term to the a*r^3+b*r^2+c*r+d distortion correction (because the r^4 term like b*r^2 has correct symmetry whereas a and c terms are largely unphysical)<br />
: Why that? The formula applies to the radius of the image, which means it is always symmetrical. a and c terms work great to correct for special types of distortion ([[Wavy distortion|wavy one]] f.e.) <small>--[[User:Erik Krause|Erik Krause]] 22:07, 21 July 2009 (UTC)</small><br />
::Yes, it does work to some extend, but it is phenomenology only.<br />
::Mathematically, assuming the lense mapping function to be holomorphic is rather close to reality, without a singularity at r=0. Less stringent, but along the same line is the symmetry argument that flipping the sign, r -> -r, and adding 180 degrees to the angle, ought to give you the same output values. Polar coordinates need special treatment at r=0, but for the sake of reasoning one can go to (x,y) cartesian coordinates. Terms for a and c require sqrt(x^2+y^2), sqrt() has a singularity at 0 but the lense does not, so a<>0 and c<>0 introduce a behaviour the lense does not have.<br />
::A few days ago we were discussing the equivalence of different camera models on the hugin-ptx list. One has to compare them to (a*r^3+b*r^2+c*r+d)*r and one finds only odd powers of r in these. There must be a reason (but such heuristic argument I would not buy standalone).<br />
::And there is a practical issue. Of course we are talking of effects at the pixel level, but I did some tests last weekend and found that the (a,b,c) parameter set for my camera lense actually varies if I choose the placement of my Control Points in different ways. Imagine, you were to follow measurement prescription 1 and find a focal length of 50mm, then you follow measurement prescription 2 and find a focal length of 45mm. Exaggerated and simplified analogy, yes, but that is the situation I could confirm with my lense for the (a,b,c) parameter set.<br />
::In practice, I remember a stitch with one lone CP in a corner, which was misaligned by 3 pixels. Finding the sharpness ok, Finetune working fine, CA not spoiling either I now do put this to the deficiency of the (a,b,c) parametrisation in panotools. -- [[User:Klaus|Klaus]] 14:01, 22 July 2009 (UTC)<br />
* allow simultaneous use of both flatfield polynomial and dustmap file<br />
* <s>implement orthographic projection (benefits from antialiasing interpolators)</s> <small>implemented in Hugin 0.8.0 [[User:Klaus|Klaus]] 16:51, 21 July 2009 (UTC)</small><br />
--[[User:Klaus|Klaus]] 14:30, 29 May 2008 (CEST)</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Improving_Hugin&diff=11627User:Klaus/Improving Hugin2009-07-21T16:51:17Z<p>Klaus: globe projection is there now</p>
<hr />
<div>* include antialiasing interpolators<br />
* add a r^4 term to the a*r^3+b*r^2+c*r+d distortion correction (because the r^4 term like b*r^2 has correct symmetry whereas a and c terms are largely unphysical)<br />
* allow simultaneous use of both flatfield polynomial and dustmap file<br />
* <s>implement orthographic projection (benefits from antialiasing interpolators)</s> <small>implemented in Hugin 0.8.0 [[User:Klaus|Klaus]] 16:51, 21 July 2009 (UTC)</small><br />
--[[User:Klaus|Klaus]] 14:30, 29 May 2008 (CEST)</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus&diff=11626User:Klaus2009-07-21T16:49:11Z<p>Klaus: add two more subpages</p>
<hr />
<div>Hello,<br />
<br />
Since March 2005, when buying a Canon Powershot A95, I did start to actually explore how to combine several photos into a panorama image. First with the program that came with the camera, but very soon I found that lacking in quality, and after a few tries I am now holding onto hugin and enblend.<br />
<br />
I do have earlier photos, for example a photo series in the Chartreuse mountain range of the French Alps that should nicely fit together into a 360 degrees panorama. With photos taken in 1988, I actually had done a hardware cut and paste at the time, but I still have to scan the slides to make a real seamless image on the computer. I also have many more digital photos as raw material which I have not yet turned into panoramas.<br />
<br />
Following the development of the open and free panoramic software, I hope my comments do help of improving these program bundles and maybe I see features implemented I desire, despite myself not engaging into the coding effort - maybe I should brush up my skills there. But (time permitting as always) I am happy to test-run the programs, and also help with postings and maybe tutorial writing.<br />
<br />
Klaus<br />
<br />
----<br />
<br />
making panoramic images is about:<br />
* '''[[Photography Guidelines]]''' - taking photos the right way<br />
* '''[[How stitching works|Stitching]]''' - computing the panoramic image: [[Remapping]], Exposure Adjustment, and Blending<br />
* '''Viewing and Publishing''' - exploiting the panoramic image potential<br />
<br />
some more stuff:<br />
* [[User:Klaus/Stitching 2008 State of the Art]]<br />
* [[User:Klaus/Improving Hugin]] - aide-memoire<br />
* [[Enblend test cases]]<br />
* [[User:Klaus/Hugin 0.8.0 comment]]<br />
* [[User:Klaus/Hugin 0.8.0 wishlist]]</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Hugin_0.8.0_wishlist&diff=11625User:Klaus/Hugin 0.8.0 wishlist2009-07-21T16:43:48Z<p>Klaus: start that page</p>
<hr />
<div>== Hugin 0.8.0 - Wish List and Constructive Criticism ==<br />
<br />
# Inner workings<br />
## Image distortion parametrisation<br>Camera lenses do have a symmetry axis at r=0 but it is not a mathematical singularity, hence the distortion correction polynomial should use only odd powers of r.<br />
## Remapping splines<br>There is a choice of interpolating splines available for image remapping, but in the case of significant image downscaling they are prone to aliasing. A set of anti-alias-filtering splines would be welcome.<br />
## Input image correction<br>Sometimes camera response is not uniform, and in case of minor defects like dirt on optical elements a flatfield correction can correct most of it, and with a built-it flatfield the correction has to be set up only once.<br />
# Output files<br />
## EXIF with output lense info<br>Currently the EXIF info does not contain the output projection specs. In case the panoramic image were to be viewed with a helper application, this info would allow a proper display. Currently rectilinear cannot be distinguished from cylindrical or equirectangular.<br />
# GUI<br />
## F3 floating window a big nuisance<br>Obscurs windows below, grabs the focus when Finetune "fails" on Control Points clicking. It is really a PITA (pinch in the armpit). F3 should toggle the window.<br />
## Hugin always opens on Assistant tab<br>For expert users would be more convenient to open on Images.<br />
## Drag-around of files in Images tab<br />
## Edit values like in spread sheet?<br />
## Make aligning sequence steps more suggestive<br>Usually one need several iterations for image aligning, starting with few parameters yielding a robust result, and then adding more and more parameters which makes optimisation more prone to find false minima in case one is not already close to the proper minimum in optimisation space.<br />
## Show Undo "topic" and Redo "topic"<br />
## Finetune with key F, similar Finetune rotation search with R?<br />
# Workflow<br />
## Start Hugin in dropping JPEGs onto Desktop icon?<br>Does not work, at least not in OSX. Select the stitch files already in the OS window on the desktop. Defined as preference, should open Hugin on the Assistant or the Images tab.<br />
## Set optimum pixel size earlier than on last tab<br>Of course nothing prevents one to visit the tabs not from left to right, but from the logics the determination of optimum pixel numbers should come earlier than the last tab as it is useful to have it right already for alignment.<br />
# Display<br />
## Bring back the doughnuts in the CP window - at least optionally.<br />
## Placing CPs in same window can be improved<br>Placing horizontal and vertical control points is not yet fully intuitive as it requires clicking into two different windows. Also thoughts should be spent on Finetune here.<br />
# Additions<br />
## Implement more complex cropping masks<br>Polygon would do, effect could be visualised in the fast preview.<br />
## Intensity histograms?<br>Currently produce output file, and then discover it is too bright or too dark in looking at "curves" in gimp.<br />
# Enblend<br />
## Seam finding<br>There are some cases when the optimised seam finder does not work.<br />
## Seam optimisation<br>Seam optimisation is already pretty good, but there is still potential to inprove. Further algorithms should be investigated.<br />
## Seam visualisation<br>Currently only mask and visualisation images from the last image pair in a blending set to survive. Optionally all these images should be written. On thing would be to find and correct bad masks and then get a better stitch in loading the masks in a second run of Hugin.<br />
# Small glitches<br />
## Drop-down menus in Control Points OSX dodgy<br />
## CRTL-Z sometimes does not work<br>Necessity to go to Hugin main menu bar where it then works<br />
## Fast preview does not update when changing to it<br>It jumps into life with a little slider action.<br />
<br />
2009-07-20 & 2009-07-21 Klaus Föhl</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Hugin_0.8.0_comment&diff=11624User:Klaus/Hugin 0.8.0 comment2009-07-21T16:20:18Z<p>Klaus: typo</p>
<hr />
<div>== Hugin 0.8.0 is out ==<br />
<br />
The panoramic stitching software Hugin 0.8.0 version has been released,<br />
and once again creating panoramic images has become smoother. Being <br />
a faithful user since years, convinced by the virtues and merits<br />
of this programme suite - and one should know about the Panotools<br />
and Enblend engines under the hood as well - I am happy to see the<br />
improvements from the last months put together into the current release.<br />
<br />
Sometime in 2005 my new camera came with a piece of stitching software,<br />
and although I shall not mention any names, that piece was crap. Really.<br />
So I was looking around, and rather sooner than later came across what<br />
was then Hugin 0.5beta. It was already doing a reasonable job then.<br />
One can learn quite a lot how software and commerce do work, quite often<br />
not to the benefit of the user, but instructive as this may be,<br />
let's leave these aspects alone for now and look at much more<br />
pleasant things, Hugin's achievements that is.<br />
<br />
Remember the days when you could still see the seam lines in a<br />
panoramic image? Even Hugin's output did show such seams,<br />
although not as badly as others, and at least the alignment was about right.<br />
But already then there was this extra piece of software called Enblend<br />
which could do away with seam lines most of the time. And with the<br />
quailty bar rising, I discovered that panoramic images did benefit<br />
if one corrected the vignetting before feeding images into Hugin,<br />
although these external programmes could cause banding in the image<br />
in exchange for removing the vignetting.<br />
<br />
Then came the introduction of vignetting correction within Hugin.<br />
First it was a simple add-on window, and one had to provide either<br />
the parameters or a flatfield by oneself. But no longer had one to <br />
pre-process the images, so on top of the original images the pto<br />
file was all that was needed to revisit a stitch if one wished to<br />
do so at a later time. And the next step was that Hugin was<br />
empowered to compute the vignetting correction out of the image<br />
material itself. It already did so for the lense parameters,<br />
and this self-contained parameter determination is pretty damn useful.<br />
<br />
Enblend was there as well. It has picked up processing speed since then,<br />
beyond the CPU speeds getting faster. And it has become smarter.<br />
There always is a seam line between images, although with Enblend<br />
you usually do not see it. In the few cases where one did,<br />
one could resort to editing the alpha channels of the intermediate<br />
image files. Still manual intervention. But then Enblend got that<br />
extra bit smarter with the capability not to determine the seam<br />
from geometry only, but to look at the image content to find a<br />
good placement, a seam line across areas where the images to be stitched<br />
differ as little as possible.<br />
<br />
A fair number of technical improvements has happened as well.<br />
Remember the times when the output was TIFF, large TIFF files<br />
into and out of Enblend? Some changes had to wait for their time,<br />
for instance the LZW algorithm lost its shackles when finally<br />
the patent expired, and one could think about using compressed TIFFs<br />
without perils. There are now compressed cropped TIFFs saving<br />
on memory and hard drive space, and JPEG is now possible as well<br />
hence one saves evoking a converter program after the Hugin run.<br />
<br />
Improvements on the GUI side? Yes indeed! Most recently the introduction<br />
of a fast interactive preview. And fast really means in real time.<br />
Even better, this new preview has some added features, and personally<br />
I do like the cropping tool which allows me to select the rectangular<br />
frame I want to have for the output JPEG image. It means Hugin is a<br />
one stop shop for panoramic image creation in most cases.<br />
<br />
Of course there are still some small quirks. I am confident the thriving<br />
Hugin community will iron them out in due course. And surely there are<br />
features I have not mentioned. Enfuse opening the door into HDR,<br />
perspective correction of single photos, proper interpolating algorithms,<br />
a wide choice of output perspectives to choose from, and more.<br />
And certainly there are several aspects which deserve<br />
my constructive criticism, and I plan to write these down in due course.<br />
But I have left the most important thing for last, and that is:<br />
<br />
Hugin is free. It is not a piece that sellers try to strip of features<br />
and then endeavour to sell to you at a premium. Being free software means<br />
that most probably Hugin is here to stay. You may even compile and modify<br />
your own copy if you deam it necessary. And the aspect I want to look<br />
at last: I have Hugin 0.8.0 (well, the release candidate) running on<br />
both Windows XP and Mac OSX Tiger, with Hugin looking pretty much the same<br />
on these different platforms, and I am looking forward to seeing <br />
the 0.7.0 to 0.8.0 upgrade on my debian Linux box.<br />
But whatever the platform, Hugin is there.<br />
<br />
2009-07-20 Klaus Föhl</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Hugin_0.8.0_comment&diff=11623User:Klaus/Hugin 0.8.0 comment2009-07-21T16:17:50Z<p>Klaus: /* Hugin 0.8.0 is out */ a few corrections</p>
<hr />
<div>== Hugin 0.8.0 is out ==<br />
<br />
The panoramic stitching software Hugin 0.8.0 version has been released,<br />
and once again creating panoramic images has become smoother. Being <br />
a faithful user since years, convinced by the virtues and merits<br />
of this programme suite - and one should know about the Panotools<br />
and Enblend engines under the hood as well - I am happy to see the<br />
improvements from the last months put together into the current release.<br />
<br />
Sometime in 2005 my new camera came with a piece of stitching software,<br />
and although I shall not mention any names, that piece was crap. Really.<br />
So I was looking around, and rather sooner than later came across what<br />
was then Hugin 0.5beta. It was already doing a reasonable job then.<br />
One can learn quite a lot how software and commerce do work, quite often<br />
not to the benefit of the user, but instructive as this may be,<br />
let's leave these aspects alone for now and look at much more<br />
pleasant things, Hugin's achievements that is.<br />
<br />
Remember the days when you could still see the seam lines in a<br />
panoramic image? Even Hugin's output did show such seams,<br />
although not as badly as others, and at least the alignment was about right.<br />
But already then there was this extra piece of software called Enblend<br />
which could do away with seam lines most of the time. And with the<br />
quailty bar rising, I discovered that panoramic images did benefit<br />
if one corrected the vignetting before feeding images into Hugin,<br />
although these external programmes could cause banding in the image<br />
in exchange for removing the vignetting.<br />
<br />
Then came the introduction of vignetting correction within Hugin.<br />
First it was a simple add-on window, and one had to provide either<br />
the parameters or a flatfield by oneself. But no longer had one to <br />
pre-process the images, so on top of the original images the pto<br />
file was all that was needed to revisit a stitch if one wished to<br />
do so at a later time. And the next step was that Hugin was<br />
empowered to compute the vignetting correction out of the image<br />
material itself. It already did so for the lense parameters,<br />
and this self-contained parameter determination is pretty damn useful.<br />
<br />
Enblend was there as well. It has picked up processing speed since then,<br />
beyond the CPU speeds getting faster. And it has become smarter.<br />
There always is a seam line between images, although with Enblend<br />
you usually do not see it. In the few cases where one did,<br />
one could resort to editing the alpha channels of the intermediate<br />
image files. Still manual intervention. But then Enblend got that<br />
extra bit smarter with the capability not to determine the seam<br />
from geometry only, but to look at the image content to find a<br />
good placement, a seam line across areas where the images to be stitched<br />
differ as little as possible.<br />
<br />
A fair number of technical improvements have happened as well.<br />
Remember the times when the output was TIFF, large TIFF files<br />
into and out of Enblend? Some changes had to wait for their time,<br />
for instance the LZW algorithm lost its shackles when finally<br />
the patent expired, and one could think about using compressed TIFFs<br />
without perils. There are now compressed cropped TIFFs saving<br />
on memory and hard drive space, and JPEG is now possible as well<br />
hence one saves evoking a converter program after the Hugin run.<br />
<br />
Improvements on the GUI side? Yes indeed! Most recently the introduction<br />
of a fast interactive preview. And fast really means in real time.<br />
Even better, this new preview has some added features, and personally<br />
I do like the cropping tool which allows me to select the rectangular<br />
frame I want to have for the output JPEG image. It means Hugin is a<br />
one stop shop for panoramic image creation in most cases.<br />
<br />
Of course there are still some small quirks. I am confident the thriving<br />
Hugin community will iron them out in due course. And surely there are<br />
features I have not mentioned. Enfuse opening the door into HDR,<br />
perspective correction of single photos, proper interpolating algorithms,<br />
a wide choice of output perspectives to choose from, and more.<br />
And certainly there are several aspects which deserve<br />
my constructive criticism, and I plan to write these down in due course.<br />
But I have left the most important thing for last, and that is:<br />
<br />
Hugin is free. It is not a piece that sellers try to strip of features<br />
and then endeavour to sell to you at a premium. Being free software means<br />
that most probably Hugin is here to stay. You may even compile and modify<br />
your own copy if you deam it necessary. And the aspect I want to look<br />
at last: I have Hugin 0.8.0 (well, the release candidate) running on<br />
both Windows XP and Mac OSX Tiger, with Hugin looking pretty much the same<br />
on these different platforms, and I am looking forward to seeing <br />
the 0.7.0 to 0.8.0 upgrade on my debian Linux box.<br />
But whatever the platform, Hugin is there.<br />
<br />
2009-07-20 Klaus Föhl</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Hugin_0.8.0_comment&diff=11620User:Klaus/Hugin 0.8.0 comment2009-07-21T15:35:14Z<p>Klaus: commenting on Hugin as useful software</p>
<hr />
<div>== Hugin 0.8.0 is out ==<br />
<br />
The panoramic stitching software Hugin 0.8.0 version has been released,<br />
and once again creating panoramic images has become smoother. Being <br />
a faithful user since years, convinced by the virtues and merits<br />
of this programme suite, and one should know about the panotools<br />
and enblend engines under the hood as well, I am happy to see the<br />
improvements from the last months put together into the current release.<br />
<br />
Sometime in 2005 my new camera came with a piece of stitching software,<br />
and although I shall not mention the name, that piece was crap.<br />
So I was looking around, and rather sooner than later came across what<br />
was then hugin 0.5beta. It was already doing a reasonable job then.<br />
One can learn quite a lot how software and commerce do work, quite often<br />
not to the benefit of the user, but instructive as it is, let's leave<br />
this aspect alone for now and look at hugin's achievements.<br />
<br />
Remember the days when you could still see the seam lines in a<br />
panoramic image? Even hugin did produce such images,<br />
although not as badly as others, and at least the alignment was about right.<br />
But already then there was this extra piece of software called enblend<br />
which could do away with seam lines most of the time. And with the<br />
quailty bar rising, I discovered that panoramic images did benefit<br />
if one corrected the vignetting before feeding images into hugin,<br />
although these external programmes could cause banding in the image<br />
in exchange for removing the vignetting.<br />
<br />
Then came the introduction of vignetting correction within hugin.<br />
First it was a simple add-on window, and one had to provide either<br />
parameters or a flatfield by oneself. But no longer had on to <br />
pre-process the images, but on top of the original images the pto<br />
file was all that was needed to revisit a stitch I one wished to<br />
do so at a later stage. And the next step was that hugin was<br />
empowered to compute the vignetting correction out of the image<br />
material itself. It already did so for the lense parameters,<br />
and this self-contained parameter determination is pretty damn useful.<br />
<br />
Enblend was there as well. It has picked up speed since then,<br />
beyond the CPU speeds getting faster. And it has become smarter.<br />
There always is a seam line between images, although with enblend<br />
you usually do not see it. In the minority cases where one did,<br />
one could resort to editing the alpha channels of the intermediate<br />
image files. Still manual intervention. But then enblend got that<br />
extra bit smarter with the capability, not to determine the seam<br />
from geometry only, but to look at the image content to find a<br />
good placement, a line along areas where the images to be stitched<br />
differ as little as possible.<br />
<br />
A few technical improvements have happened as well. Remember the times<br />
when the output was TIFF, large TIFF files into and out of enblend?<br />
Some changes had to wait for their time, for instance the LZW algorithm<br />
lost its shackles when finally the patent expired, and one could think<br />
about compressed TIFFs. There are now compressed cropped TIFFs saving<br />
on memory and hard drive space, and JPEG is now possible as well<br />
hence one saves evoking a converter program after the hugin run.<br />
<br />
Improvements on the GUI side? Yes indeed! Most recently the introduction<br />
of a fast interactive preview. And fast really means in real time.<br />
On top of it this new preview has some added features, and personally<br />
I do like the cropping tool which allows me to select the rectangular<br />
frame I want to have in the output JPEG image. It means hugin is a<br />
one stop shop for panoramic images creation in most cases.<br />
<br />
Of course there are still some small quirks. I am confident the triving<br />
hugin community will iron them out in due course. And surely there are<br />
features I have not mentioned. Enfusing opening the door into HDR,<br />
perspective correction of single photos, proper interpolating algorithms,<br />
a wide choice of output perspectives to choose from. And certainly there<br />
are several aspects which deserve my constructive criticism, and I plan to <br />
write these down in due course. But I have forgotten the most important thing.<br />
<br />
Hugin is free. It is not a piece that sellers try to strip of features<br />
and then endeavour to sell at a premium. Being free software means that<br />
most probably hugin is here to stay. You may even compile and modify<br />
your own copy if you find it necessary. And the aspect I want to look<br />
at last: I have hugin 0.8.0 (well, the release candidate) running both<br />
on Windows XP and Mac OSX Tiger, with hugin looking pretty much the same<br />
an these different platforms, and I am looking forward to seeing it<br />
installed on my debian Linux box. Whatever the platform, hugin is there.<br />
<br />
2009-07-20 Klaus Föhl</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus&diff=10869User:Klaus2008-10-10T13:53:28Z<p>Klaus: reference test cases</p>
<hr />
<div>Hello,<br />
<br />
Since March 2005, when buying a Canon Powershot A95, I did start to actually explore how to combine several photos into a panorama image. First with the program that came with the camera, but very soon I found that lacking in quality, and after a few tries I am now holding onto hugin and enblend.<br />
<br />
I do have earlier photos, for example a photo series in the Chartreuse mountain range of the French Alps that should nicely fit together into a 360 degrees panorama. With photos taken in 1988, I actually had done a hardware cut and paste at the time, but I still have to scan the slides to make a real seamless image on the computer. I also have many more digital photos as raw material which I have not yet turned into panoramas.<br />
<br />
Following the development of the open and free panoramic software, I hope my comments do help of improving these program bundles and maybe I see features implemented I desire, despite myself not engaging into the coding effort - maybe I should brush up my skills there. But (time permitting as always) I am happy to test-run the programs, and also help with postings and maybe tutorial writing.<br />
<br />
Klaus<br />
<br />
----<br />
<br />
making panoramic images is about:<br />
* '''[[Photography Guidelines]]''' - taking photos the right way<br />
* '''[[How stitching works|Stitching]]''' - computing the panoramic image: [[Remapping]], Exposure Adjustment, and Blending<br />
* '''Viewing and Publishing''' - exploiting the panoramic image potential<br />
<br />
some more stuff:<br />
* [[User:Klaus/Stitching 2008 State of the Art]]<br />
* [[User:Klaus/Improving Hugin]] - aide-memoire<br />
* [[Enblend test cases]]</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus&diff=10868User:Klaus2008-10-10T13:37:52Z<p>Klaus: write about top level structure</p>
<hr />
<div>Hello,<br />
<br />
Since March 2005, when buying a Canon Powershot A95, I did start to actually explore how to combine several photos into a panorama image. First with the program that came with the camera, but very soon I found that lacking in quality, and after a few tries I am now holding onto hugin and enblend.<br />
<br />
I do have earlier photos, for example a photo series in the Chartreuse mountain range of the French Alps that should nicely fit together into a 360 degrees panorama. With photos taken in 1988, I actually had done a hardware cut and paste at the time, but I still have to scan the slides to make a real seamless image on the computer. I also have many more digital photos as raw material which I have not yet turned into panoramas.<br />
<br />
Following the development of the open and free panoramic software, I hope my comments do help of improving these program bundles and maybe I see features implemented I desire, despite myself not engaging into the coding effort - maybe I should brush up my skills there. But (time permitting as always) I am happy to test-run the programs, and also help with postings and maybe tutorial writing.<br />
<br />
Klaus<br />
<br />
----<br />
<br />
making panoramic images is about:<br />
* '''[[Photography Guidelines]]''' - taking photos the right way<br />
* '''[[How stitching works|Stitching]]''' - computing the panoramic image: [[Remapping]], Exposure Adjustment, and Blending<br />
* '''Viewing and Publishing''' - exploiting the panoramic image potential<br />
<br />
some more stuff:<br />
* [[User:Klaus/Stitching 2008 State of the Art]]<br />
* [[User:Klaus/Improving Hugin]] - aide-memoire</div>Klaushttps://wiki.panotools.org/index.php?title=File:Img0823xstitch7.jpg&diff=10867File:Img0823xstitch7.jpg2008-10-10T13:13:35Z<p>Klaus: add gallery with ingredient images</p>
<hr />
<div>Stitching summary image with two input images and one stitched output image.<br />
<br />
<gallery><br />
Image:Img08232.jpg|input image 1<br />
Image:Img08231.jpg|input image 2<br />
Image:Img0823xstitch5.jpg|uncropped result<br />
Image:Img0823xstitch6crop.jpg|output image<br />
</gallery><br />
<br />
Tha gallery shows the ingredient images used in the composition.</div>Klaushttps://wiki.panotools.org/index.php?title=How_stitching_works&diff=10866How stitching works2008-10-10T13:08:20Z<p>Klaus: insert symbol image at the top</p>
<hr />
<div>[[Image:Img0823xstitch7.jpg|thumb|400px|right|Stitching two images]]<br />
<br />
== Introduction ==<br />
<br />
[[Stitching]] is about making one large image from several smaller photos.<br />
The ambition is to have the fact of individual ingredient photos no longer show through in the resulting image.<br />
This page shows what stitching software actually does.<br />
<br />
<!--<br />
<gallery><br />
Image:Img08232.jpg<br />
Image:Img08231.jpg<br />
Image:Img0823xstitch5.jpg<br />
Image:Img0823xstitch6crop.jpg<br />
</gallery><br />
--><br />
If you want to know how to achieve this, or what<br />
[[software]] to use, please read a [[Tutorials|tutorial]] instead.<br />
What can be done and what quality can be achieved,<br />
this shall be demonstrated step by step starting with the two photos below.<br />
<br />
[[Image:Img08232.jpg|300px]] [[Image:Img08231.jpg|300px]]<br />
<br />
At the time of photography, some [[Photography Guidelines|guidelines]] have been followed that make the photos good stitching material.<br />
<br />
----<br />
<br />
For comparison to stitching proper, the two photos have simply been overlayed in a standard<br />
image editing and retouching software. <br />
<br />
[[Image:Img0823xoverlay1.jpg|300px]] [[Image:Img0823xoverlay2.jpg|300px]]<br />
<br />
Please notice in particular the misalignment of geometrical features in the left image,<br />
and the roof misorientation in the right one.<br />
<br />
----<br />
<br />
Have a look at the following aspects to see where proper stitching software can do better.<br />
Such software usually gives a choice of either performing these steps fully automatically,<br />
or provide assistance for optimisations without requiring a try-and-error workflow.<br />
<br />
===[[Remapping]]===<br />
<br />
[[Image:Img08232remap.jpg|300px]] [[Image:Img08231remap.jpg|300px]]<br />
<br />
To project the images onto the same virtual screen, they need<br />
to be remapped, as shown above. Correcting falling lines as in this example<br />
is by choosing an appropriate orientation for the virtual screen.<br />
<br />
[[Image:Img0823xstitch3.jpg|500px]]<br />
<br />
The relative camera orientation, and the lense parameters<br />
are determined from the images overlap area.<br />
Handheld photos are fine.<br />
If the photos have been taken from the same point,<br />
expect alignment accuracy of better than a pixel.<br />
<br />
===Exposure===<br />
<br />
[[Image:Img0823xstitch4.jpg|500px]]<br />
<br />
Input images need not have the same exposure, or white balance.<br />
Together with vignetting<br />
(images are darker in the corners than in the middle)<br />
the required corrections<br />
can be derived from images with a suitably large overlap area.<br />
<br />
===Blending===<br />
<br />
Obviously, there needs to be some kind of seam between the images,<br />
but one can do better than a hard seam line (used above)<br />
or a feathered transition that affects the image character.<br />
<br />
[[Image:Img0823xstitch5.jpg|500px]]<br />
<br />
State of the art is a seam mechanism that behaves<br />
like a line for small details but averages for large scale features.<br />
<br />
[[Image:Img0823xstitch6.jpg|500px]]<br />
<br />
In addition, the seam line should be placed intelligently<br />
to avoid cutting through objects (like cloud, car or bicycle)<br />
that have moved in the time between taking the images.<br />
<br />
==Overall Result==<br />
<br />
[[Image:Img0823xstitch6crop.jpg|600px]]<br />
<br />
This is the overall result, cropped to rectangular shape,<br />
for a state-of-the-art stitching of two photos.<br />
<br />
[[Category:How it works]]</div>Klaushttps://wiki.panotools.org/index.php?title=File:Img0823xstitch7.jpg&diff=10865File:Img0823xstitch7.jpg2008-10-10T13:02:19Z<p>Klaus: summary image with two input and one stitched output image.</p>
<hr />
<div>summary image with two input and one stitched output image.</div>Klaushttps://wiki.panotools.org/index.php?title=How_stitching_works&diff=10864How stitching works2008-10-10T12:21:16Z<p>Klaus: /* Introduction */ save temp edit</p>
<hr />
<div>== Introduction ==<br />
<br />
[[Stitching]] is about making one large image from several smaller photos.<br />
The ambition is to have the fact of individual ingredient photos no longer show through in the resulting image.<br />
This page shows what stitching software actually does.<br />
<br />
<gallery><br />
Image:Img08232.jpg<br />
Image:Img08231.jpg<br />
Image:Img0823xstitch5.jpg<br />
Image:Img0823xstitch6.jpg<br />
</gallery><br />
<br />
If you want to know how to achieve this, or what<br />
[[software]] to use, please read a [[Tutorials|tutorial]] instead.<br />
What can be done and what quality can be achieved,<br />
this shall be demonstrated step by step starting with the two photos below.<br />
<br />
[[Image:Img08232.jpg|300px]] [[Image:Img08231.jpg|300px]]<br />
<br />
At the time of photography, some [[Photography Guidelines|guidelines]] have been followed that make the photos good stitching material.<br />
<br />
----<br />
<br />
For comparison to stitching proper, the two photos have simply been overlayed in a standard<br />
image editing and retouching software. <br />
<br />
[[Image:Img0823xoverlay1.jpg|300px]] [[Image:Img0823xoverlay2.jpg|300px]]<br />
<br />
Please notice in particular the misalignment of geometrical features in the left image,<br />
and the roof misorientation in the right one.<br />
<br />
----<br />
<br />
Have a look at the following aspects to see where proper stitching software can do better.<br />
Such software usually gives a choice of either performing these steps fully automatically,<br />
or provide assistance for optimisations without requiring a try-and-error workflow.<br />
<br />
===[[Remapping]]===<br />
<br />
[[Image:Img08232remap.jpg|300px]] [[Image:Img08231remap.jpg|300px]]<br />
<br />
To project the images onto the same virtual screen, they need<br />
to be remapped, as shown above. Correcting falling lines as in this example<br />
is by choosing an appropriate orientation for the virtual screen.<br />
<br />
[[Image:Img0823xstitch3.jpg|500px]]<br />
<br />
The relative camera orientation, and the lense parameters<br />
are determined from the images overlap area.<br />
Handheld photos are fine.<br />
If the photos have been taken from the same point,<br />
expect alignment accuracy of better than a pixel.<br />
<br />
===Exposure===<br />
<br />
[[Image:Img0823xstitch4.jpg|500px]]<br />
<br />
Input images need not have the same exposure, or white balance.<br />
Together with vignetting<br />
(images are darker in the corners than in the middle)<br />
the required corrections<br />
can be derived from images with a suitably large overlap area.<br />
<br />
===Blending===<br />
<br />
Obviously, there needs to be some kind of seam between the images,<br />
but one can do better than a hard seam line (used above)<br />
or a feathered transition that affects the image character.<br />
<br />
[[Image:Img0823xstitch5.jpg|500px]]<br />
<br />
State of the art is a seam mechanism that behaves<br />
like a line for small details but averages for large scale features.<br />
<br />
[[Image:Img0823xstitch6.jpg|500px]]<br />
<br />
In addition, the seam line should be placed intelligently<br />
to avoid cutting through objects (like cloud, car or bicycle)<br />
that have moved in the time between taking the images.<br />
<br />
==Overall Result==<br />
<br />
[[Image:Img0823xstitch6crop.jpg|600px]]<br />
<br />
This is the overall result, cropped to rectangular shape,<br />
for a state-of-the-art stitching of two photos.<br />
<br />
[[Category:How it works]]</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus&diff=10512User:Klaus2008-05-29T14:14:25Z<p>Klaus: link page with hugin0.8 suggestions</p>
<hr />
<div>Hello,<br />
<br />
Since March 2005, when buying a Canon Powershot A95, I did start to actually explore how to combine several photos into a panorama image. First with the program that came with the camera, but very soon I found that lacking in quality, and after a few tries I am now holding onto hugin and enblend.<br />
<br />
I do have earlier photos, for example a photo series in the Chartreuse mountain range of the French Alps that should nicely fit together into a 360 degrees panorama. With photos taken in 1988, I actually had done a hardware cut and paste at the time, but I still have to scan the slides to make a real seamless image on the computer. I also have many more digital photos as raw material which I have not yet turned into panoramas.<br />
<br />
Following the development of the open and free panoramic software, I hope my comments do help of improving these program bundles and maybe I see features implemented I desire, despite myself not engaging into the coding effort - maybe I should brush up my skills there. But (time permitting as always) I am happy to test-run the programs, and also help with postings and maybe tutorial writing.<br />
<br />
Klaus<br />
<br />
some stuff:<br />
* [[User:Klaus/Stitching 2008 State of the Art]]<br />
* [[User:Klaus/Improving Hugin]] - aide-memoire</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus/Improving_Hugin&diff=10511User:Klaus/Improving Hugin2008-05-29T12:30:45Z<p>Klaus: writing a wish list</p>
<hr />
<div>* include antialiasing interpolators<br />
* add a r^4 term to the a*r^3+b*r^2+c*r+d distortion correction (because the r^4 term like b*r^2 has correct symmetry whereas a and c terms are largely unphysical)<br />
* allow simultaneous use of both flatfield polynomial and dustmap file<br />
* implement orthographic projection (benefits from antialiasing interpolators)<br />
--[[User:Klaus|Klaus]] 14:30, 29 May 2008 (CEST)</div>Klaushttps://wiki.panotools.org/index.php?title=Historical:Idea_Brushing_Polygon&diff=10443Historical:Idea Brushing Polygon2008-05-20T18:20:17Z<p>Klaus: write-up with images</p>
<hr />
<div>Image masks for blending images are currently bitmap-based, but this information can be generated from polygon masks. Usually polygons are manipulated in grabbing the points or the faces. In hugin-ptx, relating to the Google [[SoC 2008 Masking in GUI]] project, the idea of brush strokes for easy mask generation has been put forward. <br />
<br />
The following presents an idea on how brush stroke actions with the mouse can act on polygonal outlines. It is a rough description, not yet covering all special cases.<br />
<br />
The main idea is that the start point and the initial direction<br />
of the brush stroke have an effect on how the polygon is modified.<br />
The click, hold and drag action starts away from any polygonal trace.<br />
<br />
A rectangle framing the image shall be the start polygon.<br />
<br />
==Starting the brush stroke==<br />
<br />
Two different polygon examples are shown, with the brush stroke starting at the bottom in an upwards direction.<br><br />
<small>The dot at stroke start and the arrow may not always render correctly.</small><br />
<br />
[[Image:Brush polygon idea2.svg|300px]] [[Image:Brush polygon idea5.svg|300px]]<br />
<br />
The mouse-down start point defines half-way boundaries. For each polygon this is a combination of that polygon being scaled (dashed line) and the perpendicular bisectors (dotted lines) between start point and polygon points.<br />
<br />
==Crossing the half-way mark==<br />
<br />
[[Image:Brush polygon idea3.svg|300px]] [[Image:Brush polygon idea6.svg|300px]]<br />
<br />
When the first of these half-way boundaries are crossed, the corresponding polygon is chosen, the half-way point defined, and also a trace, a part of the polygon outline, is selected as follows:<br />
<br />
The start point and the half-way point define a direction.<br />
From the start point inside the angle range 30-60 degrees left<br />
one looks for a polygon point to act as trace endpoint (full blue circle).<br />
If there are several, one chooses the "best" as endpoint,<br />
which usually means the point nearest to the 45 degrees direction.<br />
If there is no point within that angle range but a polygon face,<br />
then a candidate endpoint (open circle) is placed on it at 45 degrees.<br />
<br />
Then repeat for the angle range to the right.<br />
<br />
There is a continuous polygon trace between two endpoints (blue),<br />
any segment of it connected to an endpoint is an endpoint segment.<br />
There may be intermediate points and intermediate segments (violet).<br />
<br />
Possibly this trace should be highlighted at that point in the GUI.<br />
<br />
==Crossing into the polygon==<br />
<br />
[[Image:Brush polygon idea4.svg|300px]] [[Image:Brush polygon idea7.svg|300px]]<br />
<br />
When this highlighted trace is being crossed, any candidate endpoint is added as a new point to the polygon.<br />
<br />
* If one crosses an endpoint segment (blue line), a new point (red) is created and sticks to the pointer.<br />
* If one crosses an intermediate segment (violet line), this segment (red line plus two red points) sticks to the pointer.<br />
<br />
Each of the violet polygon points between the red sticky middle element<br />
and a blue endpoint performs a scaled version of the pointer movement,<br />
with points nearer to an endpoint moving less.<br />
<br />
This action is over when one releases the mouse button.<br />
<br />
No action is taken is the mouse does not drag across the highlighted polygon trace.<br />
----<br />
Clicking into empty space deselects all.<br />
<br />
Clicking and dragging on polygon points and lines yields standard response.<br />
<br />
Dragging with modifyer down into empty space creates a new polygon.<br />
<br />
Several polygons XOR, the resulting masks ORs with any input image bitmap mask.</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea7.svg&diff=10442File:Brush polygon idea7.svg2008-05-20T17:29:58Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea6.svg&diff=10441File:Brush polygon idea6.svg2008-05-20T17:29:25Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea5.svg&diff=10440File:Brush polygon idea5.svg2008-05-20T17:28:50Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea4.svg&diff=10439File:Brush polygon idea4.svg2008-05-20T17:28:32Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea3.svg&diff=10438File:Brush polygon idea3.svg2008-05-20T17:28:08Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Brush_polygon_idea2.svg&diff=10437File:Brush polygon idea2.svg2008-05-20T17:27:32Z<p>Klaus: idea image</p>
<hr />
<div>idea image</div>Klaushttps://wiki.panotools.org/index.php?title=Historical:Suggestion_Hugin_Preferences_Workflow&diff=10436Historical:Suggestion Hugin Preferences Workflow2008-05-20T17:17:39Z<p>Klaus: incorporated Yuv's suggestions</p>
<hr />
<div>==Feature proposal from hugin-ptx==<br />
<br />
A new ''Preferences'' pane is suggested for ''hugin'', with input field for saving path for projects and input field for saving panorama(s) (and more input fields for default (saving) path for other "things" like lens parameters?). <s>Radio buttons or </s>Drop-down menus would fit the need for choosing 1 out of N options.<br />
<br />
This addition is suggested for hugin 0.7.1<br />
<br />
==Hugin > Preferences > Workflow==<br />
<br />
On hugin startup open on<br />
* Assistant tab<br />
* Images tab<br />
----<br />
New project file<br />
: Save project file dialogue opens on<br />
:* input images directory<br />
:* previous project file directory<br />
:* custom directory<br />
: Suggested project file name is<br />
:* blank<br />
:* first_image_name-last_image_name<br />
:* current date and time<br />
:* name of directory where the project file is stored<br />
::: Here it would be cool to have some sort of expandos / regexp thing, e.g. %d1 %d2 %d3 would be the first, second, and third level directory. <br />
----<br />
Specify output prefix<br />
: Dialogue window opens on<br />
:* input images directory<br />
:* project file directory<br />
:* previous output directory<br />
:* custom directory<br />
: Suggested output prefix is<br />
:* blank<br />
:* project file name prefix<br />
:* current date and time<br />
:* custom (possibly with an expando that could look like %d4%d5.tif)<br />
----<br />
Output prefix dialogue<br />
:* show dialogue window to specifiy output prefix<br />
:* automatically set output prefix based on existing rules<br />
<br />
==Explanations==<br />
* Maybe someone can come up with a better name than "Workflow". <br />
* For an existing pto file, the "Save as" dialogue should open with that directory and that name.<br />
* For the output prefix, the suggested name could be (partly) highlighted (possible in OSX), and if one types away, the highlighted default clears. If you want to edit the suggested name, click on it first or use left-arrow or right-arrow as first key stroke.</div>Klaushttps://wiki.panotools.org/index.php?title=Talk:Enblend_Testcase_2008-05-02&diff=10435Talk:Enblend Testcase 2008-05-022008-05-19T15:46:01Z<p>Klaus: independent of --fine-mask switch</p>
<hr />
<div>What happens if you use the option --fine-mask ?<br />
[[User:Seb Przd|Seb Przd]] 16:12, 19 May 2008 (CEST)<br />
<br />
: While I have not run that again for cvs3036, with the version 3.1 from January I found that the outcome was independent of the '''--fine-mask''' option. Of course the detailed mask edge looks slightly different. Maybe one of the seams is winding clockwise and the other winding counterclockwise, and winding numbers +1 and -1 are treated differently? Just guessing... -- [[User:Klaus|Klaus]] 17:46, 19 May 2008 (CEST)</div>Klaushttps://wiki.panotools.org/index.php?title=File:Budapest45_visual.jpg&diff=10428File:Budapest45 visual.jpg2008-05-19T13:31:47Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Budapest45_blended.jpg&diff=10427File:Budapest45 blended.jpg2008-05-19T13:31:16Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Budapest5_20070827.jpg&diff=10426File:Budapest5 20070827.jpg2008-05-19T13:29:42Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Budapest4_20070827.jpg&diff=10425File:Budapest4 20070827.jpg2008-05-19T13:29:04Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Budapest45_tif.zip&diff=10424File:Budapest45 tif.zip2008-05-19T13:28:23Z<p>Klaus: enblend test case files</p>
<hr />
<div>enblend test case files</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_visual2_0fmaskoptim.jpg&diff=10421File:Scottishparliament visual2 0fmaskoptim.jpg2008-05-19T13:08:03Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_visual0_2fmaskoptim.jpg&diff=10420File:Scottishparliament visual0 2fmaskoptim.jpg2008-05-19T13:07:41Z<p>Klaus: enlend test case image</p>
<hr />
<div>enlend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_mask2_0fmaskoptim.jpg&diff=10419File:Scottishparliament mask2 0fmaskoptim.jpg2008-05-19T13:07:12Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_mask2_0fmasknoopt.jpg&diff=10418File:Scottishparliament mask2 0fmasknoopt.jpg2008-05-19T13:06:56Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_mask0_2fmaskoptim.jpg&diff=10417File:Scottishparliament mask0 2fmaskoptim.jpg2008-05-19T13:06:37Z<p>Klaus: enblend test casea image</p>
<hr />
<div>enblend test casea image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_mask0_2fmasknoopt.jpg&diff=10416File:Scottishparliament mask0 2fmasknoopt.jpg2008-05-19T13:06:21Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_blend2_0fmaskoptim.jpg&diff=10415File:Scottishparliament blend2 0fmaskoptim.jpg2008-05-19T13:05:53Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_blend2_0fmasknoopt.jpg&diff=10414File:Scottishparliament blend2 0fmasknoopt.jpg2008-05-19T13:05:34Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_blend0_2fmaskoptim.jpg&diff=10413File:Scottishparliament blend0 2fmaskoptim.jpg2008-05-19T13:05:13Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_blend0_2fmasknoopt.jpg&diff=10412File:Scottishparliament blend0 2fmasknoopt.jpg2008-05-19T13:04:55Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament2.jpg&diff=10411File:Scottishparliament2.jpg2008-05-19T13:04:25Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament0.jpg&diff=10410File:Scottishparliament0.jpg2008-05-19T13:04:00Z<p>Klaus: enblend test case image</p>
<hr />
<div>enblend test case image</div>Klaushttps://wiki.panotools.org/index.php?title=File:Scottishparliament_tif.zip&diff=10409File:Scottishparliament tif.zip2008-05-19T13:03:09Z<p>Klaus: enblend test case files</p>
<hr />
<div>enblend test case files</div>Klaushttps://wiki.panotools.org/index.php?title=Development_of_Open_Source_tools&diff=10408Development of Open Source tools2008-05-19T12:50:31Z<p>Klaus: /* release 0.7.1 */ sf ref</p>
<hr />
<div>== Panorama Related Open Source tools ==<br />
<br />
* [[Hugin]]<br />
* [[Enblend]]<br />
* [[Enfuse]]<br />
* [[Panotools]]<br />
<br />
== Contribution ==<br />
<br />
=== Why contribute? ===<br />
<br />
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.<br />
<br />
=== How to contribute? ===<br />
<br />
Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.<br />
<br />
If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.<br />
<br />
At the time of writing (03-February-2008) the building process of hugin is robust and we are looking for testers to go over bug reports and test them against the regular snapshot builds.<br />
<br />
'''Don't be afraid of failures in the building process'''<br />
* The likelihood that errors will occur when following the build processes linked below is high.<br />
* Don't worry such failure will not compromise your computer.<br />
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.<br />
<br />
If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.<br />
<br />
== Hugin 0.7.0 release schedule ==<br />
<br />
Clearing the bugs in the sourceforge bug tracker is an iterative process. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.<br />
<br />
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:<br />
# '''Volunteers''' check the bugs listed in the [https://sourceforge.net/tracker/?group_id=77506&atid=550441 sourceforge bug tracker] under group v0.7.0 against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).<br />
#* Install the latest snapshot.<br />
#* Try to reproduce the bug on your system.<br />
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).<br />
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing.<br />
#* Try again. If you can consistently reproduce the crash more than twice, raise its priority to 8. Post detailed instructions how to reproduce the crash.<br />
#* If you can confirm a bug a bug that is older than 3-4 months, please raise its priority to 6. If it is a real show stopper.<br />
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.<br />
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but it is e<br />
# The '''developers''' fix the bugs identified in the tracker.<br />
# The '''builders''' build new snapshots including the fixes.<br />
<br />
We'll repeat this process to deal with:<br />
* functional bugs: to make sure that the program does what it is meant to do<br />
* GUI bugs: to make sure that the user has full access to the program's functionalities<br />
* stability bugs: to make sure the program is robust and does not crash<br />
<br />
After the GUI bugs have been fixed<br />
* a string freeze will be issued to allow translators to prepare the translations. The string freeze will be announced on hugin-ptx and on this page.<br />
* a first release candidate will be issued to allow for robustness testing.<br />
<br />
=== Current Status ===<br />
<br />
We have started to systematically look at the bugs in the bug tracker.<br />
<br />
This list is incomplete based on testing svn2733 running on OSX. Thank you, Klaus!<br />
<br />
==== showstoppers blocking 0.7.0 release ====<br />
Please collect bugs (must be in tracker, include link) that <b>must</b> be fixed before 0.7.0 can be released.<br />
<br />
* Hugin does not stitch on Windows<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1910220&group_id=77506&atid=550441 1910220]<br />
* ...<br />
<br />
==== ought to be done 0.7.0 ====<br />
* '''DONE''' <s>get the Option buttons working in the Stitcher tab</s> ok in cvs3036<br />
* reduce image size to image content size for Stitcher cropped output<br />
* prevent modification of exposure information on merely clicking tabs<br />
* fix issues with non-latin characters in file paths on Windows [https://sourceforge.net/tracker/index.php?func=detail&aid=1908349&group_id=77506&atid=550441 1908349]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1902471&group_id=77506&atid=550441 1902471]<br />
<br />
==== may be done for 0.7.0 if easily implemented ====<br />
* '''DONE''' <s>interpolator selection</s> as of cvs3036, standard selection available<br />
*simultaneous flatfield file and vignetting coefficients support<br />
<br />
* correct top grey rim in enblend , however '''--fine-mask''' option is workaround<br />
<br />
=== release 0.7.1 ===<br />
<br />
add new pane to Preferences: [[Suggestion Hugin Preferences Workflow|Hugin > Preferences > Workflow]]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1967054&group_id=77506&atid=550444 1967054]<br />
<br />
=== release 0.7.x ===<br />
*include antialiasing interpolators<br />
<br />
=== release >0.7 ===<br />
*lots of GUI items i.e.<br />
**histograms for intensity and RGB<br />
**mass handling of Control Points, specify areas where (not) to put them<br />
<br />
<br />
== Download Test Build ==<br />
<br />
If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].<br />
<br />
== Build your Own Test Builds ==<br />
<br />
If you are ready to go through the building process, here are the instructions.<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"<br />
|-valign="top"<br />
! '''IMPORTANT:'''<br />
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [http://wiki.panotools.org/Development_of_Open_Source_tools#Packaging_and_Distribution below]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.<br />
|}<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
==== hugin ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2801<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows, used for Windows installer snapshot. Builds on ubuntu 7.10 AMD64<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2797<br />
| style="border-top: thin dotted #333333;" |<br />
builds on OSX, used for OSX snapshot package.<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2766<br />
| style="border-top: thin dotted #333333;" |<br />
Windows self-installing archives. [ftp://tksftp@tksharpless.net] "TKSpwd1"<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2733<br />
| style="border-top: thin dotted #333333;" |<br />
build on OSX. runs on Macs that have no programming packages installed.<br />
|-valign="top" <br />
|}<br />
<br />
[[older hugin revision notes]]<br />
<br />
==== libpano ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
785<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
770<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
767<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
759<br />
| style="border-top: thin dotted #333333;" |<br />
builds on AMD64 ubuntu 7.10<br />
|-valign="top"<br />
|}<br />
<br />
[[older libpano revision notes]]<br />
<br />
==== enblend ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-07<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-03<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows and ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
|}<br />
<br />
[[older enblend revision notes]]<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
* Régis B.<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
* David Haberthür<br />
* John Riley<br />
* Roger Howard<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
*[[Build Hugin for Windows with SDK | OK, SDK based]]<br />
*[[Hugin Compiling Windows | draft, from scratch]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
* Yili Zhao<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
Vasil Dimov, FreeBSD port maintainer<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* confirmed to build on FreeBSD 6.2/i386<br />
* confirmed to build on FreeBSD 7.0/amd64<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
<!-- spanned| style="border-top: thin dotted #333333;" | tbd --><br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
== Packaging and Distribution ==<br />
<br />
Instructions for packaging binaries for distribution will follow. Some important points:<br />
<br />
=== Snapshots ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number<br />
* edit the text / readme files that come with the snapshot<br />
** indicate clearly that it is unstable, experimental software<br />
** indicate where to find the latest version<br />
** indicate that the advertised features might or might not work<br />
<br />
=== Release ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
<br />
== Feedback ==<br />
<br />
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!<br />
<br />
To give good feedback, note down carefully all of this information while you are going through the instructions.<br />
# details about your computer. CPU, operating system, other particularities<br />
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.<br />
# the last step / command you entered into the command line<br />
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.<br />
<br />
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try<br />
* to use "make VERBOSE=1" when building hugin.<br />
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.</div>Klaushttps://wiki.panotools.org/index.php?title=Development_of_Open_Source_tools&diff=10407Development of Open Source tools2008-05-19T12:38:01Z<p>Klaus: /* ought to be done 0.7.0 */ add DONE</p>
<hr />
<div>== Panorama Related Open Source tools ==<br />
<br />
* [[Hugin]]<br />
* [[Enblend]]<br />
* [[Enfuse]]<br />
* [[Panotools]]<br />
<br />
== Contribution ==<br />
<br />
=== Why contribute? ===<br />
<br />
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.<br />
<br />
=== How to contribute? ===<br />
<br />
Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.<br />
<br />
If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.<br />
<br />
At the time of writing (03-February-2008) the building process of hugin is robust and we are looking for testers to go over bug reports and test them against the regular snapshot builds.<br />
<br />
'''Don't be afraid of failures in the building process'''<br />
* The likelihood that errors will occur when following the build processes linked below is high.<br />
* Don't worry such failure will not compromise your computer.<br />
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.<br />
<br />
If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.<br />
<br />
== Hugin 0.7.0 release schedule ==<br />
<br />
Clearing the bugs in the sourceforge bug tracker is an iterative process. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.<br />
<br />
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:<br />
# '''Volunteers''' check the bugs listed in the [https://sourceforge.net/tracker/?group_id=77506&atid=550441 sourceforge bug tracker] under group v0.7.0 against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).<br />
#* Install the latest snapshot.<br />
#* Try to reproduce the bug on your system.<br />
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).<br />
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing.<br />
#* Try again. If you can consistently reproduce the crash more than twice, raise its priority to 8. Post detailed instructions how to reproduce the crash.<br />
#* If you can confirm a bug a bug that is older than 3-4 months, please raise its priority to 6. If it is a real show stopper.<br />
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.<br />
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but it is e<br />
# The '''developers''' fix the bugs identified in the tracker.<br />
# The '''builders''' build new snapshots including the fixes.<br />
<br />
We'll repeat this process to deal with:<br />
* functional bugs: to make sure that the program does what it is meant to do<br />
* GUI bugs: to make sure that the user has full access to the program's functionalities<br />
* stability bugs: to make sure the program is robust and does not crash<br />
<br />
After the GUI bugs have been fixed<br />
* a string freeze will be issued to allow translators to prepare the translations. The string freeze will be announced on hugin-ptx and on this page.<br />
* a first release candidate will be issued to allow for robustness testing.<br />
<br />
=== Current Status ===<br />
<br />
We have started to systematically look at the bugs in the bug tracker.<br />
<br />
This list is incomplete based on testing svn2733 running on OSX. Thank you, Klaus!<br />
<br />
==== showstoppers blocking 0.7.0 release ====<br />
Please collect bugs (must be in tracker, include link) that <b>must</b> be fixed before 0.7.0 can be released.<br />
<br />
* Hugin does not stitch on Windows<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1910220&group_id=77506&atid=550441 1910220]<br />
* ...<br />
<br />
==== ought to be done 0.7.0 ====<br />
* '''DONE''' <s>get the Option buttons working in the Stitcher tab</s> ok in cvs3036<br />
* reduce image size to image content size for Stitcher cropped output<br />
* prevent modification of exposure information on merely clicking tabs<br />
* fix issues with non-latin characters in file paths on Windows [https://sourceforge.net/tracker/index.php?func=detail&aid=1908349&group_id=77506&atid=550441 1908349]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1902471&group_id=77506&atid=550441 1902471]<br />
<br />
==== may be done for 0.7.0 if easily implemented ====<br />
* '''DONE''' <s>interpolator selection</s> as of cvs3036, standard selection available<br />
*simultaneous flatfield file and vignetting coefficients support<br />
<br />
* correct top grey rim in enblend , however '''--fine-mask''' option is workaround<br />
<br />
=== release 0.7.1 ===<br />
<br />
add new pane to Preferences: [[Suggestion Hugin Preferences Workflow|Hugin > Preferences > Workflow]]<br />
<br />
=== release 0.7.x ===<br />
*include antialiasing interpolators<br />
<br />
=== release >0.7 ===<br />
*lots of GUI items i.e.<br />
**histograms for intensity and RGB<br />
**mass handling of Control Points, specify areas where (not) to put them<br />
<br />
<br />
== Download Test Build ==<br />
<br />
If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].<br />
<br />
== Build your Own Test Builds ==<br />
<br />
If you are ready to go through the building process, here are the instructions.<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"<br />
|-valign="top"<br />
! '''IMPORTANT:'''<br />
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [http://wiki.panotools.org/Development_of_Open_Source_tools#Packaging_and_Distribution below]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.<br />
|}<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
==== hugin ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2801<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows, used for Windows installer snapshot. Builds on ubuntu 7.10 AMD64<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2797<br />
| style="border-top: thin dotted #333333;" |<br />
builds on OSX, used for OSX snapshot package.<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2766<br />
| style="border-top: thin dotted #333333;" |<br />
Windows self-installing archives. [ftp://tksftp@tksharpless.net] "TKSpwd1"<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2733<br />
| style="border-top: thin dotted #333333;" |<br />
build on OSX. runs on Macs that have no programming packages installed.<br />
|-valign="top" <br />
|}<br />
<br />
[[older hugin revision notes]]<br />
<br />
==== libpano ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
785<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
770<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
767<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
759<br />
| style="border-top: thin dotted #333333;" |<br />
builds on AMD64 ubuntu 7.10<br />
|-valign="top"<br />
|}<br />
<br />
[[older libpano revision notes]]<br />
<br />
==== enblend ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-07<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-03<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows and ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
|}<br />
<br />
[[older enblend revision notes]]<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
* Régis B.<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
* David Haberthür<br />
* John Riley<br />
* Roger Howard<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
*[[Build Hugin for Windows with SDK | OK, SDK based]]<br />
*[[Hugin Compiling Windows | draft, from scratch]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
* Yili Zhao<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
Vasil Dimov, FreeBSD port maintainer<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* confirmed to build on FreeBSD 6.2/i386<br />
* confirmed to build on FreeBSD 7.0/amd64<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
<!-- spanned| style="border-top: thin dotted #333333;" | tbd --><br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
== Packaging and Distribution ==<br />
<br />
Instructions for packaging binaries for distribution will follow. Some important points:<br />
<br />
=== Snapshots ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number<br />
* edit the text / readme files that come with the snapshot<br />
** indicate clearly that it is unstable, experimental software<br />
** indicate where to find the latest version<br />
** indicate that the advertised features might or might not work<br />
<br />
=== Release ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
<br />
== Feedback ==<br />
<br />
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!<br />
<br />
To give good feedback, note down carefully all of this information while you are going through the instructions.<br />
# details about your computer. CPU, operating system, other particularities<br />
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.<br />
# the last step / command you entered into the command line<br />
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.<br />
<br />
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try<br />
* to use "make VERBOSE=1" when building hugin.<br />
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.</div>Klaushttps://wiki.panotools.org/index.php?title=Development_of_Open_Source_tools&diff=10406Development of Open Source tools2008-05-19T12:37:20Z<p>Klaus: /* may be done for 0.7.0 if easily implemented */ interpolators can be chosen</p>
<hr />
<div>== Panorama Related Open Source tools ==<br />
<br />
* [[Hugin]]<br />
* [[Enblend]]<br />
* [[Enfuse]]<br />
* [[Panotools]]<br />
<br />
== Contribution ==<br />
<br />
=== Why contribute? ===<br />
<br />
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.<br />
<br />
=== How to contribute? ===<br />
<br />
Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.<br />
<br />
If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.<br />
<br />
At the time of writing (03-February-2008) the building process of hugin is robust and we are looking for testers to go over bug reports and test them against the regular snapshot builds.<br />
<br />
'''Don't be afraid of failures in the building process'''<br />
* The likelihood that errors will occur when following the build processes linked below is high.<br />
* Don't worry such failure will not compromise your computer.<br />
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.<br />
<br />
If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.<br />
<br />
== Hugin 0.7.0 release schedule ==<br />
<br />
Clearing the bugs in the sourceforge bug tracker is an iterative process. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.<br />
<br />
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:<br />
# '''Volunteers''' check the bugs listed in the [https://sourceforge.net/tracker/?group_id=77506&atid=550441 sourceforge bug tracker] under group v0.7.0 against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).<br />
#* Install the latest snapshot.<br />
#* Try to reproduce the bug on your system.<br />
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).<br />
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing.<br />
#* Try again. If you can consistently reproduce the crash more than twice, raise its priority to 8. Post detailed instructions how to reproduce the crash.<br />
#* If you can confirm a bug a bug that is older than 3-4 months, please raise its priority to 6. If it is a real show stopper.<br />
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.<br />
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but it is e<br />
# The '''developers''' fix the bugs identified in the tracker.<br />
# The '''builders''' build new snapshots including the fixes.<br />
<br />
We'll repeat this process to deal with:<br />
* functional bugs: to make sure that the program does what it is meant to do<br />
* GUI bugs: to make sure that the user has full access to the program's functionalities<br />
* stability bugs: to make sure the program is robust and does not crash<br />
<br />
After the GUI bugs have been fixed<br />
* a string freeze will be issued to allow translators to prepare the translations. The string freeze will be announced on hugin-ptx and on this page.<br />
* a first release candidate will be issued to allow for robustness testing.<br />
<br />
=== Current Status ===<br />
<br />
We have started to systematically look at the bugs in the bug tracker.<br />
<br />
This list is incomplete based on testing svn2733 running on OSX. Thank you, Klaus!<br />
<br />
==== showstoppers blocking 0.7.0 release ====<br />
Please collect bugs (must be in tracker, include link) that <b>must</b> be fixed before 0.7.0 can be released.<br />
<br />
* Hugin does not stitch on Windows<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1910220&group_id=77506&atid=550441 1910220]<br />
* ...<br />
<br />
==== ought to be done 0.7.0 ====<br />
* <s>get the Option buttons working in the Stitcher tab</s> ok in cvs3036<br />
* reduce image size to image content size for Stitcher cropped output<br />
* prevent modification of exposure information on merely clicking tabs<br />
* fix issues with non-latin characters in file paths on Windows [https://sourceforge.net/tracker/index.php?func=detail&aid=1908349&group_id=77506&atid=550441 1908349]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1902471&group_id=77506&atid=550441 1902471]<br />
<br />
==== may be done for 0.7.0 if easily implemented ====<br />
* '''DONE''' <s>interpolator selection</s> as of cvs3036, standard selection available<br />
*simultaneous flatfield file and vignetting coefficients support<br />
<br />
* correct top grey rim in enblend , however '''--fine-mask''' option is workaround<br />
<br />
=== release 0.7.1 ===<br />
<br />
add new pane to Preferences: [[Suggestion Hugin Preferences Workflow|Hugin > Preferences > Workflow]]<br />
<br />
=== release 0.7.x ===<br />
*include antialiasing interpolators<br />
<br />
=== release >0.7 ===<br />
*lots of GUI items i.e.<br />
**histograms for intensity and RGB<br />
**mass handling of Control Points, specify areas where (not) to put them<br />
<br />
<br />
== Download Test Build ==<br />
<br />
If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].<br />
<br />
== Build your Own Test Builds ==<br />
<br />
If you are ready to go through the building process, here are the instructions.<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"<br />
|-valign="top"<br />
! '''IMPORTANT:'''<br />
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [http://wiki.panotools.org/Development_of_Open_Source_tools#Packaging_and_Distribution below]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.<br />
|}<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
==== hugin ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2801<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows, used for Windows installer snapshot. Builds on ubuntu 7.10 AMD64<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2797<br />
| style="border-top: thin dotted #333333;" |<br />
builds on OSX, used for OSX snapshot package.<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2766<br />
| style="border-top: thin dotted #333333;" |<br />
Windows self-installing archives. [ftp://tksftp@tksharpless.net] "TKSpwd1"<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2733<br />
| style="border-top: thin dotted #333333;" |<br />
build on OSX. runs on Macs that have no programming packages installed.<br />
|-valign="top" <br />
|}<br />
<br />
[[older hugin revision notes]]<br />
<br />
==== libpano ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
785<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
770<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
767<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
759<br />
| style="border-top: thin dotted #333333;" |<br />
builds on AMD64 ubuntu 7.10<br />
|-valign="top"<br />
|}<br />
<br />
[[older libpano revision notes]]<br />
<br />
==== enblend ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-07<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-03<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows and ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
|}<br />
<br />
[[older enblend revision notes]]<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
* Régis B.<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
* David Haberthür<br />
* John Riley<br />
* Roger Howard<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
*[[Build Hugin for Windows with SDK | OK, SDK based]]<br />
*[[Hugin Compiling Windows | draft, from scratch]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
* Yili Zhao<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
Vasil Dimov, FreeBSD port maintainer<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* confirmed to build on FreeBSD 6.2/i386<br />
* confirmed to build on FreeBSD 7.0/amd64<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
<!-- spanned| style="border-top: thin dotted #333333;" | tbd --><br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
== Packaging and Distribution ==<br />
<br />
Instructions for packaging binaries for distribution will follow. Some important points:<br />
<br />
=== Snapshots ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number<br />
* edit the text / readme files that come with the snapshot<br />
** indicate clearly that it is unstable, experimental software<br />
** indicate where to find the latest version<br />
** indicate that the advertised features might or might not work<br />
<br />
=== Release ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
<br />
== Feedback ==<br />
<br />
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!<br />
<br />
To give good feedback, note down carefully all of this information while you are going through the instructions.<br />
# details about your computer. CPU, operating system, other particularities<br />
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.<br />
# the last step / command you entered into the command line<br />
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.<br />
<br />
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try<br />
* to use "make VERBOSE=1" when building hugin.<br />
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.</div>Klaushttps://wiki.panotools.org/index.php?title=Development_of_Open_Source_tools&diff=10405Development of Open Source tools2008-05-19T12:35:02Z<p>Klaus: /* release 0.7.x */ add preferences pane</p>
<hr />
<div>== Panorama Related Open Source tools ==<br />
<br />
* [[Hugin]]<br />
* [[Enblend]]<br />
* [[Enfuse]]<br />
* [[Panotools]]<br />
<br />
== Contribution ==<br />
<br />
=== Why contribute? ===<br />
<br />
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.<br />
<br />
=== How to contribute? ===<br />
<br />
Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.<br />
<br />
If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.<br />
<br />
At the time of writing (03-February-2008) the building process of hugin is robust and we are looking for testers to go over bug reports and test them against the regular snapshot builds.<br />
<br />
'''Don't be afraid of failures in the building process'''<br />
* The likelihood that errors will occur when following the build processes linked below is high.<br />
* Don't worry such failure will not compromise your computer.<br />
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.<br />
<br />
If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.<br />
<br />
== Hugin 0.7.0 release schedule ==<br />
<br />
Clearing the bugs in the sourceforge bug tracker is an iterative process. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.<br />
<br />
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:<br />
# '''Volunteers''' check the bugs listed in the [https://sourceforge.net/tracker/?group_id=77506&atid=550441 sourceforge bug tracker] under group v0.7.0 against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).<br />
#* Install the latest snapshot.<br />
#* Try to reproduce the bug on your system.<br />
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).<br />
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing.<br />
#* Try again. If you can consistently reproduce the crash more than twice, raise its priority to 8. Post detailed instructions how to reproduce the crash.<br />
#* If you can confirm a bug a bug that is older than 3-4 months, please raise its priority to 6. If it is a real show stopper.<br />
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.<br />
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but it is e<br />
# The '''developers''' fix the bugs identified in the tracker.<br />
# The '''builders''' build new snapshots including the fixes.<br />
<br />
We'll repeat this process to deal with:<br />
* functional bugs: to make sure that the program does what it is meant to do<br />
* GUI bugs: to make sure that the user has full access to the program's functionalities<br />
* stability bugs: to make sure the program is robust and does not crash<br />
<br />
After the GUI bugs have been fixed<br />
* a string freeze will be issued to allow translators to prepare the translations. The string freeze will be announced on hugin-ptx and on this page.<br />
* a first release candidate will be issued to allow for robustness testing.<br />
<br />
=== Current Status ===<br />
<br />
We have started to systematically look at the bugs in the bug tracker.<br />
<br />
This list is incomplete based on testing svn2733 running on OSX. Thank you, Klaus!<br />
<br />
==== showstoppers blocking 0.7.0 release ====<br />
Please collect bugs (must be in tracker, include link) that <b>must</b> be fixed before 0.7.0 can be released.<br />
<br />
* Hugin does not stitch on Windows<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1910220&group_id=77506&atid=550441 1910220]<br />
* ...<br />
<br />
==== ought to be done 0.7.0 ====<br />
* <s>get the Option buttons working in the Stitcher tab</s> ok in cvs3036<br />
* reduce image size to image content size for Stitcher cropped output<br />
* prevent modification of exposure information on merely clicking tabs<br />
* fix issues with non-latin characters in file paths on Windows [https://sourceforge.net/tracker/index.php?func=detail&aid=1908349&group_id=77506&atid=550441 1908349]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1902471&group_id=77506&atid=550441 1902471]<br />
<br />
==== may be done for 0.7.0 if easily implemented ====<br />
*interpolator selection<br />
*flatfield file<br />
<br />
* correct top grey rim in enblend , however '''--fine-mask''' option is workaround<br />
<br />
=== release 0.7.1 ===<br />
<br />
add new pane to Preferences: [[Suggestion Hugin Preferences Workflow|Hugin > Preferences > Workflow]]<br />
<br />
=== release 0.7.x ===<br />
*include antialiasing interpolators<br />
<br />
=== release >0.7 ===<br />
*lots of GUI items i.e.<br />
**histograms for intensity and RGB<br />
**mass handling of Control Points, specify areas where (not) to put them<br />
<br />
<br />
== Download Test Build ==<br />
<br />
If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].<br />
<br />
== Build your Own Test Builds ==<br />
<br />
If you are ready to go through the building process, here are the instructions.<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"<br />
|-valign="top"<br />
! '''IMPORTANT:'''<br />
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [http://wiki.panotools.org/Development_of_Open_Source_tools#Packaging_and_Distribution below]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.<br />
|}<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
==== hugin ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2801<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows, used for Windows installer snapshot. Builds on ubuntu 7.10 AMD64<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2797<br />
| style="border-top: thin dotted #333333;" |<br />
builds on OSX, used for OSX snapshot package.<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2766<br />
| style="border-top: thin dotted #333333;" |<br />
Windows self-installing archives. [ftp://tksftp@tksharpless.net] "TKSpwd1"<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2733<br />
| style="border-top: thin dotted #333333;" |<br />
build on OSX. runs on Macs that have no programming packages installed.<br />
|-valign="top" <br />
|}<br />
<br />
[[older hugin revision notes]]<br />
<br />
==== libpano ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
785<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
770<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
767<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
759<br />
| style="border-top: thin dotted #333333;" |<br />
builds on AMD64 ubuntu 7.10<br />
|-valign="top"<br />
|}<br />
<br />
[[older libpano revision notes]]<br />
<br />
==== enblend ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-07<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-03<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows and ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
|}<br />
<br />
[[older enblend revision notes]]<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
* Régis B.<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
* David Haberthür<br />
* John Riley<br />
* Roger Howard<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
*[[Build Hugin for Windows with SDK | OK, SDK based]]<br />
*[[Hugin Compiling Windows | draft, from scratch]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
* Yili Zhao<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
Vasil Dimov, FreeBSD port maintainer<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* confirmed to build on FreeBSD 6.2/i386<br />
* confirmed to build on FreeBSD 7.0/amd64<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
<!-- spanned| style="border-top: thin dotted #333333;" | tbd --><br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
== Packaging and Distribution ==<br />
<br />
Instructions for packaging binaries for distribution will follow. Some important points:<br />
<br />
=== Snapshots ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number<br />
* edit the text / readme files that come with the snapshot<br />
** indicate clearly that it is unstable, experimental software<br />
** indicate where to find the latest version<br />
** indicate that the advertised features might or might not work<br />
<br />
=== Release ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
<br />
== Feedback ==<br />
<br />
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!<br />
<br />
To give good feedback, note down carefully all of this information while you are going through the instructions.<br />
# details about your computer. CPU, operating system, other particularities<br />
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.<br />
# the last step / command you entered into the command line<br />
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.<br />
<br />
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try<br />
* to use "make VERBOSE=1" when building hugin.<br />
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.</div>Klaushttps://wiki.panotools.org/index.php?title=Development_of_Open_Source_tools&diff=10404Development of Open Source tools2008-05-19T12:32:35Z<p>Klaus: /* ought to be done 0.7.0 */ option buttons do work</p>
<hr />
<div>== Panorama Related Open Source tools ==<br />
<br />
* [[Hugin]]<br />
* [[Enblend]]<br />
* [[Enfuse]]<br />
* [[Panotools]]<br />
<br />
== Contribution ==<br />
<br />
=== Why contribute? ===<br />
<br />
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.<br />
<br />
=== How to contribute? ===<br />
<br />
Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.<br />
<br />
If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.<br />
<br />
At the time of writing (03-February-2008) the building process of hugin is robust and we are looking for testers to go over bug reports and test them against the regular snapshot builds.<br />
<br />
'''Don't be afraid of failures in the building process'''<br />
* The likelihood that errors will occur when following the build processes linked below is high.<br />
* Don't worry such failure will not compromise your computer.<br />
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.<br />
<br />
If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.<br />
<br />
== Hugin 0.7.0 release schedule ==<br />
<br />
Clearing the bugs in the sourceforge bug tracker is an iterative process. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.<br />
<br />
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:<br />
# '''Volunteers''' check the bugs listed in the [https://sourceforge.net/tracker/?group_id=77506&atid=550441 sourceforge bug tracker] under group v0.7.0 against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).<br />
#* Install the latest snapshot.<br />
#* Try to reproduce the bug on your system.<br />
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).<br />
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing.<br />
#* Try again. If you can consistently reproduce the crash more than twice, raise its priority to 8. Post detailed instructions how to reproduce the crash.<br />
#* If you can confirm a bug a bug that is older than 3-4 months, please raise its priority to 6. If it is a real show stopper.<br />
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.<br />
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but it is e<br />
# The '''developers''' fix the bugs identified in the tracker.<br />
# The '''builders''' build new snapshots including the fixes.<br />
<br />
We'll repeat this process to deal with:<br />
* functional bugs: to make sure that the program does what it is meant to do<br />
* GUI bugs: to make sure that the user has full access to the program's functionalities<br />
* stability bugs: to make sure the program is robust and does not crash<br />
<br />
After the GUI bugs have been fixed<br />
* a string freeze will be issued to allow translators to prepare the translations. The string freeze will be announced on hugin-ptx and on this page.<br />
* a first release candidate will be issued to allow for robustness testing.<br />
<br />
=== Current Status ===<br />
<br />
We have started to systematically look at the bugs in the bug tracker.<br />
<br />
This list is incomplete based on testing svn2733 running on OSX. Thank you, Klaus!<br />
<br />
==== showstoppers blocking 0.7.0 release ====<br />
Please collect bugs (must be in tracker, include link) that <b>must</b> be fixed before 0.7.0 can be released.<br />
<br />
* Hugin does not stitch on Windows<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1910220&group_id=77506&atid=550441 1910220]<br />
* ...<br />
<br />
==== ought to be done 0.7.0 ====<br />
* <s>get the Option buttons working in the Stitcher tab</s> ok in cvs3036<br />
* reduce image size to image content size for Stitcher cropped output<br />
* prevent modification of exposure information on merely clicking tabs<br />
* fix issues with non-latin characters in file paths on Windows [https://sourceforge.net/tracker/index.php?func=detail&aid=1908349&group_id=77506&atid=550441 1908349]<br />
[https://sourceforge.net/tracker/index.php?func=detail&aid=1902471&group_id=77506&atid=550441 1902471]<br />
<br />
==== may be done for 0.7.0 if easily implemented ====<br />
*interpolator selection<br />
*flatfield file<br />
<br />
* correct top grey rim in enblend , however '''--fine-mask''' option is workaround<br />
<br />
=== release 0.7.x ===<br />
*include antialiasing interpolators<br />
<br />
=== release >0.7 ===<br />
*lots of GUI items i.e.<br />
**histograms for intensity and RGB<br />
**mass handling of Control Points, specify areas where (not) to put them<br />
<br />
<br />
== Download Test Build ==<br />
<br />
If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].<br />
<br />
== Build your Own Test Builds ==<br />
<br />
If you are ready to go through the building process, here are the instructions.<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"<br />
|-valign="top"<br />
! '''IMPORTANT:'''<br />
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [http://wiki.panotools.org/Development_of_Open_Source_tools#Packaging_and_Distribution below]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.<br />
|}<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
==== hugin ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2801<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows, used for Windows installer snapshot. Builds on ubuntu 7.10 AMD64<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2797<br />
| style="border-top: thin dotted #333333;" |<br />
builds on OSX, used for OSX snapshot package.<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2766<br />
| style="border-top: thin dotted #333333;" |<br />
Windows self-installing archives. [ftp://tksftp@tksharpless.net] "TKSpwd1"<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2733<br />
| style="border-top: thin dotted #333333;" |<br />
build on OSX. runs on Macs that have no programming packages installed.<br />
|-valign="top" <br />
|}<br />
<br />
[[older hugin revision notes]]<br />
<br />
==== libpano ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
785<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
770<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
767<br />
| style="border-top: thin dotted #333333;" |<br />
does not build [http://groups.google.com/group/hugin-ptx/browse_thread/thread/f69427e3b112bcca]<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
759<br />
| style="border-top: thin dotted #333333;" |<br />
builds on AMD64 ubuntu 7.10<br />
|-valign="top"<br />
|}<br />
<br />
[[older libpano revision notes]]<br />
<br />
==== enblend ====<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-07<br />
| style="border-top: thin dotted #333333;" |<br />
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2008-02-03<br />
| style="border-top: thin dotted #333333;" |<br />
builds on Windows and ubuntu 7.10 x86 32bit<br />
|-valign="top" <br />
|}<br />
<br />
[[older enblend revision notes]]<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
* Régis B.<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | OK]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
* David Haberthür<br />
* John Riley<br />
* Roger Howard<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
*[[Build Hugin for Windows with SDK | OK, SDK based]]<br />
*[[Hugin Compiling Windows | draft, from scratch]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
* Yili Zhao<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
Vasil Dimov, FreeBSD port maintainer<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* confirmed to build on FreeBSD 6.2/i386<br />
* confirmed to build on FreeBSD 7.0/amd64<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
FreeBSD 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
| style="border-top: thin dotted #333333;" |<br />
n/a<br />
<!-- spanned| style="border-top: thin dotted #333333;" | tbd --><br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
== Packaging and Distribution ==<br />
<br />
Instructions for packaging binaries for distribution will follow. Some important points:<br />
<br />
=== Snapshots ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number<br />
* edit the text / readme files that come with the snapshot<br />
** indicate clearly that it is unstable, experimental software<br />
** indicate where to find the latest version<br />
** indicate that the advertised features might or might not work<br />
<br />
=== Release ===<br />
* comply with the GPL<br />
** join a text of the GPL in the distribution<br />
** give access to the source code<br />
** credit the authors<br />
<br />
== Feedback ==<br />
<br />
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!<br />
<br />
To give good feedback, note down carefully all of this information while you are going through the instructions.<br />
# details about your computer. CPU, operating system, other particularities<br />
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.<br />
# the last step / command you entered into the command line<br />
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.<br />
<br />
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try<br />
* to use "make VERBOSE=1" when building hugin.<br />
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.</div>Klaushttps://wiki.panotools.org/index.php?title=Historical:Suggestion_Hugin_Preferences_Workflow&diff=10403Historical:Suggestion Hugin Preferences Workflow2008-05-19T12:29:58Z<p>Klaus: New preferences pane for hugin</p>
<hr />
<div>==Feature proposal from hugin-ptx==<br />
<br />
A new ''Preferences'' pane is suggested for ''hugin'', with input field for saving path for projects and input field for saving panorama(s) (and more input fields for default (saving) path for other "things" like lens parameters?). Radio buttons or drop-down menus would fit the need for choosing 1 out of N options.<br />
<br />
This addition is suggested for hugin 0.7.1<br />
<br />
==Hugin > Preferences > Workflow==<br />
<br />
On hugin startup open on<br />
* Assistant tab<br />
* Images tab<br />
----<br />
New project file<br />
: Save project file dialogue opens on<br />
:* input images directory<br />
:* previous project file directory<br />
: Suggested project file name is<br />
:* blank<br />
:* first_image_name-last_image_name<br />
:* current date and time<br />
----<br />
Specify output prefix<br />
: Dialogue window opens on<br />
:* input images directory<br />
:* project file directory<br />
:* previous output directory<br />
: Suggested output prefix is<br />
:* blank<br />
:* project file name prefix<br />
:* current date and time<br />
<br />
==Explanations==<br />
* Maybe someone can come up with a better name than "Workflow". <br />
* For an existing pto file, the "Save as" dialogue should open with that directory and that name.<br />
* For the output prefix, the suggested name could be (partly) highlighted (possible in OSX), and if one types away, the highlighted default clears. If you want to edit the suggested name, click on it first or use left-arrow or right-arrow as first key stroke.</div>Klaushttps://wiki.panotools.org/index.php?title=User:Klaus&diff=10366User:Klaus2008-05-06T13:22:47Z<p>Klaus: link</p>
<hr />
<div>Hello,<br />
<br />
Since March 2005, when buying a Canon Powershot A95, I did start to actually explore how to combine several photos into a panorama image. First with the program that came with the camera, but very soon I found that lacking in quality, and after a few tries I am now holding onto hugin and enblend.<br />
<br />
I do have earlier photos, for example a photo series in the Chartreuse mountain range of the French Alps that should nicely fit together into a 360 degrees panorama. With photos taken in 1988, I actually had done a hardware cut and paste at the time, but I still have to scan the slides to make a real seamless image on the computer. I also have many more digital photos as raw material which I have not yet turned into panoramas.<br />
<br />
Following the development of the open and free panoramic software, I hope my comments do help of improving these program bundles and maybe I see features implemented I desire, despite myself not engaging into the coding effort - maybe I should brush up my skills there. But (time permitting as always) I am happy to test-run the programs, and also help with postings and maybe tutorial writing.<br />
<br />
Klaus<br />
<br />
some stuff: [[User:Klaus/Stitching 2008 State of the Art]]</div>Klaus