| View previous topic :: View next topic |
| Author |
Message |
maxlyons
Joined: 20 Jun 2003
Posts: 3347
Location: USA
|
 Posted: Thu Jul 30, 2009 7:31 pm Post subject: PTAssembler 5.1 beta 1 |
 |
|
All,
I have just posted a beta version of PTAssembler 5.1. Changes include support for Panomatic (a fast control point picker program), numerous speed improvements to the GUI, ability to delete intermediate TIFF files, and several bug fixes/refinements. A detailed list of the main changes in this release is at the end of this post.
I have not yet updated the documentation, but will do so before creating a final release of PTAssembler 5.1.
Download here.
As always, feedback is encouraged and welcomed. I'm particularly interested in hearing about bugs and/or problems that you encounter.
Max
Feature: Added support for Panomatic as a control point picker plugin.
Empirical testing suggests that Panomatic works well with very large
numbers of images, assuming enough memory is available. 2GB seems
more than sufficient for projects with 150+ images sized at 15 megapixels
each. Panomatic seems to run quickly for small/medium sized
projects and generates very well distributed control points.
See: http://aorlinsk2.free.fr/panomatic/?p=home to download Panomatic.
Feature: Numerous GUI speed enhancements. Redesigned several time intensive
operations such as reading/writing project and script files, displaying
control point information, thinning images, etc. PTAssembler should
feel more responsive and operate more quickly...particularly noticeable
for projects containing large numbers of images and/or control points.
Feature: Added option (behavior tab of preferences screen) to remove
intermediate files when creating blended TIFF output.
Bug Fix: Corrected problem that could produce incorrect statistics
about control point information on Step 1 screen.
Bug Fix: Fixed Autocreate so that it requests the number of control
points specified by user on Autocreate tab. (Note the number of control
points cannot be accurately specified for all three supported control
point picker programs, so PTAssembler tries to request the specified
number as best as possible, depending on which control point picker
program is used).
Bug Fix: Corrected problem displaying incorrectly positioned image on
preview screen after deleting a control point.
Bug Fix: Corrected operation of option to "Auto-detect stacking groups,
and perform stacking" during Autocreate. This was not working
correctly. Autocreate also performs "thin by stack ID" operation
when stacking groups are identified.
Change: Updated Control Point Picker configuration screen and changed
default options for some control point picker programs. Note that
when running control point picker program manually (i.e. not via autocreate),
you can specify the number of points to create by modifying the command
line options for the appropriate program. Consult the documentation
for the control point picker program to learn how to specify the number
of points to request.
Change: Removed option (behavior tab of preferences screen) not to show
control point info on step 1 screen.
Change: Removed option (autocreate tab of preferences screen) to specify
maximum control point placement error. Wasn't implemented correctly,
and this can be specified by modifying the command line options for the
appropriate control point picker program (see documentation for
control point picker program).
|
|
| Back to top |
|
 |
Terrywoodenpic
Joined: 06 Mar 2006
Posts: 350
Location: Saddleworth England
|
| Posted: Fri Jul 31, 2009 6:04 am Post subject: |
|
|
Max I am being thick as usual.
I have downloaded the new 5.1 PTAssembler and also Panomatic
I have directed Pta to the location of Panomatic. see screen shot.
should there be something in the command line arguments.
As I can not get it to produce points when I start auto create.
Regards Terry
_________________
Terry
After 60 + years in photography, Now Down sized to Canon G6 Digital and Olympus OM1n film cameras, and accessories. Now up sized/added a Canon 40D and minolta G600 |
|
| Back to top |
|
|
maxlyons
Joined: 20 Jun 2003
Posts: 3347
Location: USA
|
| Posted: Fri Jul 31, 2009 7:50 am Post subject: |
|
|
| Terrywoodenpic wrote: |
I have downloaded the new 5.1 PTAssembler and also Panomatic
I have directed Pta to the location of Panomatic. see screen shot.
should there be something in the command line arguments.
As I can not get it to produce points when I start auto create. |
Terry,
I can't tell from the screenshot what you've specified as the location (the text box isn't long enough for your path). Can you post your installation information? You don't need to have anything specified in the command line arguments...it should run correctly without any additional arguments.
What happens when you start auto-create? Are there any errors/messages? Does Panomatic run, but fail to generate points, or does it not even start executing? Does Panomatic work when you select two or more images and click the (now inappropriately named) "Autopano selected" button on the step 1 screen?
Finally, can you run Panomatic from the command line?
Thanks,
Max
Last edited by maxlyons on Fri Jul 31, 2009 8:02 am; edited 1 time in total |
|
| Back to top |
|
|
PSHRutPark
Joined: 21 Jan 2007
Posts: 158
Location: New Zealand
|
| Posted: Fri Jul 31, 2009 7:55 am Post subject: Re: PTAssembler 5.1 beta 1 |
|
|
Thanks Max,
The first run of Panomatic (using "Autopano Selected" button) seems to be fine and reports "40 CPs for 1 project". But if I do a "Step 1" reset and repeat then 0 CPs are reported.
If I proceed anyway, the ACPD is incredibly large following an "Auto-Optimize". And with repeated "Auto-Optimize"(s) the ACPD increments by about what the value should be (comparing the values for AP and AP-S runs and the result of the Panomatic first run).
Something doesn't seem to be resetting for each run.
Sorry if my above description doesn't help diagnose the problem ... but something appears flakey. Maybe basing these analyses on an old project doesn't help.
I'll try a new project: ... same thing.
Later: a similar accumulating inconsistency also occurs with AP-S.
Probably best to flag my observations as a possible error and wait for other user reports. Although I do note Terry's report.
Incidentally the ToolTipText for the "Autopano Selected" button probably needs modifying.
Already appreciating the auto deletion of intermediate TIFFs.
PETER
_________________
http://www.pastoralsystems.co.nz/photography/index.html
Last edited by PSHRutPark on Fri Jul 31, 2009 8:14 am; edited 1 time in total |
|
| Back to top |
|
|
maxlyons
Joined: 20 Jun 2003
Posts: 3347
Location: USA
|
| Posted: Fri Jul 31, 2009 8:13 am Post subject: Re: PTAssembler 5.1 beta 1 |
|
|
| PSHRutPark wrote: |
The first run of Panomatic (using "Autopano Selected" button) seems to be fine and reports "40 CPs for 1 project". But if I do a "Step 1" reset and repeat then 0 CPs are reported. |
When you press reset on Step 1 (either the "reset all" or "reset selected") that simply sets the position/lens parameters (e.g. yaw, pitch, roll, a, b, c) back to zero...it doesn't delete existing control points. So, when you run Panomatic the next time with exactly the same images and settings, it will produce exactly the same set of control points. PTAssembler is smart enough not to add these control points a second time...it rejects all the control points generated during the second run of Panomatic as duplicates. This is by design.
| Quote: |
If I proceed anyway, the ACPD is incredibly large following an "Auto-Optimize". And with repeated "Auto-Optimize"(s) the ACPD increments by about what the value should be (comparing the values for AP and AP-S runs and the result of the Panomatic first run).
Something doesn't seem to be resetting for each run. |
I'm not sure I follow precisely what you are doing. And, unfortunately, in order for me to replicate the problem, I need to understand precisely that you are doing. A general idea isn't sufficient. That said, if you are not running auto-create, have you set the FOV and lens types correctly on step 2 before running auto-optimize?
The ACPD is also a function of the final image size (width x height) when the project is optimized. Perhaps that is set at a high value on the step 5 screen?
| Quote: |
| Incidentally the ToolTipText for the "Autopano Selected" button probably needs modifying. |
I agree. And the button text itself should be changed as well, given Panomatic's name. I'll fix this.
Max |
|
| Back to top |
|
|
PSHRutPark
Joined: 21 Jan 2007
Posts: 158
Location: New Zealand
|
| Posted: Fri Jul 31, 2009 8:30 am Post subject: Re: PTAssembler 5.1 beta 1 |
|
|
| maxlyons wrote: |
| PSHRutPark wrote: |
The first run of Panomatic (using "Autopano Selected" button) seems to be fine and reports "40 CPs for 1 project". But if I do a "Step 1" reset and repeat then 0 CPs are reported. |
When you press reset on Step 1 (either the "reset all" or "reset selected") that simply sets the position/lens parameters (e.g. yaw, pitch, roll, a, b, c) back to zero...it doesn't delete existing control points. So, when you run Panomatic the next time with exactly the same images and settings, it will produce exactly the same set of control points. PTAssembler is smart enough not to add these control points a second time...it rejects all the control points generated during the second run of Panomatic as duplicates. This is by design.
| Quote: |
If I proceed anyway, the ACPD is incredibly large following an "Auto-Optimize". And with repeated "Auto-Optimize"(s) the ACPD increments by about what the value should be (comparing the values for AP and AP-S runs and the result of the Panomatic first run).
Something doesn't seem to be resetting for each run. |
I'm not sure I follow precisely what you are doing. And, unfortunately, in order for me to replicate the problem, I need to understand precisely that you are doing. A general idea isn't sufficient. That said, if you are not running auto-create, have you set the FOV and lens types correctly on step 2 before running auto-optimize?
The ACPD is also a function of the final image size (width x height) when the project is optimized. Perhaps that is set at a high value on the step 5 screen?
| Quote: |
| Incidentally the ToolTipText for the "Autopano Selected" button probably needs modifying. |
I agree. And the button text itself should be changed as well, given Panomatic's name. I'll fix this.
Max |
OK.
The correct focal length is set.
To demonstrate (in this case using Panomatic): load a project; "select all" then run "Autopano Selected". When finished note the number of CPs (for my 3 image project = 40). Repeat "select all" run "Autopano Selected" and for my project number of CP = 0.
If I let the 1st and second instances above each "run" to the preview screen (with re-optimization), the first output looks correct and the second has visible errors.
Hope this helps
PETER
_________________
http://www.pastoralsystems.co.nz/photography/index.html |
|
| Back to top |
|
|
maxlyons
Joined: 20 Jun 2003
Posts: 3347
Location: USA
|
| Posted: Fri Jul 31, 2009 8:58 am Post subject: Re: PTAssembler 5.1 beta 1 |
|
|
I think I've followed your steps (as best as I understand them) but can't replicate the problem. Regarless of how many times I use "Autopano-selected" I end up with the same preview image, assuming I follow the same procedure after running "Autopano-selected".
| PSHRutPark wrote: |
| To demonstrate (in this case using Panomatic): load a project; |
Is this a project that already has control points? And, does it have non-zero values for yaw, pitch, roll, etc. Or is this a new project with no control points and default (i.e. zero) values for the position parameters?
| Quote: |
"select all" then run "Autopano Selected". When finished note the number of CPs (for my 3 image project = 40). Repeat "select all" run "Autopano Selected" and for my project number of CP = 0.
If I let the 1st and second instances above... |
What are the two instances? Is the "first instance" the project after you have run "Autopano Selected" once, and the "second instance" the same project but after you have run "Autopano Selected" twice? If so, can you save the two instances, and post (or send to me) the project files? I plan to make sure that they are identical. If not, can you elaborate?
| Quote: |
| ... each "run" to the preview screen (with re-optimization) |
Can you elaborate on letting 'each "run" to the preview screen'? After running "Autopano Selected" on step 1, do you inspect/update/modify any values on Step 2? Do you then proceed to "Auto-optimize" on Step 4? If so, can you post your ptasmblr.ini file (this will tell me the exact steps that are happening during auto-optimize).
| Quote: |
| first output looks correct and the second has visible errors. |
At this stage of the game, I assume that the first and second instances must have different values for the image position/lens paramaters (i.e. yaw, pitch, roll, a, b, c, etc.). If they were the same, then you'd have identical preview images. So, can you save and post the two different project files? Note that at this point, the project files will be different from the ones I requested above.
If my theory that you should have identical project files after running autopano-selected one or more times is correct, my goal is to figure out how you could have started with identical project files, but ended up with different results while following exactly the same series of steps.
Thanks,
Max |
|
| Back to top |
|
|
Terrywoodenpic
Joined: 06 Mar 2006
Posts: 350
Location: Saddleworth England
|
| Posted: Fri Jul 31, 2009 10:01 am Post subject: |
|
|
Hi Max
The original one I tried did not have exif data. so I entered the focal length and crop manually.
It seems that is not an option now with auto. Previously after the control points were found, I used to stop it when it complained about lack of data, and go manual from there. it saved time.
I Have now tried again with a fresh set of shots complete with exif data, and it worked very well even the preview looked excellent before blending.
The spread of points was better than I have seen before.
The optimised distances ranged between .274 and 2.098 ( I have seen far worse.)
_________________
Terry
After 60 + years in photography, Now Down sized to Canon G6 Digital and Olympus OM1n film cameras, and accessories. Now up sized/added a Canon 40D and minolta G600 |
|
| Back to top |
|
|
maxlyons
Joined: 20 Jun 2003
Posts: 3347
Location: USA
|
| Posted: Fri Jul 31, 2009 1:21 pm Post subject: |
|
|
Terry,
I'm glad to hear that you got things sorted out. However, I'm not clear how your original problem ("I can not get it to produce points when I start auto create") was solved. Panomatic doesn't need images with EXIF data to work correctly (at least I have had no problem getting Panomatic to work with images without EXIF data). My guess is that if Panomatic didn't find any points in your first set of images, that is probably related to the image content (e.g. lack of features) rather than the presence or absence of EXIF data.
Max |
|
| Back to top |
|
|
Terrywoodenpic
Joined: 06 Mar 2006
Posts: 350
Location: Saddleworth England
|
| Posted: Fri Jul 31, 2009 2:27 pm Post subject: |
|
|
| maxlyons wrote: |
Terry,
I'm glad to hear that you got things sorted out. However, I'm not clear how your original problem ("I can not get it to produce points when I start auto create") was solved. Panomatic doesn't need images with EXIF data to work correctly (at least I have had no problem getting Panomatic to work with images without EXIF data). My guess is that if Panomatic didn't find any points in your first set of images, that is probably related to the image content (e.g. lack of features) rather than the presence or absence of EXIF data.
Max |
All sorted, but I have no Idea how... as I have changed nothing...
This is the as the original test and it worked fine, with nice well spaced points.
So I am delighted. It would be interesting if any one else ever has the same problem
_________________
Terry
After 60 + years in photography, Now Down sized to Canon G6 Digital and Olympus OM1n film cameras, and accessories. Now up sized/added a Canon 40D and minolta G600 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Subscribe
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
