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.

#!/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 $_;

}

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

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

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/ … e_and_PyQt

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

fma38 wrote:

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 wrote:

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/ … e_and_PyQt

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 (2011-06-04 08:29:53)

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 (2011-06-04 08:27:20)

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 (2011-06-04 13:37:06)

christine wrote:

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.

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.

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

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/ … Merlin_FAQ

What do-you want to know exactly ?