gsf wrote:Hi All,
I'm a newbie to the topic but have been using AutoPano for a couple of years so I'm "somewhat" familiar with it.
I created a robotic mount for my iPhone from a couple of RC Servos and an Arduino board. I actuate the camera shutter of the iPhone with a hacked headset - the iPhone allows you to actuate the shutter with the "volume up" control which is really useful. This also works with my iPad Mini. I also have a Nexus 4 and I found a guy to create a simple App that simulates the "volume up" on the Nexus so I can do the same thing there and will connect to the Android using bluetooth.
I get pretty good results and until now have used three rows of 10 images with 2 at 90 degrees to each other for the zenith.
Now to get the images to stitch. When shooting with blue sky outside or white ceilings inside there isn't enough detail to create the control points and ugliness ensues. I added full rows at the nadir and zenith and tried to use the import function but this didn't work. It struck me that my problems weren't much different than what happens with DSLRs on robotic mounts so here I am. My guess is that I need to create an XML file but before doing that I thought I'd ask.
I did look into PW but my problem isn't controlling the camera it's stitching the output.
Can someone point me in the right direction to save me time? It would be appreciated.
ps... I can post some images if it will help. Also, I'm looking at turning the mount into an open source project with 3D printable components if anyone's interested..... but first things first.
gsf wrote:HI Georg,
I looks like I would have to calculate the values as didn't find much on the Web. By running PW in a "dummy" mode I assume you mean with nothing connected?
gsf wrote:I have been able to calculate all of the data needed to populate PW however it seems to fall down because of the sensor geometry not conforming to the available options. I was able to generate the xml file however PW crashed so I probably need to run it again.
gsf wrote:Hmmm... this is turning into a bit of a rat hole. The dev version crashes on startup. What was it I was trying to do again..... :-/
fma38 wrote:MacOS ports are more complicated, because of Apple philosophy concerning free software... And there system changing all the time, braking many things of the previous version is really annoying.
I strongly suggest you try with a linux or windows system, using virtual machine.
gsf wrote:I think I'm closing in on the settings but I'm confused with two settings:
Optical Multiplier coefficient - I have no idea what this is. The documentation suggests it might be the Crop Factor.
If it is, then what's the Sensor Coefficient? This was my guess for the Crop Factor.
BTW, reading the released documentation it looks like the session XML file is created by the configuration process (duh!) and since I specify where it's located.....
Really sorry about the newbie stuff, but hopefully it will only be once and I'll put it all together in case someone else wants to use a smartphone for capturing spherical panoramas.
gsf wrote:Here we go again. Just send me home
OK, opened the XML file to edit it and it looks like it uses a time stamp to tell Autopano where everything belongs.
Can Autopano just look at the mosaic description values and order images were taken and ignore the absolute timestamp?
Or can I, do I have to, go into the XML file and give it the time stamp of the first and last images so it knows what to use? I can tell I need to give some careful thought to workflow here.
Users browsing this forum: No registered users and 1 guest