[oversight] VOB, mp4 format

[atticus]

I was searching the Oversight wiki for an answer, but I could not find any for the following:
I was looking for a list of formats/file extensions that are recognized by Oversight.
I found that movies of vob extension are not shown in the jukebox.
Such file name pattern I use is: movietitle_year.vob (typically extracted from a DVD).

I'd also like to report a bug: after converting the VOB file into mp4, Oversight recognized it, but on the movie detail page the movie title also contains string "mp4" at the end (although there is an nfo file; movie data, fanart and cover are all OK - except the movie title).

Any help would be appreciated.
http://www.networkedmediatank.com/showth...rksolved=1
many thanks, Atticus

PS: btw I'm using r1271

[who]

(09-08-2010 03:07 PM)atticus Wrote:  I found that movies of vob extension are not shown in the jukebox.
Such file name pattern I use is: movietitle_year.vob (typically extracted from a DVD).

I have run into this problem when ripping episodes from my dvd's to store on the hard drive, but its easily solved.

The pch-200 is a linux device, thus it doesn't care what you name a file, it will play a file depending on the header inside the file. Thus I simply renamed my .vob files to .avi files and Oversight picked them straight up and the pch doesn't have a problem playing them.

[atticus]

(09-10-2010 03:53 AM)who Wrote:  Thus I simply renamed my .vob files to .avi files and Oversight picked them straight up and the pch doesn't have a problem playing them.

Thanks for the hint!
It's a bit misleading if one keeps safety copies of some of its movies in regard of extension<->format and also if the Oversight will be enhanced to recognize and display video file formats.
The simplest solution would be for Oversight to recognize/take into account filename.vob files outside VIDEO_TS directories.

Thanks!

[lordy]

Yup, I'll log it as an issue.

[atticus]

(09-10-2010 12:58 PM)lordy Wrote:  Yup, I'll log it as an issue.

I haven't looked at the code so don't know how Oversight does its scanning, but running on Linux it could be something like:

Code:

/usr/bin/find <path_to_videos> -name \*\.mpeg -o -name \*\.mpg -o -name \*\.avi -o -name \*\.vob -o -name \*\.mkv |sed 's/\/VIDEO_TS\/.*//'

will list the movies that should be taken into account (of course I haven't listed all the extensions).
What can be quicker than the OS find?

[who]

Wouldn't it become a problem when Oversight is looking at ripped dvd directories? They have multiple vob's for just the one movie.

[atticus]

That's why I chopped everything after (and including) VIDEO_TS done by the sed part (with the presumption having a valid DVD image when VIDEO_TS is present; well, this might need some refinement )

[lordy]

No problem , I know what needs to be done

[atticus]

Hi who, now I got what you meant.... getting rid of duplicates.
OK, put afterward a '|sort -u'

[atticus]

... or of course '|/usr/bin/uniq' if that's available. I guess this is faster than 'sort -u'