Philippe Normand a écrit : > *WARNING*: This is not intended for newbies, proceed with care! :) > > > The regexes are in the database plugin, which should be stored in a egg > file (rename the extension to .zip to extract it). In your windows > personal directory, in .elisa-0.5\plugins > \elisa_plugin_database-0.something.egg > > Extract the egg contents > Edit elisa\plugins\database\video_parser.py > Reput *everything* in the egg > Start Elisa > > And be sure to share with us the stuff you added, so that it might be > added for next release of the plugin. > > Philippe
Note that the clean way to do this is slightly more complex. You'd need to setup a development environment, checkout the bzr branch, modify there the video parser, bump the version number of the database plugin, regenerate an egg and put it in %USERPROFILE%\.elisa-0.5\plugins\. Olivier > Le jeudi 26 février 2009 à 00:40 +0000, [email protected] a écrit : >> Where exactly are the regex's that detect the movie/shows patterns on >> the windows install? I didn't see a video_perser.py file in >> >> C:\Program Files\Elisa\elisa-plugins\elisa\plugins\database\ >> or >> C:\Documents and Settings\User\.elisa-0.5\elisa\plugins >> >> My movies are all in a "Movies" directory formatted as "Movie Name >> [year] .avi|mkv"; and all movies with the year in the filename >> (between brackets) as well as all mkv files are not getting >> recognized. I can figure out the regex....I just gatta find the .py >> file =). >> >> Also, completely unrelated....is there a way to adjust the fast >> forward and rewind jump times? I thought I remembered it being in the >> elisa.conf when I was running Elisa under Ubuntu...but that was a much >> older version. >> >> >> -Buddy >> >> >> On Feb 24, 2009 10:54pm, Matej Konecny <[email protected]> >> wrote: >>> Hi, >>> I've checked the blueprint, it is indeed improvement. But isn't it >> easier just to "tag" some paths as "movies" and some "tv shows"? This >> seems easier than rather complex "pattern" and is also done in XBMC or >> boxee and I also used that in my movie-library attempt. Also, using >> only filenames is quite tricky, there will always be a pattern that >> you forgot to include. I suppose there need to be a possibility to add >> new regexp's as you find them (config file?). >>> >>> Matej >>> >>> >>> On Tue, Feb 24, 2009 at 11:11 PM, [email protected]> wrote: >>> >>> Philippe: That would be an awesome addition, absolutely! I'm >> currently >>> setting up a development version of Elisa - I haven't played with >> Python >>> before but I might have a crack at it and see what I can come up >> with... >>> >>> >>> Olivier: I'll have a look and if I can make it work, will post again >> to >>> see if it's worth contributing them. For reference, it's mainly TV >> shows >>> that it's not recognising - these are in the format '/TV Show >> Name/[SSxEE] >>> Episode Name.mkv' (SS = series/season number, EE = episode number). >>> >>> >>> >>> Will keep you posted. >>> >>> >>> >>> Cheers, >>> >>> Matt. >>> >>> >>> >>>> Matt, >>>> If you are going to write custom regexps, please contribute them >> back if >>>> you think it makes sense. >>>> Cheers, >>>> Olivier >>>> Philippe Normand a écrit : >>>>> Would the implementation of that blue-print help? >> https://blueprints.edge.launchpad.net/elisa/+spec/video-hierarchy-awareness >>>>> Anyway, you can see what regexes we apply on video filenames in >>>>> elisa/plugins/database/video_parser.py >>>>> Philippe >>>>> Le lundi 23 février 2009 à 02:23 -0800, [email protected] a >> écrit >>>>> : >>>>>> Hi all, >>>>>> Just wondering if someone could point me in the direction of the >> code >>>>>> that >>>>>> controls how files are magically understood to be a TV series, >> movie >>>>>> etc. >>>>>> I'd like to add a few extra bits to take into account the way I >> have >>>>>> stored the majority of my files so they can show up properly. >>>>>> Currently I'm having to re-name my files (for example: '1x02. >> Episode >>>>>> Name') to get them recognised and I'd prefer not to mess with >> this. >>>>>> If this isn't the right place for this message, my apologies :) >>>>>> Cheers, >>>>>> Matt.
