Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The program is very slow, especially with raw photos, and occasionally doesn't display them properly. #647

Open
MaxCodesPoorly opened this issue Nov 24, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@MaxCodesPoorly
Copy link

Environment:

  • OS: [Windows 10] latest 22H2 update
  • qView version: [6.1, 2023-08-16]

Information:
qView takes about 4 or 5 seconds to load a 6000x4000 .CR2 image (20-30MB) from an SD card with 4,500 images, while the Windows photo viewer takes less than 1.5 seconds. Even with JPEGs it feels a tiny bit sluggish.

Sometimes raw images appear corrupted or blank, but then are fine after you go to a different image and come back. This seems to only happen when flipping through photos in the program, not when opening them from File Explorer.

Also I can't use any of the mouse buttons as shortcut keys, that seems like an oversight as opposed to a bug.

@MaxCodesPoorly MaxCodesPoorly added the bug Something isn't working label Nov 24, 2023
@jurplel
Copy link
Owner

jurplel commented Jan 12, 2024

Also I can't use any of the mouse buttons as shortcut keys, that seems like an oversight as opposed to a bug.

This is tracked here.

qView takes about 4 or 5 seconds to load a 6000x4000 .CR2 image (20-30MB) from an SD card with 4,500 images, while the Windows photo viewer takes less than 1.5 seconds. Even with JPEGs it feels a tiny bit sluggish.

This unfortunately might be a place where the libraries I am using to open images are not as fast as other libraries, which is a major re-engineering effort. That is just a guess, though.

Sometimes raw images appear corrupted or blank, but then are fine after you go to a different image and come back. This seems to only happen when flipping through photos in the program, not when opening them from File Explorer.

Very interesting... can you send a test image if I get a chance to look into this in the future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants