starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

Manually created studios error when trying to view their videos #6326

New Issue
Closed
opened 2026-02-07 03:28:32 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-07 03:28:32 +03:00
Owner
Copy Link

Originally created by @ricketyboo on GitHub (Oct 5, 2024).

This issue respects the following points:

  • This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow Jellyfin's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

When adding a studio via the metadata editor or via nfo metadata it seems to be skipping some step that makes the Studio link actually work to show the full list of studio works. It seems to use this to show "more like this" but does not seem to correctly whatever is needed to display the aggregated studio view.

Reproduction steps

  1. Disable all metadata scraping (no tmdb, omdb, etc)
  2. Add a video to a library
  3. edit the metadata for the video via the editor, or edit it's nfo file; and save a new studio
  4. click on the link to the new studio in the video's "Studio" section
  5. See a spinning circle that never ends

What is the current bug behavior?

Spinning blue circle and nothing loads.

What is the expected correct behavior?

Should see a list of videos related to the studio same as when a studio has been created via metadata integrations

Jellyfin Server version

10.9.11+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.9.11

Environment

- OS: Ubuntu 22.04.5 LTS
- Linux Kernel: 6.8.8-2-pve
- Virtualization: Proxmox 8.2.4
- Clients: Web
- Browser: Firefox
- FFmpeg Version: 6.0.1
- Playback Method: n/a
- Hardware Acceleration: VAAPI
- GPU Model: Intel GPU (iHD)
- Plugins: none
- Reverse Proxy: none
- Base URL: IP
- Networking: LXC DHCP
- Storage: local

Jellyfin logs

[2024-10-05 18:17:56.254 +10:00] [INF] WS "10.11.0.2" request
[2024-10-05 18:18:19.160 +10:00] [INF] WS "10.11.0.2" closed
[2024-10-05 18:18:20.431 +10:00] [INF] WS "10.11.0.2" request

FFmpeg logs

N/A

Client / Browser logs

404 when trying to load the studio item which then goes into an uncaught error.

image

Relevant screenshots or videos

No response

Additional information

I suspect it's similar to https://github.com/jellyfin/jellyfin/issues/12500 with Genres.

There is no studio folder created in /var/lib/jellyfin/metadata/Studio/

One of my attempts to create a manual studio did result in an entry appearing in the library.db TypedBaseItems table; but I'm not sure why that one was created; but none of the others were. Regardless of it's existence in the DB, it still results in the broken page load.

Update:
When the Admin > Dashboard > scheduled tasks > scan media library runs(manual or automatic), it creates the missing studio entries, and links them to their relevant content as expected. The studio link then works.

Originally created by @ricketyboo on GitHub (Oct 5, 2024). ### This issue respects the following points: - [X] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [X] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [X] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [X] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug When adding a studio via the metadata editor or via nfo metadata it seems to be skipping some step that makes the Studio link actually work to show the full list of studio works. It seems to use this to show "more like this" but does not seem to correctly whatever is needed to display the aggregated studio view. ### Reproduction steps 1. Disable all metadata scraping (no tmdb, omdb, etc) 2. Add a video to a library 3. edit the metadata for the video via the editor, or edit it's nfo file; and save a new studio 4. click on the link to the new studio in the video's "Studio" section 5. See a spinning circle that never ends ### What is the current _bug_ behavior? Spinning blue circle and nothing loads. ### What is the expected _correct_ behavior? Should see a list of videos related to the studio same as when a studio has been created via metadata integrations ### Jellyfin Server version 10.9.11+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.9.11 ### Environment ```markdown - OS: Ubuntu 22.04.5 LTS - Linux Kernel: 6.8.8-2-pve - Virtualization: Proxmox 8.2.4 - Clients: Web - Browser: Firefox - FFmpeg Version: 6.0.1 - Playback Method: n/a - Hardware Acceleration: VAAPI - GPU Model: Intel GPU (iHD) - Plugins: none - Reverse Proxy: none - Base URL: IP - Networking: LXC DHCP - Storage: local ``` ### Jellyfin logs ```shell [2024-10-05 18:17:56.254 +10:00] [INF] WS "10.11.0.2" request [2024-10-05 18:18:19.160 +10:00] [INF] WS "10.11.0.2" closed [2024-10-05 18:18:20.431 +10:00] [INF] WS "10.11.0.2" request ``` ### FFmpeg logs ```shell N/A ``` ### Client / Browser logs 404 when trying to load the studio item which then goes into an uncaught error. ![image](https://github.com/user-attachments/assets/2ac5056a-2466-4f71-b605-5807ad6bb311) ### Relevant screenshots or videos _No response_ ### Additional information I suspect it's similar to https://github.com/jellyfin/jellyfin/issues/12500 with Genres. There is no studio folder created in `/var/lib/jellyfin/metadata/Studio/` One of my attempts to create a manual studio did result in an entry appearing in the library.db TypedBaseItems table; but I'm not sure why that one was created; but none of the others were. Regardless of it's existence in the DB, it still results in the broken page load. **Update:** When the Admin > Dashboard > scheduled tasks > scan media library runs(manual or automatic), it creates the missing studio entries, and links them to their relevant content as expected. The studio link then works.
OVERLORD added the bugstale labels 2026-02-07 03:28:32 +03:00
OVERLORD commented 2026-02-07 03:28:38 +03:00
Author
Owner
Copy Link

@ricketyboo commented on GitHub (Oct 5, 2024):

Spent some time stepping through the metadata save logic and the API response from the User Items endpoint. Had to step away abruptly and now I'm trying to update from memory, so this may be slightly vague, but:

The studio does get saved to the database in the ItemValues table, with a guid reference to the video, a magic number "type" of 3, and the string value and a sanitised string value. The studio does not have its own guid anywhere.

The Id that is used to studioId on the controller when loading video metadata that result in a 404 is being generated by a method that uses the filepath of the metadata/Studio/{studio name} to create an id. Presumably the expectation is that something should exist in that folder, which is not created during manual adds, but is created during fetcher provider saving.

The next thing I'll look at when I get some time is what the format of the working studios is, and see if there's a clean place to create the same structures via manual creation/NFO import

@ricketyboo commented on GitHub (Oct 5, 2024): Spent some time stepping through the metadata save logic and the API response from the User Items endpoint. Had to step away abruptly and now I'm trying to update from memory, so this may be slightly vague, but: The studio does get saved to the database in the ItemValues table, with a guid reference to the video, a magic number "type" of 3, and the string value and a sanitised string value. The studio does not have its own guid anywhere. The Id that is used to studioId on the controller when loading video metadata that result in a 404 is being generated by a method that uses the filepath of the metadata/Studio/{studio name} to create an id. Presumably the expectation is that something should exist in that folder, which is not created during manual adds, but is created during fetcher provider saving. The next thing I'll look at when I get some time is what the format of the working studios is, and see if there's a clean place to create the same structures via manual creation/NFO import
OVERLORD commented 2026-02-07 03:28:39 +03:00
Author
Owner
Copy Link

@ricketyboo commented on GitHub (Oct 7, 2024):

I found a workaround; When the Admin > Dashboard > scheduled tasks > scan media library runs(manual or automatic), it creates the missing studio entries, and links them to their relevant content as expected. The studio link then works without a 404.

@ricketyboo commented on GitHub (Oct 7, 2024): I found a workaround; When the Admin > Dashboard > scheduled tasks > scan media library runs(manual or automatic), it creates the missing studio entries, and links them to their relevant content as expected. The studio link then works without a 404.
OVERLORD commented 2026-02-07 03:28:40 +03:00
Author
Owner
Copy Link

@jellyfin-bot commented on GitHub (Feb 5, 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 5, 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).
OVERLORD commented 2026-02-07 03:28:42 +03:00
Author
Owner
Copy Link

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

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Feb 26, 2025): This issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
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
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#6326
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?