'Anime Episode Format' still not parsing correctly

1: Can someone please have a look at the parsing code for ‘Anime Episode Format’ input. It is still broken. Here is also an earlier problem with that section.

2: Would you consider changing the name of this section from ‘Anime’ to ‘Absolute Episode Format’ seeing that is what it is following, and it is actually more clear about the purpose of the section.

  1. Sonarr won’t parse a single digit absolute episode number, use {absolute:00} instead.

  2. No, Anime matches the series type, you can also not even include the absolute episode number in the format, relying on Season + Episode numbering instead.

  1. Well, what I’m suggesting is changing the Series type from ‘Anime’ to ‘Absolute numbering’ because saying it’s just for anime is wrong.

Its most commonly associated with Anime.

Daily is also associated with weekly episodes that use a date instead of a season and episode identifier, but its not really worth changing it.

Do you have examples where its wrong? I’d say 99%+ is anime, but I’m curious why you think its wrong.

Ex. every show that has it’s aired order screwed by the network and then it’s release gets corrected in a DVD/Blu release ie. Firefly, Futurama etc for two big examples

I’ve seen DVD ordering used in those cases, but never absolute numbering.

well how do I get Sonnar to order my files on disk by DVD Ordering if not by using ‘Anime Format’ ?

At the moment you can’t.

How about self-created naming profiles in a similar way to quality profiles. That way you can name them what you want and have as many as you want.

and, Absolute numbering basically achieves dvd ordering in most cases because that’s what people use it for in the dbs

That seems like an unnecessary complication.

Sonarr would need to support DVD ordering to handle grabbing episodes for those series though, sure you could set it the type to Absolute, but Sonarr would never find anything because they’re released with season numbers.

That seems like an unnecessary complication.

you’re wrong in my opinion, more flexible doesn’t have to mean more complicated. Have the current naming conventions there as defaults then you have an input field underneath for spawning more. Having different naming sets linked to tags could allow for diverse ordering for things like dvd-ordering etc when needed.

More flexibility is inherently more complicated it adds another layer of possible problems and another thing to troubleshoot when things aren’t working right.

Even if we add support for DVD ordering there doesn’t need to be another naming format, it would happen automatically.

so what you’re saying is “Nothing is wrong, you, the user, are wrong”?

In that case please add more documentation as to what strings are valid and not valid in the naming conventions, and why.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.