Problem with v2045 log file

Support forum for DGDecNV
Post Reply
DAE avatar
rajs
Posts: 2
Joined: Sun Mar 06, 2011 4:27 am

Problem with v2045 log file

Post by rajs »

For some reason, v2045 of DGDecNV is not writing any video info to the log file when indexing an MPEG transport stream. Here's an example log using v2044:

Code: Select all

Stream Type: Transport [188]
Video Type: AVC
Profile: High
Level: 4
Coded Size: 1920x1088
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 25.000000 fps
Colorimetry: BT.709 [1]
Frame Structure: 
Frame Type: 
Coded Number: 449
Playback Number: 449
Frame Repeats: 0
Field Repeats: 0
Bitrate: 
Bitrate (Avg): 
Bitrate (Max): 
Elapsed: 0:00:00
Remain: 0:00:00
FPS: 
Info: Finished!
and here's what v2045 produces:

Code: Select all

Stream Type: 
Video Type: AVC
Profile: 
Level: 
Coded Size: 
SAR: 
Display Size: 
Frame Rate: 
Colorimetry: 
Frame Structure: 
Frame Type: 
Coded Number: 449
Playback Number: 449
Frame Repeats: 0
Field Repeats: 0
Bitrate: 
Bitrate (Avg): 
Bitrate (Max): 
Elapsed: 0:00:00
Remain: 0:00:00
FPS: 
Info: Finished!
I have posted the transport stream (together with dgi and log files from v2044 and v2045) here: http://www.mondrianie.com/DGDecNV.html
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Problem with v2045 log file

Post by admin »

Works fine for me. Please tell me the exact steps you go through to produce that result. Also can you give me your INI file too please?
DAE avatar
rajs
Posts: 2
Joined: Sun Mar 06, 2011 4:27 am

Re: Problem with v2045 log file

Post by rajs »

I've found out what the problem is. My INI file had

Code: Select all

Enable_Info_Log=1
Full_Info=0
Editing it to

Code: Select all

Enable_Info_Log=1
Full_Info=1
fixes the problem. I suppose the only niggle is that the "Enable Info Log" in the Options menu of DGIndexNV only toggles Enable_Info_Log in the INI file. There is no command to set Full_Info.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Problem with v2045 log file

Post by admin »

Thank you for the update and analysis. I will try to address your niggle for the next version.
Post Reply