Moves runtime not read correctly from NFO files since r30362

Hi,

I'm having troubles ever since r30362 up to r31123 (latest) reading NFO files (using ember),

With r31123 everything is fine BUT the movie runtime, it only shows 1 minutes or 2 minutes movie length for all my movies instead of the correct runtime,

Does anybody experience the same trouble?

Does anybody know if something changed in XBMC's routine of reading the runtime in the NFO files?

Everything was working perfect up to r30362

I believe a debug is unnecessary so far, thank you for your help!

yes, we now read it from the media files instead.

hello spiff thanks for your fast answer

do you have any idea why e.g. for 1000 different MKV files the runtime is either 1 minutes either 2 minutes instead of reading the correct length?

if I ask that it's because up to now I was using emberMM to read the media file duration (which sounds the same routine XBMC is using now) instead of the imdb/tmdb "official" movie runtime and it was working great because it allowed me to also rename "min" to "minutes"

any help to figure out what could be going wrong would be very appreciated

thanks a lot

no idea, it sounds a bit weird. it's supposed to extract the length in minutes.

okay no problemo,

if anybody else is experiencing the same problem and/or have any clue thanks for sharing

dondre Wrote:okay no problemo,

if anybody else is experiencing the same problem and/or have any clue thanks for sharing

The problem is the .nfo generated for example by mc2 is wrong. In the duration field the time is in "1h 20 min" not "80 min".
The scraper read only the 1 or 2 or 3. Depends on how long the movie is.
The developer of the mc2 will update the app on the weekend.

that's a NASTY regression on our part. will nag the relevant parties. cheers for the heads-up

spiff Wrote:yes, we now read it from the media files instead.

So it won't fall back to the NFO if it can't get the info from the files? I use dummy files with NFO's for my offline DVD's.

read again. it's reading the duration from the nfo's just fine, it's just that it's expecting a single number.

spiff Wrote:read again. it's reading the duration from the nfo's just fine, it's just that it's expecting a single number.

Yeah I was typing my post when that post showed up. Thanks Spiff