On Monday, January 31, 2022 at 5:35:33 PM UTC-5 bruno...@gmail.com wrote:
>
> If not, then send me your sourceforge username. Note that sourceforge
> supports a fork/pull-request workflow (similar to github), so you can
> work on a separate personal repository just as easily as the main
>
Hi John, I'm just catching up on my email, do you have access to the
Hugin repository yet?
If not, then send me your sourceforge username. Note that sourceforge
supports a fork/pull-request workflow (similar to github), so you can
work on a separate personal repository just as easily as the main
It now appears to me that the limitation may be in the device driver
(Nvidia). There is quite a lot to this malfunction that seems to me to be
almost impossible to fit into the theory that the malfunction is in the
driver. But I've stepped through the code down to the point that the image
is
I guess I posted too early in the morning, while rushing out to shovel snow.
When I did the testing, I was careful about correctly computing the 2**27
zoomed image size. In my above two posts, I wasn't:
7035x4730 is just over 2**25 so at 200% it should fail.
I was correct the first time that
Oops. I meant 800% for the 3548x2365
On Sunday, January 30, 2022 at 7:34:35 AM UTC-5 johnfi...@gmail.com wrote:
>
>
> At 400% zoom, a 3548x2365 original image failed.
> At 200% it should take a 14190x9460 original image. I ought to test that,
> but I haven't yet.
>
>
>
--
A list of
On Sunday, January 30, 2022 at 12:24:42 AM UTC-5 GnomeNomad wrote:
> Which version of Hugin is this? I have v2021.0.0.52df0f76c700. Just
> tried zooming in on some of my biggest panoramas, didn't encounter any
> problems.
>
It is my own build from a mercurial clone from Jan 16. Also, I
I don't have Windows here, I have Linux, with Nvidia's driver, v 460.91.03.
Which version of Hugin is this? I have v2021.0.0.52df0f76c700. Just
tried zooming in on some of my biggest panoramas, didn't encounter any
problems.
On 1/29/22 03:09, johnfi...@gmail.com wrote:
I don't actually know
I don't actually know enough about the interface between the display driver
and the level immediately above it to know whether it is even possible for
this bug to be related to the display driver.
If it is related to the display driver, I'm using the closed source Nvidia
340 driver (the driver
Could it be related to display driver?
On January 28, 2022 2:10:46 PM HST, "johnfi...@gmail.com"
wrote:
> In my experimentation for 400% and 800% magnification, I am experiencing a
> malfunction (entire image displays as black) when the magnified image is
> over 134217728 pixels.
>
> I have
In my experimentation for 400% and 800% magnification, I am experiencing a
malfunction (entire image displays as black) when the magnified image is
over 134217728 pixels.
I have a bad code change work around for the problem and will figure out a
better code change.
*Who do I ask for the
10 matches
Mail list logo
