-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error when trying to combine 4x or 16x pixelshift from A7R4 #1
Comments
I managed to upload the images I tried to combine: |
Hi, and thanks for the report! |
Thank you for the quick response. Indeed, I use python3. I tried to run the tool with python2 but it complains about the tifffile module missing:
TLDR: No matter what I tried, I can't get python2 to find the tifffile module. I used aptitude to install the packages tifffile, python-imageio, no change. I used pip2 to install imageio, no change. I tried to install tifffile using pip2 but that fails with a missing file (one which actually is installed on my machine)
I installed tifffile via conda, no change. Now if I try to install tifffile via pip2 is says:
But python2 still doesn't find the module. |
I suggest you try pyenv to manage multiple python environments, without messing up with the system. Looking at the above error messages, it's clear that pip2 is still trying to use python3. |
commit ceb4602 should fix this, can you please confirm when you have the chance? |
I tried it and it works as expected. The 16x pixelshift shows some minor artifacts but I don't know if they are caused by RawTherapee, I'll need to capture more photos for testing. |
the 16x will show artifacts if there is a little motion, and they will be very hard to correct. That's because a 16x PS is essentially a 4x PS in which each of the frame is pre-combined. That's how the format works. It means that RT won't be able to detect and correct motion properly there, you need a pixel editor to fix them |
When combining 4 or 16 images from an R4 I get the following message:
KeyError: 1.25
I removed the try/catch block and got a stack trace:
I tried different methods to call the program, made no difference:
I'm using Debian testing (bullseye).
The text was updated successfully, but these errors were encountered: