Usually, downloading stuff based off of TVDB/Trakt info works fine. There are however notoriously horrible shows where TVDB does not seem to want to agree with scene releases. There is a thexem.de entry for it but it doesn’t seem like anyone is maintaining it, and my user level is too low to fix it. Basically the problem is that TVDB gave the new season number 14, yet the scene calls it season 15.
Now I was thinking: it’d be great if I could handle this mess directly from Drone. The way things are now, I need to unmonitor the series, then manually download new episodes and rename them to something the Drone factory can understand. I think a bunch of the steps needed to do that could be taken out if I could override what the manual search looks for in Drone. Ideally, if I click “manual search”, Drone would do what it does now. However, it could also provide an input on that screen that is filled by default with what it normally looks for and the user could override that by typing in that box. The tricky part for you would probably be recognizing this download after it finishes, but that should be solvable by linking the episode Drone is looking for with whatever it downloads.
I tried looking if there is a card like this on Trello but I couldn’t find anything, though that could be because I wouldn’t know what to call this feature. I’m sorry if this is already on your agenda or if it has already been declined as a feature request.
The problem ‘we’ have with such approaches that it doesn’t benefit the community. The whole point of things like thexem and trakt is to have one (or a few) do the hard work and all reaping the benefits.
This is also the reason why you cannot add your own scene naming exceptions.
Personally I would love to see a option to number a specific show according to the scene/tvrage instead of tvdb, in order to be less susceptible to tvdb messups on a particular show. But that’s still just avoiding the real issue.
I have an idea about aggregating indexer feeds with trakt, thetvdb and tvrage to provide a more automated approach to thexem. (ie. automatically writing drafts based on empirical data, and have it approved by a human).
But that’s just in the ‘I have an idea’ stage and likely will remain there for a long while coz it’s gonna be a pain to create.
I agree that ideally it should not be needed to have a feature like this, but for now there are series like this one (and a few others I’ve seen so far) that keep getting messed up. It’s nothing you, TVDB or Trakt can really help but it is affecting the use of the software. I either have to wait until everything is fixed or download it manually, and most of the time I even have to manually clean up the mess it caused on my filesystem. With something as simple as that one input field you could move all that manual labor into Drone: I can already make it delete files that were labeled incorrectly, so all you’d need is for Drone to be able to find the differently labeled episode.
So in short: I really do agree that it’s a feature that should not ideally be needed but while there isn’t a better solution it would be a big time saver that can probably be made within a few hours and is equally easy to refactor/remove once you have something better in place. And if potentially confusing users is an issue, you could hide it unless the “advanced” option is turned on in your settings.
Its a lot more than an input field. The input field would just let you tell drone what to search for, you would still need to be able to take those results and map them to a series and one or more episode, as well as make sure they are able to be imported (otherwise you would have to manually import them link them to the series/episode(s).
I don’t have any plans to add such a feature when we can put the effort into improving things/adding new features that will hit a wider audience.
This show isn’t even that messed up, it just has an incomplete pending draft. The draft looks correct to me, but is missing the later seasons. I can either drop the draft and it can be redone or I can approve it and the rest can be added. Thoughts?
It’s not as messed up as it was two days ago, now there are just some extra episodes on the TVDB that they’ll no doubt remove…eventually. It’s not acutely relevant to MythBusters anymore.
I won’t say I’m not disappointed that you don’t want to add a search field as I’ve come across a few other situations where I’d have liked to map my own search result to an episode (mostly for new anime though, so the impact should be small), but I do agree with your reasoning. And either way, even the current situation is a lot better than what I’m used to from other software.
I did just remember a second use case that is a lot more widespread: specials. Currently, Drone can only look for specials if they have an absolute number, and even that is only the case for anime as far as I know. Mapping a search result to a special through by means of what I described above would allow you to get specials through Drone itself where it is simply not possible in any other way.
Drone can fallback to searching for specials by name as well, I don’t know how this is handled for anime (I suspect the lack of abs cases it to fail instead of going to the name), I’ll take a look though.
