2013-06-03, 04:46
(2013-06-02, 03:59)spanktastic2120 Wrote: The runtime value you see on the info dialog in xbmc may not be the <runtime> tag, which is what PTV uses. Try making an episode nfo for one of your episodes with a <runtime> tag with a value of something like 3 hours and then refresh it in your library and select the option to not ignore the local file. Rebuild that channel in PTV and if it takes up 3 hours in the epg then you know its a <runtime> issue. Im not sure exactly what xbmc uses when it shows runtime on the info dialog, but i know ive seen the values for <durationinseconds> and <runtime> which for some reason are different tags.
Im pretty sure, though not positive, that when you scrape from thetvdb the runtime will be whatever its listed as on that site, which could be 30 minutes even though without commercials an episode is 21 minutes. And the newer versions of PTV use the runtime stored by xbmc (which again may not be the value you see on the info dialog) before parsing the file for its runtime, i think its faster this way, im not a developer so i dont know why the change was made.
Hmmm.
I have just checked and it appears some shows have <runtime> in the details (simply says 30 minutes) where some files have <durationinseconds>. XBMC must have changed how it stores tags or whatever because I have only ever used XBMC to scrape details and create NFO files for the last 3 years.
Not sure why the change has been made either but I had no issues using the old method of getting the time. It would be great to have an option in the settings to use the old way or new way. The only "issue" I had was a slightly slow guide but I only have about 20 channels setup and no online channels so it was fine for me. The last thing I want to do is update all my 50,000 NFO files with the time.