Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

servers: map composer from Jellyfin and Emby, and resync

Open
  • Is something wrong?
#1,074 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kotlin
Domain
backend, data

Research direction

Start by reading android/mediaprovider/server/.../MediaBrowserServer.kt and inspect a track response from a real Emby server to confirm which composer and conductor fields it sends. Map Jellyfin and Emby composer data to Song.composer, and check the sync-version logic; measure the Jellyfin payload increase on a large library. Done when both providers resync existing libraries and composer data is available for their tracks.

Written by the indexing model from the issue text.

Description

later next-release

Part of #1065.

Jellyfin and Emby already send the composer, but we don't read it. Without a composer, a Jellyfin or Emby track gets title-based work blocks but no composer page, no "Composer: Work" line, and no untagged-credits fallback (untaggedCredits() returns empty).

  • Jellyfin: add People to songFields (android/mediaprovider/server/.../MediaBrowserServer.kt) and map entries of Type Composer to Song.composer. Measure how much bigger the sync payload gets on a large library.
  • Emby: map BaseItemDto.Composers (NameIdPair[], filled from tags since Emby 4.6). Also map People of type Conductor if the scanner fills them. First check one track's response on a real server to see what it sends and which Fields it needs.
  • Resync: bump the Jellyfin and Emby sync version so existing libraries pick up the composer. Commit 2e1bb6027 kept the classical tag versions from resyncing these providers.

Plex has no composer field on tracks; it keeps title detection only.

Dominant language
Kotlin
Stars
232
Forks
28
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from timusus/Shuttle2

All issues in timusus/Shuttle2

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.