Log in

View Full Version : DGMPGDec 1.2.0 RC5


Pages : [1] 2 3

Guest
5th February 2005, 20:34
Here is what I'd like to release as 1.2.0. I removed video demuxing as it is not ready for prime time. This version adds more accurate delay calculation for cuts, and debug info and hinting. The current Info data can be output via OutputDebugString() and the hinting currently includes progressive/interlaced and colorimetry. Please refer to the Changes text file.

http://neuron2.net/fixd2v/dgmpgdec120rc5.zip

Dark-Cracker
5th February 2005, 22:38
thank u for your hard work :)

just by curiosity does the CLI still have some limitation if the path have some *illegal* character ? (like the "," or "[" ).

Bye.

len0x
5th February 2005, 22:42
Originally posted by Dark-Cracker

just by curiosity does the CLI still have some limitation if the path have some *illegal* character ? (like the "," or "[" ).


Yes, it does. But now input files can be loaded from a text file that has a list of files to be loaded.


@Neuron2

Great stuff! info=2 works as expected. I wonder what are the exact values that can be produces by colorimetry info?

Dark-Cracker
5th February 2005, 23:02
thank u for the quick answer :)

++

Guest
5th February 2005, 23:21
Originally posted by len0x
I wonder what are the exact values that can be produced by colorimetry info? I'm too busy to type it. Please see table 6-9 of ISO 31818-2 (on my web site).

len0x
5th February 2005, 23:32
That's exactly what I needed, thanks. (Now I understand what numbers mean - I knew that there are five types of matrix coefficients, but didn't know 3 was a reserved number).

shpitz
6th February 2005, 03:39
neuron2,

awesome work you're doing m8.

i was wondering if you can make dgindex autoload split mpg files as well, just like dvd2avi does.

i think that would be an awesome feature.

thanks

Guest
6th February 2005, 03:50
Originally posted by shpitz
i was wondering if you can make dgindex autoload split mpg files as well, just like dvd2avi does. Don't know what you are talking about, sorry.

If you mean autoincrement, I replaced it with multiple selection and auto sorting. Just highlight all the files in the open dialog, or drag and drop the whole lot. Autoincrement worked only for limited patterns; if yours matched you were lucky, otherwise you whined. Now nobody can whine. :D

Edit: Credit goes to Cyberia for proposing/designing the new scheme. I get credit for finding the sorting algorithm in an obscure GNU function.

shpitz
6th February 2005, 04:00
auto selection is a great solution,

thanks a lot m8, awesome job !!!

makes life sooooooooooooo much easier now hehe

Guest
6th February 2005, 08:38
Darn, I just noticed that I broke the Info screen. I also found that the Second_Field variable is not initialized! So field structure clips will work or not work depending on what random value it takes.

I'll try to fix these and make an RC2 later today (Sunday).

alfixdvd
6th February 2005, 13:04
From versions 1.2.0.b5 to 1.2.0.RC1, I can play any movies from avs scripts, if the movie is Bottom Field First

Either Windows Mediaplayer or MediaPlayer classic, don't show anything, only a black window, neither the length of the movie at the status bar

With Top Field First any problem

With version 1.0.12 all's right.

The avs script is :

LoadPlugin("C:\dvdtools\DgDecode\\DGDecode.dll")
MPEG2Source("VTS_01_1.d2v",idct=5)
ConvertToYUY2

What's the problem ?

Best regards
alfixdvd

Guest
6th February 2005, 21:09
Tell me more. Is it an elementary stream, a VOB, or a transport stream?

Better yet, place a small part of the source MPEG on my ftp site and then notify me! A hundred MEG is OK.

ftp.neuron2.net
user: guest@neuron2.net (enter it just like that)
pwd: guest

I just tried a TFF VOB with 1.2.0 RC2 (see link at top of this thread) and it was fine. I really need the file that fails. Thank you.

Cyberia
7th February 2005, 01:52
Bug Report on RC2
-----------------

Info Panel issues

1) several relevant fields on the info panel are not populated when advancing through the slider/buttons.

2) Frame Size and Profile take two frame advance clicks to populate on the Info panel.

3) If the Play is stopped when 'Info' field indicates 'video error 1' the error cannot be cleared by sliding/advancing frames or by loading a new vob(!) Only clicking Play again clears the error.


New Items

1) Could the various time fields display tenths of seconds?

2) Could the Info panel appear when sliding/advancing frames, not just if Play/Preview are used? Alternatively, you could provide an item under Options to toggle the Info panel.

Backwoods
7th February 2005, 03:29
DGIndex locks up on me when I try to save a D2V from a M2T I loaded. The M2T is from the Sony HDR-FX1 camera. When I first loaded the file the PIDs were auto-detected and the GOP caution box came up, but trying to load the file again, the PIDs were not detected.

Guest
7th February 2005, 04:44
Tell me the DGIndex version and put the file on my ftp server. That's the only way I can help you. Try setting both the PIDs to 2 before loading the file.

ATM
7th February 2005, 04:45
Been trying to use info=1 in mpeg2source to see what the colorimetry info is so I can decide if I need to use colormatrix or not but I'm having some weird problems. If I load the script with just a line like mpeg2source("thing.d2v",info=1) it either crashes VDubMod or just hangs it up, but if i play the script in mpc it will either 50% of the time work and I can see the info or it will just hang up as well. Is there just something I am doing wrong?

Guest
7th February 2005, 04:48
All I can say is what I just told the previous poster.

Tell me the version and put a file on my server!

ATM
7th February 2005, 04:52
I thought I was using RC2, but I was using RC1. I just changed to RC2 and the problem is solved and loads just fine now. So never mind. :)

Guest
7th February 2005, 04:57
Thanks for the update. I'll sleep better tonight. I pulled a 36-hour straight programming session to make RC2 and I still haven't slept yet after 48 hours. :)

clone83
7th February 2005, 05:29
@ neuron2: can u plz add the save project and demux video back to the newer versions cause i found i was getting much better vids from it when i encode it later on.....?

Guest
7th February 2005, 05:35
It'll come back when I get the bugs out. I don't like to release buggy stuff if I can avoid it.

Having said that, why do you think the quality is better with demuxed video compared to frame-served video? I can't think of any reason for that to be true.

clone83
7th February 2005, 05:42
im not sure why it is like that but it is....

Guest
7th February 2005, 05:56
Well, can you at least tell me what the two processes are that cause the noticeable difference.

clone83
7th February 2005, 06:00
all i do is demux the vid and then work on it in vdm with some filters and then i mux the audio.

p.s im always interested in new way of encoding if u have any suggestions....? and do u have msn cause i would like to talk to you in private about some deals that i could possibly offer you....?

Guest
7th February 2005, 06:10
There's no difference between demuxing and opening in VDubMod versus using DGDecode to serve via the D2V file. Except that VDubMod does not honor pulldown flags and so is technically an incorrect decoder. And of course DGDecode allows you to use Avisynth scripting before sending the video to VDub. You may be getting the "poor man's IVTC" effect.

Please describe the quality difference that you observe.

You can PM me with any deals you have in mind. Thank you.

Cyberia
7th February 2005, 06:11
Originally posted by neuron2
Thanks for the update. I'll sleep better tonight. I pulled a 36-hour straight programming session to make RC2 and I still haven't slept yet after 48 hours. :)

Oh My God! Thats dedication. Much appreciated.

Let's all give neuron2 a Thank You!

clone83
7th February 2005, 07:48
Thank You Neuron2 and i will get around to sending u a pm asap....

Leak
7th February 2005, 08:02
Originally posted by neuron2
Thanks for the update. I'll sleep better tonight. I pulled a 36-hour straight programming session to make RC2 and I still haven't slept yet after 48 hours. :)

Dude! Off to bed! NOW! :eek:

If I tried to pull that off, I could stay at the hospital instead of working there...

alfixdvd
7th February 2005, 08:10
Excuse me neuron2, I want to say :" I can't play any movies from avs scripts, if the movie is Bottom Field First.

This night, I send you two mpeg BFF.

best regards
alfixdvd

Backwoods
7th February 2005, 10:16
Originally posted by neuron2
Tell me the DGIndex version and put the file on my ftp server. That's the only way I can help you. Try setting both the PIDs to 2 before loading the file.

Both were set to 2 and it still would freeze. I'm using DGIndex 1.2.0 RC2.

If I run the M2T through HDTV2MPEG the resulting MPG2 file saves and demuxes fine in DGIndex 1.2.0 RC2. I'll upload a snippet of the M2T for you tomorrow.

len0x
7th February 2005, 12:31
Wow, D2V structure changed drastically! Quick question: previously 2,3,12,13 values meant TFF, what's the equivalent now?

Guest
7th February 2005, 14:57
@alfixdvd & Backwoods

Standing by for the failing streams...

@len0x

Please see the D2V format document included in the zip file. If the last digit is in this set { 2, 3, 6, 7, a, b, e, f }, the tff bit is set.

In the next release I'll push the frame type to the upper nibble. Then the old 0,1,2,3 will still be visible. The end marker will then be ff.

tritical
7th February 2005, 16:07
Reading the D2V_format text I am confused about the following statement:
One important issue still to be addressed is that upsampling based on this flag should be done *before* pulldown is applied. Currently it appears that it is not being done that way.
Assuming this is referring to dgdecode, unless something has changed drastically, the upsampling is done before pulldown. It is done right after post-processing and before showQ, all of which are done on the decoded pictures before they are copied out to the other storage buffers from which pulldown is performed using the copyeven/copyodd functions. Or am I missing something?

loni_blues
7th February 2005, 16:51
@neuron2

Thanks for the continuous and hard work!
And sorry but, with RC2 I cannot open the d2v file in Gordian Knot, while it still can be done with the d2v made with RC1. The d2v file seems complete, though. Is it a bug in RC2?
Regards.

len0x
7th February 2005, 16:54
Originally posted by neuron2
In the next release I'll push the frame type to the upper nibble. Then the old 0,1,2,3 will still be visible. The end marker will then be ff.

By next version you mean another RC of 1.2.0 or 1.3?

len0x
7th February 2005, 16:56
Originally posted by loni_blues

And sorry but, with RC2 I cannot open the d2v file in Gordian Knot, while it still can be done with the d2v made with RC1. The d2v file seems complete, though. Is it a bug in RC2?

I suggest that you usually ask about such problems in GK forum, where you can also find a new version of GK bundled with 1.2.0RC2.

alfixdvd
7th February 2005, 16:59
Hi neuron2.

I will not to send you any file, because with version 1.2.O RC2 all works fine.

But with versions 1.2.0.b5 to 1.2.0.RC1, I can't play any movies from avs scripts, if the movie is Bottom Field First.

What's wrong ?

best regards.
alfixdvd

Guest
7th February 2005, 17:23
Originally posted by len0x
By next version you mean another RC of 1.2.0 or 1.3? I mean the very next thing I put out, 1.2.0 RC3 or final. I already have it coded and tested.

Guest
7th February 2005, 17:26
Originally posted by tritical
Reading the D2V_format text I am confused about the following statement:

Assuming this is referring to dgdecode, unless something has changed drastically, the upsampling is done before pulldown. It is done right after post-processing and before showQ, all of which are done on the decoded pictures before they are copied out to the other storage buffers from which pulldown is performed using the copyeven/copyodd functions. Or am I missing something? You're right. I didn't actually look at the code. :)

BTW, all of the contortions you went through in making the Info screen (for re-ordering and random access) were completely finessed by letting DGIndex put flags in the D2V. When he indexes he plays through linearly and so it is much easier for him to do all that.

Guest
7th February 2005, 17:27
Originally posted by alfixdvd
Hi neuron2.

I will not to send you any file, because with version 1.2.O RC2 all works fine.

But with versions 1.2.0.b5 to 1.2.0.RC1, I can't play any movies from avs scripts, if the movie is Bottom Field First.
I wrote earlier that the Second_Field variable was not initialized. Glad RC2 is working for you!

len0x
7th February 2005, 17:30
Originally posted by neuron2
I mean the very next thing I put out, 1.2.0 RC3 or final. I already have it coded and tested.

Great, thanks!

tritical
7th February 2005, 19:43
BTW, all of the contortions you went through in making the Info screen (for re-ordering and random access) were completely finessed by letting DGIndex put flags in the D2V. When he indexes he plays through linearly and so it is much easier for him to do all that. Yep, definitely much easier. Never expected the d2v file to contain all that info, but it is very useful to have it indexed in it.

Backwoods
8th February 2005, 01:10
Originally posted by neuron2
@alfixdvd & Backwoods

Standing by for the failing streams...

I cut a piece out of the TS and that 2 second segment ran fine in your latest release then I recaptured a segment from the tape of the same scene and the file loaded and saved fine. It seems to be just this one TS I captured. If it wasn't 1 gig I would upload it to you, if you are really interested in it, I could mail it to you snail method.

Guest
8th February 2005, 01:38
@Backwood

Let's just keep an eye on things. If you have any further problems with other files, please shout. Thank you.

moonwatcher
8th February 2005, 15:26
when using DGIndex 1.0.12 this does not occure, but when using the new 1.2.0 RC2 it does.

Movie: Blade Runner
System: NTSC
Flags: Force Film
CPU: Pentium 4 Prescott 3.2GHz 478pin
AVIsynth: 2.55 build: Sep 1 2004

AVS:

LoadPlugin("DGDecode.dll")
clip = mpeg2source("br.d2v")
return clip

i generate the d2v project file, i use a simple avisynth script and i get an Evaluate: Unrecognized exception! on line 2.

again, exactly the same does not occure with 1.0.12

Lior.

Guest
8th February 2005, 15:36
Are you absolutely sure that you used 1.2.0RC2 for both DGIndex and DGDecode? If so, please provide a small clip that shows the problem. My ftp server is given in this thread. Also post the first 20 or so lines of the failing D2V file. Thank you.

moonwatcher
8th February 2005, 15:55
DGIndexProjectFile07
1
61 T:\DVD Content\BLADE_RUNNER_16X9\VIDEO_TS\VTS_01_PGC_01_1.VOB

Stream_Type=1
iDCT_Algorithm=5 (1:MMX 2:SSEMMX 3:FPU 4:REF 5:SSE2MMX)
YUVRGB_Scale=1 (0:TVScale 1:PCScale)
Luminance_Filter=0,0 (Gamma, Offset)
Clipping=0,0,0,0 (ClipLeft, ClipRight, ClipTop, ClipBottom)
Aspect_Ratio=16:9
Picture_Size=720x480
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)
Frame_Rate=23976
Location=0,0,0,7FF79

c00 1 0 2048 2 1 3f 3c 35 3e 3f 38 3d 3e 3b 3c 3d 3a
800 1 0 20480 2 1 1f 1c 35 3e 3f 38 3d 3e 3b 3c 3d 3a
800 1 0 36864 2 1 1f 1c 35 3e 3f 38 3d 3e 3b 3c 3d 3a
800 1 0 53248 2 1 1f 1c 35 3e 3f 38 3d 3e 3b 3c 3d 3a
800 1 0 69632 2 1 1f 1c 35 3e 3e 3b 3c 3d 3a 3f 3c 39
800 1 0 382976 2 1 1e 1f 34 3d 3e 3b 3c 3d 3a 3f 3c 39
800 1 0 915456 2 1 1e 1f 34 3d 3e 3b 3c 3d 3a 3f 3c 39
800 1 0 1404928 2 1 1e 1f 34 3d 3e 3b 3c 3d 3a 3f 3c 39
800 1 0 1894400 2 1 1e 1f 34 3d 3e 3b 3c 3d 3a 3f 3c 39
800 1 0 2379776 2 1 1e 1f 34 3d 3e 3b 3c 3d 3a 3f 3c 39

just for the record:
when trying to mix-and-match 1.0.12 and 1.2.0RC2 i got resonable errors: "MPEG2Source: couldn't open source file, or absolete D2V file"

about the upload: do you want a part of the VOB file?

is it possibly machine specific, ie something to do with the prescott CPU?

Guest
8th February 2005, 15:58
Yes, I need a clip that I can use to make the problem happen. Up to several hundred Meg is fine. Be sure that the problem happens with the cut clip.

No I doubt it's machine specific.

moonwatcher
8th February 2005, 16:17
checked with a diffrent PAL stream (no force film) and it works fine.
checked with the last vob (78mb):
when opened with DGIndex i get the followi8ng message:

WARNING! Opening GOP is not closed.
The first few frames may not be decoded correctly.

(i guess because its not the first VOB)

but the same problem occures, is it enough to upload this, i am not sure how to cut properly one of the VOBs (which are 1024mb naturally), if its not good then ill cut you the first two hundered MB from the first VOB.

Guest
8th February 2005, 16:21
Yes, any VOB is fine if it makes the problem occur! Cut away the end of the VOB leaving the beginning intact. Test that the problem occurs with the truncated VOB. Then upload it. Thank you.

Do you know how to truncate a file? One way is VOBSplit on the Doom9 full download page.