You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google does not make it particularly easy for third-party apps to recognise a stack of images. My Google Pixel 6 stores JPEG and RAW in this unorthodox naming convention:
A general solution might be to allow a user to formulate a regular expression or string pattern to identify the stack of images. The list of patterns could grow over time, so all users would benefit. To make it user-friendly, you could specify the part that is not common (if you remove it, you would get duplicated names). In my example, that would be:
["-01.COVER.jpg","-02.ORIGINAL.dng"]
You could have more than two strings specifying a collection or stack of images.
The OS that Immich Server is running on
Docker
Version of Immich Server
v1.99.0
Version of Immich Mobile App
1.101.0 build.131
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
version: "3.8"## WARNING: 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: immichservices:
immich-server:
container_name: immich_serverimage: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}command: [ "start.sh", "immich" ]volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:roenv_file:
- .envports:
- 2283:3001depends_on:
- redis
- databaserestart: alwaysimmich-microservices:
container_name: immich_microservicesimage: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}# extends:# file: hwaccel.yml# service: hwaccelcommand: [ "start.sh", "microservices" ]volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:roenv_file:
- .envdepends_on:
- redis
- databaserestart: alwaysimmich-machine-learning:
container_name: immich_machine_learningimage: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}volumes:
- model-cache:/cacheenv_file:
- .envrestart: alwaysredis:
container_name: immich_redisimage: redis:6.2-alpine@sha256:b6124ab2e45cc332e16398022a411d7e37181f21ff7874835e0180f56a09e82arestart: alwaysdatabase:
container_name: immich_postgresimage: tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0#env_file:#- .envenvironment:
POSTGRES_PASSWORD: ${DB_PASSWORD}POSTGRES_USER: ${DB_USERNAME}POSTGRES_DB: ${DB_DATABASE_NAME}volumes:
- pgdata:/var/lib/postgresql/datarestart: alwaysvolumes:
pgdata:
model-cache:
Your .env content
nothing special here
Reproduction steps
- get your Hand on a Google Pixel Phone
- set it to shoot raw and jpeg
- shot a picture
- install immicht android app
-> see that the image appears twice in the timeline
I have uploaded a stack of images here so it is easier to reproduce:
https://www.swisstransfer.com/d/17567b00-561c-42c2-9a54-400fe0bd9f1d
Additional information
No response
The text was updated successfully, but these errors were encountered:
The bug
Google does not make it particularly easy for third-party apps to recognise a stack of images. My Google Pixel 6 stores JPEG and RAW in this unorthodox naming convention:
PXL_20240407_152207242.RAW-01.COVER.jpg
PXL_20240407_152207242.RAW-02.ORIGINAL.dng
A general solution might be to allow a user to formulate a regular expression or string pattern to identify the stack of images. The list of patterns could grow over time, so all users would benefit. To make it user-friendly, you could specify the part that is not common (if you remove it, you would get duplicated names). In my example, that would be:
["-01.COVER.jpg","-02.ORIGINAL.dng"]
You could have more than two strings specifying a collection or stack of images.
The OS that Immich Server is running on
Docker
Version of Immich Server
v1.99.0
Version of Immich Mobile App
1.101.0 build.131
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
No response
The text was updated successfully, but these errors were encountered: