Scan for updates does not recognize changed bitrate #6328

Closed
opened 2026-02-07 03:28:49 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @pixel24 on GitHub (Oct 7, 2024).

Describe The Bug
When I replace an album on the server after digitizing it with a higher bitrate, the media scan (after updates) does not recognize this. The media info in the web client still shows the "old" bitrate. The folder and file names have remained exactly the same. When I perform a full scan (replace metadata), the correct bitrate is shown. However, this full scan takes a very long time.

Steps To Reproduce

  1. Copy any album XY with 128 kBit to the server
  2. Scan the library (changes)
  3. Replace the album with a 256 kBit version (same folder and file names)
  4. Scan the library (changes)
  5. Search for the album in the web client
  6. Select a track -> Media Info
  7. It still shows 128 kBit.

System (please complete the following information):

  • Platform: Debian 12.5
  • Browser: Firefox
  • Jellyfin Version: 10.9.11
Originally created by @pixel24 on GitHub (Oct 7, 2024). **Describe The Bug** When I replace an album on the server after digitizing it with a higher bitrate, the media scan (after updates) does not recognize this. The media info in the web client still shows the "old" bitrate. The folder and file names have remained exactly the same. When I perform a full scan (replace metadata), the correct bitrate is shown. However, this full scan takes a very long time. **Steps To Reproduce** 1. Copy any album XY with 128 kBit to the server 2. Scan the library (changes) 3. Replace the album with a 256 kBit version (same folder and file names) 4. Scan the library (changes) 5. Search for the album in the web client 6. Select a track -> Media Info 7. It still shows 128 kBit. **System (please complete the following information):** - Platform: Debian 12.5 - Browser: Firefox - Jellyfin Version: 10.9.11
OVERLORD added the bugstale labels 2026-02-07 03:28:49 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Feb 7, 2025):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Feb 7, 2025): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@jellyfin-bot commented on GitHub (Feb 28, 2025):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Feb 28, 2025): This issue was closed due to inactivity.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#6328