[file] has a runtime of 0, is it a valid video file?

Help & Support
1

This is the first time I’ve come across this, but I’m getting the following this morning:

[/[edited path]/[showname].2x01.720p HDTV x264-FoV/[showname].2x01.720p_hdtv_x264-fov.mkv] has a runtime of 0, is it a valid video file?

It’s an 800mb file and I’ve confirmed it does play, so I’m not sure what’s throwing it off?

Let me know what else you need :slight_smile:

EDIT: I’m on 2.0.0.1665

EDIT2: This is from the Wanted > Missing page. Not sure if Drone thinks it’s still downloading (the tooltip says “Episode Downloading 100%”)? It’s completed in SAB.

2

mediainfo is unable to determine the run time, could be a number of reasons why, please PM me the release name so I can take a look.

Its downloading 100% because drone see’s it completed in SAB, but not yet imported. We have some work to do to expose the import failure in the UI (and show that instead of downloading).

3

No worries, I’ve PM’d that to you :slight_smile:

4

That file was nuked and a repack was released, the file is incomplete which is likely why mediainfo fails to process it.

5

That would indeed explain it! Sorry, I really should have checked for that.

Plus I guess Drone hasn’t grabbed the proper/repack as it still thinks this one is underway. Bit of an edge case I guess.

Thanks Markus :wink:

6

Yeah, I suspect thats the reason as well. Definitely an edge case.

7

I’m also having this issue. avprobe and mediainfo both return the expected runtime.

Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High 10@L5.1
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 16 frames
Codec ID                                 : V_MPEG4/ISO/AVC
Duration                                 : 23mn 43s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Scan type                                : Progressive
Title                                    : AVC
Writing library                          : x264 core 129 r2230 1cffe9f
Encoding settings                        : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=crf / mbtree=1 / crf=18.0 / qcomp=0.60 / qpmin=0 / qpmax=81 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
8

@Tolstyak which version of media info are you using? Which OS are you using?

9 
libmediainfo0:amd64                                         0.7.58-1
mediainfo                                                   0.7.58-1

I’m on Debian 7.6, with a few testing packages installed.

10

Might be in how drone is asking for the runtime is incompatible with that version of media info. Looks like 0.7.58 is over two years old.

At this point, I’d suggest upgrading to at least 0.7.64 (the version we include with drone for Windows right now).

11

Turns out it was just an ACL issue. The user nzbdrone was running as couldn’t read the mkv file. The error text threw me off. Thanks for your assistance.

12

Thanks for letting us know, glad its sorted.