J
IImmich
•Created by J on 10/14/2023 in #help-desk-support
time zone issues with sidecar
Created another sidecar with completely different timestamp and time zone, Immich ignores the time from the sidecar. It only took the timezone from the sidecar and shifted the displayed time on the web.
2 replies
IImmich
•Created by TIEB62 on 9/9/2023 in #help-desk-support
Retrieve / Provide Device ID
I think there’s an option in the cli so you don’t need to edit it
4 replies
IImmich
•Created by TIEB62 on 9/9/2023 in #help-desk-support
Retrieve / Provide Device ID
For a one off operation, I believe you can get the device id from the assets table from the db
4 replies
IImmich
•Created by Jakob on 9/9/2023 in #help-desk-support
Change geolocation result
My workaround for now is to save the location names in the sidecar (at least for those that geonames was not correct/precise), so that when I rescan metadata, I can correct the db without hunting for the few wing ones.
11 replies
IImmich
•Created by Jakob on 9/9/2023 in #help-desk-support
Change geolocation result
I had the same problem of geonames giving me inaccurate names. I had to update the db manually and remove the tstada volume. But any rescanning will wipe the manual change.
11 replies
IImmich
•Created by gabemcg on 9/5/2023 in #help-desk-support
Exclude faces from detection
No problem. I think there’s an alternative to this disabling process. On the page where you manage face visibility, there’s an “eye” icon. It toggles hiding all faces. So you can let face recognition run, hide all faces, then click on the faces you want to keep. Should be better than clicking on all the ones you want to hide.
12 replies
IImmich
•Created by gabemcg on 9/5/2023 in #help-desk-support
Exclude faces from detection
Never tried it myself though. But I think it should work. Keep in mind tough that if you later need to run face recognition on missing assets, those photos will go through face recognition.
12 replies
IImmich
•Created by gabemcg on 9/5/2023 in #help-desk-support
Exclude faces from detection
Yep. I think if you’re sure you don’t want face recognition for a bunch of photos from CLI import, disable it and import. Then reenable it afterwards.
12 replies
IImmich
•Created by gabemcg on 9/5/2023 in #help-desk-support
Exclude faces from detection
There’s a toggle for disabling face recognition in the web interface.
12 replies
IImmich
•Created by CyberSocialist on 8/20/2023 in #help-desk-support
ERROR [TypeOrmModule] Unable to connect to the database
I think this is a docker compose default, not related to Immich. https://docs.docker.com/compose/environment-variables/set-environment-variables/#substitute-with-an-env-file
37 replies
IImmich
•Created by J on 8/15/2023 in #help-desk-support
Reverse geotagging and searching
Yeah, I don’t want to manually change the db either, would rather have all info in the XMP as the single source of truth.
Sometimes the GeoNames db is wrong. For now I can manage with running a SQL script and deleting the typesense volume once in a while.
I looked at the exiftool xmp tag list, there seems to be a tag for location called LocationCreated in the iptcExt namespace, which is a recommended namespace (by its author). I never used it and don’t know if it’s a common one.
10 replies
IImmich
•Created by J on 8/15/2023 in #help-desk-support
Reverse geotagging and searching
Thanks for bringing that up. I manage all my metadata using XMP sidecars. I read the thread here where @hackerman and you were working out how to implement this feature. I saw you were discussing whether to store a hash of the sidecar files in the db so a sync job can pick up changes in the sidecar. But I lost track of the long thread, and wasn’t able to get a sense of what the “discover” and “sync” jobs are exactly doing. It sounds like “discover” finds new sidecars that were not in the file system before, and “sync” will just extract everything from every sidecar from scratch.
If my understanding is correct, neither discover or sync sidecar jobs would pick up my metadata changes while not destroying my manual edits in the db. A solution might be to write my city/state values in the sidecar, and Immich will just ingest them. I think this works in general for other metadata as well. For any piece of information, if Immich finds it in the sidecar, just use that. In the other direction, any metadata worth persisting (face regions, comments) can be saved in the sidecar. Of course there’s the question of which XMP tag maps to which column in the db. And I understand the devs may not want to go this route, which boils down to defining yet another “standard” of how people should manage their metadata. I should stop here, this post is already too long. 😅
10 replies
IImmich
•Created by J on 8/15/2023 in #help-desk-support
Reverse geotagging and searching
Coming back to say deleting the typesense volume works. It was also pretty fast. And embarrassingly I also tried “extract all metadata” even though @jrasm91 clearly said that would overwrite my manual changes. But this leads me to think about how to manage metadata.
Consider this scenario: I want to make changes to the original metadata (eg to correct a wrong time stamp on picture X), I’ll have to run the extract all metadata job, but this will overwrite all my changes to the reverse geotagging in the db (for other unrelated photos). I don’t think the extract missing metadata job will work because none of the photos are missing metadata. So short of an update metadata job, I’ll have to delete photo X and reupload.
This can happen to many photos because apparently I can’t seem to remember to change my camera’s clock every time daylight saving time changes, at least for the first couple of days. Another issue with deleting and reuploading is the expensive ML tasks will have to run again. Of course I should clean up the metadata before uploading them to Immich. But I may also want to make changes to the metadata later on.
So in general, there seems to be some conflict between managing “primary” and “secondary” metadata: when changes are made to the “primary” metadata, in order for them to be picked up by Immich, all “secondary” metadata has to be recalculated as a side effect, potentially erasing manual fixes to the sometimes wrongly calculated “secondary” metadata.
I hope I’m making sense here, and would appreciate the dev’s perspectives.
10 replies
IImmich
•Created by J on 8/15/2023 in #help-desk-support
Reverse geotagging and searching
Thank you! By “extract all”, you mean the extract all metadata job, right? It sounds like this job also triggers “pushing” metadata to typesense, besides extracting and inserting metadata to the db. Is it going to be faster if I simply let typesense build a new index by deleting the old docker volume (assuming the metadata extraction job will send the metadata to typesense for every picture)? I’m curious because if I make small changes to the metadata on just a few pictures, running metadata extraction on all assets sounds a bit less efficient. Of course building a new typesense index every time there’s minor changes to metadata is also expensive (plus there may be other data that’s indexed by typesense). Maybe some sort of update mechanism can be considered? Anyways thanks for the quick reply.
10 replies