Re: [hugin-ptx] Hugin-2011.2.0_rc3 released

2011-08-21 Thread Allan Seidel
Hello Luval,

I filed a new report.

OS X Hugin reassigns Completed PTBatcherGUI queue list
processeshttps://bugs.launchpad.net/hugin/+bug/830655

Allan


On Tue, Aug 16, 2011 at 7:24 AM, Yuval Levy goo...@levy.ch wrote:

 Hi Allan,

 On August 16, 2011 07:38:12 am AKS-Gmail-IMAP wrote:
  There remains something fundamentally wrong with how new stitch
  processes are added to PTBatcherGui in OS X.

 Thank you for testing and for your feedback.


  Do I need to open a specific bug entry for this or is there
  one already?

 If what you observe prevents consistently OS X 10.5 from stitching, you can
 add your observations to the existing ticket [0].


  There may be much to describe the symptoms and the
  conditions needed to see them. Vary the names and sizes of added
  stitch processes for the same project to observe the symptoms.

 If what you observe is applicable only to specific situations that needs to
 be
 triggered, I would recommend opening a new ticket [1].  It seems to me that
 this is the case, and that you have done a very thorough job at documenting
 it.  This makes the new ticket even more valuable.

 Thanks!
 Yuv


 [0]: https://bugs.launchpad.net/hugin/+bug/697039
 [1]: https://bugs.launchpad.net/hugin


-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Re: [hugin-ptx] Re: 20110623 hugin-mac-2011.1-5322_5c296e79fe54-build2 (NO 2011.2 beta build)

2011-07-01 Thread Allan Seidel
I was seeing this only when from the Assistant tab.

On Fri, Jul 1, 2011 at 12:12 PM, Harry van der Wolf hvdw...@gmail.comwrote:


 Hi Allan and George,

 Thanks for testing.
 By now I have the idea that there is a bug in ptbatcher on OSX as somehow
 the queue status is constantly reset.

 I will file a bug in the bug tracker.

 Harry

 --
 You received this message because you are subscribed to the Google Groups
 Hugin and other free panoramic software group.
 A list of frequently asked questions is available at:
 http://wiki.panotools.org/Hugin_FAQ
 To post to this group, send email to hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx


-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Re: [hugin-ptx] Re: 20110623 hugin-mac-2011.1-5322_5c296e79fe54-build2 (NO 2011.2 beta build)

2011-06-30 Thread Allan Seidel
I tested this version on Tiger running on an Intel. It functions just like
it does on the PPC 10.5.8.

On Thu, Jun 30, 2011 at 6:56 PM, grow george...@gmail.com wrote:

 Harry,

 Thanks for this version.

 You may have seen me commenting on another thread - about getting
 caught again by an old preferences file.   I should have learned as
 that tripped me up once before!   Anyway once I got rid of the old
 preferences things went a lot more smoothly.

 Later I ran into some other (small) problems with PTBatcherGUI.

 When I am in a cycle of stitch-- adjust -- stitch again ...  I tend
 to hit the stitch button and save the output files each time with a
 slightly different name and into a new folder.  When I do this  the
 previous batches seem  to always:
   a) remain in PTBatcher's batch list
   b) restart when I try to start a new stitch
   c) provoke  a  pop-up dialogue with Overwrite Files ... OK

 The problem is that if you have run a stitch saving the intermediate
 output files the list of files to be overwritten just gets longer and
 longer with the dialogue window stretching to accommodate the list.
 Eventually the bottom of window goes off the bottom of the screen
 taking the buttons with it.  This leaves the user with no way of
 responding other than to Force-Quit the batcher and then relaunch and
 tidy up the batch before proceeding.

 all the best

 George

 On Jun 23, 9:27 pm, Harry van der Wolf hvdw...@gmail.com wrote:
  Hi mac users,
 
  Another OSX developmesnt build. This is NOT a 2011.2.0 beta build. I'm
 still
  struggling with the PTBatcherGui concept to work on all platforms with
  parameters. If this works I will apply it to the trunk for the following
  beta build.
 
  What's changed:
  - removed Snow Leopards open from the bundle again.
  - I switched to a 2 step approach: Make a standard open call to open the
  PTBatcherGui.app bundle needed for a bundle instance running, after 3
  seconds followed by a linux like call directly to the PTBatcherGui
 binary
  to add the project with all necessary parameters. It's a horrible
  work-around but I think it will work and on all platforms.
  - Still no python.
 
  Charlie Reiman gave me a hint how it could be done as well in a much
 better
  way (for those who followed the discussions), but for the time being it
 has
  reduced functionality. Hopefully we can improve that at a later stage.
 
  Information and binaries via my website
  
 http://panorama.dyndns.org/index.php?lang=ensubject=Hugintexttag=Hugin.
  (The binaries themselves are served from hugin.panotools.org who kindly
  provide the disk space and bandwidth).
 
  Hoi,
  Harry

 --
 You received this message because you are subscribed to the Google Groups
 Hugin and other free panoramic software group.
 A list of frequently asked questions is available at:
 http://wiki.panotools.org/Hugin_FAQ
 To post to this group, send email to hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx


-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Re: [hugin-ptx] Re: Hugin-2011.0.0_rc1 released

2011-05-23 Thread Allan Seidel
Perhaps these have been mentioned before. I am seeing problems in the
Control Points tab. For example when starting to pick a point on the left
side image a duplicate version of that image appears at the bottom of the
frame and the right image enlarges a bit, overflowing the original space
allocated for that image. Also, the operation to move a control point is not
usable. The point does not appear to move.

Allan

On Mon, May 23, 2011 at 12:42 AM, Harry van der Wolf hvdw...@gmail.comwrote:

 Hi, Yuv,

 2011/5/22 Yuval Levy goo...@levy.ch

 On May 22, 2011 12:32:43 PM Harry van der Wolf wrote:
  As always: Information and binaries via my website
  
 http://panorama.dyndns.org/index.php?lang=ensubject=Hugintexttag=Hugin
 .
  (The binaries themselves are served from hugin.panotools.org who kindly
  provide the disk space and bandwidth).

 should we wait a few days for test reports about this binary before
 declaring
 2011.0.0 final?


 Yes, please wait a few days. I assume it will be OK apart from the
 stitching error on 10.5 Leopard (18-19% of the users) which still requires
 the work around to push the project to PTBatcherGui. It does work on 10.4
 and 10.6. We've tried so much options and nothing works. I'm afraid it will
 remain a known bug  for this release.


 so far there have been no negative reports from other platforms.

 I would like to close 2011.0.0 and move on to 2011.2.0 - python scripting.


 Yes. That will be the next challenge: to get it working on OSX.


 Thanks
 Yuv


 Thanks for your ongoing support to get a new release out.

 best,

 Harry

 --
 You received this message because you are subscribed to the Google Groups
 Hugin and other free panoramic software group.
 A list of frequently asked questions is available at:
 http://wiki.panotools.org/Hugin_FAQ
 To post to this group, send email to hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx


-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Re: [hugin-ptx] Re: Towards a non-patented control point detector

2010-02-26 Thread Allan Seidel
Thanks Aron. This fix solved three weeks of problems.

On Thu, Feb 25, 2010 at 11:24 AM, Aron H aron.hel...@gmail.com wrote:

 Changes:
   Pablo, there seems to be a typo in the CMakeModules/
 FindVIGRA.cmake, line 21
 FIND_LIBRARY( VIGRALIBRARIES
 needs to change to
 FIND_LIBRARY( VIGRA_LIBRARIES



-- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: [OSX] hugin-mac-2009.4.0-Beta1 for download

2009-10-07 Thread Allan Seidel
Does a change to the Celeste parameters in preferences result in better
performance for these images without removing desirable points? There are
also people in these images. Sometimes they are also like clouds. By the
way, from my perspective I am struck by the total absence of litter and
excess body weight in these images.

Allan
On Wed, Oct 7, 2009 at 6:55 AM, grow george...@gmail.com wrote:


 Allan,

 Thanks.

 I tried the JPEGs on my machine and just as you had found ...
  Auto-pano-sift created 35 control points and Celeste removed the 32
 of them that were on the clouds.
 So then I created two 8-bit TIFF files and again Auto-pano-sift
 created 35 control points and Celeste removed the 32 of them that were
 on the clouds.

 So then I loaded the original 16-bit TIFF files and Auto-pano-sift
 again created 35 control points BUT this time Celeste removed only 9
 of them.  I took screen captures and can see no pattern.

 The screens are here

 http://hugin-ptx.googlegroups.com/web/GR__BeforeCeleste.jpg?hl=en-GBgsc=KotfnAsgkA1LQtdhBzYiUCK1XXkP
 and here:

 http://hugin-ptx.googlegroups.com/web/GR_after1stCeleste.jpg?hl=en-GBgsc=KotfnAsgkA1LQtdhBzYiUCK1XXkPand

 as I said I can’t see much pattern to the cloud-control-points removed
 and those that remain.

 So it seems that Celeste is not as good at removing control points on
 16-bit TIFF images.

 all the best

 George

 On 7 Oct, 03:52, AKS-Gmail-IMAP aksei...@gmail.com wrote:
  OSX hugin-mac-2009.4.0-Beta1 on this G4 removed all 64 control points
  autopano-sift-c had matched on the clouds in your two jpg photos.
 
  Allan
 
  On Oct 6, 2009, at 9:00 PM, grow wrote:
 
 
 
 
 
   OK,
 
   Here they are:
  
 http://hugin-ptx.googlegroups.com/web/5-of-9_IMG_0052.jpg?hl=en-GB
  
 http://hugin-ptx.googlegroups.com/web/4-of-9_IMG_0049.jpg?hl=en-GB
 
   As for the other error - the crashing Enblend  running out of memory -
   I re-ran the stitch at 10,000 x 5,000 and it worked OK  ... I can live
   with that.
 
   all the best
 
   George
 
   On 7 Oct, 01:18, Yuval Levy goo...@levy.ch wrote:
   hi George,
 
   try with high quality JPEG. if we can't reproduce the error, you can
   always upload the heavier TIFFs in a second time.
 
   thanks for your effort
   Yuv
 
   grow wrote:
   Bruno,
 
 Can you upload these two photos somewhere?
 
   I am happy to do so ... at present they are 16-bit TIFF files and
   are
   each 70+Mb ... do you think that their size/resolution/TIFF-ness
   might
   would be significant?  If so I can upload them onto one of my sites
   and provide a link ... if not and high-quality JPEGs would do I
   could
   make those and upload them here.
 
   all the best
 
   George
 
   On Oct 6, 8:56 pm, Bruno Postle br...@postle.net wrote:
   On Tue 06-Oct-2009 at 07:18 -0700, grow wrote:
 
   This should probably have gone on a thread about Celetse  ...
   but I am
   working on that panorama I mentioned with the current Beta and
   have
   found that I don't  seem to  to have the sort of clouds that
   Celeste
   recognises.
   This could be a problem with celeste as you say, or something wrong
   with the build or installation.  Can you upload these two photos
   somewhere?
 
   --
   Bruno
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---



[hugin-ptx] Re: Control point generation in difficult conditions - some success

2009-09-25 Thread Allan Seidel
I also tried a similar method with GIMP on your photos using other filters
such as unsharp mask with the same substitution idea in mind. Match points
were found, but they tended to be on the upper elements that would introduce
parallax errors when used as match points. It seems to me that for these
photos you need to match to elements occurring only in the narrow band in
the middle of each image that is directly below the camera while also
cropping each image in Hugin so that only that middle portion is used for
the final image. It looks like reliable matching would be possible in these
images if the auto process were to compare large areas for matching instead
of small areas. Perhaps the processes have a variable to control this.

Allan
On Fri, Sep 25, 2009 at 3:56 AM, Oskar Sander oskar.san...@gmail.comwrote:

 I made a workaround with some sucess that I have yet to try on a bigger
 scale than on two pictures. Have a look at this project [1].

 I pre processed the photos using Adbe lightroom.   I made quite radical
 adjustments:
Sharpening 91 at radius 1.0
Exposure +0.4 EV
Contrast  +100

 Doing this, APC finds 11 CP instead of 0.  Of which 2 were completely off,
 but they are excluded automatically if ransac is used, see [1].

 To the human eye (mine:-) the selected CP doesn't use the obvious and most
 prominent features, but this is still good progress!

 My idea is to run CP finding on preprocessed images, and then substitute
 these for the originals before the stich step.

 I'd like to understand the APC inner working better though, maybe there are
 potential improvements. I've been peeking a bit in the code of APC and the
 LoweFeature detector. It seems to look for contrast rich areas, is it using
 the colour channels separately or luminance?  Any suggested reading?

 Dale, there is a reference to layout mode in the parameter list, but that
 may be one not-yet-working feature of APC (right?)



 [1]
 http://sites.google.com/site/thebigo1984/mosaiks/UW_low_contrast_workaround.zip?attredirects=0

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---



[hugin-ptx] Re: Changing [OSX] hugin-mac AutoCP parameters is possible.

2009-09-10 Thread Allan Seidel
Hello Harry,

I thought OS X users should know that they could change the plug-in
parameters. Your idea to save multiple parameter versions for the same
plug-in type is a great idea. If it were me creating the Hugin interface I
would not have the parameter settings accessible only in Peferences. I'd
have the setting available in the context where it is used. In other words
the parameters would be visible and easily changed with a double click on
their representation.  One way to do this would be to have the Peference
pane openable to the settings location upon that double click. That same
concept could be applied througout Hugin where applicable.

I don't know how the different os packages are created. It seems to me
that one can code the parameter less plugin concept without needing to
change the current the OS X plug-in structure. Hugin knows all about these
plug-in files. It can easily read each plug-in's argument line, report it in
Peferences and then alter the argument if needed.

Allan


On Tue, Sep 8, 2009 at 12:20 AM, Harry van der Wolf hvdw...@gmail.comwrote:



 2009/9/8 AKS-Gmail-IMAP aksei...@gmail.com



 Harry van der Wolf wrote regarding the plug-in method for AutoCP
 matchers used in the OS X implementation:


   The disadvantage of Ippei's

 implementation is that you can't change parameters which you can with
 Thomas

 solution.



 Ah but Harry you can change easily the parameters for the OS X AutoCPs.
  In each of the OS X AutoCP packages is an XML property list plist file
 called Info.plist.  OS X will open that file using the Property List Editor.
 Using the editor you may change the HginAutoCPArgs key to be anything you
 want. You may even keep the plist open after saving the change so to quickly
 change the arguments for the next AutoCP run.

 Allan


 Hi Allan,

 Thanks for your reply. I know that you can do that as I myself created a
 couple of them after the first release by Ippei.
 The same plist editor also gives you the chance to change the name
 displayed inside hugin. So you can copy them, change the parameters and
 displayed name and you have a new plugin
 The problem is that many users simply don't know where these plugins are or
 how to open them.

 I want to look into the option where we have parameter less plugins that
 can be selected and configured from the new Preferences panel.
 That leaves you with only one plugin per AutoCP creator, but you can call
 it many times based on the settings.

 Harry

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---