You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was found in V1.29 Build 4811.491
I have some shows with double episodes, for example episode 1 and 2 of Stargate Universe
is a double episode. The avi file is named "1x01x02 - Air Part 1 & Air Part 2.avi".
When I do a search for missing episodes ("Media -> Missing episodes report...") MCM
understands that this file contains both episode 1 and episode 2 of the first season.
However I have "Keep show current with new episodes" enabled for this show and the
logic here is a bit different and does not seem to fully understand the concept of
double episodes. MCM keep insisting on continuously searching for "stargate universe
S01E02" and "stargate universe 1x02". I can get around this bu setting "Skip TV episodes
before" to a date after this episode was aired, but that doesn't really solve the main
problem.
Reported by christer.johansen on 2011-02-22 18:56:10
The text was updated successfully, but these errors were encountered:
Have you tested this with the following name convention?
S01E01-E02
I find this to be the least problematic between all of the media organization tools
I use - and I have not experienced your stated issue when using this format.
Reported by micheal%espinola.net@gtempaccount.com on 2011-02-22 19:29:56
No, I have not tested the SxxExx file name convention. I actually prefer the SxEE naming
convention, if not for any other reason because it's a bit shorter and it kind of "look
nicer". Silly reasons maybe but I don't really want to change naming convention.
I'm sure this issue will be fixed and in the mean time I can live with it like it is.
Thanks though for your suggestion.
Reported by christer.johansen on 2011-02-22 19:50:53
Originally reported on Google Code with ID 507
Reported by
christer.johansen
on 2011-02-22 18:56:10The text was updated successfully, but these errors were encountered: