Can I manage to make PLEX recognize properly my season folder?

I guess nobody’s saying you couldn’t do something this way.
You should just consider that it’ll collide with other naming schemas used by others – there’s the users who will place all kind of information in square brackets, there’s the users who run their season/episode complex as a single 3+ digit number (last 2 digits representing the episode, preceding digits representing the season).

I’m sure there’s the 0.01% of users who might be interested in digging up their own regular expressions. I’m just not sure why to break / complicate things for the rest. At some point you need to establish a schema that works for the majority of users, not just 1-2 users who happen to like their names differently (no offense… I like tinkering around too, occasionally).

As Volts summarized it… it’s file names; I don’t need them to be esthetic/beautiful… and to be fair… Vikings [S06] 01 isn’t necessarily a beauty too, is it? :wink:

There’s already a whole bunch of feature suggestions addressing this in their own way (see below) – down to other users asking to include more stuff in file names (ranging from sort titles to chapter/collection references…


same goes for movie naming schema

1 Like

I’m sorry to say this but what you said has no sense. The usage of RegEx to match part of a string / file name is precisely what can and will fit / match any custom naming schema that the end-user will use.

I just gave a example of file names with brackets and matching what is inside the brackets. But it could be any other naming schema example of course.

It would be a solution for almost every user.

That is a very unrealistic percentage in order to try to justify a comment with which more than argue is a try to ridicule and / or minify the importance and the potential and the versatility of allowing the usage of regex.

I’m just not sure why do you think that adding a new feature that the end-user can choose to use or to ignore, it can complicate or affect in any way the user experience of that user.

There are many options that the end-user can choose to enable or disable by demand. Those options complicate things to the user?. No, the user can keep settings in their default state. Same for a RegEx feature, which it could be activated and used if the end-user wants to, or can keep it disabled to let PLEX use its internal logic to parse file names as normally.

Honestly, I find it incredible how easily you call “complication” to an improvement.

Most people doesn’t care about enabling this or disabling this else when adding files into PLEX. A end-user only starts to care when he/she finds a problem, when PLEX doesn’t do the things in the way that the end-user expected. And there is exactly when and where the end-user could have the choice to activate and use RegEx to solve this kind of problems. Complication?. Come on…

Yes, at some point the devs need to establish a starting point, a point of reference. A default naming schema.

But at some point the devs can manage to improve it, by adding alternatives. Personalization, advanced features, etc.

I appreciate the links. But without the need to search, just looking at how strict and singular the naming scheme is, it is obvious that there must be tens if not hundreds or thousands of users demanding more versatility in the mechanics of name parsing. And that shows the importance that have to improve the current naming schema.

The question is why the developers do not satisfy the huge demand of this type of requests, and they prefer to keep with a single, strict naming schema that ‘no body’ likes.

I will approach it in another way:

1) Company X develops a program.

2) One of the most important behaviors of this program is to analyze movie file names to identify their titles via online services. For this, the program imposes its own implicit naming schema, the standard schema.

3) This implicit internal logic in its current state cannot meet the demand of the thousands of users who do not use the implicit naming schema imposed by the program.

What should the company do?

A) Continue to enforce its strict naming schema and ignore all user requests regarding this issue?. In other words, force the end-user to adapt to our way of thinking and doing things.

That would be the worst choice, and the most unfair for the end-user.

B) Try to listen to some suggestions from the hundreds of user complaints on this topic, and gradually try to add more versatility into the logic of our imposed naming schema to try to include a couple of more alternative naming schemas?.

This would be appreciated, of course, but it will be very slow and it will not be enough since the diversity of naming patterns is much bigger than the time that developers would need to add support and test all of them in their workspace by following this slow methodology.

C) Implement a new functionality with which to allow the end-user to specify, through Regex, his own pattern to capture the required “variables” used by our implicit naming schema (season number, chapter number, poster file, whatever else) from file names?.

Of course, this would be the best solution, since this would instantly support any type of naming schema.

For me it is very clear what choice would have the more sense.

I can have an opinion, and others can have their own and different opinions than mine, but I think such a clear obviousness like what the huge improvement impact and the final solution that RegEx would be in the end-user side it should not be debated, questioned or argued. Because opinions are opinions, but facts are always facts.

If anyone has the intention of debating these arguments, I first ask that he/she please try to admit to themselves that I am right in what I have said, and if he/she still think that I am not right and Regex will not be a solution, then you are free to publish your refutation, we live in a democracy with freedom of expression, but my way of thinking is not going to change because I consider these what I’ve exposed to be the facts.

Thanks for read.

I’d like to see something like an additional field you can edit and lock on the season folder so you can at least add a custom name.

AHS comes to mind for a show I wouldn’t mind this applied to.

Apologies… I can see how you could perceive my post in this way while it was certainly not intended to diminish your point. I was not trying to “win” an argument – just making the case for the other perspective.
As I stated above… it’s perfectly ok to ask for it – I just don’t think that Plex will open this up (given the bandwidth of related requests and yes… also that only a small handful of users will actually use such an option – I stand by that).

You can.
The Plex TV Series agent can be configured to lookup season names ( > Manage Library > Edit...Advanced > Use season titles). After enabling this option you might need to refresh the show’s metadata for Plex to add the information.
If you’re still using another agent (or don’t want Plex to download the information) you can manually set the Title for those seasons.

2 Likes

glad i finally signed up to the forum, i’m learning stuff all the time.

Also I feel a bit dumb because the option is right there not sure how I missed it before.

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