gddxb wrote:

There is definitely a huge difference between APG and PTGui Pro when it comes to stitching fish-eye images.

PT Gui stitched this without any manual intervention (apart from setting the image circle crop) in about a minute:

http://08.ae/panos/downtownsunset/sunset.html

That's 3 shots from a Canon 8-15 on a Phase One IQ180.

This is the starting point with APG:

http://08.ae/imgs/APGfish.jpg

I can't help thinking the two programs are optimised for different things. APG is fantastic at large panos. It will do in hours what PT Gui takes weeks. Literally.

is it possible to make the three fisheyes public downloadable, like attaching a resized jpg version to forum? I cant believe apg cant do the same result with same less effort...
Georg

gkaefer wrote:

gddxb wrote:

There is definitely a huge difference between APG and PTGui Pro when it comes to stitching fish-eye images.

PT Gui stitched this without any manual intervention (apart from setting the image circle crop) in about a minute:

http://08.ae/panos/downtownsunset/sunset.html

That's 3 shots from a Canon 8-15 on a Phase One IQ180.

This is the starting point with APG:

http://08.ae/imgs/APGfish.jpg

I can't help thinking the two programs are optimised for different things. APG is fantastic at large panos. It will do in hours what PT Gui takes weeks. Literally.

is it possible to make the three fisheyes public downloadable, like attaching a resized jpg version to forum? I cant believe apg cant do the same result with same less effort...
Georg

Hi Georg -

Unfortunately I'm traveling now and won't be able to upload them until next Thursday.

Kind regards,

Gerald.

Hi.. I tend to keep with batch fusion/auto.. Never hand an issue before so really not sure what it happening... I am wondering.. could it be the small area of the pano.. ???

Now.. xml.. ?? oh dear, never tired that... So, what do I do... I have only ever seen the xmp with the RAW... which is just the data files to remember the settings... How do I use the xml files and where are they... Love to try that one....

Destiny...

Yes Leifs.. we are all learning new things.. I have just sent an email to Urs for guidance since your post seems to lack direction...

Destiny...

leifs wrote:

Destiny wrote:

Now.. xml.. ?? oh dear, never tried that...

oh dear !
why buy a VR drive 2 and not enjoy the power of it's excellent XML-files ?
maybe you can manage without the XML with your 10.5mm.  with the XML's you can tap another world !

leifs

Last edited by Destiny (2012-08-18 02:52:41)

Been there done Ed... Thanks for that info.. To be  honest Ed, I shouldn't have to do any of this.. Considering the images were captured using a motorised pano head I am confused as to why it will not stitch.. Sorry, I will pass on sending the files.. I sent them to Alex which took forever.. painful..

Destiny

Artisan S. wrote:

Des,

Regarding your caravan......this is a typical example of APG/APP being trown of kilter by fake CP's...no nadir shot present so that should not interfere the procedings......please check the CP's and remove everything above 5....then ad some CP's in the critical area's (like the bottom of the cupboard and the laminate on the floor) of course remove everything above 5 again then use the Full Optimize button and check for an RMS under 3 near 2.....afterwards I only striaghten out the verticals since APG has no clue were they are (it doesn't do lines). Left on it's own devices APG/APP only creates CP's in the center of the frames and tends to forget about the bottom and the tops of the frames so concentrate your effort on those....a bit of CP editing can go a long way, this takes the best part of 5 minutes if you've got the hang of it.

Greets, Ed...

If in doubt....upload the files and let me have a go at them.....be happy to spend an hour or some to get this done. I'll wind up with a Nikon and 10.5 sooner or later (btw a Nikon D200/D300 can do 9 EV steps using it's own software, nice) so a bit of problem training in that area won't hurt.

Destiny wrote:

Hi Ed.. Thanks for looking that up for me.. I have read about that before but I was thinking the comment about xml was something else when stated here.. So.. I have captured my images using my VR Drive, using the settings 6 X -30 and 6 X 60 which I could have used xml to programme this into my VR Drive.. But what I would like to know.. I have fused my images using Photomatix, so how is xml going to change anything with my stitching... I was under the impression that I could use the data when using Papywizard for importing my images using that plugin in apg that haven't been previously fused.. So how is xml going to help my cause..?? I don't use the LDR or HDR feature of apg since it never come out as I want it.. or have I missed something... I have already determined that power of xml for large giga pixel panos would be great feature of the VR Drive..

Destiny..

When you intend to process the images in PM BEFORE stitching: while shooting tell the head to write only ONE shot per position though it fires the camera x times. That enables you to use the XML even with pre-processed images.
The head otherwise writes x shots per position into the XML, i guess, for the use of stacked sets - and that can´t work with pre-processed images (if you don´t want to manually edit the XML and change x shots into one shot per position).

Klaus

Destiny wrote:

Thanks K and E for the xml advice.. Looks like I owe you a bucket with a handle filled will beer and an old log turned into a pair of shoes...

I am going to look in to more.... Clearly I need to spend time getting my head around this feature... I also need to get my head around the VR Drive HDR which I have really only just began to understand.. Never enough time in the day... During Term brake I will work it all out.....

My shooting pattern is actually an off-shoot from my dear Nodal Ninja 4... Andrew suggested the pattern so I took it over to my VR Drive... I rather like it.. Actually, the default shooting pattern that my VR Drive suggest is -45 X 6 and 45 X 6... I never tried it.... The good thing about the VR Drive is the fact I can program any shooting pattern in and go back to it...

The thing is.. I think my issue is the size of the area I shot the VR in, since I do not get this issue with lager spaces.. The PTGui pano has a small stitching error near the oven, but again I am sure this is due to the size of the area since I just do not see any errors when capturing a normal room..

Once I worked out the xml feature I will try a small area again and test the difference it makes..... What I do not get is where the xml file is since when I download the images there is no xml files, just RAW... I see the xmp after RAW conversion but thats it.. So, how to I get to see the xml codes.. Also, I am assuming I just set the VR Drive under bracketed to ONE.. but set my camera to capture the bracketed shots.. Not sure how that will work.. seems to me it will go to the next shot and the camera will capture it with a EV of -2 and the next snot +2 etc., so I must be way wrong there... oh hum... I feel like a blond today.. So, where on the VR Drive to I tell it to capture ONE shot but allow it to do the bracketed process.. ??? I am sure the penny will drop at some stage... but since I am having a blond moment I am guessing no time soon.. LOL...

Destiny...

Usually the bracketing-sequence is done by the camera independently from the head.

The usual procedure is:
1) head triggers camera once -->> camera fires the bracketing sequence. XML says: one shot per position.
2) head triggers camera x times on each position. XML says: x shots per position.

Variations: a device triggers the camera while overruling the internal camera-software - PromoteControl or VR Drive 2 as example can do that.
That can mean the device controls the bracketing sequence.
In my case it´s PromoteControl or MagicLantern - independently from the head-control and what it writes into the XML-file. That provides maximal flexibility.

So i can tell the head-control to write ONE shot per position - though the camera is triggered x times by the extra-device, or i can tell the head-control to write x shots per position.

I prefer to handle moving the head and firing the camera seperately: i can use ML or Promote also without the head when shooting "normal" pictures.

Klaus