vivo motion photos appear as a photo and a video

[qingxianaaa]

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

• Yes

The bug

When backing up vivo motion photos to Immich, it displays as a separate photo and an MP4 video. Hoping for better adaptation to vivo's motion photo format

The OS that Immich Server is running on

debian12,docker

Version of Immich Server

v2.0.1

Version of Immich Mobile App

v2.0.1

Platform with the issue

• Server
• Web
• Mobile

Device make and model

vivo x100 pro

Your docker-compose.yml content

#
# WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose
#
# Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.

name: immich

services:
  immich-server:
    container_name: immich_server3
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - /vol2/1000/docker/imi/im/im/library:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
#      - /vol2/1000/docker/imi/im/im/library:/up
    env_file:
      - .env
    ports:
      - '2284:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false

  immich-machine-learning:
    container_name: immich_machine_learning3
    # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
    environment:
      - HTTP_PROXY=http://192.168.9.222:1088
      - HTTPS_PROXY=http://192.168.9.222:1088
  redis:
    container_name: immich_redis3
    image: docker.io/valkey/valkey:8-bookworm@sha256:fec42f399876eb6faf9e008570597741c87ff7662a54185593e74b09ce83d177
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always
  database:
    container_name: immich_postgres3
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library

# The location where your database files are stored. Network shares are not supported for the database
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
TZ=Etc/GMT-8

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=immich
DB_DATABASE_NAME=pppppppp

Reproduction steps

1.Take motion photos with your vivo phone, then open the Immich mobile app to back them up
2.
3.
...

Relevant log output

Additional information

[bo0tzz]

Do the files have any metadata (like ContentIdentifier or MediaGroupUUID) that links them?

[qingxianaaa]

"vivo's motion photos do not primarily rely on internal metadata like ContentIdentifier or MediaGroupUUID for linking. They are primarily associated through a paired JPEG image file and an MP4 video file sharing the same filename prefix and stored in the same directory.

[bo0tzz]

Then we can't reasonably support that, filename based matching is too brittle.

[lutao043]

已经打算换手机了，vivo的方案太草率

[xqboyyy]

Features that Google Photos cannot achieve:)

[huijian222]

Vivo wants to follow Apple‘s path, although it uses an Android system. LOL

[peterk89]

Hey, just to let you know that Vivo X300 and X300 Pro no longer have this issue. Live Photos are saved as they should be in Immich and displayed correctly. The problem was never Immich, but Vivo.

[lingkai5wu]

实际上，会造成这种情况的 vivo 动态照片的组成是：一张普通 JPEG 静态图 + 一段独立 MP4 视频，二者通过 vivo 私有元数据中的 com.android.camera.livephoto 字符串配对，这个字段是强ID，是可以建立一一对应的关联的，具体可以看看 #26840 (comment)

[duruonanni]

For what it's worth, I hit this on an X100 Ultra and ended up writing a small tool for it.

The two files are IMG_x.jpg and IMG_x.mp4 in the same folder. Nothing standard links them. The only shared value is a private JSON blob at the tail of each file (com.android.camera.livephoto). Immich reads Apple's ContentIdentifier and Google's Camera:MotionPhoto, so there is nothing for it to match on.

The tool does two things. It pairs and merges a folder of files into a standard single-file Motion Photo, which any reader following the Google spec can play. It also runs against an existing Immich library: pair by the private ID, set livePhotoVideoId, hide the clip, then merge the files in place. Mine has around a thousand photos from the last couple of years, all merged, and the phone stopped re-uploading the separate clips afterwards.

X300 and later do not need this. Those already write standard single-file motion photos, so this is for X100 and older bodies.

Repo: https://github.com/duruonanni/motion-photo-bridge
pip install motion-photo-bridge

One caveat from testing: the merged file plays fine in Immich and in the phone gallery, but uploading it to a platform like Xiaohongshu still posts a still frame. That looks like a capture-provenance check on the platform side rather than a format problem, so I left it alone.