Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of runtime element in NFO #1175

Closed
Omertron opened this issue Mar 15, 2015 · 2 comments
Closed

Use of runtime element in NFO #1175

Omertron opened this issue Mar 15, 2015 · 2 comments

Comments

@Omertron
Copy link
Member

Original issue 1176 created by Omertron on 2010-01-06T04:33:31.000Z:

Running 1252 and all XML regen'd by that version.

It appears that the <runtime /> tag in an NFO is not used at all by YAMJ.
Instead it appears it is getting it from (I am guessing) either a scraper
or MediaInfo scan. What I am trying to do is have a consistent manner in
which the runtime is displayed. At this point in time it seems to vary
based on where YAMJ is getting its information and video parts.

Example 1 - The Spirit (1 part vid)
<runtime>1h 42mn</runtime>

Example 2 - Seven Pounds (2 part vid)
<runtime>123</runtime>

The issue seems to be that when there is a 2 part video it gets the runtime
from a difference source than when a 1 part video. This is almost a whole
different issue. The issue I am reporting though, is that the <runtime>
element in a XMBC style NFO is never picked up. I have used used several
test values in regeneration or fresh creation and it never seems to use
that value.

On a side note, if the 2 part vid runtime was converted from straight
minutes to the hr - min format that would be nice too.

@Omertron
Copy link
Member Author

Comment #1 originally posted by Omertron on 2010-01-06T10:52:38.000Z:

<empty>

@Omertron
Copy link
Member Author

Comment #2 originally posted by Omertron on 2010-02-07T21:22:01.000Z:

Hi,
fixed in r1340

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant