DGMPGDec 1.4.9 Final

[Guest]

>it reported error

You still didn't tell me the error message!

Making an intermediate AVI and all that is not needed. AutoGK will do everything for you, including setting up and invoking DGIndex/DGDecode. Why are you trying to do everything manually? Anyway, this is not a DGMPGDec issue. You should put this issue in the (Auto)GK forum.

OK, what's your next issue *with DGMPGDec*.

[eEXPERTxtreme]

Hmmph... Actually, audio works for some video .... >_+
Anyway, forget the audio... it must be something other...

And hmm it works pretty much now...

Thanks for help :)

:thanks:

And, erm.... I use AUTOGK only for making a .mp3 file, and for calculating needed size (it calculates it in VDUBMOD).
Though, AUTOGK doesn't give me the best quality... That's why I do many things manually, I get much better quality :)
I noticed that, fortunately ^^
Okay, if I'll have any other question, I'll post...
THanks again!

[BigDid]

Hi,

Concerning AutoGK and Dgindex 1.49 see MoreFAQ 5.15

Did

[Zap250]

With all those improvements I'm surprised you designated it version 1.4.9 instead of 1.5. Good job neuron2 and thanks for keeping it updated!

[Guest]

Yeah, the numbering is a bit arbitrary, I agree.

[peter100m]

@neuron2: It seems like the documentation in 1.4.9 for the D2V file format is wrong. When looking at a version16 D2V I see 8 fields whereas the documentation describes only 7 fields. Is there an added field recently?

[SpAwN_gUy]

hello, i think my first post here...

okay recently i've been using x264farm (see the HowTo in my signature for more details).
and i've faced one problem(well, not a problem, but very annoing).
there is an "Use full paths" option.. yes, it works great,.. but..
in order to work perfectly i need to store Relative paths in .d2v
so if file placement is:
d:\dvd\onedvd\vob\*.vob
and when i place .d2v here:
d:\dvd\onedvd\some.d2v
if checked "Use full paths" contents of .d2v are:

d:\dvd\onedvd\VOB\VTS_01_1.VOB
d:\dvd\onedvd\VOB\VTS_01_2.VOB
d:\dvd\onedvd\VOB\VTS_01_3.VOB
etc...
and when unchecked i get just:

VTS_01_1.VOB
VTS_01_2.VOB
VTS_01_3.VOB
etc... and... in the end this file does not work...
so i have to modify it like

VOB\VTS_01_1.VOB
VOB\VTS_01_2.VOB
VOB\VTS_01_3.VOB
etc... so i would work...

is it possible to make such option or change the behavior of "unchecked" "Use full paths", so output d2v would store "Relative paths"?

[Guest]

@neuron2: It seems like the documentation in 1.4.9 for the D2V file format is wrong. When looking at a version16 D2V I see 8 fields whereas the documentation describes only 7 fields. Is there an added field recently? I only see 7. Can you post the top of the D2V file?

[peter100m]

Here's the top of a D2V created with 1.4.9
DGIndexProjectFile16
1
D:\video\samples\vob\sample1\VTS_01_1.VOB

Stream_Type=1
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=720x576
Field_Operation=0
Frame_Rate=25000 (25/1)
Location=0,0,0,b9a

d00 1 0 2048 0 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 208896 0 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 475136 0 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 796672 0 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2


Here's the D2V output of the same file with 1.4.8 and there's one column less in the file

DGIndexProjectFile13
1
D:\video\samples\vob\sample1\VTS_01_1.VOB

Stream_Type=1
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=720x576
Field_Operation=0
Frame_Rate=25000 (25/1)
Location=0,0,0,B9A

d00 1 0 2048 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 208896 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 475136 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
d00 1 0 796672 1 1 92 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2

[Guest]

So now there are 7 when there used to be 6. All 7 are documented. What is the problem?

Your red highlighted field is the documented 'skip' field.

[peter100m]

Ok.
No problem, the info is in the documentation now but was not present in the DGIndexManual.html I had for 1.4.9 (the header said 1.4.9, date was 2007-01-23).
I downloaded 1.4.9 again from your site and there the info was.
Thank you and sorry to bother for nothing :)

[kypec]

...is it possible to make such option or change the behavior of "unchecked" "Use full paths", so output d2v would store "Relative paths"?
But how much "relative" the path should then be?
How could one tell which of these
VOB\VTS_01_1.VOB
onedvd\VOB\VTS_01_1.VOB
dvd\onedvd\VOB\VTS_01_1.VOB
meets your criteria of relativity? :confused:

[SpAwN_gUy]

But how much "relative" the path should then be?
How could one tell which of these
VOB\VTS_01_1.VOB
onedvd\VOB\VTS_01_1.VOB
dvd\onedvd\VOB\VTS_01_1.VOB
meets your criteria of relativity? :confused:

okay.. i'll explain...

theese files work Perfectly
FileSystem(FS):G:\DVDRiP\AFRO\DVD1\01\VTS_02_1.VOB
G:\DVDRiP\AFRO\DVD1\AS01\AS01.d2v
AS01.d2v internals:DGIndexProjectFile16
7
..\01\VTS_02_1.VOB

FS:G:\DVDRiP\Yatta\01-03\VOB\VTS_01_1.VOB
G:\DVDRiP\Yatta\01-03\01.d2v
01.d2vVOB\VTS_01_1.VOB

well. it's simply windows's Relative paths with those (as far as i remember)
"..\" - directory up
".\" - same dir (well.. blanc - also works.. as in 01.d2v)
and "..\..\" - 2 directories up.

and, of course, there can be no "relativeness" when files are locaten on different drives.

:thanks: in advance.

if it will help.. i've found some peace of code, that might actually work..
http://forum.java.sun.com/thread.jspa?threadID=584546&tstart=30

[Guest]

Thank you and sorry to bother for nothing :) Don't worry, it's my fault because I should mark the beta version manuals instead of calling them all 1.4.9.

[LordIntruder]

Hello. :)


I'm using the 1.4.9 final.

I intend to rip a serie divided on 3 DVD.

VOB from DVD1 are located on drive H.
VOB from DVD2 are located on drive H in another directory.

and as there is not enough space on this drive, I copied VOB from DVD 3 on drive D.

I launch DGindex, I select VOB from DVD1 on drive H, I click "Add", select VOB from DVD2 (the vob are then added at the end), I click "Add" then I select VOB from DVD3 on drive D and here, rather to logically see the VOB being added at the end of the list, they are put first on top.

Drive "D" is before "Drive "H" so Dgindex add the VOB at the beginning of the list. Of course I can select VOB one by one, click "down" and then they will be at the correct order.

Is it a normal behaviour? Otherwise I would suggest to always add the VOB at the end of the list instead of lying on the alphabetic driver order.

Could I also suggest to add the possibility to select all VOB in the list? We can't select several VOB at once and move them up or down in one click, instead we have to do it for each VOB. Yeah I'm a lazy guy. ;)

Except that very tiny and minor problem, 1.4.9 rocks for me. :)

Again thanks you for your work Neuron2. :)

[Guest]

I understand your issue and it is logical to exclude the path prefix from the path before sorting. I will try to do something for you for the next release. Thank you for pointing it out. I'm lazy too. :)

I will also try to solve the "filename with commas" issue as well as the relative path issue discussed above.

[The Scientist]

Not to try to give you any extra work but what's the chances of you adding a command line option to disable any pop-up window warnings etc in one of your next betas.

[Guest]

The chances are pretty good, I reckon.

[The Scientist]

That's great :) cheers

[decayed.cell]

Getting all sorts of errors when compiling the asm files with VS8's Microsoft Macro Assembler

1> Assembling: idctmmx.asm
1>idctmmx.asm(52) : error A2008: syntax error : TEXTEQU
1>idctmmx.asm(1120) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1120): Main Line Code
1>idctmmx.asm(1120) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1120): Main Line Code
1>idctmmx.asm(1120) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1120): Main Line Code
1>idctmmx.asm(1120) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1120): Main Line Code
1>idctmmx.asm(1121) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1121): Main Line Code
1>idctmmx.asm(1121) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1121): Main Line Code
1>idctmmx.asm(1121) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1121): Main Line Code
1>idctmmx.asm(1121) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1121): Main Line Code
1>idctmmx.asm(1122) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1122): Main Line Code
1>idctmmx.asm(1122) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1122): Main Line Code
1>idctmmx.asm(1122) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1122): Main Line Code
1>idctmmx.asm(1122) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1122): Main Line Code
1>idctmmx.asm(1123) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1123): Main Line Code
1>idctmmx.asm(1123) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1123): Main Line Code
1>idctmmx.asm(1123) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1123): Main Line Code
1>idctmmx.asm(1123) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1123): Main Line Code
1>idctmmx.asm(1124) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1124): Main Line Code
1>idctmmx.asm(1124) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1124): Main Line Code
1>idctmmx.asm(1124) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1124): Main Line Code
1>idctmmx.asm(1124) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1124): Main Line Code
1>idctmmx.asm(1125) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1125): Main Line Code
1>idctmmx.asm(1125) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1125): Main Line Code
1>idctmmx.asm(1125) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1125): Main Line Code
1>idctmmx.asm(1125) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1125): Main Line Code
1>idctmmx.asm(1126) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1126): Main Line Code
1>idctmmx.asm(1126) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1126): Main Line Code
1>idctmmx.asm(1126) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1126): Main Line Code
1>idctmmx.asm(1126) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1126): Main Line Code
1>idctmmx.asm(1127) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(5): Macro Called From
1> idctmmx.asm(1127): Main Line Code
1>idctmmx.asm(1127) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(9): Macro Called From
1> idctmmx.asm(1127): Main Line Code
1>idctmmx.asm(1127) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(17): Macro Called From
1> idctmmx.asm(1127): Main Line Code
1>idctmmx.asm(1127) : error A2070: invalid instruction operands
1> DCT_8_INV_ROW_1_s2(21): Macro Called From
1> idctmmx.asm(1127): Main Line Code
1>idctmmx.asm(1129) : error A2022: instruction operands must be the same size
1> DCT_8_INV_COL_4_s2(8): Macro Called From
1> idctmmx.asm(1129): Main Line Code
1>idctmmx.asm(1129) : error A2022: instruction operands must be the same size
1> DCT_8_INV_COL_4_s2(33): Macro Called From
1> idctmmx.asm(1129): Main Line Code
1>idctmmx.asm(1129) : error A2022: instruction operands must be the same size
1> DCT_8_INV_COL_4_s2(38): Macro Called From
1> idctmmx.asm(1129): Main Line Code
1>idctmmx.asm(1129) : error A2022: instruction operands must be the same size
1> DCT_8_INV_COL_4_s2(55): Macro Called From
1> idctmmx.asm(1129): Main Line Code
1>Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"

Manually calling NASM via command line for mcsse.asm worked fine though :o

[Guest]

I'm using MASM 6.14.8444 for the ml-compiled objects. You can get it on the net.

[decayed.cell]

I'm using MASM 6.14.8444 for the ml-compiled objects. You can get it on the net.
After some googling I got ml 6.15 from the VC6 Processor Pack - works fine :D

[njahnke]

Not to try to give you any extra work but what's the chances of you adding a command line option to disable any pop-up window warnings etc in one of your next betas.

The chances are pretty good, I reckon.

i'll put in another vote for this option. i get a lot of people cutting pieces of vobs out and having dgindex throw up that "opening gop not closed" warning every time it opens a file totally destroys the purpose of the cli in my mind (headless operation becomes impossible).

thanks so much for your hard work on this essential tool.

[Isochroma]

I often play mpeg-2 .ts files using Haali's splitter, and then after identifying the audio tracks' language by ear, I use DGIndex to index them. At that stage I choose which track(s) to demux. However, Haali's splitter reports all PIDs in decimal, while DGIndex shows them in Hex. So I get out Calc and do the conversion to figure out which track is which.

So the wish for a future version is a decimal output in addition to the hex already provided, like this:

AC3/DTS Audio on PID 0x112d (4397)

Thanks!

[InorganicMatter]

Hey guys, sorry if I stupid, but I dunno much of anything about the internal workings of DGIndex.

Anyways, the old version (1.4.8) would automatically correct field order problems. The new version (1.4.9) does not automatically correct, and instead leaves it up to the user to correct the problem.

This creates a huge amount of problems for MPEG-4 GUIs that use DGIndex for one-click and batch encoding. Several times now, it has stopped my jobs a few moments after I clicked "start" and walked away, only to come back hours later to find the job still hasn't started yet, and is just sitting there saying "Field Order problem detected!"

[Guest]

Yes, I'll give you decimal PID output too.

I'm going to suppress all popups when in CLI mode.

[InorganicMatter]

I'm going to suppress all popups when in CLI mode.

That'll work, thanks! :)

[d0ORk]

When I'm trying to load a .m2ts File into the DgIndex it says "No audio or video data found". But it's the main movie and the file plays well in Mediaplayer Classic. I can load the trailers without problems, but not the mainmovie.

[Guest]

It's probably not MPEG2. Did you check that possibility?

[d0ORk]

It's a m2ts file. Mediainfo says:

Vollständiger Name : x:\not4ureyes\00009.m2ts
Format : BluRay Video
Format/Family : MPEG-2
Dateigröße : 30.6 GiB

[dk75]

d00Rk, to be on safe side, do you means that main file (30gb) plays well within MPC too or only trailers plays fine?

[d0ORk]

The main file plays well in MPC

[Guest]

DGMPGDec supports MPEG1 and MPEG2 streams only.

[d0ORk]

Thats why I wanted to try it. It's a MPEG2 File

[Guest]

Post a link to an unprocessed source sample so that I can duplicate your issue.

What do you get when you do Stream/Detect PIDs?

[d0ORk]

cant make a sample as i cant load it into dgindex :)
tsremux wouldnt do an unprocessed sample

[Guest]

Just use any old binary splitter utility. It doesn't matter.

Again, what do you get when you do Stream/Detect PIDs?

[d0ORk]

It's this:

http://mitglied.lycos.de/macpackz/Unbenannt.JPG

[Guest]

I don't see any MPEG 1/2 video there. What makes you so sure it is MPEG2?

Highlight PID 0x1011 and hit Set video. If it doesn't display video, then it is not MPEG 1/2. Unless there's a bug, of course. :)

[d0ORk]

Mhh.
TSRemux and Mediainfo say it's MPEG2

[Guest]

If you want to go any further with this I'm going to need the stream sample. It's not hard to just do a binary cut. Use google to find a binary splitter utility.

[Sharktooth]

Im in a process to update all the outdated softwares in MeGUI auto-update server so i have a question for Donald.
Is it safe to update from DGIndex 1.4b17 to the final version?
Is the DGIndex output and commandline options changed in any way between those versions?

[Guest]

Hate to be picky, but I've never heard of DGIndex 1.4b17.

EDIT: Please see the followup post below.

[3ngel]

There is a problem with the Main .m2ts file of "Chronos" BluRay.
DgIndex says "Could not find PAT/PMT tables!"
TsRemux detects them just fine.

[Guest]

Hate to be picky, but I've never heard of DGIndex 1.4b17. I guess you mean 1.4.9b17. If so, it should be safe. Here are the changes between b17 and final:

* The reporting of matrix coefficients was off by one GOP so if they changed, one GOP would be reported wrongly. Fixed.

* Multiple __vid__ and __aud__ per line are now supported.

* Audio-only demuxing of LPCM audio was fixed.

* Making a range that cuts from the start failed for some program streams. Fixed.

* Added support for demuxing LPCM from M2TS (Blu-Ray) files. Note that the raw PCM is demuxed (same as xport.exe). You must use an audio processor, such as sox.exe, to repackage it as you want it (typically as a WAV file). Refer to the DGIndex Users Manual for instructions in that regard (Audio/Output Method section). PID detection and the Info dialog are supported for this new audio type. Thanks to drmpeg for showing the way with xport.exe.

* Added a warning pop-up to notify the user that a field order transition was detected.

* Added the __del__ keyword for Avisynth templates for generating the audio delay in DelayAudio(__del__).

[Guest]

There is a problem with the Main .m2ts file of "Chronos" BluRay.
DgIndex says "Could not find PAT/PMT tables!"
TsRemux detects them just fine. May I please get a transport stream fragment so that I can reproduce the problem? Thank you.

[3ngel]

How do i cut a piece from an .m2ts?

[Guest]

Open the file in VirtualDub's hex editor (Tools).

Then do Edit/Truncate file. Set an address of 0x1800000 to give me about 25Meg from the start of the file.

WARNING: Do it on a copy of the original file!

[3ngel]

Done it.
Where i upload it?

[Guest]

Megaupload.com

Then post the link they give you.

Thank you for taking the trouble to help improve DGMPGDec!