[papywizard v2] Annoncement, feedback, bug report

[bradtem]

by bradtem » Fri Jun 25, 2010 7:13 pm

By the way, here's a quick and dirty perl script I wrote to correct yaw and pitch values in papywizard xml files if you didn't set the reference.

Code: Select all

#!/local/bin/perl

$pitchmod = shift @ARGV;
$yawmod = shift @ARGV;


while( <>  ) {
    if( ($pitch, $yaw) = /<position pitch="([\d.-]+)".*yaw="([\d.-]+)"/ ) {
        $newpitch = $pitch + $pitchmod;
        $newyaw = $yaw + $yawmod;
        s/pitch="$pitch"/pitch="$newpitch"/;
        s/yaw="$yaw"/yaw="$newyaw"/;
    }
    print $_;

}

[mediavets]

by mediavets » Sat Jun 26, 2010 9:30 am

I am investigating an issue that has emerged recently whereby you don't get any thumbnail preview in the Papywizard Import filter UI - see screenshot.

It seems this does not occur with PW 2.1.18 and all earlier versions.

It seems to occur mostly but not always with PE 2.1.19.

It seems to occurs always with PW 2.1.20.

In all instances you can nevertheless continue and the detection and stitch proceeds as expected.

Is this failure to display the thumbnail preview the result of some change in the PW data XML format?

Why might it occur sometimes but not always with PW 2.1.19?

[fma38]

by fma38 » Sat Jun 26, 2010 10:26 am

Is it not the problem we identified some days ago, with utf-8 characters in the header fields?

[mediavets]

by mediavets » Sat Jun 26, 2010 10:48 am

Is it not the problem we identified some days ago, with utf-8 characters in the header fields?

I'm 'lost' now.

The problem the other day related to PW custom preset XML files as I recall.

Doies the same thing somehwo affect PW XML data files?

Below are header sections from PW 2.1.17 and PW 2.1.20 XML data files they look pretty much the same to me - not sure what changed between versions b andf c anyway?

Anyway who needs to fix something to make it work - is this an issue with Papywizard or an issue with APP/APG coding?

Header section from PW 2.1.17 XML data file.

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<papywizard version="b">
    <header>
        <general>
            <title>
                Here goes the title
            </title>
            <gps>
                Here goes the location
            </gps>
            <comment>
                Generated by Papywizard 2.1.17
            </comment>
        </general>
        <shooting mode="mosaic">
            <headOrientation>
                up
            </headOrientation>
            <cameraOrientation>
                portrait
            </cameraOrientation>
            <stabilizationDelay>
                0.5
            </stabilizationDelay>
            <startTime>
                2010-05-23_16h42m17s
            </startTime>
            <endTime>
                2010-05-23_17h04m56s
            </endTime>
        </shooting>
        <camera>
            <timeValue>
                0.9
            </timeValue>
            <bracketing nbPicts="1"/>
            <sensor coef="1.5" ratio="3:2"/>
        </camera>
        <lens type="rectilinear">
            <focal>
                150.0
            </focal>
        </lens>
        <mosaic>
            <nbPicts pitch="10" yaw="10"/>
            <overlap minimum="0.25" pitch="0.25" yaw="0.25"/>
        </mosaic>
    </header>

Header section from PW 2.1.20 XML data file.

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<papywizard version="c">
    <header>
        <general>
            <title>
                Here goes the title
            </title>
            <gps>
                Here goes the location
            </gps>
            <comment>
                Generated by Papywizard 2.1.20
            </comment>
        </general>
        <shooting mode="mosaic">
            <headOrientation>
                up
            </headOrientation>
            <cameraOrientation>
                portrait
            </cameraOrientation>
            <stabilizationDelay>
                0.5
            </stabilizationDelay>
            <counter>
                002
            </counter>
            <startTime>
                2010-06-24_19h32m25s
            </startTime>
            <endTime>
                2010-06-24_19h41m49s
            </endTime>
        </shooting>
        <camera>
            <timeValue>
                1.0
            </timeValue>
            <bracketing nbPicts="1"/>
            <sensor coef="1.5" ratio="3:2"/>
        </camera>
        <lens type="rectilinear">
            <focal>
                150.0
            </focal>
        </lens>
        <mosaic>
            <nbPicts pitch="10" yaw="10"/>
            <overlap minimum="0.25" pitch="0.25" yaw="0.25"/>
        </mosaic>
    </header>

[fma38]

by fma38 » Sat Jun 26, 2010 2:01 pm

The version 'c' just add the counter tag... I don't think this is the cause of the problem...

[fma38]

by fma38 » Sat Jun 26, 2010 2:07 pm

The problem the other day related to PW custom preset XML files as I recall.

You may be right. But I'm pretty sure we found the cause of this problem, some days ago...

[mediavets]

by mediavets » Tue Jul 13, 2010 11:35 am

The link to godmode.deb (http://www.gbiloba.org/download/maemo/godmode.deb) is broken from this page of instructions for imstalling Papywizard on Nokia N800 and N810 Internet Tablets:
http://www.autopano.net/wiki-en/action/view/Install_Papywizard_v2_on_Nokia_N8x0#Install_the_required_program_packages_-_godmode.2C_Python_2.5_runtime_and_PyQt

I have been unable to locate an alternative source for this file.

[fma38]

by fma38 » Tue Jul 13, 2010 2:55 pm

Look here:

http://wiki.maemo.org/Root_access#rootsh

[mediavets]

by mediavets » Tue Jul 13, 2010 3:18 pm

Look here:

http://wiki.maemo.org/Root_access#rootsh

Frederic,

Thanks for this link to a 'workaround'.

Does this mean we've lost godmode.deb forever?

If so then we'll need to update the install instructions I guess.

[fma38]

by fma38 » Tue Jul 13, 2010 4:06 pm

Yes, I think rootsh is the new official mechanism. Someone on the forum has used it some weeks ago...

If it works fine, you can update the wiki.

[mediavets]

by mediavets » Tue Jul 13, 2010 4:42 pm

Yes, I think rootsh is the new official mechanism. Someone on the forum has used it some weeks ago...

If it works fine, you can update the wiki.

It seems to work fine so I've updated the wiki:
http://www.autopano.net/wiki-en/action/view/Install_Papywizard_v2_on_Nokia_N8x0#Install_the_required_program_packages_-_rootsh.2C_Python_2.5_runtime_and_PyQt

[fma38]

by fma38 » Thu May 05, 2011 5:25 pm

Ok, I released the 2.1.21 version of Papywizard. Main changes:

+ Added 'Clauss' plugin
+ New serial baudrate param
+ Added 'Trigger only once" param in shutter plugins
+ New dialog for Goto feature
- removed some calls to event loop in main controller on MacOS
- removed "reverse direction' feature (use new 'nearest-corner')
- increased timer 'repeat' param max value up to 99999
x fixed connect param in pluginsField
x fixed missing ':' in 'Merlin/Orion' plugin
x fixed 'Generic Tethered' plugin params usage
x fixed 'nearest-corner' bug when not connected

[christine]

by christine » Sat Jun 04, 2011 6:40 am

Hi all,

Received my Merlin panohead and papywizard two weeks ago and set it up, using a MacbookPro and a Nikon D7000. A few problems understanding the directions to start with but worked it out. I wrote a couple of presets in papywizard for a VR using a fisheye lens and one for a rectilinear 70mm zoom, all working fine, good results (I have a software background).

Then I went to write some presets for gigapixel photos with a rectilinear 200mm zoom, which we've done before by hand. I find that if the increments in pitch in the preset are 8 degrees or more, all works fine, but of course that's not close enough to stitch the photos and I need about 5 degree intervals. When I set the increment to less than 8 degrees, at the end of the first row the camera just goes out of control and moves upwards continually, moving out of the shooting pattern shown in papywizard. In all cases the display on papywizard is correct in all respects and the panohead behaves perfectly until that point.

I tried the preset generator on the web which assumes zenith at 0,0 and has very small increments and the panohead goes out of control as soon as it starts.

I'm stuck. Given that I hear the panogear can use intervals of 0.1 degrees, what is the problem? The timing is bad as I was intending to have these presets ready for a commercial shoot next week. Can anyone help with suggestions?

xml is:

<preset name="0_40_fl200TRIAL">
<tooltip>
focal length: 200mm
horizontal FOV: 0 to 40
vertical FOV: 20 to -20
initial position 0,0
planar projection
</tooltip>

<shoot>

<!-- row 1 -->
<pict yaw="0." pitch="20."/>
<pict yaw="10." pitch="20."/>
<pict yaw="20." pitch="20."/>
<pict yaw="30." pitch="20."/>
<pict yaw="40." pitch="20."/>
<!-- row 2 -->
<pict yaw="40." pitch="15."/>
<pict yaw="30." pitch="15."/>
<pict yaw="20." pitch="15."/>
<pict yaw="10." pitch="15."/>
<pict yaw="0." pitch="15."/>
<!-- row 3 -->
<pict yaw="0." pitch="10."/>
<pict yaw="10." pitch="10."/>
<pict yaw="20." pitch="10."/>
<pict yaw="30." pitch="10."/>
<pict yaw="40." pitch="10."/>
<!-- row 4 -->
<pict yaw="40." pitch="5."/>
<pict yaw="30." pitch="5."/>
<pict yaw="20." pitch="5."/>
<pict yaw="10." pitch="5."/>
<pict yaw="0." pitch="5."/>
<!-- row 5 -->
<pict yaw="0." pitch="0."/>
<pict yaw="10." pitch="0."/>
<pict yaw="20." pitch="0."/>
<pict yaw="30." pitch="0."/>
<pict yaw="40." pitch="0."/>

</shoot>
</preset>

Last edited by christine on Sat Jun 04, 2011 7:29 am, edited 1 time in total.

[mediavets]

by mediavets » Sat Jun 04, 2011 6:48 am

Welcome to the forum....

Do I understand that you are trying to create a preset to shoot a full spherical pano using a zoom lens set at 200mm focal length on a D7000?

[christine]

by christine » Sat Jun 04, 2011 7:08 am

Hi Andrew,

No, I'm trying to do a small shot of about 40 degrees yaw which will be in a planar projection, using the D7000 and an 18-200 lens. When I've got that working, I can then use the code to expand it.

I have a preset working nicely already for a full spherical VR using a fisheye lens.
Chris.

Last edited by christine on Sat Jun 04, 2011 7:27 am, edited 1 time in total.

[fma38]

by fma38 » Sat Jun 04, 2011 7:51 am

Why don't you use the mosaic mode? Just give all informations to Papywizard (focal lens and so), and it will compute the correct increments...

[christine]

by christine » Sat Jun 04, 2011 8:08 am

Hi Frédéric,

As I'm setting this up for others to use I thought the presets would be easier for them. I can try it in Mosaic mode, but I would like to have confidence in the format of the presets and the Panogear and at the moment I'm failing to understand what I did wrong.

Without having any idea what I'm talking about Could this be anything to do with the alternate drive (?) being set at 7 degrees as in the default which I haven't changed? I tried some tests just taking the first two rows as examples:

If row1 in the code above is 20 degrees and I set row2 to either 15, 14 or 13 degrees, the camera continues to move up above the shooting pattern as shown in the image as soon as it tries to go to the first position in row2
If row1 is 20 degrees and I set row2 to 12 degrees or less, everything works fine.

In other words, the smallest increment I am able to set is without an error is 8 degrees. Is it something to do with the smaller camera movements when it's set smaller than 8 degrees? Papywizard version is 2.1.20

Chris.

Last edited by christine on Sat Jun 04, 2011 12:37 pm, edited 1 time in total.

[fma38]

by fma38 » Sat Jun 04, 2011 11:51 am

Strange... I don't understand the issue...

[mediavets]

by mediavets » Sat Jun 04, 2011 1:11 pm

Hi Frédéric,

As I'm setting this up for others to use I thought the presets would be easier for them. I can try it in Mosaic mode,

I suggest you do that.

Are you aware of the various (different) ways to define the scope of a Mosaic shoot?:

1. Set opposing corner positions.

2. Directly enter desired panoFOV.

3. Directly enter no. of rows and columns.

With options 2 and 3 the software will compute shooting positions centred on the position set as the reference position. So these two options are easy for others to use. Much easier in my opinion that offering a preset for a partial pano.

but I would like to have confidence in the format of the presets and the Panogear and at the moment I'm failing to understand what I did wrong.

Without having any idea what I'm talking about Could this be anything to do with the alternate drive (?) being set at 7 degrees as in the default which I haven't changed? I tried some tests just taking the first two rows as examples:

If row1 in the code above is 20 degrees and I set row2 to either 15, 14 or 13 degrees, the camera continues to move up above the shooting pattern as shown in the image as soon as it tries to go to the first position in row2
If row1 is 20 degrees and I set row2 to 12 degrees or less, everything works fine.

In other words, the smallest increment I am able to set is without an error is 8 degrees. Is it something to do with the smaller camera movements when it's set smaller than 8 degrees? Papywizard version is 2.1.20

If you wish to test your theory that it's associated with use of Alternate drive then turn it off and see what happens.

..........

The only time I've seen the Merlin mount 'go crazy' was when I had light leaking through the base of the bubble level affecting the integrity of the optical encoders. This is easily fixed by taping over or under the bubble level.

[mediavets]

by mediavets » Sat Jun 04, 2011 3:06 pm

Christine,

I 'tidied up' your custom preset and it worked fine for me using the File/Import preset file... method on a Nokia N800 Internet Tablet with Papywizard 2.1.1.21.

Here's my variant of your preset - just added header and <papywizard> tags and closing </preset> tag as I recall.

You must save it with UTF-8 encoding.

Your tooltip description is incorrect; the vertical FOV defined in the preset is '0 to 20' not '20 to -20' not that that will make any difference to the operation of the preset.

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<papywizard>
<preset name="0_40_fl200TRIAL">
    <tooltip>
        focal length: 200mm
        horizontal FOV: 0 to 40
        vertical FOV: 20 to -20
        initial position 0,0
        planar projection
    </tooltip>
   
    <shoot>

                <!-- row 1 -->
                <pict yaw="0." pitch="20."/>
                <pict yaw="10." pitch="20."/>
                <pict yaw="20." pitch="20."/>
                <pict yaw="30." pitch="20."/>
                <pict yaw="40." pitch="20."/>
                <!-- row 2 -->
                <pict yaw="40." pitch="15."/>
                <pict yaw="30." pitch="15."/>
                <pict yaw="20." pitch="15."/>
                <pict yaw="10." pitch="15."/>
                <pict yaw="0." pitch="15."/>               
                <!--  row 3 -->
                <pict yaw="0." pitch="10."/>
                <pict yaw="10." pitch="10."/>
                <pict yaw="20." pitch="10."/>
                <pict yaw="30." pitch="10."/>
                <pict yaw="40." pitch="10."/>
                <!-- row 4 -->
                <pict yaw="40." pitch="5."/>
                <pict yaw="30." pitch="5."/>
                <pict yaw="20." pitch="5."/>
                <pict yaw="10." pitch="5."/>
                <pict yaw="0." pitch="5."/>         
                <!-- row 5 -->
                <pict yaw="0." pitch="0."/>
                <pict yaw="10." pitch="0."/>
                <pict yaw="20." pitch="0."/>
                <pict yaw="30." pitch="0."/>
                <pict yaw="40." pitch="0."/>
               
        </shoot>
</preset>
</papywizard>

[christine]

by christine » Sat Jun 04, 2011 4:08 pm

Thanks Andrew, I really appreciate the help The code I posted was cut from my presets.xml file which contained other presets, so didn't have the top and bottom tags included - sorry, I should have said that. It's good to know that it runs correctly for you.

>The only time I've seen the Merlin mount 'go crazy' was when I had light leaking through the base of the bubble level affecting the integrity of the >optical encoders. This is easily fixed by taping over or under the bubble level.

It certainly 'went crazy' so this might be the problem. Unfortunately I can't try any more until next Saturday as the panogear is offsite for the week... with the trusty Nodal Ninja in tow.

I'll let you know how I get on and what the problem was if we can solve it. Back in a few days.
Chris.

[christine]

by christine » Sat Jun 25, 2011 7:53 am

Hi Andrew and all,

Sorry it took me so long to get back to you. I only just got back to the panohead problem.

I tried mosaic mode and it works perfectly in every respect. Now that I've got used to it, mosaic mode is actually easier as it allows for quick adjustment of the area being shot.

The presets still don't work. The camera wanders off upwards at the beginning of the second row still. I can't understand how my preset worked for Andrew's gear but not for ours. However now that it works perfectly in mosaic mode, I'm tempted to dump the presets and not worry about them. Guess I'm just reporting it here in case anyone else has the problem and the information might be useful.

I'll only have to use a preset for a 360 spherical gigapixel but I think I'll worry about that later when there is a need for it. I now believe that the panohead is not faulty in any way and that was my main concern.

I really appreciate your willingness to help me.
Chris.

[walterfiton9]

by walterfiton9 » Sun Jul 24, 2011 7:43 am

Hi there I am new here
one question, dose anybody know which (equipment) Bernd Prà¶schold use to rotate his camera?
http://www.sternstunden.net/ (video number(2) in the list, is the video where all the stars are fix, do not move, and the earth (horizon) rotate around them.

it is a Merlinor or other?
Many many thanks for your help

Walter

[RobSherratt]

by RobSherratt » Sat Oct 20, 2012 2:55 pm

Any news about the papywizard web site and wiki?
They are both currently inaccessible.
http://www.papywizard.org just shows an FTP download view.
None of the links from here work, just get 404 not found
http://www.autopano.net/wiki-en/action/view/PapyMerlin_FAQ

Thanks,
Rob

[claudevh]

by claudevh » Sat Oct 20, 2012 3:24 pm

Hello Rob,

This is correct that "papywizard.org" isn't working but the wiki work as it must:
http://www.autopano.net/wiki-en/action/view/PapyMerlin_FAQ

What do-you want to know exactly ?