u/Friend_man2007

How to force Romanized/Romaji track names for Japanese music? (Jellyfin + Symfonium search issue)

Hi everyone,

I am having a lot of trouble searching for my Japanese music collection on my mobile client, and I am looking for the best way to handle foreign character metadata.

My Current Setup:

* Downloader: Lidarr integrated with slskd (Soulseek)

* Media Server: Jellyfin

* Mobile Client: Symfonium

The Goal:

I want to be able to search for my Japanese tracks using Romanized names (Romaji) inside Symfonium. Right now, searching is a nightmare because a huge portion of the tracks show up in Jellyfin with their original Kanji/Kana titles.

The Struggle:

Jellyfin reads the tags exactly as they are imported. I need a way to ensure my tracks use Romanized or English metadata so that Symfonium's search indexing actually picks them up when I type in English characters.

My Questions for the Jellyfin community:

  1. Is there a post-processing trick, MusicBrainz Picard plugin/script, or custom metadata provider for Jellyfin that automates Romaji transliteration before scanning?

  2. If you use Symfonium, does the app have any built-in features to handle phonetic searching for Japanese characters that I might have missed?

  3. Would it be better to look into external tagging scripts (like Mp3tag or custom python scripts) to fix the file tags before Jellyfin ever touches them?

Appreciate any advice or workflow setups you all use for foreign language libraries!

*(Note: Also posted to r/lidarr to figure out the automation and acquisition side of this).*

reddit.com
u/Friend_man2007 — 14 days ago
▲ 4 r/Lidarr

Best workflow for matching Japanese metadata using slskd/Soulseek? (Struggling with Kanji vs. Romaji releases)

Hi everyone,

I am trying to set up a seamless workflow for handling Japanese music, but I am running into massive struggles with track naming, automation, and metadata matching.

My Current Setup:

* Downloader: Lidarr integrated with slskd (Soulseek)

* Media Server: Jellyfin

* Mobile Client: Symfonium

The Goal:

I want to be able to search for my Japanese tracks using Romanized names (Romaji) inside my mobile app. Right now, searching is incredibly difficult because a huge portion of the tracks are imported with their original Kanji/Kana titles.

The Struggle:

Lidarr often struggles to automatically match Japanese releases via slskd, or it grabs releases that default strictly to Japanese characters. I need a reliable way to favor English/Romanized pseudo-releases from MusicBrainz during the automated process.

My Questions for the Lidarr community:

  1. How do you configure your profiles, metadata settings, or release preferences to heavily favor English/Romanized/Pseudo-releases for Japanese music?

  2. Is there a custom script or naming token setup in Lidarr you use to handle foreign character transliteration on import?

  3. Should I handle this entirely inside Lidarr, or do most of you use an external tagger as a manual bridge before the files hit your media folder?

Any advice or workflow adjustments would be greatly appreciated!

*(Note: Also posted to r/jellyfin to look at the media server side of the metadata puzzle).*

reddit.com
u/Friend_man2007 — 14 days ago