>
>> Is this YPR the "global" optimised one, or a custom YPR for the image
>> pair whose CPs are being edited/created?
>>
>>
> The optimisation is done only for image pair which is currently edited.
> The result of the optimisation is only used internally to determine the
> position of the new cp.
Am Sonntag, 31. Mai 2015 10:24:41 UTC+2 schrieb bugbear:
>
>
> Is this YPR the "global" optimised one, or a custom YPR for the image
> pair whose CPs are being edited/created?
>
>
The optimisation is done only for image pair which is currently edited. The
result of the optimisation is only used
On 30 May 2015 at 07:47, T. Modes wrote:
>
> Am Freitag, 29. Mai 2015 22:46:00 UTC+2 schrieb bugbear:
>>
>>
>> Given that hugin has a handy panotools library available,
>> might I suggest that a quick 'n' dirty YPR model be applied
>> to the two windows?
>>
>
> From the release notes of 2015.0
>
2015-05-30 8:47 GMT+02:00 T. Modes :
> Am Freitag, 29. Mai 2015 22:46:00 UTC+2 schrieb bugbear:
>>
>>
>> Given that hugin has a handy panotools library available,
>> might I suggest that a quick 'n' dirty YPR model be applied
>> to the two windows?
>>
>
> From the release notes of 2015.0
> * The f
Am Freitag, 29. Mai 2015 22:46:00 UTC+2 schrieb bugbear:
>
>
> Given that hugin has a handy panotools library available,
> might I suggest that a quick 'n' dirty YPR model be applied
> to the two windows?
>
>From the release notes of 2015.0
* The fine-tune and auto-estimate functions in the c
