DGMPGDec 1.4.6 Final

neuron2 · 10th October 2005, 16:47

Here is 1.4.6 Final.

http://neuron2.net/dgmpgdec/dgmpgdec146.zip

1. Fixed a bug in indexing for some field structure streams.

2. The 'This I picture starts a new GOP' flag in the D2V file was not being
set correctly. This flag is not used by DGDecode, so the impact was only to
the diagnostics produced by Parse D2V.

3. The D2V file format version number was bumped to 12. (This should have
been done for version 1.4.5; better late than never.)

4. Fixed a problem in DGDecode that could cause a lockup when navigating
on the timeline with some unusual field structure streams.

5. Increased the maximum number of input files from 256 to 512.

6. Incorporated fix to DGVfapi (by 'tritical') that prevents a failure when
a large number of VFAPI-served files are opened at once.

7. Changed DGIndex/DGDecode so that when DGDecode sets the frame rate
in Avisynth, it uses the exact fractional representation for
fps_numerator/fps_denominator (changes by 'tritical').

This way, e.g., NTSC clips get the exact 24000/1001, 30000/1001, or
60000/1001 rate instead of 23.976, 29.970, or 59.94.

DGIndex was actually getting the framerate correct, but when it wrote the
d2v file, it would multiply the floating point value up by 1000 and then save
it. Then DGDecode would use that value for the numerator and 1000 for the
denominator. Now, when DGIndex gets the fps value from the lookup table it
also gets numerator/denominator values from a lookup table. Then in the d2v
file it writes, e.g.:

Frame_Rate=29970 (30000/1001)

with numerator and denominator in parentheses. DGDecode then uses those
values when setting the frame rate in Avisynth.

This change bumps the D2V file format version number to 13.

8. The message box that pops up for transport streams when no data is
found has been clarified to direct the user to use the Stream menu to set
the PIDs.

9. Fixed a hang when the CLI -HIDE option is used and the input file cannot
be opened.

10. The video overlay is now not claimed when the -HIDE or -MINIMIZE CLI
options are used.

11. File version properties were added for DGIndex, DGDecode, and DGVfapi.
If you right click on the EXE, DLL, or VFP files and select properties, you can
now obtain file version information.

12. The DGIndex Information dialog now shows an overall average bitrate for
the entire previewed video in addition to the windowed value. The windowed
value now reports every 32 frames instead of every 64 frames.

13. DGVfapi's handling of audio from avisynth scripts was fixed. It didn't set
values for dwBlockAlign and dwReadedSampleCount, and it should be
converting the output to 16-bit integer if it isn't already in that format.
Changes by 'tritical'.

14. The old "Fix D2V" tool is back in a new guise: the "Correct Field Order"
option. Refer to the manual for details.

15. Fixed the truncation of the last few bytes of demuxed M2V files.

16. Fixed a problem that limited the number of files that could be opened at
once from the File Open Dialog (drag-and-drop to the DGIndex window was
OK). It should now be possible to open up to 512 files at once via the open
dialog.

richardlfyang · 11th October 2005, 03:59

Tks! I'll try it!

AllTimeSToneD · 13th October 2005, 14:02

It seems like i discovered accidently a bug (or a limitation)?

If i try to open 314 transport stream files each 100mb in size DGIndex gives me a error window and crashed once clicked OK or Cancel.

Something about "0x00418e82 ..... Memory 0x00000000"

I could post a screenshot of the error window but that probably wouldn't help much as my WinXP is on german. I've tried to limit the number of files to 256 files and it worked. So it looks to me like a limitation of max 256 files.

Is that one fix-able? I would like to be able to open all the files at once.

Btw the bug/limitation exists on both (using drag and drop and open file/add).

neuron2 · 13th October 2005, 14:41

MAX_FILE_NUMBER is currently 256, as you suggest. I will bump it to 512 in the next beta. Will that be enough? What is your application scenario that causes such a situation?

AllTimeSToneD · 13th October 2005, 18:16

Quote:

Originally Posted by neuron2

Will that be enough?

Yes probably yes

Quote:

Originally Posted by neuron2

What is your application scenario that causes such a situation?

Capping a European HD stream of RotK while the streaming software splits the incoming stream in 100MB chunks. That would result as you can already guess in a few hundred ts files.

pbkg · 14th October 2005, 13:38

Is there any difference between the processing of PAL and NTSC in the program? If not then I guess you could ignore this, but otherwise, there may be a problem...

Why? Looking through the source code of previous versions, it seems that unless framerate == 25 fps, then the preview gives the video type as NTSC when it should be PAL. But, the two Australian government owned broadcasters both have decided that their "High Definition" (snigger, snigger), service should be 50 fps, rather than the standard 25 fps (two of the commercial stations run their HD at 1080i PAL @ 25 fps as far as I can tell, and the other is all over the place like a dogs breakfast for me, with their "HD" service PID currently the same as the SD PID, ie the same video, but different audio....). As far as I can tell, this is part of the digital standard (50fps via PAL @ 720x576), but it could catch people out. I would upload a copy of a file, but I would be here all night on my connection....

neuron2 · 14th October 2005, 14:06

That is only a display issue for the info dialog. Thanks for pointing it out. Maybe it's worth displaying 50fps as "PAL".

Tima · 14th October 2005, 22:33

As far as I can see, there's no explanation in help files about what 'Video %xx' in 'Video Type' means.. 'Bug'?

foxyshadis · 15th October 2005, 10:06

Quote:

Originally Posted by Tima

As far as I can see, there's no explanation in help files about what 'Video %xx' in 'Video Type' means.. 'Bug'?

http://neuron2.net/dgmpgdec/DGIndexManual.html#FieldOp

This is the same help file that comes with DGIndex. (Although you sort of have to know what you're looking for to look for this chapter.)

neuron2 · 15th October 2005, 14:19

Actually, Tima found a document bug, because I still had "FILM" vs. "NTSC", although the display now shows "Film" vs. "Video". Here are the corrected sections:

http://neuron2.net/dgmpgdec/DGIndexManual.html#FieldOp
http://neuron2.net/dgmpgdec/DGIndexManual.html#video

calinb · 18th October 2005, 23:36

I’m having trouble with HDTV .mpg files created by my Dvico Fusion5 card. Dgdecode doesn't find/demux the AC3 audio track. Dgdecode handles Fusion5 .ts files okay but, for some strange reason, my Fusion5 card creates corrupted .ts files from one QAM channel that I like to watch (PBS) so I must record to .mpg files on this channel. I found that the Windows mpeg demultiplexer DSF works great (audio + video), but the Windows splitter DSF and MPC internal parser/splitter seek very poorly. The Elecard/Moonlight DSF doesn’t work at all! The Fusion playback filters work fine, of course.

Any chance I could interest you in a sample file, Donald? Thanks much, if you have the time to take a look.

neuron2 · 18th October 2005, 23:40

Yes, sure. Upload it to my FTP and notify me of the filename. You didn't say what problem you have with DGIndex!

I am involved in another thread about this card using .mpg, in which DGIndex can't get the audio right, but gets the video fine.

Is yours the Australian or ATSC format card?

calinb · 18th October 2005, 23:46

doh! Sorry Donald, I just realized my ommision and edited my posting, but you replied before I could get it finished. Yeah, it's the audio. I'm posting to the Dvico Q/A site about the corrupted .ts files on this one cable 256 QAM channel too, but the card should create either .mpg or .ts (.tp) output files. Both output options work on all channels but this one, which requires mpg output. I have the ATSC card. Point me to the other thread and maybe I can help there too. They could try transport stream output, as an alternative.

AMED · 21st October 2005, 08:27

I have a small request with regarding saving a project file.

Could the default behaviour be changed to check the name of the parent folder and if it isn't named VIDEO_TS then use that name of the parent folder for the project name?

eg.

Code:

if parent folder name is not VIDEO_TS
   use parent folder name for naming of project when saving
else parent folder name is VIDEO_TS or files are from multiple locations
   use current naming convention
end

neuron2 · 21st October 2005, 15:07

Quote:

Originally Posted by calinb

doh! Sorry Donald, I just realized my ommision and edited my posting, but you replied before I could get it finished. Yeah, it's the audio. I'm posting to the Dvico Q/A site about the corrupted .ts files on this one cable 256 QAM channel too, but the card should create either .mpg or .ts (.tp) output files. Both output options work on all channels but this one, which requires mpg output. I have the ATSC card. Point me to the other thread and maybe I can help there too. They could try transport stream output, as an alternative.

http://forum.doom9.org/showthread.php?t=101507

It appears to be a very similar, if not identical case.

I don't see a file uploaded from you yet.

neuron2 · 21st October 2005, 15:09

Quote:

Originally Posted by AMED

Could the default behaviour be changed to check the name of the parent folder and if it isn't named VIDEO_TS then use that name of the parent folder for the project name?

Sorry, but no. Different people have different conventions for where they save project files, and if I try to implement them all, they'd conflict. Better to keep it simple and basic.

calinb · 21st October 2005, 20:15

Quote:

Originally Posted by neuron2

http://forum.doom9.org/showthread.php?t=101507

It appears to be a very similar, if not identical case.

I don't see a file uploaded from you yet.

Sorry about the delay in uploading the samples, Donald. I uploaded calinb_cap.zip to the site. I also sent the zip file to Dvico (Fusion developer). It contains an .mpg, .tp, and .m2t file.

Fusion crashes after many seconds or a few minutes with .tp capture only. The .tp files are usually corrupted. Dvico is working that issue.

The .tp and .m2t files may or may not be useful to you in getting to the bottom of this. The .m2t file was captured from the firewire port of my cable STB on the same channel. with my Apple Mac mini. Again, may or may not be related to gumballguy's and my problem. If you can make DGIndex work with the .mpg file, we could abandon other cumbersome workarounds!

Donald, please check my PM for a Dvico contact address. Again, may or may not be useful.

mg262 · 6th November 2005, 00:20

In the MPEG2Source documentation with this release, there is the following line:

0: Use value specified by DGIndex (iDCTs 6 and 7 unavailable in DGIndex)

I have no problem selecting those modes in DGIndex, and they are documented in its manual. Is it that this line has not been updated yet (which would be entirely understandable given the rate at which you update the software), or -- probably more likely -- am I misreading it completely? If the latter, I would be grateful for the correct reading...

This is a very minor point... I hope you don't mind me bringing it up.

Thanks in advance,
M.

neuron2 · 6th November 2005, 02:49

It's a document bug. Read it this way:

0: Use value specified by DGIndex

Thank you for pointing it out. It will be repaired in the next beta.

Tima · 7th November 2005, 22:13

Donald, how much is the write buffer of DGIngex for now? Could you make it configurable to o just bigger (to make user able to avoid fragmentation of files that are written during demux, when f.e. used vobs are on the same drive)?

10th October 2005, 16:47	#1 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	DGMPGDec 1.4.6 Final Here is 1.4.6 Final. http://neuron2.net/dgmpgdec/dgmpgdec146.zip 1. Fixed a bug in indexing for some field structure streams. 2. The 'This I picture starts a new GOP' flag in the D2V file was not being set correctly. This flag is not used by DGDecode, so the impact was only to the diagnostics produced by Parse D2V. 3. The D2V file format version number was bumped to 12. (This should have been done for version 1.4.5; better late than never.) 4. Fixed a problem in DGDecode that could cause a lockup when navigating on the timeline with some unusual field structure streams. 5. Increased the maximum number of input files from 256 to 512. 6. Incorporated fix to DGVfapi (by 'tritical') that prevents a failure when a large number of VFAPI-served files are opened at once. 7. Changed DGIndex/DGDecode so that when DGDecode sets the frame rate in Avisynth, it uses the exact fractional representation for fps_numerator/fps_denominator (changes by 'tritical'). This way, e.g., NTSC clips get the exact 24000/1001, 30000/1001, or 60000/1001 rate instead of 23.976, 29.970, or 59.94. DGIndex was actually getting the framerate correct, but when it wrote the d2v file, it would multiply the floating point value up by 1000 and then save it. Then DGDecode would use that value for the numerator and 1000 for the denominator. Now, when DGIndex gets the fps value from the lookup table it also gets numerator/denominator values from a lookup table. Then in the d2v file it writes, e.g.: Frame_Rate=29970 (30000/1001) with numerator and denominator in parentheses. DGDecode then uses those values when setting the frame rate in Avisynth. This change bumps the D2V file format version number to 13. 8. The message box that pops up for transport streams when no data is found has been clarified to direct the user to use the Stream menu to set the PIDs. 9. Fixed a hang when the CLI -HIDE option is used and the input file cannot be opened. 10. The video overlay is now not claimed when the -HIDE or -MINIMIZE CLI options are used. 11. File version properties were added for DGIndex, DGDecode, and DGVfapi. If you right click on the EXE, DLL, or VFP files and select properties, you can now obtain file version information. 12. The DGIndex Information dialog now shows an overall average bitrate for the entire previewed video in addition to the windowed value. The windowed value now reports every 32 frames instead of every 64 frames. 13. DGVfapi's handling of audio from avisynth scripts was fixed. It didn't set values for dwBlockAlign and dwReadedSampleCount, and it should be converting the output to 16-bit integer if it isn't already in that format. Changes by 'tritical'. 14. The old "Fix D2V" tool is back in a new guise: the "Correct Field Order" option. Refer to the manual for details. 15. Fixed the truncation of the last few bytes of demuxed M2V files. 16. Fixed a problem that limited the number of files that could be opened at once from the File Open Dialog (drag-and-drop to the DGIndex window was OK). It should now be possible to open up to 512 files at once via the open dialog. Last edited by neuron2; 4th February 2006 at 15:43.

13th October 2005, 14:41	#4 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	MAX_FILE_NUMBER is currently 256, as you suggest. I will bump it to 512 in the next beta. Will that be enough? What is your application scenario that causes such a situation? Last edited by neuron2; 13th October 2005 at 14:59.

15th October 2005, 14:19	#10 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	Actually, Tima found a document bug, because I still had "FILM" vs. "NTSC", although the display now shows "Film" vs. "Video". Here are the corrected sections: http://neuron2.net/dgmpgdec/DGIndexManual.html#FieldOp http://neuron2.net/dgmpgdec/DGIndexManual.html#video Last edited by neuron2; 15th October 2005 at 14:32.

18th October 2005, 23:36	#11 \| Link
calinb Registered User Join Date: Apr 2002 Posts: 304	I’m having trouble with HDTV .mpg files created by my Dvico Fusion5 card. Dgdecode doesn't find/demux the AC3 audio track. Dgdecode handles Fusion5 .ts files okay but, for some strange reason, my Fusion5 card creates corrupted .ts files from one QAM channel that I like to watch (PBS) so I must record to .mpg files on this channel. I found that the Windows mpeg demultiplexer DSF works great (audio + video), but the Windows splitter DSF and MPC internal parser/splitter seek very poorly. The Elecard/Moonlight DSF doesn’t work at all! The Fusion playback filters work fine, of course. Any chance I could interest you in a sample file, Donald? Thanks much, if you have the time to take a look. Last edited by calinb; 18th October 2005 at 23:42.

21st October 2005, 08:27	#14 \| Link
AMED Registered User Join Date: Sep 2004 Location: Auckland, New Zealand Posts: 125	I have a small request with regarding saving a project file. Could the default behaviour be changed to check the name of the parent folder and if it isn't named VIDEO_TS then use that name of the parent folder for the project name? eg. Code: if parent folder name is not VIDEO_TS use parent folder name for naming of project when saving else parent folder name is VIDEO_TS or files are from multiple locations use current naming convention end Last edited by AMED; 21st October 2005 at 13:17.

11th October 2005, 03:59	#2 \| Link
richardlfyang Registered User Join Date: Sep 2005 Posts: 17	Tks! I'll try it!

13th October 2005, 14:02	#3 \| Link
AllTimeSToneD HDTV Nerd Join Date: Dec 2001 Location: Beerland Posts: 63	It seems like i discovered accidently a bug (or a limitation)? If i try to open 314 transport stream files each 100mb in size DGIndex gives me a error window and crashed once clicked OK or Cancel. Something about "0x00418e82 ..... Memory 0x00000000" I could post a screenshot of the error window but that probably wouldn't help much as my WinXP is on german. I've tried to limit the number of files to 256 files and it worked. So it looks to me like a limitation of max 256 files. Is that one fix-able? I would like to be able to open all the files at once. Btw the bug/limitation exists on both (using drag and drop and open file/add).

14th October 2005, 13:38	#6 \| Link
pbkg Registered User Join Date: May 2003 Posts: 1	Is there any difference between the processing of PAL and NTSC in the program? If not then I guess you could ignore this, but otherwise, there may be a problem... Why? Looking through the source code of previous versions, it seems that unless framerate == 25 fps, then the preview gives the video type as NTSC when it should be PAL. But, the two Australian government owned broadcasters both have decided that their "High Definition" (snigger, snigger), service should be 50 fps, rather than the standard 25 fps (two of the commercial stations run their HD at 1080i PAL @ 25 fps as far as I can tell, and the other is all over the place like a dogs breakfast for me, with their "HD" service PID currently the same as the SD PID, ie the same video, but different audio....). As far as I can tell, this is part of the digital standard (50fps via PAL @ 720x576), but it could catch people out. I would upload a copy of a file, but I would be here all night on my connection....

14th October 2005, 14:06	#7 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	That is only a display issue for the info dialog. Thanks for pointing it out. Maybe it's worth displaying 50fps as "PAL".

14th October 2005, 22:33	#8 \| Link
Tima Registered User Join Date: Aug 2004 Location: Russia, Novosibirsk Posts: 124	As far as I can see, there's no explanation in help files about what 'Video %xx' in 'Video Type' means.. 'Bug'?

18th October 2005, 23:40	#12 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	Yes, sure. Upload it to my FTP and notify me of the filename. You didn't say what problem you have with DGIndex! I am involved in another thread about this card using .mpg, in which DGIndex can't get the audio right, but gets the video fine. Is yours the Australian or ATSC format card?

18th October 2005, 23:46	#13 \| Link
calinb Registered User Join Date: Apr 2002 Posts: 304	doh! Sorry Donald, I just realized my ommision and edited my posting, but you replied before I could get it finished. Yeah, it's the audio. I'm posting to the Dvico Q/A site about the corrupted .ts files on this one cable 256 QAM channel too, but the card should create either .mpg or .ts (.tp) output files. Both output options work on all channels but this one, which requires mpg output. I have the ATSC card. Point me to the other thread and maybe I can help there too. They could try transport stream output, as an alternative.

6th November 2005, 00:20	#18 \| Link
mg262 Clouded Join Date: Jul 2003 Location: Cambridge, UK Posts: 1,148	In the MPEG2Source documentation with this release, there is the following line: 0: Use value specified by DGIndex (iDCTs 6 and 7 unavailable in DGIndex) I have no problem selecting those modes in DGIndex, and they are documented in its manual. Is it that this line has not been updated yet (which would be entirely understandable given the rate at which you update the software), or -- probably more likely -- am I misreading it completely? If the latter, I would be grateful for the correct reading... This is a very minor point... I hope you don't mind me bringing it up. Thanks in advance, M.

6th November 2005, 02:49	#19 \| Link
neuron2 _ Join Date: Jan 2002 Posts: 16,647	It's a document bug. Read it this way: 0: Use value specified by DGIndex Thank you for pointing it out. It will be repaired in the next beta.

7th November 2005, 22:13	#20 \| Link
Tima Registered User Join Date: Aug 2004 Location: Russia, Novosibirsk Posts: 124	Donald, how much is the write buffer of DGIngex for now? Could you make it configurable to o just bigger (to make user able to avoid fragmentation of files that are written during demux, when f.e. used vobs are on the same drive)?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode