panoramicessentials.com wrote:Hey everyone,
Yesterday Kolor launched the sale of Panoshoot a wireless control module designed and developed by Javier Quintata and myself (Adam Shehadeh). You can get information from our website http://www.panoshoot.com. I will make myself available at most hours of the day for the next few days to answer any questions or concerns you may have about Panoshoot.
Adam
panoramicessentials.com wrote:Hey everyone,
Yesterday Kolor launched the sale of Panoshoot a wireless control module designed and developed by Javier Quintata and myself (Adam Shehadeh). You can get information from our website http://www.panoshoot.com. I will make myself available at most hours of the day for the next few days to answer any questions or concerns you may have about Panoshoot.
Adam
mediavets wrote:What is the minimum size and resolution of diplay required to use a mobile or tablet device with Panoshoot??
mediavets wrote:What is the practical minimum size of display and resolution of display required on a touch orientated device.
mediavets wrote:Can you change UI orientation between portrait and landscape on the fly? Does the layout change at all when you do?
meadiavets wrote:Do you an online emulator fpr the Panohoot device so that potential customers could get a feel for how the system operates before purchasing the hardware?
mediavets wrote:This seems a bit 'clunky' but maybe I don't quite understand it?:
mediavets wrote:Why not ask Kolor to establish a new section of the forum for Panoshoot questions?
Rami wrote:mediavets wrote:Why not ask Kolor to establish a new section of the forum for Panoshoot questions?
We are going to create a dedicated section for Panoshoot.
Panoshoot on the Kolor Store: http://www.kolor.com/buy/panoshoot.html
Adam created video tutorials that are on YouTube: http://www.youtube.com/playlist?list=PLqPZ7zvLePxdxyLtbTblD7kpiFlGXfja0
mediavets wrote:panoramicessentials.com wrote:Hey everyone,
Yesterday Kolor launched the sale of Panoshoot a wireless control module designed and developed by Javier Quintata and myself (Adam Shehadeh). You can get information from our website http://www.panoshoot.com. I will make myself available at most hours of the day for the next few days to answer any questions or concerns you may have about Panoshoot.
Adam
There's no shortage of alternative controllers for the Panogear/Merlin mount now.
I note that you state on your Web site:
"Although it is initially designed for Kolor's Panogear, Panoshoot will soon be available for other motorized mounts. "
Can you share any insights into your meaning of 'soon' and 'other motorized mounts'?
mediavets wrote:Rami wrote:mediavets wrote:Why not ask Kolor to establish a new section of the forum for Panoshoot questions?
We are going to create a dedicated section for Panoshoot.
Panoshoot on the Kolor Store: http://www.kolor.com/buy/panoshoot.html
Adam created video tutorials that are on YouTube: http://www.youtube.com/playlist?list=PLqPZ7zvLePxdxyLtbTblD7kpiFlGXfja0
So who is going to be responsible for supporting Panoshoot users?
Kolor via the Kolor forum; or Panoshoot via their online support ticket system?
mediavets wrote:Bounce...for Adam and/or javqui...mediavets wrote:panoramicessentials.com wrote:Hey everyone,
Yesterday Kolor launched the sale of Panoshoot a wireless control module designed and developed by Javier Quintata and myself (Adam Shehadeh). You can get information from our website http://www.panoshoot.com. I will make myself available at most hours of the day for the next few days to answer any questions or concerns you may have about Panoshoot.
Adam
There's no shortage of alternative controllers for the Panogear/Merlin mount now.
I note that you state on your Web site:
"Although it is initially designed for Kolor's Panogear, Panoshoot will soon be available for other motorized mounts. "
Can you share any insights into your meaning of 'soon' and 'other motorized mounts'?
panoramicessentials.com wrote:As with any product development you don't want to give a solid date because nothing is ever guaranteed to work out the way we plan but I can safely say that sometime in April 2013 we should have Skywatcher compatibility.
mediavets wrote:panoramicessentials.com wrote:As with any product development you don't want to give a solid date because nothing is ever guaranteed to work out the way we plan but I can safely say that sometime in April 2013 we should have Skywatcher compatibility.
Is there a Skywatcher mount that would be capable of rotating a camera/lens around the No Parallax Point (aka Entry Pupil)?
panoramicessentials.com wrote:mediavets wrote:panoramicessentials.com wrote:As with any product development you don't want to give a solid date because nothing is ever guaranteed to work out the way we plan but I can safely say that sometime in April 2013 we should have Skywatcher compatibility.
Is there a Skywatcher mount that would be capable of rotating a camera/lens around the No Parallax Point (aka Entry Pupil)?
The Skywatcher Allview mount specifically, I forgot that Skywatcher is a broad term. I am not sure if it is used for panoramas. I currently sell the Allview mount and most of my sales have gone to astronomy and videographers. From my perspective the Allview mount is too bulky for panoramic photography especially if you are a landscape photographer who has to carry it out into the field.
mediavets wrote:panoramicessentials.com wrote:mediavets wrote:Is there a Skywatcher mount that would be capable of rotating a camera/lens around the No Parallax Point (aka Entry Pupil)?
The Skywatcher Allview mount specifically, I forgot that Skywatcher is a broad term. I am not sure if it is used for panoramas. I currently sell the Allview mount and most of my sales have gone to astronomy and videographers. From my perspective the Allview mount is too bulky for panoramic photography especially if you are a landscape photographer who has to carry it out into the field.
Oh....I had understood that the AllView mount was 'plug-compatible' with the Panogear/Merlin mount for control using, say, Papywizard.
Perhaps I am mistaken?
See: http://www.kolor.com/forum/f45-allview
mediavets wrote:XML format data files:
1. Why can you not store more than one XML data file at a time on the Panoshoot device? As I understand it you must download the XML data file after each panorama shoot before you can shoot another panorama, unless you choose to overwrite the first XML data file. Or have I misunderstoofd the decsription in the User Manual?
2. What happens if you set you an automatic repeat of a shoot? Do the initial and repeat shoots co-ordinate data get recorded in a single XML data file? If so, that wouldn't that be virtually useless with the APP/APG Papywizard Import wizard which is surely the reason to record the shooting co-ordinates in a data file?
3. Can you post an example of an XML data file created by Panoshoot please?
gkaefer wrote:mediavets wrote:XML format data files:
1. Why can you not store more than one XML data file at a time on the Panoshoot device? As I understand it you must download the XML data file after each panorama shoot before you can shoot another panorama, unless you choose to overwrite the first XML data file. Or have I misunderstoofd the decsription in the User Manual?
ad 1.
I prognosticate that this is no deficit, because you Need to have connected an note/net/ultra-book/andoid/idevice whichever Java/browser capable devcice to get directly connected to the builtin webserver of the device to Access the UI. So if you have your device connected via wlan to the panoshoot device to use the device than the download of the one XML file should be done automatically...
Georg
mediavets wrote:1. The idea of using the Panshoot UI to build presets by moving the head under program control and then setting a PicPoint is ludicrous, quite impracatical in my opinion.
mediavets wrote:2. The alternative offered is to import a list of shooting co-ordinates in CSV format. Why didn'y you adopt the existing Preset XML definition/format creatd for Papywizard presets? There are several preset buolding tools for that format.
mediavets wrote:3. What happens during a shoot if a preset includes co-ordinates that lie outside the user-defined Yaw and Pitch limits set in Panoshoot?
mediavets wrote:4. Several robotic pano head systems - amongst others the T&C controller for Merlin and Panoneed, and the Seitz VRDrive2 - can calculate an optimal shooting pattern for spherical panos on-the-fly, ie. not a regular grid/matrix. Papywizard does not, instead it uses presets, data files that describe/define a pattern of shooting co-ordinates. Why did you choose to adopt the less user-friendly preset approach rather than have the program calculate a pattern on-the-fly using the camera and lens data you have already stored in the system?
mediavets wrote:1. Why can you not store more than one XML data file at a time on the Panoshoot device? As I understand it you must download the XML data file after each panorama shoot before you can shoot another panorama, unless you choose to overwrite the first XML data file. Or have I misunderstoofd the decsription in the User Manual?
mediavets wrote:2. What happens if you set you an automatic repeat of a shoot? Do the initial and repeat shoots co-ordinate data get recorded in a single XML data file? If so, that wouldn't that be virtually useless with the APP/APG Papywizard Import wizard which is surely the reason to record the shooting co-ordinates in a data file?
mediavets wrote:3. Can you post an example of an XML data file created by Panoshoot please?
mediavets wrote:…. About XML download. …..Yes, but it appears from the manual that it is not automatic.
mediavets wrote:1. I'm not sure I really understand what the various fields/values in the Timing Profiles mean (screenshot from manual below).
Are the Stabilization Pause, Obturator Time and After Shot Pause additive?
Stabilization Pause:
-range:0 to 25 seconds
-resolution (step increments):100 ms (0.1 s)
-description:Time between the head movement and the first shoot. This time is related to robotic head-camera inertia stabilization.
Obturator time:
-range:0 to 46 hours
-resolution (step increments):10 ms (0.01 s)
-description:Time of “shutter signal†ON. Small values define the minimum time that the camera needs to understand a valid pulse.
Large values are useful to shoot very long exposure images (close to 2 days for astronomy photography).
After shot pause
-range:0 to 46 hours
-resolution (step increments):10 ms (0.01 s)
-description:Pause between shoots in a multiple-shoot or bracketing mode and before next movement. Small values define the minimum time that the camera needs to process the image before accept the next shoot. Large values are useful for time-lapse images.
mediavets wrote:2. Obturator is such an unsual word - why did you choose it? I am particularly confused by what it represents and how it should be calculated. (And yes, I've watched the tutorial videos).
mediavets wrote:3. For how long is the Snap connector contact closed - is it the Obturator Time value?
mediavets wrote:4. The Speed/Accuracy trade off is intriguing. Can you say more about how this wroks and the implications of choosing higher speed over accuracy in the real world of pano shooting and stitching?
mediavets wrote:Apparently you can connect to and control your Panogear/Merlin mount plus Panoshoot module from anywhere in the world.
So....why would you want to do that?
I guess I lack imagination because I'm struggling to envisage a scenario in which I might wish to do that.
javqui wrote:Presets and PicPoints:mediavets wrote:1. The idea of using the Panshoot UI to build presets by moving the head under program control and then setting a PicPoint is ludicrous, quite impracatical in my opinion.
We believe that is not the primary intention of this feature. The intention is to edit PicPoints on the field or set a few Picpoints for a quick job on the field, not to load a complete set of PicPoints as we mention in an early post. Just image load something like 2000 PicPoints manually, one by one, it’s ridiculously crazy.mediavets wrote:2. The alternative offered is to import a list of shooting co-ordinates in CSV format. Why didn'y you adopt the existing Preset XML definition/format creatd for Papywizard presets? There are several preset buolding tools for that format.
The import PicPoints mechanism is not the alternative, is the main and practical method to load PicPoints data.
XML is a format to interchange data between computers that can be read by humans but difficult to write by humans. You can easily be lost in complex and large XML files without the help of specialized XML formatter app. XML is a nice format for non tabular data, but the cost is a lot of redundancy with file size increase and extra processing.
Simple Comma-delimited format is a lot easier and natural to handle by humans, standard between different platforms and supported for all calc programs like Spreadsheets (excel, open office), math lab and many others. You can type a tabular data easily on whatever platform with a simple text editor (even with a Smartphone) without worry about type all marker rules for each row, column or element. You need validate the XML file to check that you don’t miss any mandatory element delimiter that could invalidate the file.
Probably we didn’t have enough time to evaluate all preset building tools that you mention, but some of them use spreadsheets as the main calc tool. If you have a specific case, we will do our best to create a spreadsheet equivalent. (Users will not need install extra apps in computers and learn extra tools)
In short XML is extremely inefficient with highly structure data (it was not its primary design goal [url][url]http://en.wikipedia.org/wiki/XML#Criticism[/url] )[/url] and PicPoints (including advanced modes) and Papywizard use a highly structured tabular data. We want to simplify the Panoshoot programming to permit end user be focus in the specific details of their application, not in the details of XML rules.
Users browsing this forum: No registered users and 1 guest