Talk:Example Workflow
From Autopano
Greetings,
It is quite common for users to work on a batch of panos - say from one shoot, create .pano files for those panos they want to keep - after processing, then run a batch render against the stored panos, when their machine is not doing anything else!
I had been in the habit of loading the stored .pano files into the APP main window and then doing render all. But doing that means you have to go through the stage where the .pano files are loaded, blended etc.
But, of course, there is an alternative: you load APP, click on the render icon, and then use the 'add project' feature of the render batch window. Then you get to render directly.
All this can be worked out from the documentation, i.e. each stage is documented: but I can't find this process documented as a useful workflow.
Could we find some way of adding such 'tips and tricks' to the documentation? Since users can see the documentation is presently under development perhaps you could trawl for suggestions, via the 'Using Autopano' part of the forum.
More work, but could strengthen the advice available. I would be happy to repeat what I have written here in the forum to help get things started.
PS. Of course, for this to work, you have to either use the default render settings, or use the Render dialogue with Apply, at the .pano creation/storage stage!
DJA
Mind: not made up
I'm not sure what Alex would want, or what's best in terms of writing thorough and useful (and usable!) documentation.
One part of me prefers plenty of short, simple, to-the-point articles/pages. Several simple steps and that's all.
Another part wants every little feature, bug, workaround, process, workflow, good/bad practice, even habit - documented.
What you suggest (the first-create-panos-then-batch-render-them) seems a nice twist; however on a larger scale it's just a personal preference. I, for one, use the workflow described in this page - render while editing, just set the priority to Lowest. So after I finish with all panorama editing, I already have ready TIFFs for Photoshop work and by the time I finish the PS work... APP's done rendering long before that.
My point is that such "tips" are not suited for a first-time user, or a casual user even. Those are for the mid-range people that seek to improve their skills, but don't yet have their own set of habits and ways. I'm not comfortable with setting such things in stone, as each has to discover what works best for him.
So maybe what you're talking about is like a schematic of sorts, like a UML diagram, consisting of the main steps of pano creation and each APP user can plot their steps and describe specific hints, steps, etc.
