Regarding the XML download restriction on iOS devices, we test several solutions.
At the end, we choose the most obvious and easiest for end user. This option require more work from our side, that we are doing happily to provide the best user experience.
We are compressing and saving the XML inside Panoshoot. With this solution we will be able to:
1- Have the full option to use Panoshoot WITHOUT any external device (means no app, smartphone, tablet or PC required). Just click the joystick button and you will have your pre-defined session running with your XML report safely stored for further download. This option is very useful if your smartphone or tablet has low battery in the middle of a job.
2- Bypass the Safari iOS limitation to download files. Use your iPhone/iPad to handle your panogear. After finish the job, download all the files in your iMac or computer where the XML file will be used.
3- Store multiple XML files and download all of them as a multisession XML file (currently not supported by APP importer, but we are ready for the future). It will provide a convenience way to organize in a single XML file a multisession job, like shooting several panos in a multi room house.
This solution involves a little more work and we want to fully test it in different platforms before release our last update.
We clear the pending bug list reported from users (particularly presets) and introduce new features that we consider will be very useful for photographers.
We will delay the update release by this Friday. We wish to exceed the Panoshoot owner expectations.
â€œPanoshoot is moving up your Panogear robotic head to a new level of capacity, features, precision and speed, where even some high tag price heads canâ€™t reach. â€œ
- The default download option is individual XML file. You will need to turn on the Multisession XML file feature in order to get your single XML file job.
- Panoshoot can store up to 80 XML log files or about 10.000 picture shoot records. Max. Capacity is based in average user data stored in Panoshoot (It could be lower or even higher).
Hey javqui! (is that your name?
IÂ´m not quite sure to having really understand.
As you might know i assisted Josef Graessle in developing the Panoneed head and the TC-handheld controller over a long time - step by step orienting on real use.
We decided to completely abandon the principle of generating user-defined presets as xml files before shooting.
The TC generates itÂ´s pattern each time you shoot. Of course shooting a sphere itÂ´s the same pattern all the time - relating on the lens and the sensor you use.
Changing the lens means the TC changes the pattern to match the lens you use then.
What i meant saying XML: the controller writes an xml file each time you shoot.
So EACH session of pictures have itÂ´s OWN xml-file. Shooting spheres itÂ´s simple: you can simulate shooting a sphere by having the head run it. That xml file you can use for all spheres according to the lens- and the sensor-values you used for simulating.
So i was speaking of the individual output-xml when shooting mosaics. LetÂ´s say: youÂ´re in the field and shoot 20 different mosaics. At home you want to stitch them using the XML for positioning.
Clearly you need an individual matching XML for each mosaic. And the controller must be able to store all the XML files. The TC handheld stores some hundreds up to some thousands of them - depending on the number of shots in each session.
How many individual XML-files can be stored in your device for using them at home for supporting each individual stitch by positioning the images?
Are they stored in the controlling device - the smartphone - or in the device which is physically conected to the head?
Being able to store all the shootings iÂ´m doing on a job as xml for processing the sessions at home is essential. I usually use 35mm and sometimes 50mm and 85mm for indoor panos - here you always have shots showing nothing but white walls or ceilings - or when shooting in the open many shots showing nothing but clear blue sky, or (even worse) fast moving clouds . . . . impossible for a stitcher to set correct-matching control points. Without precise XML-positioning youÂ´re definitely lost.
As an example - two scenes 85mm, the other scenes 35mm:http://360impressions.de/KBogen413/