Support forum for DGDecNV
Sharc
Posts: 233 Joined: Thu Sep 23, 2010 1:53 pm
Post
by Sharc » Fri Oct 25, 2019 11:20 am
I have a source which DGDecNV decodes, demuxes and plays correctly, but fails to create the full index.
The .dgi is just:
Code: Select all
DGAVCIndexFileNV22 DGIndexNV 2053.0.0.190 X32
C:\Program Files Video\DGDecNV\x32 Binaries\
D:\Temp\mer.ts 331482164
DEVICE 0
DECODE_MODES 0,0,0,0,0
STREAM 1 0
PKTSIZ 188
VPID 4113
RANGE 0 0 331482163 0
DEMUX
DEPTH 8
ASPECT 0 0
COLORIMETRY 2 2 2
SPS 25
PPS 79
SIZ 1920 x 1088
DISP 0,1920,0,1080
FPS 60000 / 1001
CODED 0
PLAYBACK 0
0.00% FILM
ORDER -1
Is something odd with the file? A sample is uploaded here (sorry it is 300MB, I could not trim it to less)
https://www.mediafire.com/file/m9r0g80u ... r.zip/file
Guest
Post
by Guest » Fri Oct 25, 2019 5:29 pm
Sharc
I downloaded your file and got the same results with an older version
Tried remuxing with TsMuxer, and that error-ed out, could not figure out video codec stream
Tried remuxing with MKVToolNix and it could not identify the video within the .ts container
I would say that at least your sample is corrupt
MediaInfo does recognize it though
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Sat Oct 26, 2019 8:45 am
DGIndexNV was not accepting profile_idc = 244 as valid. I have fixed that and everything works fine after that. Fix will be in the next slipstream. Thank you for pointing this out, Sharc .
Probably the other apps that fail with this stream also do not handle profile_idc = 244. 244 stands for High 4:4:4 Predictive, however, that profile also allows for 4:2:0. Perhaps this is the reason it is rejected by other apps, i.e., lack of 4:4:4 support in NVDEC for AVC. In the linked stream we have a High 4:4:4 Predictive profile, but the colorimetry is 4:2:0.
I'm curious to know where this stream came from. NVENC?
Sharc
Posts: 233 Joined: Thu Sep 23, 2010 1:53 pm
Post
by Sharc » Sun Oct 27, 2019 3:12 am
Rocky wrote: ↑ Sat Oct 26, 2019 8:45 am
I'm curious to know where this stream came from. NVENC?
AFAIK the original "meridian" file is from here (scroll down to the bottom).
https://media.xiph.org/video/derf/
A converted HD .mp4 snippet for encoder and metric testing purpose was made available here, see 4th paragraph.
https://forum.videohelp.com/threads/394 ... ost2562157
I wrapped it into a .ts container for trimming by means of DGDecNV, and reporting the indexing issue.
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Sun Oct 27, 2019 5:43 am
Thank you!
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Sun Oct 27, 2019 6:57 am
Netflix Meridian. Sneaker converted a sample to 1920x1080 8bit 4:2:0 from the 300GB file for testing
https://mega.nz/#F!BlNDGIgJ!7lBUBs61l1oiIIBScrMyYg
Do we know what sneaker used to convert to HD and what was the command line? I am trying to determine how profile 244 came about. Also, the file in your first link is not 300GB; it says 96GB.
Sharc
Posts: 233 Joined: Thu Sep 23, 2010 1:53 pm
Post
by Sharc » Sun Oct 27, 2019 9:07 am
Seems to be x264. This is what I get from MediaInfo about his 'source.mp4' file:
Code: Select all
General
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/mp41/isom/avc1)
File size : 2.71 GiB
Duration : 40 s 40 ms
Overall bit rate : 581 Mb/s
Encoded date : UTC 2017-03-13 12:03:26
Tagged date : UTC 2017-03-13 12:03:26
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 4:4:4 Predictive@L5.1
Format settings : CABAC / 16 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 16 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 40 s 40 ms
Bit rate : 581 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 4.674
Stream size : 2.71 GiB (100%)
Writing library : x264 core 148 r2744 b97ae06
Encoding settings : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x1:0x131 / me=umh / subme=9 / psy=0 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=0 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc=cqp / mbtree=0 / qp=0
Encoded date : UTC 2017-03-13 12:03:26
Tagged date : UTC 2017-03-13 12:03:26
Codec configuration box : avcC
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Sun Oct 27, 2019 9:19 am
OK, but was profile 244 explicitly requested on the command line?
Sharc
Posts: 233 Joined: Thu Sep 23, 2010 1:53 pm
Post
by Sharc » Sun Oct 27, 2019 9:46 am
No idea. I didn't find a post of his commandline.
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Tue Oct 29, 2019 2:08 pm
OK, no problem, thank you.
Sharc
Posts: 233 Joined: Thu Sep 23, 2010 1:53 pm
Post
by Sharc » Tue Oct 29, 2019 2:27 pm
Slipstream 191 solved the issue.
Rocky
Posts: 3638 Joined: Fri Sep 06, 2019 12:57 pm
Post
by Rocky » Tue Oct 29, 2019 8:43 pm
Thank you for the status update,
Sharc !