vaslag wrote:Someone have experienced problems stitching a session shooted with bracketing using panoshoot + panogear?
For me, the shooting runs okay, but when i try to stitch the results via Papywizard plugin, in the detection phase, Autopano Giga hangs and exit the program.
If anyone succeed, is possible to post the resulting xml to compare with mine?
Thanks
vaslag wrote:Someone have experienced problems stitching a session shooted with bracketing using panoshoot + panogear?
For me, the shooting runs okay, but when i try to stitch the results via Papywizard plugin, in the detection phase, Autopano Giga hangs and exit the program.
If anyone succeed, is possible to post the resulting xml to compare with mine?
Thanks
mediavets wrote:vaslag wrote:Someone have experienced problems stitching a session shooted with bracketing using panoshoot + panogear?
For me, the shooting runs okay, but when i try to stitch the results via Papywizard plugin, in the detection phase, Autopano Giga hangs and exit the program.
If anyone succeed, is possible to post the resulting xml to compare with mine?
Thanks
Do you want to post your XML file here so we can take a look at it?
vaslag wrote:Hi.... this is my xml file.... If you need it, i can try with other configurations to provide you other samples....Ask me the tests you want and i'll do it....
For me is an important issue, i'm changing from Epic Pro to Panogear,
vaslag wrote:I'm shooting hi-res HDR 360*180 panos. The main reason is that Epic pro doesn't allow a non regular shooting pattern (less shots near zenit-nadir).
Other main reason is having the xml file, ho help stitching skies and some areas without good stitching points.
Today I'll send the test pattern you asked.
vaslag wrote:I'm shooting hi-res HDR 360*180 panos. The main reason is that Epic pro doesn't allow a non regular shooting patern (less shots near zenit-nadir).
shais wrote:vaslag wrote:I'm shooting hi-res HDR 360*180 panos. The main reason is that Epic pro doesn't allow a non regular shooting patern (less shots near zenit-nadir).
Sorry for jumping in, but, is there some sort of calculator or generator I could use to make my own picpoints for 270X180 panos?
Shai
mediavets wrote:Unfortunately Panoshoot doesn't use the Papywizard custom preset format but you could use a Papywizard orientated custom preset generator and transpose the data to a Panoshoot format I suppose.
shais wrote:mediavets wrote:Unfortunately Panoshoot doesn't use the Papywizard custom preset format but you could use a Papywizard orientated custom preset generator and transpose the data to a Panoshoot format I suppose.
Could you recommend on one such tool? (I haven't worked with Papywizard)
vaslag wrote:Here is the link to download the test files. 3*3 HDR mosaic + xml
https://dl.dropboxusercontent.com/u/421 ... x3test.zip
<?xml version="1.0" encoding="utf-8"?>
<papywizard version="a">
<header>
<general>
<title>
4886
</title>
<gps>
Here goes the location
</gps>
<comment>
Generated by Papywizard 2.1.5
</comment>
</general>
<shooting mode="mosaic">
<headOrientation>
up
</headOrientation>
<cameraOrientation>
portrait
</cameraOrientation>
<stabilizationDelay>
0.5
</stabilizationDelay>
<startTime>
2013-11-14_19h31m17s
</startTime>
<endTime>
2009-11-14_19h34m12s
</endTime>
</shooting>
<camera>
<timeValue>
0.7
</timeValue>
<bracketing intent="exposure" nbPicts="3"/>
<sensor coef="1.5" ratio="3:2"/>
</camera>
<lens type="rectilinear">
<focal>
18.0
</focal>
</lens>
<mosaic>
<nbPicts pitch="3" yaw="3"/>
<overlap minimum="0.20" pitch="0.20" yaw="0.20"/>
</mosaic>
</header>
<shoot>
<pict id="1" bracket="1">
<time>2013-11-14_19h31m17s</time>
<position yaw="-35.877" pitch=" 52.747" roll="0"/>
</pict>
<pict id="1" bracket="2">
<time>2013-11-14_19h31m21s</time>
<position yaw="-35.877" pitch=" 52.747" roll="0"/>
</pict>
<pict id="1" bracket="3">
<time>2013-11-14_19h31m25s</time>
<position yaw="-35.877" pitch=" 52.747" roll="0"/>
</pict>
<pict id="2" bracket="1">
<time>2013-11-14_19h31m37s</time>
<position yaw="-1.670" pitch=" 52.747" roll="0"/>
</pict>
<pict id="2" bracket="2">
<time>2013-11-14_19h31m41s</time>
<position yaw="-1.670" pitch=" 52.747" roll="0"/>
</pict>
<pict id="2" bracket="3">
<time>2013-11-14_19h31m45s</time>
<position yaw="-1.670" pitch=" 52.747" roll="0"/>
</pict>
<pict id="3" bracket="1">
<time>2013-11-14_19h31m58s</time>
<position yaw=" 35.324" pitch=" 52.747" roll="0"/>
</pict>
<pict id="3" bracket="2">
<time>2013-11-14_19h32m02s</time>
<position yaw=" 35.324" pitch=" 52.747" roll="0"/>
</pict>
<pict id="3" bracket="3">
<time>2013-11-14_19h32m06s</time>
<position yaw=" 35.324" pitch=" 52.747" roll="0"/>
</pict>
<pict id="4" bracket="1">
<time>2013-11-14_19h32m20s</time>
<position yaw=" 35.324" pitch=" 1.302" roll="0"/>
</pict>
<pict id="4" bracket="2">
<time>2013-11-14_19h32m24s</time>
<position yaw=" 35.324" pitch=" 1.302" roll="0"/>
</pict>
<pict id="4" bracket="3">
<time>2013-11-14_19h32m28s</time>
<position yaw=" 35.324" pitch=" 1.302" roll="0"/>
</pict>
<pict id="5" bracket="1">
<time>2013-11-14_19h32m40s</time>
<position yaw=" 1.672" pitch=" 1.302" roll="0"/>
</pict>
<pict id="5" bracket="2">
<time>2013-11-14_19h32m44s</time>
<position yaw=" 1.672" pitch=" 1.302" roll="0"/>
</pict>
<pict id="5" bracket="3">
<time>2013-11-14_19h32m48s</time>
<position yaw=" 1.672" pitch=" 1.302" roll="0"/>
</pict>
<pict id="6" bracket="1">
<time>2013-11-14_19h33m00s</time>
<position yaw="-35.311" pitch=" 1.302" roll="0"/>
</pict>
<pict id="6" bracket="2">
<time>2013-11-14_19h33m04s</time>
<position yaw="-35.311" pitch=" 1.302" roll="0"/>
</pict>
<pict id="6" bracket="3">
<time>2013-11-14_19h33m08s</time>
<position yaw="-35.311" pitch=" 1.302" roll="0"/>
</pict>
<pict id="7" bracket="1">
<time>2013-11-14_19h33m23s</time>
<position yaw="-35.311" pitch="-52.841" roll="0"/>
</pict>
<pict id="7" bracket="2">
<time>2013-11-14_19h33m27s</time>
<position yaw="-35.311" pitch="-52.841" roll="0"/>
</pict>
<pict id="7" bracket="3">
<time>2013-11-14_19h33m31s</time>
<position yaw="-35.311" pitch="-52.841" roll="0"/>
</pict>
<pict id="8" bracket="1">
<time>2013-11-14_19h33m43s</time>
<position yaw="-1.668" pitch="-52.841" roll="0"/>
</pict>
<pict id="8" bracket="2">
<time>2013-11-14_19h33m47s</time>
<position yaw="-1.668" pitch="-52.841" roll="0"/>
</pict>
<pict id="8" bracket="3">
<time>2013-11-14_19h33m51s</time>
<position yaw="-1.668" pitch="-52.841" roll="0"/>
</pict>
<pict id="9" bracket="1">
<time>2013-11-14_19h34m04s</time>
<position yaw=" 35.325" pitch="-52.841" roll="0"/>
</pict>
<pict id="9" bracket="2">
<time>2013-11-14_19h34m08s</time>
<position yaw=" 35.325" pitch="-52.841" roll="0"/>
</pict>
<pict id="9" bracket="3">
<time>2013-11-14_19h34m12s</time>
<position yaw=" 35.325" pitch="-52.841" roll="0"/>
</pict>
</shoot>
</papywizard>
vaslag wrote:On my point of view, there are 2 possible solutions....
1- Develop an import plugin for panoshoot for Autopano (perhaps is the better solution).
2- Make panoshoot xml files papywizard compliant (maybe a software to make it automatic).
If not, what are the sense of the xml files on panoshoot? Having this xml files is one of the strong points of panogear+panoshoot.
What is your opinion?
vaslag wrote:So, you are sugesting investing in some device papywizard compatible, and forget about panoshoot for the moment?
Sincerly, I bought panoshoot because is the only option available in kolor website, and I trust that is a finished and perfect working product.... and the module looks more like an unfinished product, just great perspectives (not so good news for kolor guys....).
I don't want to spend more money obviously, but I have work to do, not sure if I can wait until all this problems where solved...
Users browsing this forum: No registered users and 0 guests