mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
[bug] Incorrect metadata for TV Shows in specific format #1194
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#1194
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sorinyo2004 on GitHub (Jan 12, 2020).
I am using Jellyfin.Server 10.4.3.0 (Turnkey Linux container, Debian OS), I added new library of type "TV Shows" for video tutorials and pointed to the path where the media is located.
The media is in the below structure and format:
3D Buzz - MMO Development Class
- Part 01 - Part 01 - Chapter 1 the beginning
- P01E01 - Wecome to the class.mp4
- P01E02 - Story concept initial proposal.mp4
...
- Part 02 - Chapter 2 making some noise
- P02E01 - Random num gen rd session 4 pt 1.mp4
- P02E02 - Random num gen rd session 4 pt 2.mp4
...
In the web interface the "Seasons" are detected correctly but in each season the video files are in wrong order; for example in "Part 01 - Part 01 - Chapter 1 the beginning" (this folder contains 72 video files) the order of the files is
- P01E01 - Wecome to the class
- P01E02 - Story concept initial proposal
- P01E06 - Lees testing framework for rd
- P01E03 - Meeting 11 story concept 1
- P01E07 - Lees terrain rd pt 1
...
The odd thins is that in "Part 02 - Chapter 2 making some noise" (this folder contains 55 video files) the files are ordered like it should.
I found that in the "Metadata Manager", the files that have a number at the end are detected and put in wrong order
@stale[bot] commented on GitHub (May 15, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@sorinyo2004 commented on GitHub (May 18, 2020):
I have updated to latest stable version (10.5.5). The metadata that I corrected was altered (automatically) with the incorrect episode number.
The issue still persists.
@stale[bot] commented on GitHub (Sep 16, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.