[CLOSED] Invalid data found

Support forum for DGDecNV
Post Reply
Xunkar
Posts: 15
Joined: Sun Aug 18, 2019 5:17 am

[CLOSED] Invalid data found

Post by Xunkar » Fri Sep 06, 2019 10:03 am

I'm working on a Star Wars BluRay, and while there hasn't been any error or warning when indexing the m2ts with DGIndexNv, ffmpeg gives me a non-fatal error when encoding the AviSynth script all of a sudden. Here are the details

Script:

Code: Select all

DGSource("D:\Ripping\VOB\00800.dgi")
Prefetch(6)
FFMPEG Command:

Code: Select all

ffmpeg -i .script.avs -hide_banner -loglevel info -y -c:v libx264 -preset slow -crf 19 -tune grain -an "00800@1920x1080.mkv"
Error "D:\Ripping\VOB\00800.dgi: Invalid data found when processing input" The resulting video does not show any obvious artifacts or anything wrong though, but it's the first time I'm getting this error (and my workflow hasn't changed).

DGIndexNv log:

Code: Select all

Stream Type: Transport [192]
Video Type: AVC
Profile: High
Level: 4.1
Coded Size: 1920x1088
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 23.976024 fps
Colorimetry: Unknown [2]
Frame Structure: Frame
Frame Type: I
Coded Number: 1
Playback Number: 1
Frame Repeats: 0
Field Repeats: 0
Bitrate: 
Bitrate (Avg): 
Bitrate (Max): 
Audio Stream: 1100: DTS HDMA C+L+R+SL+SR 48 1536
Audio Stream: 1101: AC3 5.1 48 448
Audio Stream: 1102: AC3 5.1 48 448
Audio Stream: 1103: AC3 5.1 48 448
Audio Stream: 1104: DTS C+L+R+SL+SR 48 768
Audio Stream: 1105: AC3 5.1 48 448
Audio Stream: 1106: AC3 2.0 48 224
Audio Stream: 1107: AC3 2.0 48 224
Elapsed: 0:06:36
Remain: 0:00:00
FPS: 
Info: Finished!

4352: D:\Ripping\VOB\00800 PID 1100 C+L+R+SL+SR 48 1536.dts
4353: D:\Ripping\VOB\00800 PID 1101 5.1ch 48KHz 448Kbps.ac3
4354: D:\Ripping\VOB\00800 PID 1102 5.1ch 48KHz 448Kbps.ac3
4355: D:\Ripping\VOB\00800 PID 1103 5.1ch 48KHz 448Kbps.ac3
4356: D:\Ripping\VOB\00800 PID 1104 C+L+R+SL+SR 48 768.dts
4357: D:\Ripping\VOB\00800 PID 1105 5.1ch 48KHz 448Kbps.ac3
4358: D:\Ripping\VOB\00800 PID 1106 5.1ch 48KHz 224Kbps.ac3
4359: D:\Ripping\VOB\00800 PID 1107 5.1ch 48KHz 224Kbps.ac3
4608: D:\Ripping\VOB\00800 PID 1200.sup [total 1658, forced 0]
4609: D:\Ripping\VOB\00800 PID 1201.sup [total 1348, forced 29]
4610: D:\Ripping\VOB\00800 PID 1202.sup [total 29, forced 29]
4611: D:\Ripping\VOB\00800 PID 1203.sup [total 1325, forced 30]
4612: D:\Ripping\VOB\00800 PID 1204.sup [total 1312, forced 0]
4613: D:\Ripping\VOB\00800 PID 1205.sup [total 1350, forced 29]
4614: D:\Ripping\VOB\00800 PID 1206.sup [total 1412, forced 0]
4615: D:\Ripping\VOB\00800 PID 1207.sup [total 1378, forced 0]
4616: D:\Ripping\VOB\00800 PID 1208.sup [total 1395, forced 0]
4617: D:\Ripping\VOB\00800 PID 1209.sup [total 1374, forced 0]
4618: D:\Ripping\VOB\00800 PID 120a.sup [total 2229, forced 0]
4619: D:\Ripping\VOB\00800 PID 120b.sup [total 1610, forced 0]
4620: D:\Ripping\VOB\00800 PID 120c.sup [total 2344, forced 0]
4621: D:\Ripping\VOB\00800 PID 120d.sup [total 1605, forced 0]
4622: D:\Ripping\VOB\00800 PID 120e.sup [total 2377, forced 0]
4623: D:\Ripping\VOB\00800 PID 120f.sup [total 1606, forced 0]
4624: D:\Ripping\VOB\00800 PID 1210.sup [total 2375, forced 0]
4625: D:\Ripping\VOB\00800 PID 1211.sup [total 1605, forced 0]
4626: D:\Ripping\VOB\00800 PID 1212.sup [total 2378, forced 0]
4627: D:\Ripping\VOB\00800 PID 1213.sup [total 1605, forced 0]
4628: D:\Ripping\VOB\00800 PID 1214.sup [total 2378, forced 0]
4629: D:\Ripping\VOB\00800 PID 1215.sup [total 1605, forced 0]
4630: D:\Ripping\VOB\00800 PID 1216.sup [total 2378, forced 0]
4631: D:\Ripping\VOB\00800 PID 1217.sup [total 1606, forced 0]
4632: D:\Ripping\VOB\00800 PID 1218.sup [total 2377, forced 0]
4633: D:\Ripping\VOB\00800 PID 1219.sup [total 1608, forced 0]
4634: D:\Ripping\VOB\00800 PID 121a.sup [total 2376, forced 0]
4635: D:\Ripping\VOB\00800 PID 121b.sup [total 1605, forced 0]
4636: D:\Ripping\VOB\00800 PID 121c.sup [total 254, forced 254]
4637: D:\Ripping\VOB\00800 PID 121d.sup [total 222, forced 222]
4638: D:\Ripping\VOB\00800 PID 121e.sup [total 29, forced 29]
The DGI is too big to paste but can be found here https://mab.to/Og6KB4bXC

User avatar
admin
Site Admin
Posts: 4382
Joined: Thu Sep 09, 2010 3:08 pm

Re: Invalid data found

Post by admin » Fri Sep 06, 2019 10:19 am

First, I don't know if it is relevant to the message, but get rid of the prefetch(6). DGSource is a HW decoder and the HW operates serially.

Regarding the error message, I do not provide support for ffmpeg nor get involved with debugging it. Please consult with the authors for problems with ffmpeg. If you can show a problem in DGDecNV then of course I would address it.

Google "ffmpeg Invalid data found when processing input" and you'll see all kinds of reports for many different applications, and many different possible causes.

I'm going to mark this closed as not a DGDecNV issue. If you can post again showing that there is such an issue then I will be happy to reopen it.

Post Reply