[PR #14100] [MERGED] Terminate at null char for audio tags #13838

New Issue

OVERLORD · 2026-02-07T07:19:59+03:00

OVERLORD commented

2026-02-07 07:19:59 +03:00

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/14100
Author: @gnattu
Created: 5/13/2025
Status: ✅ Merged
Merged: 5/19/2025
Merged by: @crobibero

Base: master ← Head: terminate-tag-at-null

📝 Commits (2)

6f0e331 Terminate at null char for audio tags
2541cf3 Use LeftPart extension

📊 Changes

2 files changed (+71 additions, -24 deletions)

View changed files

📝 MediaBrowser.Providers/MediaInfo/AudioFileProber.cs (+58 -24)
📝 src/Jellyfin.Extensions/StringExtensions.cs (+13 -0)

📄 Description

Some users may use a misbehaved tag editor that writes a null char to the tag when not allowed by the tagging system. Terminates all string value from the tag at null char and ignore everything after.

Having a null char in the metadata fields not only affects value display, it will actually crash some job like nfo saving where the writer cannot handle null char gracefully.

Changes

Issues

Fixes #13674

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/14100 **Author:** [@gnattu](https://github.com/gnattu) **Created:** 5/13/2025 **Status:** ✅ Merged **Merged:** 5/19/2025 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `terminate-tag-at-null` --- ### 📝 Commits (2) - [`6f0e331`](https://github.com/jellyfin/jellyfin/commit/6f0e3318e56a84f88f2e5a1250279017295cf43b) Terminate at null char for audio tags - [`2541cf3`](https://github.com/jellyfin/jellyfin/commit/2541cf30afd63ceed6a59682ca185e9dda19cf9d) Use LeftPart extension ### 📊 Changes **2 files changed** (+71 additions, -24 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Providers/MediaInfo/AudioFileProber.cs` (+58 -24) 📝 `src/Jellyfin.Extensions/StringExtensions.cs` (+13 -0) </details> ### 📄 Description Some users may use a misbehaved tag editor that writes a null char to the tag when not allowed by the tagging system. Terminates all string value from the tag at null char and ignore everything after. Having a null char in the metadata fields not only affects value display, it will actually crash some job like nfo saving where the writer cannot handle null char gracefully.  **Changes**  **Issues**  Fixes #13674 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

OVERLORD added the pull-request label 2026-02-07 07:19:59 +03:00

OVERLORD closed this issue

2026-02-07 07:20:01 +03:00

Sign in to join this conversation.

Branches Tags

master

release-10.11.z

renovate/skiasharp-monorepo

JPVenson-patch-1

renovate/morestachio-5.x

release-10.9.z

openapi-cache

release-10.10.z

explicit-load

explicit-load-v2

feature/entity-framework

only-count-folder-item

fix/ci-workflow-refactor

release-10.8.z

release-10.7.z

EraYaN-add-management-interface

release-10.6.z

release-10.5.z

release-10.4.z

release-10.3.z

release-10.2.z

release-10.1.0

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#13838