-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
FFMPEG errors due to invalid video file location (primarily with iOS live photos) #9198
Comments
Did you ever get this sorted out? I am seeing similar behaviour. I do not have any iOS devices uploading assets. originalPath is like this |
Hey, to be honest I stopped checking at some point, since on the surface everything works or at least seems to. My live photos play without issue in the app and on the web from the re-encoded video stream. |
Thanks for the response. Thinking a bit harder about this, I think when I restored a backup or migrated I changed the mountpoint from /encoded-videos to /videos or something? I can find the file at another path, but the database reference is to and old path I guess. |
This is a duplicate of #9390, which has been fixed. The "double extension" bug likely caused the storage template to move the file right before transcoding, leading to the input file "not being found". |
The bug
Hi,
after #8410 has been closed as likely being caused corrupt videos, I thought I'd open a new issue about that. Pretty much every time, I upload a live photo (iOS), I see the error signature posted below.
The only times I get away without this showing up is when uploading larger bulks and the server is occupied with handling face detection for other assets and transcoding other videos. I have all job concurrency set to
1
, but to me that still has the flavor of a race condition as it looks like the video files were already moved from theupload/
(temporary) location to thelibrary/
folder. Also the filename seems a bit weird with the duplicate.mov
!?Anyways, seeing this gives me a bad feeling, however, I cannot detect a consequence of the failure. The motion part is - in the cases I checkedd - successfully encoded at some point after the error.
Thanks once more for the great work!
The OS that Immich Server is running on
Raspbian
Version of Immich Server
v1.103.1
Version of Immich Mobile App
v1.103.0
Platform with the issue
Your docker-compose.yml content
default
Your .env content
Reproduction steps
Relevant log output
Additional information
May be a race condition, so reproduction steps may not work for everyone.
The text was updated successfully, but these errors were encountered: