Google Takeout has MVIMG files without extension that are marked as unsupported

[satmandu]

e.g., from the import log:

2025-01-16 10:40:48 WRN unsupported file file=Google Photos:<album>/MVIMG_20180722_120942 reason=unsupported file type

ls MVIMG_20180722_120942*
-rw-r--r-- 1 satadru satadru 4028582 Jan 12 14:32 MVIMG_20180722_120942
-rw-r--r-- 1 satadru satadru 7655876 Jan 12 14:32 MVIMG_20180722_120942.jpg
-rw-r--r-- 1 satadru satadru     854 Jan 12 15:18 MVIMG_20180722_120942.jpg.json
file MVIMG_20180722_120942
MVIMG_20180722_120942: ISO Media, MP4 v2 [ISO 14496-14]

Is there a way to get those to import properly?

[satmandu]

I am using this command from a completely untarred set of google photos takeout exports, with immich-go built from source on Ubuntu 24.10.

immich-go --server=http://localhost:2283 -k=API_KEY \
upload from-google-photos -u -a --include-untitled-albums \
--manage-burst=Stack --manage-heic-jpeg=StackCoverHeic \
--manage-raw-jpeg=StackCoverJPG \
Google\ Photos/

[simulot]

Immich neither support files without extension.

Usually, for android, movie part of the motion pictures is also embedded into the JPG. In that case the JPG is sufficient for immich to create the live picture. Then then MVIMG without extension can be discarded. An easy check is to drop the JPG on the immich page, and check.

In the takeout, when the JPG is compressed by Google Photos, the resulting file is corrupted. The movie part isn't located at the place indicated by metadata... and immich doesn't find the movie part. Therefore, the API call to link the JPG with its movie fails. The image remains still.

If the JPG doesn't contains the movie part, the MP4 extension can be added to the name when the file is uploaded ... An API call can link the JPG with the movie.

[satmandu]

Ah, I guess they are being handled! Thanks for the explanation.

[simulot]

I let this open, to manage the eviction of MVIMG files