-
Notifications
You must be signed in to change notification settings - Fork 58
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
Large HEIC files not generating preview. #472
Comments
It seems like the error message was truncated. Was there any more content after Also, would it be possible for you to provide a failing test image file? |
Here is the complete log for this event:
And here a direct download link, to avoid any re-encoding on another platform: |
Unfortunately I think that's a relatively generic error from the underlying tool (ImageMagick). What Imagick version do you have installed? You might try seeing what happens when using ImageMagick to access that file+layer directly from the command line. |
I tried running the command on the file but it says "command not found". I am using the Apache docker container, any idea where the executable is stored? I cannot find the information! edit: Upon trying to install the imagemagick. I see that this version is already installed: (8:6.9.11.60+dfsg-1.6+deb12u1
Edit2: The command seems to be "convert" Here a test with the command and an image presenting the bug
Edit3: I tried modifying the policy.xml for ImageMagick-6 under `/etc/ImageMagick-6/' in the latest docker image with unreasonably large limits, still not dice!
|
I seem to have fixed it. Either this previous modification in the previous comment; Or lowering 'preview_max_memory' from 8000 to 1024 |
It seems like the nextcloud update overwrote the "/etc/ImageMagick-6/policy.xml" file. Changing the values to
Is indeed the fix. It seems like the default value (128MP) is limiting new Samsung phones! It would be perhaps wise to increase those values by default to at least 250MP, as 200MP cameras are a thing on phones now. |
I think you're running a custom Docker image. You'll have do something like either mount that file into your container and/or handle it in your Dockerfile if you want to retain it.
I presume the default is coming from the package, not by us. But when you update your image all that gets replaced unless you do the prior thing. That said, it's entirely possible some doc additions (https://github.com/nextcloud/documentation) would be appropriate somewhere to suggest some reasonable numbers for people to use. |
Same issue on NC 30 RC1
|
@AndyXheli Have you tried this? |
I invite you to read the title of this issue. |
Hi @maxi1134, Your comment seems unrelated and not necessary for this issue. The error I'm experiencing appears to be the same as the one described in the existing ticket, so creating a duplicate ticket wouldn't be helpful. If you don't have any relevant information on how to resolve this issue, please refrain from posting unrelated comments. Thank you! |
Fix for those having this issue with large files above. |
I am running into this same issue in my nextcloud docker container. I've created a new policy.xml in a bind mount path the container has access to, with the above recommended changes. I've then set the "MAGICK_CONFIGURE_PATH" environment variable on the container to the path of my modified policy.xml. However, I'm still seeing the same errors. |
@gianlazz The You can debug your policies by running the following command in your container: |
This seems cleaner than any my fix. Using a variable is saner than modifying the file in-situ |
@st3iny so upon trying the I've updated my custom nextcloud container dockerfile that I use with the Memories app container to apt install magick as per below. # Use the official Nextcloud image as the base image
FROM nextcloud:latest
# Install FFmpeg
RUN apt-get update && \
apt-get install -y ffmpeg && \
apt-get clean && \
rm -rf /var/lib/apt/lists/*
# Install latest imagemagick
RUN apt update && apt install -y imagemagick Now with the container running with the
However I'm still getting the same error after these changes. |
Ok, your policies seem to look fine. It could be related to an outdated version of |
I see this in the logs:
ImagickException Failed to read the file File: /maxi1134/files/InstantUpload/Camera/2024/05/20240502_192302.heic Imagick says:
Which is odd; Since the lower res pictures taken work perfectly.
The reason I use HEIC is that live motion pictures don't seem to work with jpeg/mp4 on my S24 ultra.
Thanks for reading!
The text was updated successfully, but these errors were encountered: