Recent changes to issues

Ticket 9 discussion

Anonymous — Sat, 08 Aug 2015 06:51:15 -0000

Originally posted by: brandon....@gmail.com

Fixed in rev 4.

Status: Fixed

Ticket 8 discussion

Anonymous — Sat, 08 Aug 2015 06:51:14 -0000

Originally posted by: brandon....@gmail.com

Fixed in rev 4.

Status: Fixed

Ticket 72 discussion

Anonymous — Sat, 08 Aug 2015 06:51:14 -0000

Originally posted by: brandon....@gmail.com

This is now fixed in the latest version in svn. (Not to be confused with the latest released version which is yet to incorporate these changes).

Ticket 72 discussion

Anonymous — Sat, 08 Aug 2015 06:51:14 -0000

Originally posted by: james.cu...@returnpath.com

@brandon: Sorry for the late reply.

Here's the list of settings in my DB matching query: SELECT * FROM settings WHERE value LIKE '%dbschemaver';

Ticket 72 discussion

Anonymous — Sat, 08 Aug 2015 06:51:14 -0000

Originally posted by: brandon....@gmail.com

Hi,
This should now be fixed in the lastest svn revision (not in the release package). issues has to do with mythvideo being incorporated into the main myth code and no longer being a plugin (as of 0.25). It now also supports the config.xml file for mysql details.

Status: Fixed

Ticket 72 discussion

Anonymous — Sat, 08 Aug 2015 06:51:14 -0000

Originally posted by: brandon....@gmail.com

Thanks for the patch and sorry for the seriously delayed response. Firstly, what version of mythtv are you currently running, and, secondly, do you think 'mythvideo.DBSchemaVer' is no longer used and its purpose has been merged with 'DBSchemaVer'?

Could I ask you to supply me with the list of all entries in the settings table where value is like '%dbschemaver'. Thank you.

Ticket 71 discussion

Anonymous — Sat, 08 Aug 2015 06:51:13 -0000

Originally posted by: brandon....@gmail.com

I'm going to close this issue. I know its a bugger when things don't parse correctly, but i'm going to put a higher priority on tv show parsing correctly than the odd movie that doesn't parse correctly.

FYI: If you notice a movie didn't parse correctly and has no meta data, you can edit the details in mythfrontend, then the next time the script is run it should conduct searches with the details in the database and not parse the filename.

Status: WontFix

Ticket 71 discussion

Anonymous — Sat, 08 Aug 2015 06:51:13 -0000

Originally posted by: Dominic....@gmail.com

Yes I did modify the imdb.pm & ttvdb.pm files with the paths I listed above. I'll change this back.

I see what you're getting at, not an easy balance to keep there. I don't think you can make it more accurate for movies without sacrificing accuracy for series, and vice versa. Going on what you've described the only thing I could think of getting better accuracy for both is by having a command line option to enforce a strict file and/or directory naming convention. That way you could specify delimiters for things like title, year of production, season and episode details. Obviously this would require a bit of work to ensure the video repository structure matches this standard and would probably only present a real advantage when making mass updates.

Anyway, given what you've explained I wouldn't worry about this one too much. I'm currently reparsing my entire collection, so I'll let you know the problem cases.

Cheers!

Ticket 71 discussion

Anonymous — Sat, 08 Aug 2015 06:51:13 -0000

Originally posted by: brandon....@gmail.com

Firstly, can i ask if you have modified those two scripts at all? Only one of the Ttvdb plugins and one of the Tmdb plugins should be running. If you have not made any changes then i'll look into it. I'll consider making the error messages less 'alarming'.

What you have suggested for the prematch won't work. The main problem is that the script is 100% confident that 127 is season episode info, with the general assumption that the tite is to the left of that. This representation is problematic, but i have seen it used in cases where the filename includes the title and excludes the title of the show. There is an AI based parser in the script (kind of a last ditch effort) that may pick up on this format of season episode info if there is more the 5 episodes, so i might remove this specific parser completely thus allowing it to work in your specific case. The problem with doing this though is the AI mode only works if all the files are in the same directory, so if you are kicking off a new season of a show with only one or two episodes then the AI doesn't work for a while.

Starting to see the juggling act :-)

I'll see what i can do if I get the script to check the length of the prematch (prematch refers to the info to the left of the season episode data match) when it finds a season episode match, if the length is short, then maybe it is not an episode, and perhaps it is a movie.

It would be good if you could post some other files (include complete path) that fail due to a similar reason.

Seriously glad you like the script, and spread the word where posible.

Ticket 71 discussion

Anonymous — Sat, 08 Aug 2015 06:51:13 -0000

Originally posted by: Dominic....@gmail.com

Thanks for the quick reply. I am running MythTV 0.23.1, here is the output from the stat command;

htpc@htpc:~$ mythvideo-scanner.pl --stat
mythvideo-scanner
https://code.google.com/p/mythvideo-scanner/
Version: 3.1, Rev: 142

Grabber: Ttvdb, Version: 2.1, ttvdb.py:
Grabber: Tmdb, Version: 2.1, tmdb.py:
Grabber: Ttvdb, Version: 1.1, ttvdb.py: v1.0.9
Grabber: Tmdb, Version: 1.1, tmdb.pl: v0.1.8
Grabber: Imdb, Version: 2.0, Rev: 140
Grabber: Tvrage, Version: 1.1, Rev: 128
Grabber: Cinecurry, Version: 1.0, Rev: 140

Wasn't causing an issue and the scripts still appeared to be working, just I was getting a message about not being able to find the scripts with the original paths in there. Sounds like a side effect of running MythTV 0.23.1 on an older release of Mythbuntu perhaps?

As for the prematch issue, I see now it is a bigger issue than just being able to cloak out the path as often directories are being used to separate series and seasons, in which case you'd want the script to be looking at the path to help define the prematch.

I'll have a look at the --hint option, though I have a couple of dozen movies with this issue. Good that it keeps this data for future lookups though. Another idea I had was being able to specify a base path as a command line option. Idea being that the section of the path matching that specified in the base path command line option is omitted from being used in the prematch. For example if I set the base path command line option to /var/lib/mythtv/videos then the prematch from above would only include 127 Hours. This way if I had a TV series nested in directories underneath this base path they would still be used in the prematch. Does this sound viable at all?