Another oddball naming issue- with Star Trek Enterprise and TNG, but not with Voyager

Chunking along here.

Got the BluRays out and chomping through it.
Making good progress.

I’ll have it all fresh in a couple hours.

THEN, I’ll see WTH is happening :roll_eyes:

1 Like

Quick update. I’ve changed “Ordering” for the entire TNG series to “TVDB Aired”,
now the episode this play seems to be correct. Let me also try this for Enterprise.

Would someone explain why I have to do this, but others do not?

If DVD ordering and Aired ordering are different

Then you’ll need undo their confusion.

1 Like

I think I figured out your problem. It does come down to the ordering, BUT in your case your library is set to TMDB instead of TVDB. And TMDB has for both TNG and Enterprise listed the first episodes as a single one. Not for Voyager, that’s why you didn’t have any issues there.

1 Like

Is this a setting, or are you referring to the naming of the files?

I think the easiest way around this is to split S1E1 and S1 E2 into separate files and name them appropriately, and do this for all 3 of the problem series. However, the split will need to manually be done, as I doubt there are any tools which know were E1 ends and E2 begins.

I’ve checked the ordering.
When I posted the messages, they were all set to library default (I didn’t even know about these settings). I’m now using TVDB Aired, which is a small improvement in the display of each episode.

It really comes down which database ordering you generally want to follow with your naming scheme. I switched my library default over to TVDB Aired right away, because I knew from the get-go that all my files had been named to comply with that.

1 Like

It’s a setting. While PMS goes by the SxxExx number, the metadata you get displayed, is either As-Aired or DVD when such a divergence exists.

FireFly was probably the worst offender

1 Like

Miami Vice comes to mind as well. For the last season in particular, ordering between aired and DVD was totally off.

1 Like

Wow, what a blast from the past. I would love to see Miami Vice again.
Thanks for the memories.

I’ve only been using Plex and Synology for about a year, but there is so much I don’t know about it.

Do you mean the path to the TV Show directory on my Synology?
Would you post a screenshot of the setting that you’re referring to so that I don’t get it wrong?
Thanks

Are you re-ripping from image files or the BR discs themselves?
I’ve kept copies of all of my DVDs & BR discs (as ISOs) on the NAS, in case I ever need to rip them again. I gave the physical media to the library because I had no more space. Most of my NAS capacity is dedicated to those ISO files.

Reripping from the discs.

I don’t have enough storage to keep ISO and full rips of everything.

1 Like

Synology hides a great deal of the underpinnings in their GUI.
They show you only what they want you to have access to.

As of DSM 7, they created an environment where we only run our apps the way they want us to ( in a tiny constrained sandbox )

As an engineer, I like the GUI because it’s very user-friendly.
Also as a developer, it’s difficult to do a lot of things.

It may be based on Linux but that’s where it ends.

1 Like

@cappy2112

I’ve got all but one season ripped. I was too tired and botched it up.
It’s ripping again now.

1 Like

No problem.

From here:

image

Then from the Add Folders tab:

For TV libraries Plex tends to have issues if the root of the TV series folder doesn’t contain the series. i.e., if the root is TV_Shows/ and then under that you do something like organizing by letter so within the root before the series folders you have TV_Shows/S/ as you directory structure. That would then mean something like Star Trek would have the path TV_Shows/S/Star Trek as the directory path.

After the responses from when I posted that, however, it might not be relevant. Only reason I asked is because the post I replied to for that (the one right above it), the paths of the files just made me curious for some reason. Looking back at it, I’m not 100% sure why anymore :D.

-Shark2k

1 Like

Which SW do you use for ripping, and which OS is your ripping platform?
I"m looking for something new (and reliable), but I’m on MacOS. The two programs I’ve been using to go from disc to IDO file are not as reliable as I’d like.

I’m now having an unfixable issue with Handbrake (on Mac), it crashes whenever I open any file.
I’ve got a thread going in the Handbrake forum, but we haven’t found a solution yet. This happened suddenly after several days of compressing the Star Trek series mentioned earlier

This is always problematic. PMS will, by nature of the grouping, look for a series named S.

While it might seem a pain, since you like your media structured more granular,
give PMS that detail too. (There’s no limit to the number of folders you can add)

e.g. Add the following folders to ‘Television’ library section:

/nas/TV_Shows/A
/nas/TV_Shows/B
/nas/TV_Shows/C
.
.
.

Trick: You can COPY/PASTE the directory names in that top bar. Browsing down to the directory is not needed.

2 Likes

I user MakeMKV and MKVToolNix.

Handbrake is not a “ripping” tool. HandBrake can read a disc but everything coming out of it is re-encoded so you lose right there.

Here you can see where I’m at in the ripping process. Everything here is done.
Part of S02 and all of S03 needs to come over.

[chuck@lizum Star Trek The Next Generation.2008]$ ll
total 28
drwxrwxr-x  8 chuck chuck  136 Sep  7 10:40 ./
drwxr-xr-x 58 chuck chuck 4096 Sep  7 11:38 ../
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:39 Season 01/
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:40 Season 02/
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:40 Season 04/
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:40 Season 05/
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:40 Season 06/
drwxrwxr-x  2 chuck chuck 4096 Sep  7 10:40 Season 07/
[chuck@lizum Star Trek The Next Generation.2009]$ du -h .
197G	./Season 01
150G	./Season 02
191G	./Season 04
184G	./Season 05
190G	./Season 06
189G	./Season 07
1.1T	.
[chuck@lizum Star Trek The Next Generation.2010]$

I expect about 1.3 → 1.4 TB when done