View Full Version : DGMPGDec 1.4.9 Final
Pages :
1
2
[
3]
4
5
6
7
8
9
Guest
31st December 2006, 17:33
I just noticed a previous post, and wanted to say that WAV supports 6-channels, so it is possible to output 5.1 in WAV format. I've made 5.1 WAVs with BeSweet before, and they play just fine. Please read the user manual to learn what is possible with DGIndex. I don't have any plans to enhance the audio support.
Guest
31st December 2006, 17:36
It looks like the preview-field isnt exactly shure it's interlaced or not; The indicator keeps switching between interlaced/progressive. This has been discussed to death. You need to read the DGIndex user manual.
During this time the FILM-oercentage is slowly lowering; It started with 100% film, but the percentage is slowly gowing down. And to top this off, the frame structure remains at "FRAME" all the time, even when the indicator sais its interlaced. See above.
My guess is that the indicator hovers between approx. 80% progressive / 20% interlaced in some places and 90 / 10 in others, and approx 75% FILM.
What settings do i use now ? Did you read the user manual?
Twisted Ladder
5th January 2007, 17:36
Can I make a request? When using "__aud__" in the template script, it chooses the file name of the last audio track rather than the first. So when using Demux All Tracks, it will pick the commentary or a foreign language instead of the main audio. You may just ask why I don't set it to Demux Tracks and only demux Track 1, but some DVDs do not have any audio in Track 1 and will instead use a different track to store the audio.
mvdzwaan
5th January 2007, 17:41
I already got one wish realised but I got another one.
'Choose other avs template' should default to the avisynth plugin dir (or the dir where dgindex is started from)...
please :)
Guest
5th January 2007, 18:42
I have implemented and tested both the suggestions, for which thank you: 1) use first audio track encountered for __aud__, and 2) default AVS template to "template.avs" in the DGIndex executable directory. Next beta is coming soon.
Zarxrax
5th January 2007, 21:17
I think I have encountered something that can only be a bug. I can confirm this with both the latest beta and the older 1.4.8, with two different dvds I tried (both of the same tv series).
It has to do with the "use full paths" option. If I turn it off, the d2v files generated will simply not work. If I try to load the d2v file back into dgindex, the window will stay the default size and nothing will appear in it. However, dgindex will use 100% cpu and the progress marker will move very slowly until it reaches the end. When it finally reaches the end, DGIndex will crash.
At first I thought maybe this was because I saved the d2v files to a different folder than the vobs, but I also tried saving into the same folder that the vobs are in, and the problem still occurs. I don't really need to use relative paths though so its not a big deal for me.
Guest
5th January 2007, 23:02
@Zarxrax
Bug confirmed, fixed, and tested. It will be included in the next beta. Thank you for pointing it out.
Guest
6th January 2007, 06:50
http://neuron2.net/dgmpgdec/dgmpgdec149b8.zip
* The __aud__ variable in the AVS template now uses the first audio track found instead of the last.
* 204-byte transport packets are now supported.
* The info dialog now includes a stream type field.
* An error popup now appears if frame repeats are encountered (only field repeats are currently supported).
* If an exception occurs during processing, a message box pops up and allows the user to choose to continue or to abort.
* The D2V file version is bumped to 15.
* The AVS template path now defaults to a file called "template.avs" in the same directory as DGIndex.exe.
* Fixed a bug in INI file loading that caused some parameters to be read incorrectly.
* An error popup now appears if the user attempts to execute "Demux Audio Only" when the audio method is set to "Decode AC3 Track to WAV".
* Fixed a bug in relative path handling that crashed DGIndex when "Load Project" was performed.
Twisted Ladder
6th January 2007, 18:22
DGIndex seems to be generating corrupted AC3 streams now...
1.4.8: http://www.evilshare.com/04311004-eef8-1029-b2ec-00a0c993e9d6
1.4.9 Beta 8: http://www.evilshare.com/8b57bea0-eefa-1029-b2ec-00a0c993e9d6
SeeMoreDigital
6th January 2007, 18:33
DGIndex seems to be generating corrupted AC3 streams now...I've just used 1.4.9 Beta 8 to de-mux the streams from a couple of .TS and .VOB sources.... The AC3 streams work fine here!
EDIT: By-the-way....
Seeing as though the following "Save Project and Demux Video" option....
http://img156.imageshack.us/img156/4776/dgindexju8.png
....is able to de-mux more than "save" .d2v, .avs and video streams. Would not a different expression be more appropriate?
Cheers
Guest
6th January 2007, 19:15
DGIndex seems to be generating corrupted AC3 streams now...
1.4.8: http://www.evilshare.com/04311004-eef8-1029-b2ec-00a0c993e9d6
1.4.9 Beta 8: http://www.evilshare.com/8b57bea0-eefa-1029-b2ec-00a0c993e9d6
Seeing the demuxed files doesn't help me. I would really appreciate it if you could supply the source file. I also need your settings in DGIndex.
What kind of source stream is it? Are you sure it has no errors?
Guest
6th January 2007, 19:17
Would not a different expression be more appropriate? That function is just Save Project *plus* demuxing of the video. Now, if you wanted to argue about the naming of "Save Project" then you might have a point.
MacAddict
6th January 2007, 20:07
I'm having a strange issue with Beta 8 here as well. Just ripped a disc using my normal RipIt4Me method and then I attempted to index it. I'm getting an error about half way through saying "Too many pictures per GOP(>500). Now beta 7 and beta 3 do not give me this error. Seems something changed here...I'll investigate a bit further.
Twisted Ladder
6th January 2007, 22:43
http://www.evilshare.com/19ea116c-ef1f-1029-b2ec-00a0c993e9d6
Using the default settings, 1.4.8 and 1.4.9b7 demux a 3.38 MB AC3 file, while 1.4.9b8 demuxes a 3.36 MB AC3 that plays in super-fast-forward mode.
Guest
7th January 2007, 01:41
Thank you very much, Twisted. I'll look at that right away.
MacAddict, you're next, although I suspect it's probably the same problem.
Guest
7th January 2007, 03:43
Silly me. Try this fixed version:
http://neuron2.net/dgmpgdec/dgmpgdec149b9.zip
MacAddict
7th January 2007, 16:34
Donald,
Happy to report that beta 9 indexed my 'offending' movie properly. Many thanks for the quick fix and Happy New Year.
Edit- It seems GordianKnot has problems opening up d2v file from beta 9. Not always but 2 out of 4 I tried this evening causes Gknot to error and then crash with a memory reference. Anyone else had this problem? I'm back to beta 7 now and things are back to normal.
d'Oursse
9th January 2007, 07:34
That function is just Save Project *plus* demuxing of the video. Now, if you wanted to argue about the naming of "Save Project" then you might have a point.
As the demux audio feature is in the audio submenu, wouldn't it be more logical to put the "demux video" feature be in the video submenu ?
Guest
9th January 2007, 22:46
Edit- It seems GordianKnot has problems opening up d2v file from beta 9. Not always but 2 out of 4 I tried this evening causes Gknot to error and then crash with a memory reference. Anyone else had this problem? I'm back to beta 7 now and things are back to normal. The D2V file format was changed. I am not familiar with GKnot but I guess that it has to be modified to work with the new format.
Guest
9th January 2007, 22:47
As the demux audio feature is in the audio submenu, wouldn't it be more logical to put the "demux video" feature be in the video submenu ? It's an augmentation of Save Project, so I don't want to decouple them.
d'Oursse
10th January 2007, 18:18
and what about a check box in the save window ?
guada2
14th January 2007, 00:00
Hello neuron2,
I have some questions about the last DGMPGDec 1.4.9 Beta 9:
- .d2v and .d2v.bad I don't see the real different.(size is the same)
- say me what sotfware support this extension (.d2v.bad)
- i saw the post of TIMA:
http://forum.doom9.org/showthread.php?t=116841&page=5,
What do yo think about this:
D2V Fix Output
Field order transition: 2 -> 0
900 5 0 45211648 1 1 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
900 5 0 45713408 1 2 90 b0 a0 b0 a0 b0 a0 b0 a0 b0 a0 b0 a0
corrected...
900 5 0 45211648 1 1 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a3
900 5 0 45713408 1 2 90 b0 a0 b0 a0 b0 a0 b0 a0 b0 a0 b0 a0
Field order transition: 0 -> 2
900 5 1 269264896 1 5 90 b0 a0 b0 a0 b0 a0
900 5 1 269561856 1 6 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
corrected...
900 5 1 269264896 1 5 90 b0 a0 b0 a0 b0 a1
900 5 1 269561856 1 6 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
:thanks:
Guest
14th January 2007, 00:52
- .d2v and .d2v.bad I don't see the real different.(size is the same) The D2V Fix Output shows you exactly what was changed. If you read the reference manual for DGIndex, you will find an explanation of the D2V file format, which will allow you to interpret the D2V Fix Output.
- say me what sotfware support this extension (.d2v.bad) The manual explains the significance of this file.
- i saw the post of TIMA:
http://forum.doom9.org/showthread.php?t=116841&page=5 This link leads nowhere. What is your point?
What do you think about this I think you encountered two field order transitions, which were corrected.
guada2
14th January 2007, 11:15
Thank you very much for your explanations.
I should read the manual. ;)
To soon,I hope.
baserc
14th January 2007, 12:33
Many thanks
Sharro
15th January 2007, 22:57
Hi Everybody.
Thanks neuron2!! :-)
After 1 year without any encode I'm back!
I was preparing d2v's with beta 9 for a couple of dvd's I wanted to encode to XVID and on 1 of them I got "field order corrected".
To kill my curiosity I played both file's avs on mpc and the .bad looked perfect while the .d2v had jagged lines as if it was interlaced even though all dvd's are PAL progressive.
Unfortunately I had already encoded the dvd's before I tried this, so I decided to look more carefully at the encode and in the scenes with more motion if step frame by frame I get the feeling that I'm looking at a PAL deinterlaced encode (ghosting effect).
My knowledge about DGindex is scarce as I'm on pal region so ... but... is there anything to worry about it and is this information that you need more details about?
Sorry if this as been answered on any other post, believe me I did a search and sorry for my lame explanation of what I see but I miss all the technical jargons.
All the best,
Sharro
Guest
15th January 2007, 23:33
To kill my curiosity I played both file's avs on mpc and the .bad looked perfect while the .d2v had jagged lines as if it was interlaced even though all dvd's are PAL progressive. It's highly strange to think that this check could be triggered by a progressive PAL DVD, which presumably would not have RFF flags.
is this information that you need more details about? Yes! At a minimum post both the D2V files. Better yet, post an unprocessed source fragment that I can use to duplicate your issue.
Sharro
16th January 2007, 00:19
...Yes! At a minimum post both the D2V files. Better yet, post an unprocessed source fragment that I can use to duplicate your issue.
I've attached both d2v's, a Prt Scr jpg and fix.txt .
The problem must be within the beggining of the first vob.
I also tried the last vob of the dvd and a small part from the middle of the first vob extracted with chopperxp didn't gave the error... still ... the part from the right beggining of the first vob...BINGO...error
I've sent you the link through PM, download it quickly as I can't keep it there for long.
FYI it also happened with Beta 8
Hope it helps.
All the best,
Sharro
Guest
16th January 2007, 00:59
You PM'ed link is dead. Please use a reliable upload site, such as MegaUpload.
Sharro
16th January 2007, 01:08
Not dead...but looks like it's dying.
http://www.megaupload.com/?d=S9EB8MHY
All the best,
Sharro
Guest
16th January 2007, 05:27
It's a pathological video. Because the entire clip (and presumably the whole movie) is progressive, you can ignore field order entirely, and just use the uncorrected D2V file.
The correction introduces a one field phase shift, so if you want to use the "corrected" D2V, you'll need (for example) Telecide(post=0) to align the fields.
For non-progressive video, where the correction would be important to have, the one-field phase shift is insignificant.
I hope that is clear enough for you to understand what is happening. I wish it were simpler but DGIndex wants to produce a clip with a single field order when you set that option, and he doesn't know that the actual content is progressive.
Sharro
16th January 2007, 09:52
Neuron2,
Thanks for your reply.
Quote:
"It's highly strange to think that this check could be triggered by a progressive PAL DVD, which presumably would not have RFF flags."
But if Dgindex detects the pal stream couldn't you make it avoid the field order correction ?
All the best,
Sharro
Guest
16th January 2007, 15:13
No, because the stream might not be progressive. And no, DGIndex cannot rely on the pogressive frame flag as it often lies.
Sharro
16th January 2007, 15:54
One last suggestion and I'll STFU!! :-)
To avoid confusing the users maybe the "field order corrected" message should mention something about these pathological pal videos.
All the best,
Sharro
Guest
17th January 2007, 08:26
* Revised the track selection interface to be more user friendly.
* Added preliminary support for frame repeats. These are increasingly being found in 720P streams. Now you can process these videos through DGDecode/Avisynth with proper audio/video sync.
http://neuron2.net/dgmpgdec/dgmpgdec149b10.zip
G_M_C
17th January 2007, 18:26
Just installed the new b10 over b8. But it seems it has a bug; When i open a m2v with the new beta dgindex freezes completely, i have to kill it thrue the taskmanager to get some control back over my system.
Extra info: Dual xeon, only flashfxp was running at the time.
Guest
17th January 2007, 18:44
I cannot duplicate that. Does it happen with all M2Vs? Please provide a failing stream to allow me to reproduce your problem.
G_M_C
17th January 2007, 19:04
I cannot duplicate that. Does it happen with all M2Vs? Please provide a failing stream to allow me to reproduce your problem.
K, ill look into this later on, when i can close flashfxp and are able to restart/reboot.
Mug Funky
18th January 2007, 00:49
@ Sharro and Neuron2:
FWIW, often small bits of black are used to allow end chapters to be put into features. this allows you to skip the credits (the minimum chapter length is 15 frames, and you need a chapter at the end to have an end action).
these bits of black can quite easily be in a different field-order to the main feature...
also they can be used to put space between different parts of a program or different episodes, etc.
i'm not sure if this would cause the issue you're having though.
G_M_C
18th January 2007, 11:44
I cannot duplicate that. Does it happen with all M2Vs? Please provide a failing stream to allow me to reproduce your problem.
I've done a reboot and installed the b10 in a totally clean directory/environment, and the troubles seem to have gone.
I'm gonna try to replicate the "old situation" later on, to see if i can find out when in actually locked up (i seem to remember the auto-defrag service was doing its thing even that might have had an influence). If i find out why/when/how it happened, i'll report back. In the mean time: Thx for all the efforts you put into this programm :)
Guest
19th January 2007, 03:56
This version now correctly renders the video within DGIndex for streams with frame repeats. Also, Field Operation=Raw is now supported for such streams.
http://neuron2.net/dgmpgdec/dgmpgdec149b11.zip
EDIT: This beta is withdrawn.
SeeMoreDigital
19th January 2007, 13:00
Hi Don,
As you may already know there's a few people over in this thread (http://forum.doom9.org/showthread.php?t=120652) experimenting with .EVO file sources.
Anyway, yesterday I thought I'd see how well DGIndex would react with .EVO files containing MPEG-2 video and DolbyDigital+ audio. Sufficed to say there was no problem accessing and de-muxing the MPEG-2 video stream. Not surprisingly though, the audio stream was not detected.
May I ask whether you have any interest in providing support for these new audio stream formats?
Cheers
PuppZ
19th January 2007, 13:31
Hi!
The new beta11 behaves strangely.
I use the script below:
mpeg2source("tenchi01.d2v")
TFM(d2v = "tenchi01.d2v") ---> latest TIVTC 1.0 final
UnBlend()
TDecimate(mode = 1)
hqdn3d(2,1.5,6,4.5)
According to DGIndex the source is 95,58% Film 29.97fps interlaced, Frame Struct: Frame. Maybe soft telecined? I set Field Operation to Honor Pulldown Flags, because using Ignore Pulldown without TFM+TDecimate gives the decimated frame count on 29.97fps (video runs faster) and Force Film gives correct frame count at a correct frame rate but leaves some blended frames even after UnBlend. There's no any other option in Field Operation. With Beta10 everything is fine. With Beta11 I get the following TFM error: d2v frame count does not match filter frame count (51843 vs 71841)! With the latest DGIndex in Honor Pulldown Flags mode I get abnormally higher frame count.
Guest
19th January 2007, 14:59
May I ask whether you have any interest in providing support for these new audio stream formats? What's an EVO and where do they come from? What are the audio specs? I don't have time to search through that long thread. Can you point me to a sample clip?
Guest
19th January 2007, 15:03
The new beta11 behaves strangely.
You'll have to demonstrate a problem with just my filters. Remove everything after mpeg2source() and then serve into VirtualDub and get the frame count. Are you claiming that it is different for beta 10 and beta 11? Also compare the D2V files in the two cases. Are they different? You may want to contact tritical about this if you can't demonstrate an issue with just DGIndex/DGDecode.
EDIT: OK, I duplicated the issue. Beta 11 is withdrawn. I'll release beta 12 tonight. Thank you for pointing this out.
SeeMoreDigital
19th January 2007, 15:23
What's an EVO and where do they come from? What are the audio specs? I don't have time to search through that long thread. Can you point me to a sample clip?EVO is the designated container for the HD-DVD format.
It's very flexible and capable of storing the following (EOE): -
Audio formats
LPCM (up-to 7.1)
Dolby Digital, Dolby Digital EX, Dolby Digital Plus
DTS, DTS-ES, DTS-EX
MP2 (MPEG-1 Layer-2)
Dolby TrueHD (Lossless)
DTS-HD Base Stream (Lossless)
DTS-HD Extended Stream (Lossless)
MLP (Meridian Lossless Packing)
Video Formats
MPEG-2 Part-2 (High-Def and Std-Def)
MPEG-4 Part-10 (aka: AVC)
VC-1
Drevil_xxl has provided some samples here: -
ftp://mplayerhq.hu/MPlayer/samples/evob/
DELSCENE1.EVO and DELSCENE7.EVO samples appear to contain 720x480 MPEG-2 video and Dolby Digital Plus (http://en.wikipedia.org/wiki/Dolby_Digital_Plus) audio.
Cheers
Guest
19th January 2007, 15:31
How are the decrypted files being obtained? Where are the specs for the EVO container format?
SeeMoreDigital
19th January 2007, 15:40
How are the decrypted files being obtained? Where are the specs for the EVO container format?Sorry Don... I can't help you with either of these questions.... I'm useless aren't I?
Guest
19th January 2007, 15:44
One day when the HDDVD-BD war is over I'll buy an HD player and maybe then I'll be motivated to work in this area. Anyway, it looks like they have working demuxing methods.
Guest
19th January 2007, 15:52
The new beta11 behaves strangely. Yes, I have now duplicated it. Beta 11 is withdrawn. Standby for the fixed version.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.