Update ghcr.io/immich-app/immich-machine-learning Docker tag to v3.3.3 #26
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/ghcr.io-immich-app-immich-machine-learning-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v3.2.4→v3.3.3Release Notes
immich-app/immich (ghcr.io/immich-app/immich-machine-learning)
v3.3.3Compare Source
Well, you know how it goes... Misclick once and a release is sacrificed 😅 The second patch release
v3.3.3has some more bug fixes, notably a major performance improvement for the explore page.What's Changed
🐛 Bug fixes
Full Changelog: https://github.com/immich-app/immich/compare/v3.3.1...v3.3.3
v3.3.1Compare Source
This patch addresses various bugs around people sharing, as well as a scroll issue on mobile. Further, there is now an indicator showing which people are shared.
What's Changed
🌟 Enhancements
🐛 Bug fixes
📚 Documentation
🌐 Translations
New Contributors
Full Changelog: https://github.com/immich-app/immich/compare/v3.3.0...v3.3.1
v3.3.0Compare Source
v3.3.0
Welcome to Immich
v3.3.0!This release includes people sharing, birthday memories, auto-stacked mobile edits, and a variety of other enhancements and bug fixes. Keep reading below for the full list of highlights.
Highlights
Shared people management
We are very pleased to release the next big milestone towards better sharing: people can now be shared!
As a user you can share people with another user in your cluster group:
When sharing a person with another user, the shared person:
By default, changes to the name & date of birth are reflected for both users. On the web, the “Edit person” modal has an option to change the name/date of birth for “Only me” instead of the whole group.
Also, there is a preference for this behavior in the “Sharing settings”, which can be changed to make this the default behavior when editing a person. The setting can be changed here: https://my.immich.app/user-settings?isOpen=feature+people.
The setting has two options:
Lastly, by allowing cross-user merging, you can now merge a face from your own assets with people shared with you from other users. This is especially helpful if you didn't want to re-run facial recognition after joining a cluster group before. Now, after setting up bi-directional sharing, users can manually link people together.
Birthday memories
In an effort of making Immich more joyful to use, we are introducing memories for people's birthdays.
If it's the birthday of a person in your library, Immich will now celebrate that with a special memory featuring previous birthdays.
Auto-stacked mobile edits
When using something other than Immich for editing images on your phone, Immich will now stack those edits on top of the original. This allows for Immich to show all edits in one place, without cluttering the timeline.
This should provide a more organized timeline, especially when you heavily rely on editing assets on your phone.
Sync OAuth claims on every login
Immich supports OAuth claims for storage quota, the user role, and the preferred username. Up until now, those were only synced on registration.
Now, they can be synced on every login, allowing you to do active user management through your IDP, updating quotas and roles as you go and as necessary, and Immich will adopt those changes.
Higher quality thumbnails and previews
Immich now uses a more accurate image resampling method, improving detail preservation and brightness, especially for high contrast details. All image formats benefit from this change.
Before
After
Thumbnails already generated before this release won’t be affected by this change. To make it apply to existing thumbnails, you can run thumbnail generation on all assets in the job panel.
Machine learning performance and accuracy improvements (opt-in)
After a long list of optimizations, ML is both significantly faster and uses less memory. This affects every backend, including CPU inference. However, the level of improvement varies by model and backend. Cases where certain backends (such as OpenVINO) produced wrong outputs at times should be resolved.
RKNPU, used by Rockchip boards, now supports every model in the catalog including OCR for the first time, bringing it to parity with other backends. Additionally, TensorRT RTX is now used for Ampere (30xx) and newer NVIDIA GPUs, improving performance significantly.
To fully benefit, set
MACHINE_LEARNING_MODEL_REVISION=v2to allow more optimized models to be downloaded and used. Many of the improvements rely on these optimized models and will not take effect when using the old ones. The outputs of the new and old models are numerically equivalent, so switching doesn’t require re-running any tasks. This setting will be the default in a later release.As always, keep in mind that the very first time you load a model requires more preparation work, so don’t be surprised if it takes some time at first. This preparation is cached and reused, so loading the model will be much faster after the first time.
New OCR models
The PP-OCRv6 family is now supported. These models are significantly more accurate than the previous PP-OCRv5 generation while all being multilingual. PP-OCRv6_tiny is efficient and suitable for modest hardware, PP-OCRv6_small is a notable jump in accuracy compared to PP-OCRv5_mobile, and PP-OCRv6_medium improves on PP-OCRv5_server as the highest quality and most demanding option.
Notable fix: correct storage size on MacOS
The block size used to calculate the storage capacity and usage has some nuances to it. In some situations (*cough*** Docker on MacOS *cough*), we didn’t have enough information to correctly compute accurate values. With this release, the reported storage usage and capacity should now be correct.
Technical details
Recent NodeJS releases now expose the
frsizeproperty, which is sometimes different frombsize(“block size”). In those cases the calculate storage sizes could often be off by a factor of4096(or more). In fact, #4318 has been our fourth oldest open issue (including the renovate dashboard), opened just over three years ago. Now, with accurate block sizes our storage calculation should be correct, even in Docker on MacOS.We are very happy to finally see this issue resolved, even though it only meant a dependency bump and a tiny code change for us.
As always, please consider supporting the project.
🎉 Cheers! 🎉
Support Immich
If you find the project helpful, you can support Immich by purchasing a product key at https://buy.immich.app or our merchandise at https://immich.store
What's Changed
🚀 Features
🌟 Enhancements
🐛 Bug fixes
📚 Documentation
🌐 Translations
New Contributors
Full Changelog: https://github.com/immich-app/immich/compare/v3.2.4...v3.3.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
bd1b0712e4to6c9e20bad6Update ghcr.io/immich-app/immich-machine-learning Docker tag to v3.3.0to Update ghcr.io/immich-app/immich-machine-learning Docker tag to v3.3.16c9e20bad6tob8ff190532Update ghcr.io/immich-app/immich-machine-learning Docker tag to v3.3.1to Update ghcr.io/immich-app/immich-machine-learning Docker tag to v3.3.3View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.