hugin-devs team mailing list archive

[tmodes <1067191@xxxxxxxxxxxxxxxxxx>]

The batch processor works always on the saved project files. When you send the project file to the batch processor, the project file is automatically saved.
It was an intentionally design decision.
If we would it implement that it works how you imagine it, it would require to keep the temporary project file in some kind of cache. And after finishing the stitching the temporary file would be deleted. But then I hear the users complaining, why are my changes to the project lost.
Also this approach does not work with queuing project files for the assistant queue.
So the batch processor works only on saved files. If you need different versions, save it under different names.

** Changed in: hugin
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1067191

Title:
  Lost individual settings in delayed stitch mode

Status in Hugin - Panorama Tools GUI:
  Won't Fix

Bug description:
  One panorama can be stitched with different settings many times to chooze best variant from results. It is better then chooze from preview, because preview is not accurate.
  On immediate start stitching jobs, individual settings are kept for each job.
  On delayed start all jobs use sewttings from last project save.

  How to reproduce:
  1) preferences -> stitching -> Start stitching jobs immediately (ON)
       preferences -> stitching -> Run stitching jobs in parallel (OFF)
       preferences -> stitching -> Overwrite existing files (ON)
  2) align some panorama
  3) go to preview and set some good projection
  4) save project and create panorama
  5) during job runs quickly set another projection from preview, NOT SAVE and create panorama again, under diff name (it will be queued after current job in "wait"  status
  6) wait all jobs done, see two different panoramas
  7) preferences -> stitching -> Start stitching jobs immediately (OFF)
  8) repeat steps 2-5
  9) run two waiting jobs from batcher
  10) see two same panoramas with 1st settings.

  Expected behaviour:
  in delayed mode same as in immediate mode

  You as developer can say: "Save project ander different name each time"
  I as user say: "It is not intuitive. If immediate mode works fine, why not for delayed mode?"

  OS:
  Debian Weeze with Sid parts
  Hugin 2012.0.0.a02bf216f42d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1067191/+subscriptions