Aperture - AI-Powered Recommendations for Emby

[drakke 0]

hello !!
Bug with Emby: toggling a source library in Admin → Settings → Configuration fails with HTTP 400 params/id must match format "uuid". The UI sends PATCH /api/settings/libraries/15528, i.e. the Emby library ID (provider_library_id), instead of the row UUID (library_config.id). Emby library IDs are numeric, so no Emby library can be enabled or disabled from the UI. Workaround: update library_config.is_enabled directly in the database.

[drakke 0]

hello !!
Feature request: allow generating separate recommendation libraries per source library (or per group of source libraries), e.g. “AI Picks – Series”, “AI Picks – Anime” and “AI Picks – Adult”, instead of one combined TV library per user. This would mirror how libraries are organized in Emby. Ideally each generated library would only draw from sources the user can access in Emby, since STRM files bypass Emby’s library permissions.

Edited Monday at 10:29 PM by drakke

[TheGru 165]

Aperture 0.7.11 dev build is available

A new development build is up on GHCR. Use the :dev tag to try it. If your Docker setup uses :latest, change the image to:

ghcr.io/dgruhin-hrizn/aperture:dev

Pull the image and recreate the Aperture app container with your existing database and mounts. Back up your database first. If you want to pin this exact build, use ghcr.io/dgruhin-hrizn/aperture:0.7.11-dev.2.

What’s new

• Fewer repeat picks. Aperture now remembers what it suggested to each user. Movies and shows wait 180 days by default before they can come back, and returning titles can only fill a small share of the list. Admins can tune the movie and TV cooldowns separately.

• Separate TV picks for different Emby libraries. You can map sources to named outputs such as Series and Anime. Each group ranks picks from enabled sources the user can access in Emby. I also fixed the source-library toggle for numeric Emby IDs.

• Private Emby playlists are available as a preview. If you’ve run into duplicate Continue Watching entries with generated libraries, this is the mode I’d like feedback on. It references the original Emby items. I verified that playback reporting updated the original movie’s play count on Emby 4.10.2. I’d be interested to hear how it behaves on your client or with your Wrapped exporter.

• Clearer output and sync controls. You can turn media-server publishing off separately for movies and TV to remove the corresponding managed output. There’s also a new Import Media Server job that syncs users, the catalog, and watch history without spending AI tokens.

• More variety in movie picks. Ratings and recurring themes help shape the rankings, and the list can reserve a few spots for well-rated films outside your usual genres.

I upgraded my own Unraid instance from 0.7.10 and verified that admin settings, user settings, job schedules, and uploaded artwork carried over.

Thanks to everyone who reported the Emby issues. If you try this build, please include your Emby server version, client, and output mode when reporting what you see.

[TheGru 165]

Aperture 0.7.11-dev.3 is available

If you’re already on 0.7.11-dev.2, this is a small follow-up with two changes:

• A short guide on your next sign-in. Admins see where to configure TV groups, publishing modes, recommendation cooldowns, and no-token imports. Regular users get a separate overview of fresher picks, more variety, and the Emby playlist preview. Each person can dismiss their own dialog, and Aperture remembers that choice.

• Updated documentation. The release notes and guides now explain how to configure the new features, what to expect from each Emby output mode, and how to upgrade. Read the updated release notes

Use the :dev tag to get this build. If you’re already on that tag, pull it again and recreate the Aperture app container. I tested the upgrade from dev.2 on my Unraid instance and verified that settings and uploaded artwork carried over.

ghcr.io/dgruhin-hrizn/aperture:dev