hi frederic! (i'm writing on the nokia . . . )

i tried to find the positions using my Manfrotto click-head. But that seems to be not
precise enough.
horizontal angles and numbers are easy to tfind . . . but then it becomes very dificult finding the relation of angles and numbers of shots.
maybe there is some formula!? I bet i missed it . . .

be back in the late aftternoon, klaus

Ok, here is a xsl stylesheet to transform a data xml file generated by Papywizard (from mosaic mode, for example), into a preset xml file you can import...

Note how simple it is to transform xml

<?xml version="1.0" ?>

<!--
    This stylesheet can transform a data xml file generated by Papywizard
    into a preset xml file which can be loaded in Papywizard.
-->

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" version="1.0" indent="yes"/>
    <xsl:param name="name" />
    <xsl:param name="tooltip" />

    <!-- Global template -->
    <xsl:template match="/">
        <papywizard>
            <preset name="{$name}">
                <tooltip>
                    <xsl:value-of select="$tooltip" />
                </tooltip>
                <shoot>
                    <xsl:apply-templates select="//position" />
                </shoot>
            </preset>
        </papywizard>
    </xsl:template>

    <!-- Template for each input position -->
    <xsl:template match="position">
        <pict yaw="{@yaw}" pitch="{@pitch}" />
    </xsl:template>

</xsl:stylesheet>

To use the stylesheet, you need a xslt processor. Under linux, you can do:

$ xsltproc --stringparam name <name> --stringparam tooltip <tooltip> --output presets.xml papywizard.xsl papywizard.xml

where <name> is the preset name, <tooltip> the info of that preset, papywizard.xsl is the stylesheet xml file, papywizard.xml the xml data file, and presets.xml the generated preset xml file. You can use other names...

Don't know how to do that under Windows, but I'm looking for a simple solution which can work in a simple web navigator (most of them knows how to do xsl transformations), in local.

Last edited by fma38 (2008-10-30 16:04:28)

fma38 wrote:

I found this for windows:

http://www.sagehill.net/docbookxsl/Inst … essor.html
http://saxon.sourceforge.net
http://www.altova.com/altovaxml.html

Her's another:
http://xslt-processor.awgar-stone-limit … 4free.com/

This one has very simple GUI rather than being a command line tool.

It doesn't take parameters but seems to work just fine.

You have edit the output file to add the 'preset name' and 'tooltip' text but that is simple enough to do with amny text editor, such as Notepad or Wordpad.

Last edited by mediavets (2008-10-30 18:06:56)

Same preset again ( 3+6+12+6+3(28mm) which means 17mm@1,6)

Camera not moved in between - just started "shoot" again.

Last edited by klausesser (2008-10-30 21:30:01)

Frederic

I have been thinking about proposed future feature allowing manual entry of pano FOV for shooting mosiac panos.

The way I would like it to work is this:

1. Move head to point at location you wish to be 0/0 in finished pano and select Home/ Centre button to set.

2. Enter values for pano FOV.

3. Shoot.

I want the resulting pano to have the centre point I set in step 1.

Is this how you envisaged it working?

Last edited by mediavets (2008-11-02 16:42:12)

Klaus, even if you launch detection on the same set of images, you won't get exactly the same result.

I finally made a web interface to convert output file to preset file:

http://www.gbiloba.org/papywizard.psp

Comments are welcome.

fma38 wrote:

I finally made a web interface to convert output file to preset file:

http://www.gbiloba.org/papywizard.psp

Comments are welcome.

Excellent, thanks - it works well - could we have English sub-titles?

Last edited by mediavets (2008-11-02 22:16:22)

Thanks Andrew

Sorry, Klaus, as my web site is in french, I wrote the page in french. If it works fine, I will try to integrate it to the project page, in english.

Further thoughts and ideas about custom presets.

Custom presets are a very powerful and useful feature of Papywizard.

As things stand we have two Modes for shooting - Mosaic and Preset. The Preset mode offers users the ability to chose presets and the Mosiac mode does not offer presets.

As described in the Papywizard User Guide:
http://74.125.93.104/translate_c?hl=en& … tompresets
"Papywizard now has 2 modes: Mosaic mode, and Preset mode. The first one is mainly used for partial panos, and is especially designed for hi-res panos, using a large tele-lens. The second one is designed for full-spherical panos, using a wide-lens or a fisheye. The second one is designed for full-spherical panos, using a wide-or a fisheye lens."

These two modes have different graphic displays to indicate progress during shooting. The Mosiac mode display is designed to display mosaic shhoots and the Preset mode display is desgined to displaky spherical shoots.

Currently custom presets are intended to be used for spherical panos.

It is now very easy to creat a preset for a mosaic pano from a mosaic 'shoot' (can be in simulation mode) data file using an XSLT program or the new on-line translator:
http://www.gbiloba.org/papywizard.psp

However if these mosaic presets are then used for pano shoot in Preset mode the graphic display of shooting progress used is that designed for spherical panos and this can be confusing for the user as many shots (any that have negative values for yaw) typically will be taken but will not appear in this display.

It is agreed that a later release of Papywizard will allow manual entry of pano FOV values in Mosiac mode, in addition to the current method of defining the pano limits using the Move arrows. But there are at present no plans to offer selection of presets in the Mosaic mode of shooting.

I would like to propose that both Mosaic and Preset modes of shooting should offer 'relevant' presets.

To this end I offer this proposal:

1. That Preset mode be renamed Spherical mode - which makes it clear what this mode is intended for.

2. That instead of one default preset and one custom preset file we have at least two of each - in the first instance a default preset_mosaic file and a default preset_spherical file, likewise a custom preset_mosaic file and a custom preset_spherical file would be permitted.

3. In each of the shooting Modes - Mosaic and Spherical (was Preset) only the relevant presets would be offered to the user, read from the appropriate default+custom preset files. This would ensure that the graphical shooting progress displays used were appropriate to the preset type (mosaic or spherical)  and displayed progress of the shoot correctly.

4. Consideration could be given to allowing multiple custom preset files named - preset_mosaic_<whatever>.xml and preset_spherical_<whatever>.xml - all would be read (at start up?) and all presets added to the appropriate default presets. This would make it easier for users who would not then have to edit the current single preset.xml file (or the dual custom preset files concept proposed above) to add new custom presets, instead they could use the preset files generated for example from the data file translator directly.

I think these ideas for development are consistent with the current design approach and would improve and enhance useability. They would also make it easier to develop and manage the proposed on-line 'library' of presets from which users could choose a subset for their particular camera/lens combination for various styles of shooting panos.

Last edited by mediavets (2008-11-03 14:04:20)

mediavets wrote:

fma38 wrote:

I finally made a web interface to convert output file to preset file:

http://www.gbiloba.org/papywizard.psp

Comments are welcome.

Excellent, thanks - it works well - could we have English sub-titles?

Would it be possible also to add a 'Save/Save as'  button to allow user to download and save the generated preset file (preferably with option of choosing location and file name) to his/her local file system?

When saving the progam could propose a file name prefix of preset_mosaic_ or preset_spherical_ as per my earlier ideas.

Last edited by mediavets (2008-11-03 14:22:56)

Hi!

I really don´t know . . here two examples of using the 28mm preset (17mm@1,6) using a 17-85mm Canon-lens on the 20D.

Either the head is too unprecise, or there is too small overlap (don´t know where to look for it), or the lens-distortion is too heavy. I have no idea. I lined-up the camera perfectly, levelled the head, set it to "o" (home) and shot.

To straighten the lens-distortion first and stitch afterwards is very uncomfortable - so i will abandon the 17-85mm for panos and will stick to the Nikon 20mm@1,6 with spheres. Even without Exifs and so on.

best, Klaus

P.S.: the tooltips say: 3-6-12-6-3 - but i can´t see 12 in a row . . . i see 3, i see 6 and i see 2x6 in 2 rows.
There´s no row with 12 - as the tooltips suggest. Am i wrong interpreting?

P.S.2: the log is absolutely unreadable - it´s darkblue letters on a black background . .

P.S.2: cancelling "import preset file" fail - neither "Abbrechen" nor "ok" work. Have to kill the app via the main-window.

Last edited by klausesser (2008-11-03 17:16:17)