github imagegenius/docker-immich v1.129.0-ig376

ImageGenius Changes:

support GPU acceleration with CUDA for machine-learning

immich Changes:

v1.129.0

Welcome to release v1.129.0 of Immich. The road-to-stable is bumpy, but at least, we have made memories together with the recent changes and issues with the new memories implementation 😋. We owe you an explanation for the changes. Please find it, along with the highlights of this release below:

  • Videos in memories are now playable on the web.
  • Shortcuts (L and Shift+L) to add assets to an album or shared album on the web.
  • Fixed an issue where opening Immich pauses playing music on iOS
  • The shared link now has a generated QR code for easier sharing.

Memories

Obviously, there have been some bugs related to implementing the new memories. For that, we apologize. We can be better about testing these new features moving forward.

In this release, we’ve added a migration that:

  • deletes all previous memories
  • resets the memory generation status field
  • automatically runs the memory generation job

This should fix all of the memory issues that have happened since v1.127.0.

Future improvements

There are some specific things planned with regard to memories, which this (painful) transition has enabled us to do:

  • Adjust/edit memories: the new change makes it possible to add/remove other assets from the memory
  • Share memories: memories can hopefully soon have a shared-link implementation similar to albums
  • More types of memories: based on location, people, date ranges, events, etc.
  • View past memories: on-this-day memories are cool, and now we have the data saved to let you browse memories from yesterday, last week, or tomorrow.

More technical details

There has been a lot of confusion around memories over the last few days that we wanted to clear up. Here are some important details:

  • In v1.127.0, memories transitioned from a single on-the-fly database query to a background job
  • The new job runs nightly and generates memories for several days in the future
  • After updating, there were no memories because the job hadn’t run yet
  • The job can be manually run via Admin > Jobs > Create Job > Memory Generation
  • There is a metadata table that tracks what days memories have already been generated for and skips those days the next time it runs
  • Memories that aren’t marked as favorite will be deleted after 30 days
  • This delete process is also a job that can be run manually. It’s called Memory Cleanup

Unfortunately, there were two main bugs that wreaked havoc on memories:

  • An “off by one bug”, that resulted in the memories being generated twice for the same day
  • A bug with the “years ago” calculation. It turns out that the "single database query” was broken when used for anything other than “today”. E.g., generating a memory for tomorrow would result in “0 years”

Both bugs were fixed in v1.128.0, but because memories are pre-generated, the broken ones still existed and were being used. The “Cleanup” job doesn’t delete pre-existing memories until they’re 30 days old. Even if they were manually removed, the “memory status field” would prevent those days from being regenerated anyway. These issues should now be fixed in this release, which essentially resets everything memory-related back to 0.

Support Immich

If you find the project helpful, you can support Immich by purchasing a product key at https://buy.immich.app or purchase our merchandise at https://immich.store

What's Changed

🚀 Features

🌟 Enhancements

🐛 Bug fixes

📚 Documentation

🌐 Translations

New Contributors

Full Changelog: immich-app/immich@v1.128.0...v1.129.0

Don't miss a new docker-immich release

NewReleases is sending notifications on new releases.