v3.2.0 #31408
Replies: 8 comments 2 replies
|
Really happy about shared clustering! Though I'll wait until some non-destructive means of doing it will be possible. I've opted to very-small-clusters + lots of manual merging to get best possible clusters, loosing them and having to re-do everything is not viable for me. |
|
I love Immich 🥇 |
|
I'm very excited for the shared clustering as that has been a long time gripe of pretty much every Immich user, although I find the release notes on this feature far too vague since there are a lot of questions that are left unanswered. Here are some that have popped up while waiting for the new version to deploy:
I added other users to my group but for now I will hold off fully committing to this as the hard facial recognition data reset is a deal-breaker for me and probably a lot of other people. |
|
These are all great questions. Here is some information about the topic that I hope helps to clear up the current state of the feature. Worth noting too -- we do plan to add in "people clustering" in the future, making it possible to merge cross-user people together instead of requiring resetting everything. This might be something we can automatically kick off in the background so no resetting is ever required. We decided to release the feature as is and get some feedback, especially since some number of users will have no issue re-running facial recognition and can immediately start benefiting from it. Joining a group means clustering can happen on a shared pool of faces. All the benefits of the group come from the facial recognition algorithm running on the shared data to create new "people" records that will now contain faces from all/any of the users and their associated assets. You can join a group and not re-run clustering, but that means that you will only see your preexisting "people" records and they will continue to only contain faces for your own assets. Additional assets uploaded by anyone in the group might start to link to those "people". The problem is the group might have duplicate "people" records now. For example "Jason" might exist twice in the cluster group, once for my original person and once for another user. The machine learning algorithm needs to pick and choose which version to link new faces to. Re-running facial recognition resets everything and will create a single, unified version of "Jason" containing faces from both users.
|
|
Really great! Also the compose builder is a great great addition for beginners! Nice release devs! |
|
Love to see the new "searching within albums" feature. I was just wanting to do that a couple days ago! |
|
To clarify, the new API enables the feature. We haven't implemented the feature yet |
|
Pretty excited about people sharing. Wifey can now finally see all the photos of the kids via searching etc. I do however have 350 people current named, and similar number more unnamed (people in crowds etc). The rework is going to be - extensive. |
|
I like the new search UI. However, a common things I searched in the previous UI was "Untagged" and "Not in Album" within a date range. I don't see a way to indicate "Untagged" in the new UI. Am I missing something? |
|
How can I contribute to translations if there are no new strings available for the Weblate project (Russian)? |
Uh oh!
There was an error while loading. Please reload this page.
v3.2.0
Welcome to Immich
v3.2.0!This release includes many new features as well as the usual collection of bug fixes and cleanups. Keep reading below for a list of highlights.
Highlights
Docker compose builder
We recently released our new docker compose builder, which lets you put together a custom compose file for Immich more easily. Please try it out and give us your feedback!
Search API v2 (server)
We have built an entirely new search API that, amongst other things, will support searching within albums and combining multiple search filters with both AND and OR operations. Some of these features will be exposed to the search UI interfaces in the future, others will be used to power other fancy features as well as give 3rd party tools more functionality. If you are interested in the particular changes and examples for how to use the new API, feel free to check out the PR #30179 as well as our API documentation at https://api.immich.app/endpoints/search/searchAssets.
Revamped search UI (web)
We have a new designer who helped us remodel the search modal, which has been pretty complex before and looks a lot more visually appealing in our opinion now. It still supports the same functionality, but with some quality of life additions as well as a significantly simpler look. In the future, we will extend this to also include some of the new features enabled by the new search API. Stay tuned and give us your feedback on the new design!
New search modal filtering by images with Jason in it, taken in the last 30 days in BC, Canada, tagged "Long Beach" with the context search term "Swimming"
Advanced filters showing camera make, model, and lens model, as well as filers for favorite and archive status, and album membership
View own people in shared assets
We are very happy to ship the first step towards better sharing. You can now have people recognized across trusted users, which also allows you to view people you already have records of in any shared assets!
In the user sharing settings there is a new section; cluster group.
The user sharing settings showing a cluster group with Jane Doe and Mich in it
You can invite users on your instance that you trust to your own group, or join another group you have been invited to. These cluster groups make it possible to identify people in assets shared by users in the same group. They also likely improve accuracy, as the clustering will operate on a bigger pool of faces. People names and birth dates are still set on a per-user level and aren’t (yet) shared with users in the same group.
As of now, this requires resetting facial recognition for all users in the group, in order for the changes to apply retroactively for all assets. This means, names and birth dates will be lost, and the results can vary slightly compared to before. Only faces recognized by machine learning will be affected by this. We may be able to do some non-destructive merging in the future, but for now this is a necessary step in order to fully benefit from the feature. That is why we put a button in the sharing settings for every user in the group (specifically also non-admins) to reset the facial recognition for that group.
Workflow tags trigger and actions
Workflows have gotten a new trigger. You can now do automations when an asset has been tagged.
In order to use this new trigger, there is also a new filter that allows you to match specific tags. It supports matching for all, any, or none in the provided list.Lastly, a new workflow action to add tags to the current asset has also been added. It allows to add a list of tags at once.
Dedicated memories page
The new memories page allows you to view past memories. You can also favorite memories and they will show up here and never get deleted. The goal is for this to be a place you can come back to at any point and reminisce in old memories.
Tag renaming (web)
Finally, you can also rename existing tags. This is a small addition to the edit tag modal on web, but under the hood was more complicated than you might expect.
View assets in map viewport (web)
Similarly to showing a timeline all assets in a cluster on the map when clicking on it, you can now open a timeline for assets currently in the viewport. There is a new button among the map controls to show assets in the area. It will open a timeline that will update as you pan around the map.
The map page showing a timeline of assets currently in the viewport on the right
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
MemoryVideoViewerelement is not visible by @Zlendy in fix(web): do not play memory video if theMemoryVideoViewerelement is not visible #30947📚 Documentation
🌐 Translations
New Contributors
Full Changelog: v3.1.0...v3.2.0
This discussion was created from the release v3.2.0.
All reactions