High-resolution image rendering could be improved nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

Here is what I see when I zoom in using Amethyst VS what I see in the browser:

Reply to this note

Please Login to reply.

Discussion

I just posted this note. I include the actual link to the website the map came from. Scroll to the bottom to get the link to the fully functional map.

https://primal.net/e/note1yr8urm8xd3ypqdpl57ysff8cslgv6r23la02zu4mc75yd7aq7efsq84jc0

Hey, Gigi, was this image uploaded from Amethyst like that? I am trying to replicate but new uploads show a much higher-res image. I am not sure what could have interferred with the resolution calculations. 🤔

No, it wasn't uploaded by any client. It's hosted on the website of the research faculty. It just has a very high resolution, and it might be that the image rendering module that Amethyst is using in its "gallery" view can't deal with a resolution that high?

nostr:note10hd87fw8waay0fzla6vx34mrp8k733skl8ghddttg6rlv8qz0zqqdlw4sg

ohhh interesting... I will do some research into this. Can you share the original link? I think the only two links in the message was from Nostr.build.

Scroll to the bottom of the page.

nostr:note1yr8urm8xd3ypqdpl57ysff8cslgv6r23la02zu4mc75yd7aq7efsq84jc0

Thanks! Let me look into some details of the upstream lib we use. Its likely that it is downloading the full image but compressing before showing on screen.

It turns out the app crashes if I enable these large images to be displayed. I need a fix in the upstream library we use :(

Not too bad for. as expected pixelation.

Oh wait, nvm. I was zooming in on the second image, not thw OP image. Yup.