* It's more work to do shell/script automation with `./*` commands instead of just `.` (e.g. I don't know the bash/zsh command to find empty folders and I would need to google it every time. * If/when folders are empty, it's a PITA to prune them. I don't like using season folders because. If we're talking about making text files to map to a database, maybe they could handle this too. Providing good support for multiple episodes in a single file is hard because you then need to know the timecode that each episode starts/ends.
But in Panty & Stocking with Garterbelt, TVDB lists each 10 minute episode seperately, even though they were broadcast in pairs.
This is based on the way the show was broadcast, and ignores the episode numbering system used within the show. For example, in Saiki K each episode is 24 minutes long (comprising 5 mini episodes, "compilation episode order"). TVDB doesn't really have a consistent way of handling these. One other thing which makes the situation tricky is split-episodes/multi-episodes. I think it would be better to have something that anyone can publish to, without having to spend time justifying their contribution to moderators. (Plex only supports TV vs DVD order, not custom orders.) Additionally, given the strict governance of TVDB, I'm not sure it's the best place for orders. Regarding #2, TVDB does already support alternative orders, but they aren't supported by Plex. So maybe it would be better if there's some kind of unique episode identifier, and TVDB / whatever database commits to maintaining this identifier even if they change the structure of a show. But as we've seen, TVDB can and will change these. Regarding #1, the obvious solution seems to be to just map file names to season+episode combinations. Mapping the episodes in the database to alternative watch orders. Mapping the files on disk to the episodes in a database like TVDB.Ģ. I've thought about this before, and I think there are two aspects to the problem.ġ.
0 kommentar(er)
