control point generator help needed
Emad ud din Btt
Emaad
www.flickr.com/emaad
Andres
Emad ud din Btt
If you're in a hurry, you could check out Microsoft ICE (google for links)...
--
You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
--
Emaad
www.flickr.com/emaad
Yuval Levy
> I need urgent help for a control point generator that can handle 300 images
> 360x180 architectural panoramas. Please! Mention best possible CP generator
> and also share it's parameters or steps to follow.
if you live in a jurisdiction that is not covered by the SURF patent, you may
want to give Panomatic a try.
To build it [0]
To use it, assuming all your input images are JPG and are in the same folder:
panomatic -o project.pto *.jpg
go have lunch and when you are back open the resulting project.pto file in
Hugin and continue working on it.
Yuv
[0] http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Pan-o-matic
Tom Sharpless
I'm not expert on the problem of aligning large sets of images. But I
can tell you the Hugin CP finders will not handle this either. It is
because they try to find CPs between every possible pair of images,
and the number of possibilities grows too large too fast.
The way to do it with APSCP, etc, would be to process separate groups
of images that actually do overlap, then add all the found CPs to a
project file that names all the images (this would involve changing
the image numbers on the CPs to match the ones in the project). For
example if your pano is in rows and columns, each group might be a
central image and 4 neighbors.
I believe PTGui partially automates this, in that you can select some
images and ask it to just find CPs between those. But I'm not sure it
works for more than 2 images at a time, I've never tried more.
There must be CP finders that can handle your problem, because
stitching gigapixel images from hundreds of photos is now quite a
popular activity. I would start by checking the GigaPan website.
Also I would look for a script (perhaps by Bruno Postle) for doing it
with the Hugin tools.
I keep suggesting that someone should make Hugin do CP finding
intelligently, when the arrangement of the source images is already
known. But so far nobody has volunteered.
Regards, Tom
On Dec 25, 10:42 am, Emad ud din Btt <xyzt...@gmail.com> wrote:
> Andres I have tried ICE before but i dont think it can handle 300 image.
>
> > If you're in a hurry, you could check out Microsoft ICE (google for
> > links)...
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Hugin and other free panoramic software" group.
> > A list of frequently asked questions is available at:
> >http://wiki.panotools.org/Hugin_FAQ
> > To post to this group, send email to hugi...@googlegroups.com
> > To unsubscribe from this group, send email to
> *Emaad*www.flickr.com/emaad
Emad ud din Btt
Emaad
www.flickr.com/emaad
Yuval Levy
> I keep suggesting that someone should make Hugin do CP finding
> intelligently, when the arrangement of the source images is already
> known. But so far nobody has volunteered.
when did you last check Hugin? Thomas Modes has added the multi-row strategy
a while ago...
Yuv
Emad ud din Btt
www.flickr.com/emaad
Emad ud din Btt
Yuval Levy
> I have latest hugin windows build downloaded from thepanz.
you'll find the official ones at
http://sourceforge.net/projects/hugin/files/hugin/
Matthew has been very fast and efficient to produce binaries for Windows, like
Harry for OSX.
Yuv
Emad ud din Btt
Emaad
www.flickr.com/emaad
Tom Sharpless
recent releases it is unable to generate any control points, and
offers no help to understand why. It does present under preferences/
control point detectors a promising-looking option called "Autopano-
SIFT-C (multrow/stacked)". But of course that is not supported by the
files in the release.
Is that what you are talking about? If so, please state clearly:
-- where do I get it?
-- how do I install it?
-- what do I need to know to run it?
What I was talking about would be Hugin actually controlling CP
finding in an intelligent way; behind an intelligible UI that would
let the user specify a 'shooting grid'; the bottom line being
automatic alignment of gigapixel (and smaller) image sets.
Until Hugin ships with the ablility to auto-align a pano, it will
continue to be ignored by a lot of people who could benefit from it.
Andreas Metzler
> On Dec 25, 1:41 pm, Yuval Levy <goo...@levy.ch> wrote:
>> On December 25, 2010 12:38:39 pm Tom Sharpless wrote:
>>> I keep suggesting that someone should make Hugin do CP finding
>>> intelligently, when the arrangement of the source images is already
>>> known. But so far nobody has volunteered.
>> when did you last check Hugin? Thomas Modes has added the
>> multi-row strategy a while ago...
> I have 2010.2.0.d8ce0ba947cc open in front of me. Like most other
> recent releases it is unable to generate any control points, and
> offers no help to understand why. It does present under preferences/
> control point detectors a promising-looking option called "Autopano-
> SIFT-C (multrow/stacked)". But of course that is not supported by the
> files in the release.
[...]
Hello Tom,
Upgrading does not automatically make the new control point detector
presets available. You'd need to either add them manually or use the
[reset to default] button.
If you have autopano-sift-c available, choosing Autopano-SIFT-C
(multirow/stacked) as cp-detector instead of regular Autopano-SIFT-C
should give better (i.e. faster) results.
The heuristics used is described on
http://wiki.panotools.org/Hugin_Parameters_for_Control_Point_Detectors_dialog
Afaict there is no way for the user to simply change the way it works
(except manually for selecting a subset of images in which cps are to
be searched). The heuristics assume that images are sorted this way:
1 2 3 4
5 6 7 8
...
If autopano-sift-c is not available to you the setting obvously will
not work for you. Especially in that case you really should upgrade to
2010.4.0 rc1, which *includes* cpfind.
All this does not fulfill ...
> What I was talking about would be Hugin actually controlling CP
> finding in an intelligent way; behind an intelligible UI that would
> let the user specify a 'shooting grid'; the bottom line being
> automatic alignment of gigapixel (and smaller) image sets.
... but should be an improvement over the
compare-all-images-with-each-other-approach.
hth, cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Jan Martin
1 2 3 4
5 6 7 8
...
--
You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
Yuval Levy
On December 26, 2010 10:11:23 am Tom Sharpless wrote:
> I have 2010.2.0.d8ce0ba947cc open in front of me. Like most other
> recent releases it is unable to generate any control points, and
> offers no help to understand why. It does present under preferences/
> control point detectors a promising-looking option called "Autopano-
> SIFT-C (multrow/stacked)". But of course that is not supported by the
> files in the release.
I guess you are on Windows. "not supported by the files in the release" is a
Windows-specific problem. It may have been solved recently with a better
installer that compensates for Window's lack of package management.
> Is that what you are talking about? If so, please state clearly:
Yes
> -- where do I get it?
> -- how do I install it?
The package manager or installer knows where to get third party CP generators
from and how to install them. From the chatter on this ML I believe the
2010.4 Windows installer has been improved, but I can't tell for sure.
As an extra bonus, 2010.4 will also bring you cpfind. That's Hugin's CP
generator. It is still in its infancy, so you may prefer to use your tried
tested and trusted third party CP generator. icpfind [0] enables the use of
heuristic strategies with third party CP generators.
> -- what do I need to know to run it?
The PTO file is the interface that "tells" cpfind/icpfind about images and
lenses. The strategy is described in [1].
> What I was talking about would be Hugin actually controlling CP
> finding in an intelligent way;
that's the above linked strategy.
> behind an intelligible UI
the *I*nterface is the PTO file. And Hugin is the UI to the PTO file.
> that would let the user specify a 'shooting grid';
I see and understand the need to let the user specify a 'shooting grid'.
Underlying such a 'shooting grid' is a 'shooting sequence'. cpfind/icpfind
builds on that sequence and thus does not really need the grid.
Would a 'shooting grid' optimize CP detection beyond what the 'shooting
sequence' already does? Probably yes, but only marginally. icpfind/cpfind
could go straight on to trying to connect all overlapping images.
Where the grid would help even more is with the optimization; and there it is
already taken into account, again, through the PTO file.
So what is missing is the *UI* part. We already have templates (Menu -> File
-> Apply Template) which covers the most important aspect: repeatabilit.
What is missing is a 'Distribute' function/button on the Images Tab, where the
user can specify the shooting pattern in terms of:
- number of rows
- number of columns
- vertical shooting direction (topdown or bottomup)
- horizontal shooting direction (leftright, rightleft, leftsnake, rightsnake)
- number of brackets
and that function would automatically distribute the hundred of pictures on
the panosphere.
Did I miss something?
> the bottom line being automatic alignment of gigapixel (and smaller)
> image sets.
actually the automatism is already given with the sequence-based heuristic,
and the whole UI would be just added manual intervention to make the process
more robust.
> Until Hugin ships with the ablility to auto-align a pano, it will
> continue to be ignored by a lot of people who could benefit from it.
No intention to stir up controversy but this argument is moot.
Yuv
[0] <http://wiki.panotools.org/Icpfind>
[1]
<http://wiki.panotools.org/Hugin_Parameters_for_Control_Point_Detectors_dialog#Multi-
row_panorama>
Yuval Levy
> For aerial photography, is there a mode that uses the latitude/longitude
> info of geotagged images to place them instead of just assuming a pattern
no, but you can file a ticket with a feature request.
and: the current heuristic probably does not need the pre-placement for CP
detection, but it may help the optimizer later on.
actually the airplane example illustrate a point where the current heuristic
is better than any pattern assumption. if your plane flies randomly no pre-
filled pattern will help. but the sequence of adjacent images assumed by the
current heuristic still works, unless a gremlin hidden in your computer
renamed the files out of sequence.
Yuv
Emad ud din Btt
Emaad
www.flickr.com/emaad
Andres
Offtopic, but for historical correctness
Regards,
Andres
Tom Sharpless
On Dec 26, 1:16 pm, Andreas Metzler <ametz...@downhill.at.eu.org>
wrote:
> > On Dec 25, 1:41 pm, Yuval Levy <goo...@levy.ch> wrote:
> >> On December 25, 2010 12:38:39 pm Tom Sharpless wrote:
> >>> I keep suggesting that someone should make Hugin do CP finding
> >>> intelligently, when the arrangement of the source images is already
> >>> known. But so far nobody has volunteered.
> >> when did you last check Hugin? Thomas Modes has added the
> >> multi-row strategy a while ago...
> > I have 2010.2.0.d8ce0ba947cc open in front of me. Like most other
> > recent releases it is unable to generate any control points, and
> > offers no help to understand why. It does present under preferences/
> > control point detectors a promising-looking option called "Autopano-
> > SIFT-C (multrow/stacked)". But of course that is not supported by the
> > files in the release.
>
> [...]
>
> Hello Tom,
>
> Upgrading does not automatically make the new control point detector
> presets available. You'd need to either add them manually or use the
> [reset to default] button.
>
> If you have autopano-sift-c available, choosing Autopano-SIFT-C
> (multirow/stacked) as cp-detector instead of regular Autopano-SIFT-C
> should give better (i.e. faster) results.
>
> Afaict there is no way for the user to simply change the way it works
> (except manually for selecting a subset of images in which cps are to
> be searched). The heuristics assume that images are sorted this way:
>
> 1 2 3 4
> 5 6 7 8
> ...
>
> If autopano-sift-c is not available to you the setting obvously will
> not work for you. Especially in that case you really should upgrade to
> 2010.4.0 rc1, which *includes* cpfind.
>
use the 2-step finder (from a previous build) and set it to work on a
20 x 2 array, shot with a 50mm lens. After 7 minutes 30 sec it
reported 11 unconnected groups. One of those contained the complete
upper row, several others were correctly aligned segments of the lower
row (which is mostly water). Then I tried the "all images at once"
option. It took about 13 minutes but produced a better result: 14
images in one connected group, plus six disconnected images. Under
the same option, the one-step apsc crashed (out of memory) in the
matching stage.
PTGui aligned this set in 2 min 30 sec, leaving 4 disconnected images
in the lower row.
I will repeat once more and then shut up: Hugin's CP finding is a
disgraceful mess, which prevents me -- and I expect many others --
from using this otherwise excellent stitcher. At the very least,
there must be a web page that spells out how to get and use the
various finders now available. I am sick of hearing "oh, that is
patented, so we can't talk about it." Yes You Can.
At best, someone will put together a distributable package that 'just
works'.
Best for 2011, Tom
Yuval Levy
> Well, I configured the "Autopano-SIFT-C (multirow/stacked)" option to
> use the 2-step finder (from a previous build) and set it to work on a
> 20 x 2 array, shot with a 50mm lens.
and how does 2010.4 with cpfind (not Autopano-SIFT-C) perform on that same set
of 20x2 images?
> I will repeat once more and then shut up: Hugin's CP finding is a
> disgraceful mess
No. You should not judge Hugin by the performance of third party tools. If
you want to complain about Hugin, please try cpfind first. Comments,
discussion, critique, feedback, improvements to cpfind are welcome. And if
you find cpfind to be a "disgraceful mess", we'll take notice.
> At the very least,
> there must be a web page that spells out how to get and use the
> various finders now available.
You (and anybody interested) are welcome to create such a page. The Panotools
wiki is a good place to host it. Hugin has nothing to do with it.
> I am sick of hearing "oh, that is
> patented, so we can't talk about it." Yes You Can.
Patents don't prevent talking. There is a lot of talk around, e.g. in this
very same thread with Panomatic and Microsoft ICE suggested to Emaad as
potential solutions to his CP finding needs. And if these tools do the work
for you, please use them...
> At best, someone will put together a distributable package that 'just
> works'.
... but don't ask others to contravene to SourceForge's terms and conditions
or to take legal risks to satisfy your wishes. Patents do prevent
distribution.
Although, distribution is mainly prevented by technical inferiority. If your
operating system had proper packet management, you would not be complaining
about "bad packages". You're barking up the wrong tree.
Yuv
Emad ud din Btt
Can anyone, explain how CPfind works. I have allowed CPfind to work for hours but it keeps iterating.
"
Emaad
www.flickr.com/emaad
kfj
On 27 Dez., 10:24, Emad ud din Btt <xyzt...@gmail.com> wrote:
> My second question is....Control point generation is most important part of
> panorama creation. So Why we cant work or discuss over it?
> When we talk about PTgui, Autopano or other commercial softwares, we assume
> its a full package and CP generation is part of it.I am not into comparisons
> here but you will admit CP generation is essential part of Panorama creation
> softwares.
them in some projects. You can easily create them manually. But often
- not always - the input lends itself to automatic CP generation and
the CPGs do a good job. It's an area where there is a great wealth of
tools available. See, amongst others:
http://autopano.kolor.com/
http://aorlinsk2.free.fr/panomatic/
http://user.cs.tu-berlin.de/~nowozin/autopano-sift/
CPGs work, but there are strings attached:
- you may have to invest some effort in obtaining, installing and
interfacing to them
- you may have to learn how to use them - most are actually
documented, some of them even quite thoroughly, and especially on
Windows you have a very good selection, but they may not work for you
'out of the box' with standard parameters.
- you may not be allowed to use them commercially, due to software
patent issues
- finally, no CPG can work if the input isn't suitable, so sometimes
failing to get CPs from a CPG throws a light on flaws in your
photography.
Kay
Yuval Levy
On December 27, 2010 04:24:02 am Emad ud din Btt wrote:
> Yuv, I have reported CPfind experience in my last email.
>
> "I have tried CPfind. It worked great for two projects. It added CPs for
> 217 images in 1008 seconds. I used default 10 cp settings. It even added
> its max 50 cps per image to these 217 images in very short time. But I
> dont know why its not working like that now for even smaller number of
> images. It goes on iterating again and again. Than keep displaying
> strategies and than back to iteration process. My previous experience with
> autopano sift c is somewhat same. It also keeps iterating even if you
> leave it for 24 hours. I have tested
it is impossible to help you / come to a conclusion from what you describe
above. If I understand correctly: cpfind and autopano-sift-c work for the
same large set of images and don't work for a smaller set of images? can you
make the smaller set of images available?
if two cp generators fail the same images set, an issue with the input images
should be considered/tested. you could try other CP generators on the same,
failing set of images.
also: did you try cpfind and autopano-sift-c from the command line? just to
exclude an unrelated GUI freeze/problem, I'd run the tests from the command
line.
> Can anyone, explain how CPfind works.
http://wiki.panotools.org/Cpfind
> Please! Read my email and help me.
It's a two way street. Can't help you without your help.
> My second question is....Control point generation is most important part of
> panorama creation. So Why we cant work or discuss over it?
Is CP generation really the most important part of panorama creation? I don't
think so. Image alignment is certainly crucial, but there are other ways to
align images than by generating CPs (manual or generated) and optimizing CPs.
> When we talk about PTgui, Autopano or other commercial softwares, we assume
> its a full package and CP generation is part of it.I am not into
> comparisons here but you will admit CP generation is essential part of
> Panorama creation softwares.
Panorama creation is a _workflow_ not a _software_.
There is more than one workflow to create panoramas, and while CP generation
is 'essential' to _your_ workflow, it was not to the workflow underlying the
creation of [0]; and it is certainly not essential part of any software.
It is wrong to assume that CP generation _must_ be part of any software just
because there are software that you deem to be 'full packages'. What is the
definition of 'full package' anyway?
Following your logic, you will admit that blending is 'essential part of
Panorama reation softwares'. And yet Enblend is not part of Hugin. Those are
two separate distinct packages. Hugin must redistribute Enblend with the
Windows installer to palliate a major design fault in the Windows operating
system: it does not have a package manager. In systems with package manager,
all Hugin has to do is 'tell' the package manager that it needs Enblend.
Applying the same logic to the CP generation, it would make sense for the
Hugin Windows installer to distribute a CP generator because it can't simply
'tell' the package manager that it needs one. Unfortunately the
(re)distribution of most CP generators is encumbered by patents. Blame it on
the patent holders and on the legal system in which we operate (SourceForge is
located in the United States).
Even if one or many software packages do cover what you think is essential to
your workflow, it is wrong to expect any other software package to do the
same. Your workflow is your responsibility, not the responsibility of the
software package or its authors.
The performance and bugs of third-party tools is not the responsibility of
those developing, building, packaging or distributing Hugin. Feel free to
discuss them, but don't expect them to be part of Hugin, nor for Hugin
developers to take responsibility for them.
Yuv
Emad ud din Btt
above. If I understand correctly: cpfind and autopano-sift-c work for the
same large set of images and don't work for a smaller set of images? can you
make the smaller set of images available?
exclude an unrelated GUI freeze/problem, I'd run the tests from the command
line
There is more than one workflow to create panoramas, and while CP generation
is 'essential' to _your_ workflow, it was not to the workflow underlying the
creation of [0]; and it is certainly not essential part of any software.
those developing, building, packaging or distributing Hugin. Feel free to
discuss them, but don't expect them to be part of Hugin, nor for Hugin
developers to take responsibility for them.
Emaad
www.flickr.com/emaad
kfj
On 30 Dez., 10:02, Emad ud din Btt <xyzt...@gmail.com> wrote:
> hugin alling.JPG
With images like that, you're asking for trouble. Your images are
narrow-angle, and the content is often barely more than blank walls or
featureless surfaces. You can't reasonably expect a CP generator to
find CPs in this situation. If you force it to produce it's best shot
guess at what CPs might be there, it will likely come up with plenty
of false CPs. Then you can't optimize the thing. I recommend you to
buy a fisheye lens if you want to make indoor panoramas like this -
with a wider angle lens you at least have a chance to have enough
overlapping content in successive images.
Kay
Yuval Levy
We had a major change of plan here because of the weather, so I can only
answer you short.
You were complaining about cpfind and autopano-sift-c hanging indefinitely.
But the screenshot you sent me tells me that the problem lies somewhere else.
Also, I see in your taskbar that there are three Hugin windows open. One is
the fast preview (screenshot). One is the main window. And the third one?
The screenshot you send shows an optimization issue, not a CP generation
issue. Optimization is a garbage-in garbage-out process, and bad CPs may well
be the 'garbage-in'.
Let's try to go at this one step at a time, together. OK?
I want you to start an empty instance of Hugin.
Go into the Images Tab and hit on the "Add individual images" tab.
Add all of your images.
Save this project as step1.pto.
Start a command line in the same folder where you saved step1.pto and issue
the command:
cpfind -o step2.pto step1.pto
Post step1.pto and step2.pto to this mailing list.
Thanks
Yuv
Emad ud din Btt
answer you short.
But the screenshot you sent me tells me that the problem lies somewhere else.
Emaad
www.flickr.com/emaad
Emad ud din Btt
Emaad
www.flickr.com/emaad
Yuval Levy
Python. Attached (for Kay).
Now to Emaad:
On January 1, 2011 02:09:25 am Emad ud din Btt wrote:
> Hi Yuv,
>
> CPfind has added cps to images now. It took 5997.08 seconds = 1.67 hours
> from command line. I am sending pto files with this email. Please! Check.
I started checking. Then I realized that this is a waste of time.
How can you expect such a messy input to result in anything else but garbage?
You need to clean up your files; be more precise in your statements; and learn
to quote properly; before you can expect any help.
FILES:
There are 173 images in the projects you attached. These images belong to at
least two categories, if not three:
* 76 are JPG images that seem to be out of camera JPGs
* 97 are TIFF images that from their file names seem to be the result of some
enfusion
* of the 97 TIFF, some seem to be duplicate (e.g. PC180070_enfused_1.tif and
PC180070_enfused) and some seems to be enfused multiple times (e.g.
PC180139_enfused_enfused.tif)
clean up! either load only one set of enfused images; or one set of JPG
images. If the input is incomplete or garbage, you can't expect anything but
garbage in return. Don't blame it on Hugin, on cpfind, on autopano-SIFT-C, or
on anything that is not between the back of your chair and your keyboard.
CPFIND:
cpfind has "successfully" connected the 173 images with 26007 points. I don't
have the actual images and can't judge the quality of those points, but there
are definitely too many. It is garbage-in garbage out. Before doing anything
you need to clean up the input images mess.
STATEMENTS:
You stated in [0] that "It also keeps iterating even if you leave it for 24
hours.". You stated this in relationship with CPfind and with Autopano-SIFT-
C.
You need to understand that once the CPs are generated, it is no longer CPfind
or Autopano-SIFT-C. It is the Optimizer. And given the garbage fed into it,
I don't blame the Optimizer for not coming up with anything meaningful.
Even if those were 26K real CPs, you would be competing for the largest
gigapixel pano ever (assuming a recent full frame camera and 20% image
overlap). No wonder your computer churns for hours and hours.
This is not the first time that you are looking for help on this mailing list
and make unclear statements about what went wrong [1]. This is not helpful,
nor is it respectful of the time of those trying to help.
Moreover, your quoting is poor and makes it difficult to follow/understand a
thread with you. Please next time quote properly.
I have now wasted about half hour of my time to try to understand you.
If you want a reply from me in the future, you need to improve massively on
your end. You need to clean up your files; be more precise in your
statements; and learn to quote properly; before you can expect any help.
Until then, I will ignore you / your posts.
Yuv
[0] http://groups.google.com/group/hugin-ptx/msg/9fc8f88d2ab211f7
[1] http://groups.google.com/group/hugin-ptx/t/c1f8d1d51e9f455a
kfj
On 1 Jan., 20:32, Yuval Levy <goo...@levy.ch> wrote:
> First: I updated the ptoimggen.py script to deal with Windows paths. I love
> Python. Attached (for Kay).
a Unix machine, ptos coming from Windows users will be properly
treated. But it makes the script non-portable. How about a Windows
user wanting to process a pto from a Unix machine?
name = os.path.basename ( line.n.value.replace ('\\', '/') ) +
'_dummy.jpg'
will only work one-way.
I think the best solution might be to use
name = re.sub ( '.*[/\\]' , '' , line.n.value )
which discards everything up to the last slash or backslash. What do
you say?
Kay
Yuval Levy
> name = re.sub ( '.*[/\\]' , '' , line.n.value )
>
> which discards everything up to the last slash or backslash. What do
> you say?
that you're the Python King and I have been away from Windows for too long to
care ;-)
well done, Kay.
Yuv
Bruno Postle
>
> With images like that, you're asking for trouble. Your images are
> narrow-angle, and the content is often barely more than blank
> walls or featureless surfaces. You can't reasonably expect a CP
> generator to find CPs in this situation.
One way of working around this is to mark the blank areas of walls
temporarily with post-it notes or similar. These help aligning the
shots and can easily be painted out after stitching.
--
Bruno
Emad ud din Btt
There are 173 images in the projects you attached. These images belong to at
least two categories, if not three:
* 76 are JPG images that seem to be out of camera JPGs
* 97 are TIFF images that from their file names seem to be the result of some
enfusion
* of the 97 TIFF, some seem to be duplicate (e.g. PC180070_enfused_1.tif and
PC180070_enfused) and some seems to be enfused multiple times (e.g.
PC180139_enfused_enfused.tif)
images. If the input is incomplete or garbage, you can't expect anything but
garbage in return. Don't blame it on Hugin, on cpfind, on autopano-SIFT-C, or
on anything that is not between the back of your chair and your keyboard.
cpfind has "successfully" connected the 173 images with 26007 points. I don't
have the actual images and can't judge the quality of those points, but there
are definitely too many. It is garbage-in garbage out. Before doing anything
you need to clean up the input images mess.
You stated in [0] that "It also keeps iterating even if you leave it for 24
hours.". You stated this in relationship with CPfind and with Autopano-SIFT-
C.
You need to understand that once the CPs are generated, it is no longer CPfind
or Autopano-SIFT-C. It is the Optimizer. And given the garbage fed into it,
I don't blame the Optimizer for not coming up with anything meaningful.
Even if those were 26K real CPs, you would be competing for the largest
gigapixel pano ever (assuming a recent full frame camera and 20% image
overlap). No wonder your computer churns for hours and hours.
This is not the first time that you are looking for help on this mailing list
and make unclear statements about what went wrong [1]. This is not helpful,
nor is it respectful of the time of those trying to help.
Moreover, your quoting is poor and makes it difficult to follow/understand a
thread with you. Please next time quote properly.
I have now wasted about half hour of my time to try to understand you.
If you want a reply from me in the future, you need to improve massively on
your end. You need to clean up your files; be more precise in your
statements; and learn to quote properly; before you can expect any help.
Until then, I will ignore you / your posts.
Yuv
Emaad
www.flickr.com/emaad
kfj
On 2 Jan., 22:10, Yuval Levy <goo...@levy.ch> wrote:
> > name = re.sub ( '.*[/\\]' , '' , line.n.value )
>
> that you're the Python King and I have been away from Windows for too long to
> care ;-)
I've used it long enough to feel for it's users.
I've made the change to ptoimggen.py and beautified the script, also
added an option to name a specific output. See
http://bazaar.launchpad.net/%7Ekfj/%2Bjunk/script/annotate/head%3A/main/ptoimggen.py
Kay
Yuval Levy
On January 3, 2011 03:43:41 am Emad ud din Btt wrote:
> Here is my reply
http://groups.google.com/group/hugin-ptx/msg/6551ccc0aca0f842
can you distinguish between quoted text and reply? I can't. please start by
quoting properly.
> Until then, I will ignore you / your posts.
> Yuv
>
> Emotions are everywhere one must be gentle. I have explained myself very
> well in a fair tone. But language you used is very harsh and insulting. You
> can have difference of opinion but that does not give you right to use such
> language on such forums. This is also not first time I have to face such
> bad language from you. But I said nothing. If you don't like something or
> do not want to do something than its your right to do so.
>
> You reply to my post or ignore me or you do whatever. But be GENTLE.
no intention to offend you, but I also have no time to embellish text. please
don't read emotions where there are no. electronic communication leaves a lot
of void between the lines and readers fill them... with their own imagination
and emotions. a writer can trigger emotions in his readers, but that does not
mean that he feels those emotions. some writers are really good at
deliberately controlling the emotion they trigger. others (like me) are not.
so i have triggered a bad emotion in you, sorry. was not my intention.
afaik nobody has yet invented the emotion-reading email client.
this is not the first time I am trying to give you advice, and it is not the
first time that I get the impression that the advice does not lead to the
expected results, which i believe are the same for you and for me: helping
you make the best out of Hugin. As I stated repeatedly, it is not possible to
help you based on wrong / incomplete statements; and it is not possible to
help you without proper communication / feedback channel.
try again
Yuv
Emad ud din Btt
Emaad
www.flickr.com/emaad
Dale Beams
E-Mail me privately, or chat with me on IRC and I'll see if I can help you.
Dale
Date: Sun, 9 Jan 2011 12:39:19 +0500
Subject: Re: [hugin-ptx] Re: control point generator help needed
From: xyz...@gmail.com
To: hugi...@googlegroups.com