On Wed, 10 Aug 2022, 23:58 johnfi...@gmail.com,
wrote:
>
>
> On Wednesday, August 10, 2022 at 5:15:33 PM UTC-4 bruno...@gmail.com
> wrote:
>
>> On Wed, 10 Aug 2022, 22:07 johnfi...@gmail.com, <> wrote:
>>
>> These other parameters allow different planes. The basic use is for
>> stitching a
On Wednesday, August 10, 2022 at 5:15:33 PM UTC-4 bruno...@gmail.com wrote:
> On Wed, 10 Aug 2022, 22:07 johnfi...@gmail.com, <> wrote:
>
>>
>> I still hope this question gets a reply from someone who does know what
>> those parameters are intended for and what other tools might be using them.
On Wed, 10 Aug 2022, 22:07 johnfi...@gmail.com, <> wrote:
>
> I still hope this question gets a reply from someone who does know what
> those parameters are intended for and what other tools might be using them.
>
'Mosaic' XYZ control points are mapped onto a vertical plane that is
directly in
Can you clarify some points. (I'm partially asking in case this helps
someone else give you a better answer, but also because I also want to do
some dynamic range things better in hugin than I currently know how to, so
I think your clearer question might draw out a better answer for me).
Your
On Wednesday, August 10, 2022 at 3:24:57 PM UTC-4 Florian Königstein wrote:
> I searched all source code files of Hugin++ for the string "tilt" (e.g.
> there could be variables tilt_x, tilt_y, tilt_z like in libpano13). But
> there wasn't found anything.
> So Hugin probably does not use tilt.
I searched all source code files of Hugin++ for the string "tilt" (e.g.
there could be variables tilt_x, tilt_y, tilt_z like in libpano13). But
there wasn't found anything.
So Hugin probably does not use tilt.
I don't know the meaning of it.
But I wouldn't delete the tilt from libpano13. Hugin
Hi, I'm stitching some pano from a DJI Mavic 3 which have great dynamic
range, but the output does not. What is the cheapest way to retain the full
dynamic range? Is this to do with the raw processing? Or do I need create
multiple tiffs with different settings and run some exposure fusion? I
Do the Pano13 tilt parameters TiX, TiY, TiZ and TiS exist in some form in
Hugin or only in libpano13?
What are they tilting?
Looking at the code, I can't backtrack from implementation to intent.
They are effectively lens parameters, right?
I am thinking in terms of a division between lens
>
> I hope you didn't enable any FOV optimization. I certainly think that is
> fundamentally broken in hugin and isn't safe to mix into any kind of
> controlled test.
>
No, I didn't optimize FOV.
>
>> And in ill-conditioned mathematical problems like here small differences
>> in roundoff
