Sie sind nicht angemeldet.

1

Montag, 2. Mai 2016, 21:35

KRpano tools 19pr4 reduces detail?

Hi all!

For example, nativ pics are cubefaces 1909x1909 (equi 6000x3000).
18.3 generate 3-levels multiresolution 1910x1910, 956x956 and 512x512.
19pr4 generate only 2-levels multiresolution 1792x1792 and 1024x1024.
This means that the maximum resolution of 19pr4 is significantly less than the nativ resolution of original files.
Why is there a degradation of image quality in 19pr4?

Timescale

Schüler

Beiträge: 120

Wohnort: Netherlands

Beruf: Archaeologist, Timescale R&D

  • Nachricht senden

2

Montag, 2. Mai 2016, 22:01

multires.config

Have you checked the settings in multires.config?

3

Montag, 2. Mai 2016, 22:18

I used default settings in both cases.
levels=auto
maxsize=auto
maxcubesize=auto

What else do I need to check?

4

Montag, 2. Mai 2016, 22:33

Other example:
cubefaces 3501x3501
19pr4 generate 3584x3584 1792x1792 768x768
18.3 generate 3502x3502 1752x1752 876x876
3584x3584 is significant more than nativ pics... But added one additional interpolation, which doesn't enhance the image quality :(((

Timescale

Schüler

Beiträge: 120

Wohnort: Netherlands

Beruf: Archaeologist, Timescale R&D

  • Nachricht senden

5

Montag, 2. Mai 2016, 22:52

I don't use the tool myself so I'm not sure, but I'm just wondering, what does something like "levels = auto" do when you say, change it? Say to 3? Just checking alone probably won't solve a lot of problems..

6

Montag, 2. Mai 2016, 23:34

Yes, you are right, "levels = 3" can be a solution for the particular case 6000x3000. I get 1910x1910, 1024x1024 and 512x512.
But I have the panoramas with different image resolution. "levels = 3" is not enough for equi 14.000x7.000. In this case, I need 4-levels multiresolution as minimum.
I think, every time to edit the configuration file manually is not a good idea. How to return the algorithm which correctly worked in 18.3 to the current version 19pr4?

Timescale

Schüler

Beiträge: 120

Wohnort: Netherlands

Beruf: Archaeologist, Timescale R&D

  • Nachricht senden

7

Montag, 2. Mai 2016, 23:42

I think you need to take a look at : http://krpano.com/tools/kmakemultires/config/#levelstep and http://krpano.com/tools/kmakemultires/config/#minsize and maxsize.

These seem to explain how to setup the configfiles.

Again, I don't use these tools so I don't really know, but Klaus generally documents these sorts of things quite well.

8

Dienstag, 3. Mai 2016, 00:28

I don't see the differences in the multires.config files in 18.3 and 19pr4. But I see the different results. So, I think that the bug is in a different place. Maybe I'm wrong.
I hope that Klaus will tell the solution to this problem.

PS
Timescale, thank you very much for attention to my problem *smile*

9

Samstag, 7. Mai 2016, 10:15

Hi,

that's not a bug - that's intention for faster tile GPU uploading of non-power-of-2-sized tiles (at the edges of the images) and better image quality due mipmapping (less aliasing).

Disable the 'adjustlevelsizesformipmapping' setting in the config files if you don't want or like that behavior:
http://krpano.com/tools/kmakemultires/co…esformipmapping

Best regards,
Klaus