Runtime import to XBMC

I am currently having a major issue with the import of the Runtime valu into XBMC. The occure, slightly differently, whether I set the option to use a numeric value only for Runtime. When the nfos are imported, all details except the Runtime is displayed correctly within XBMC. The values shown there can be 1 minutes, the correct valu, or some very large value, such as 1713399145.

I have checked the XBMC database values for Duration, and they seem to be correctly imported, so I suspect the problem lies within XBMC and have raised this as a query with them, but wanted to raise it here as well. If I use XBMC to scrape the details, all is correct.

I have even tried this with a completely fresh install of XBMC, both with numeric only values for the Runtime, and also values ending in min (123 min). I do not get consistent displays for the runtime.

Has anyone else seen this behaviour.

I am running the latest Dharma nightly build of XBMC on Windows 7 64, and 3.317 of Media Companion.

I have done a little more investigation within XBMC by importing just a small subset.

The runtime values are correctly imported into the c11 field of the movie table within XBMC. But theis information does not seem to be displayed within the skin. This seems to be from the iVideoDuration field from the streamdetails table. This information does not seem to be generated directly from the Runtime information, as this info is not within the original nfo file.

I just wanted to confirm I am having the same issues. I am using Media Companion gen2 3.317 to scan my movies with save media runtime as numerical only ticked. XBMC r32050. With Transparency! 3.06 (SVN). A lot of my movies have "1713399145 Minutes" in the Runtime field. I have no idea why this happens. Very few are correct.

Hitcher from the XBMC forum has explained that XBMC uses the <duration>1h 34mn</duration> entry, not the Runtime entry, but MC still writes this as Hours and minutes. Any chance that this could be changed in the same manner as the changes made to Runtime?

I have now edited my database manually to copy the entries for the Runtime field in Movies to the Duration field in streamdata. Did not take long as I exported a query to excel, edited the data, and then imported it back. This has fixed all entries.

I now have to manually edit any new nfos created by MC to ensure that the Duration entry is numeric only, copied from thr Runtime value. I am not skilled enough to write a script to do this, but the number of new entries is small.

FWIW - nope, not seeing this issue at all.
I'm using XBMC_Xbox_30492 with the PM3HD skin

What I am seeing at the moment is that MC does not pick up the runtime value from IMDB at all (although this is new). Maybe because of this, MC does not create a Duration field with the runtime value, even if I add a Runtime value, or get MC to rescan it fom the file.

The Duration entry is what is needed by XBMC, hence the current need for a manual edit.

Again, I'm seeing no issues with the run-time data being scraped from IMDB by MC 3.317.

Can you post examples/screenshots?

A screenshot would no add anything. MC just does not scrape the Runtime. It leaves the field blank. This now happens for every film I scrape. In addition.

Here is an nfo just created for the film 2001, as you can see, it does not contain either Duration or Runtime fields.

http://pastebin.com/7Q60q1Nt

I am also having that exact issue. For me it leaves the Runtime field blank if I scrape more than one movie at a time. If I scrape a single movie everything scrapes fine.

In XBMC most of my movies show this in the runtime field.

OK, here is what is happening.

If under General Preferances you check the "Save media runtime as numerical only" option and then scrape or Batch Rescrape movies it does not create or it removes the <runtime> field from the .nfo.

If you uncheck the "Save media runtime...." option and Scrape or Batch Rescrape all is good and the <runtime> field is created / added to the .nfo.

There is definately an issue with this setting....

The work around at the moment is to uncheck the "Save media runtime..." option then Batch Rescrape the runtimes. Then re-check the option and re-build the .nfo's.

As Rastan mentions if you right click on the movie and Rescrape Specific then it scrapes the time correctly but this is no help if you want to update all your movies.

I am also seeing that the <duration> field is only created on the initial scrape and then vanishes once you change the enable the numerical only option. The only way to get it back is to uncheck the numerical only option and then re scrape specific. It will nto return if you batch re-scrape.

AnthonyB, did you read the first post and check the option for "save media run...." and then check your .nfo's after scraping or re-scraping more than one movie's runtime, because if you do this you will see exactly what everyone is talking about.

Thanks,

Mark.

EDIT: just tried as forgot earlier, you can select multiple movies and Right Click/Rescrape Specific and it will update <runtime> correctly however as XBMC uses Duration it does nto help the situation. I think the whole issue boils down to the fact that the <duration> field vanishes and the only way to get it back is to re-scrape the media tags.

I have now tried version Media Companion gen2 3.400 and the problem remains.

Welcome back Billyad2000 bye the way, and thanks for all the effort.

Regards, Richard

I tried this for the first time last night, and am having very poor results with runtime. Most of my movies have 0 minutes or ridiculous numbers, and these values are stored in the runtime field in the nfo file, so it's not a matter of what XBMC is seeing. I find with many that if I manually right-click and tell it to rescrape runtime from IMDB then I often get a correct value, however no batch process seems to do this correctly. As an example "The 400 Blows" shows a runtime of 219706 min in the nfo file. Manually running the rescan on runtime changes it to 99 minutes. Those that are showing 0 minutes, which is about a third of my collection, also have runtime set to 0 min in the nfo file.

As can be seen from the earlier posts, XBMC imports from the Duration field of the NFO, not the Runtime field. It is this that is not correctly created by MC.

RDHoworth wrote:

As can be seen from the earlier posts, XBMC imports from the Duration field of the NFO, not the Runtime field. It is this that is not correctly created by MC.

Well I'm going to have to remove the source and re-add it in XBMC to see how it comes out this time, but as I recall I saw those same bizarre numbers in XBMC as I was seeing in MC. Approx. 1/3 0 min, 1/3 correct, 1/3 huge numbers. Many of my nfo's don't appear to have duration also.

I just went through the process of removing the source and adding it back in to XBMC and it rescanned the library, and sure enough, the runtime values from my nfo files are showing up now. A few are still wildly wrong after my attempts to force the rescrape, but the vast majority appear correct now. XBMC and MC are showing the same values.