panostart advanced options ?

[juju]

Hello everyone,

As I try to improve my photo workflow, I'm looking for a way to integrate panostart inside, instead of doing everything manually with hugin.

Today, while reviewing my pictures, I rate/tag stuff and adding a 'pano' tag to a group of pictures that could be used to generate a panoramic, checking it after if I have the time.

Most of the time, those pictures are in sequence with less than x seconds between them, the same aperture. The rest can change especially if mode is auto/semi-auto and sometimes, the same picture could be taken multiple times (if I use bracketing: same settings but different exposure compensation)

As described on http://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Creating_hugin_projects_on_the_command-line, I did a panostart on a test folder but it generates way to many false pto.

The man page is a bit reduced so didn't find much help here.

I'm looking for a way that panostart takes in account (as options)

* Exposure Compensation: generate only for on EC level and if possible, put a note than other EC are available if in manual review they appear better than default. With bracketing, EC level can 0/-1/1, -2/-1, 0/-0.3/+0.3, ...

* define a minimum number of image in the pano, else it's not. For me, I don't do panoramic with less than 3 images (outside of use bracketing)

* use tags. As said before, I use a 'pano' tag and others. I want to say: here, there is a 'pano' tag, there is a lot of chance there is pano, maybe with a bit more images around if I did the tagging quickly; hey, here there is 'text' tag, there is no way it's inside a panoramic.

* define if panoramic source pictures use same orientation or mixed (landscape/portrait). For me I always keep the same orientation.

* add a processing tag before or after (better) the whole process. for example, 'panostart' or 'maybe_panostart' if process failed

Any ideas/advices ?

Thanks a lot,

juju

Note: sorry if this message is published twice. don't find it in archive whereas I sent it few hours ago.

[Bruno Postle]

On Oct 12, 2012 4:45 PM, "juju" <julie...@gmail.com> wrote:
>
> As I try to improve my photo workflow, I'm looking for a way to integrate panostart inside, instead of doing everything manually with hugin.
>
> Today, while reviewing my pictures, I rate/tag stuff and adding a 'pano' tag to a group of pictures that could be used to generate a panoramic, checking it after if I have the time.
> Most of the time, those pictures are in sequence with less than x seconds between them, the same aperture. The rest can change especially if mode is auto/semi-auto and sometimes, the same picture could be taken multiple times (if I use bracketing: same settings but different exposure compensation)
>
> As described on http://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Creating_hugin_projects_on_the_command-line, I did a panostart on a test folder but it generates way to many false pto.

Yes panostart works well for the kind of panoramas I was shooting when it was written, in particular it only really works when all the photos in a folder are a series if panoramas. When the folder is a mixture with 'normal' photos it gets confused.

I don't have a solution for this, my current technique with these mixed folders is to view the folder as thumbnails in Nautilus or gthumb, select each panorama series manually, right click and create an unaligned .pto project for each. Then I send these to the Hugin batch processor for aligning and stitching.

This is just as quick as your tagging idea, but it isn't as automatic as I'd like, I need a tool that can be given a list of these .pto projects and will do the right thing: aligning and stitching if unaligned, otherwise stitching if already aligned - This could be done with a Makefile or the Hugin batch processor, I'm not sure, maybe both.

--
Bruno