As the name suggest, this preset generator is used to generate 360/180 preset using any focal length.
2. Where is the screen shot? a) Picture 2 shows an initial opening screen b) Picture 3 shows an preset generated screen
3. How to install? a) Open notepad or any text editor b) Copy the following code (remove the "Code:" part) c) Paste that in the text editor d) Save it with a name (like pw_360_preset.html) e) Double click on the name. It will be opened in the default browser. f) You can create a shortcut as well (see Picture 1).
5. What are the fields on the screen? a) Crop Factor: This dropdown box shows all the possible sensor crop for the DSLR currently available. Some example, choose 1.0 for full frame DSLR/film cameras irrespective of camera maker choose 1.3 for Canon 1D series choose 1.5 for Nikon crop cameras like D40 etc choose 1.6 for Canon Rebel series choose 2.0 for 4/3 and micro 4/3 system Note that if you use any point and shoot camera, use the crop factor of 1.0 and its 35mm equivalent focal length. For example, Canon A590 has 140mm (35mm equivalent) at tele end. So use crop factor of 1.0 and focal length of 140mm. b) Aspect Ratio: Choose the maximum sensor aspect ratio for a given camera. Mostly it is 3:2 ration for DSLR. Some camera offer in camera crop of 4:3 and 16:9. It is best to use the native aspect of the sensor. c) Overlap: This is the overlap percentage between the adjustant shots in yaw and pitch axis. d) Orientation: Orientation of the camera when taking the mosaic - Landscape or Portrait. e) Focal Length: The focal length of the lens used. Don't do any conversion here. If you use 50mm lens on a 1.6 crop body, just enter 50 and not 80. f) Width in Pixels: Source Camera sensor width in pixels. The default value is populated with Rebel XSI sensor width 4272. g) Height in Pixels: Source camera sensor height in pixels. The default value is populated with Rebel XSI Sensor height 2848. h) Generate (button): Press this button to generate the preset. i) Preset (text area): The generated preset will be shown here.
6. How to use it? Select a value that matches your camera. Select the correct aspect ratio for your camera. Select an overlap percentage. Select the orientation of the camera. Enter the focal length of the lens. Enter the Source Camera sensor width in pixels (whole number) Enter the Source camera sensor height in pixels (whole number) Press the "Generate" button.
This creates a preset in the bottom text area. The preset name will be 35<2 digit crop factor><orientation>_<focal length>_<rows>_<columns>. Now copy this to a file same as the preset name with an extension of .xml. For example, you use Canon 450D in portrait with 50 mm lens. The preset name will be 3516P_100_17_57.
Load this preset file into the PW using File->Import Preset File menu.
Once you set the home position correctly, then select the preset (3516P_100_17_57) and take the mosaic.
7) what is in the tooltip? a) The tooltip has a Source section where the format used, focal length used, rows and columns are mentioned. b) The tooltip also has a Target section which shows the resultant horizontal, vertical FOV and sizes for the mosaic and for 360/180.
I just tried the calculation with crop 2 and 9mm FL, my uncomfortable xls-calc ends in 5-7-5 shots at +55 0 -55 degree, I decrease the no of pics for the tilted rows with cosine of angle. The diff is 7 pics.
Jean-Pierre Merlin/Orion firmware : 01.09.81 panohead + Papywizard on XP PC and Linux Ubuntu 9.1 & Nokia 800 Manfrotto 303 PAN HEAD with Nikon D70 + Nikon 18-70 in kit - Nikon 80-200 F 2.8 old - Sigma 10-20 Assembly : Ptgui 9.1.3
Yes. It is around 180 degrees. The reason is that I exclude about 20 degrees from 180 degrees due to the large head. I can remove that restriction. The reason I put that restriction is for larger focal length where it does not make any sense to take 2 or more rows of 30 plus shots taking the base of the head. Let me know if you want to remove the restriction.
portrait instead works 17 or 19 focal instead works overlap 20 instead works
error I get:
Details zum Fehler auf der Webseite
Benutzer-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
Zeitstempel: Sun, 26 Jul 2009 09:53:51 UTC
Meldung: 'numa.1' ist Null oder kein Objekt
issue: setting focal length with preset generator CONTRA PW logfile value for focal length. negative effects: no...(?)
1. I choose with the preset generator the focal length of my lens used to correct value, lets say 18mm. 2. important: the matrix register of pw contains a focal length lets say 111.1mm (IMAGE 02) 3. use this preset to take my pano (IMAGE 01) 4. the pw produces a logfile, containing a block <focal> wich hold the value set by matrix register and not set by preset. (IMAGE03)
autopano import does not affect this. using both version of logfiles (focal 18.0 and focal 111.1) for pw import module gives me same (correct) result.
A preset file does not contain any focal information; then, when Papywizard writes the header of the xml data file, it reads its internal informations. If you didn't change the focal according to the one you are really using, then the header is wrong.
But this header is not used by APP; instead, it reads the real focal from the EXIF of the pictures, which is a much precious information.
Canon 20D + 17-40/f4 L USM + 70-200/f4 L USM + 50/f1.4 USM Merlin/Orion panohead + Papywizard on Nokia N800 and HP TC-1100
As you found out, the current preset generator assumes the 360/180 as a rectangular sheet with the top-left as the 0 yaw and 0 pitch. You can change the values of yaw, pitch by changing the code in initialize_positions function. It starts with 0 yaw and 0 pitch. You can add your offset of 90 degree before the for loop.
I am also thinking of changing the assumption of "360/180 as a rectangular sheet with the top-left as the 0 yaw and 0 pitch" to take nadir shot, zenith shot and the rest of the FOV as a cylinder - the classical manual head way of doing things. I'll find sometime to do it and upload the script.
The reason I ask is it appears to me to be usefull for having some canned coverages, but it doesnt take into account the coverage at the poles as needing a lot less images, so in the end it gives you a preset, but wont necessarily speed the shooting of the first and last rows.
Amy I mistaken?
Can such a generator be made to make the first and last rows account for the lower necessary shots??
Canon 50D, 20D, 1D MKII Tok 10-17FishEye,Canon 10-22, 24-70 2.8, 50 1.4, 70-200 2.8IS, 300 2.8,1.4x,2.0x 303SPH, Panosaurus, Merlin+Parallax Bluetooth+USB to PC and Nokia N810