DGMPGDec 1.4.3 Final!

[Guest]

- DGIndex doesn't displays the second frame when viewing the frames in reverse order (using arrows)

- When _clicking_ on the time bar, DGIndex displays nothing at all. These are well-known deficiencies of timeline navigation inherited from DVD2AVI. Can't say when I'll do anything about it.

- when changing to any mode except Single Step, the '>' button is greyed out. It restores only after switching to Single Step. If a file is not loaded, all the buttons should be greyed. The bug is that when you select Single Step with no file loaded, the > button gets enabled. When a file is loaded, the > button is always enabled when not playing/previewing, and during playing/previewing, it should be enabled only in single step mode. If that is not what you see, please tell me the exact steps you take to make it happen.

[Guest]

@Tima

The timeline bugs are well-known legacies from DVD2AVI. Can't say when I'll ever do anything about it. The > bug needs fixing right away.

@mgh

That needs fixing right away too.

I'll crank out a 1.4.3 tonight with these fixes.

[Guest]

when i say yes and then the d2v fails to load via avisynth Are you sure about that? I duplicated the spurious warning but not this part. Make sure you're not picking up an older DGDecode version (possibly in your plugins folder). Can you please double check and if it is still a problem tell me what the failure message is and if possible upload a source stream to my FTP and tell me the filename.

[mgh]

It says older version of d2v. Not possible because I have a DGIndex folder containing both and I use template.avs with following lines
loadplugin("C:\Program Files\dgindex\\DGDecode.dll")
mpeg2source("__src__",cpu=6)
Newer versions,i extract zip/rar file into same folder overwriting all files and I do not keep DGDecode.dll in my avisynth plugins folder.
Will upload small clip.

[Guest]

You're picking up an invalid DGDecode. You'll have to figure out why.

For one thing, your path has two backslashes.

I would search the harddisk for all copies of DGDecode and remove all but the newest one.

[mgh]

Thanks. Problem solved but a new one now.
Using colourlike filter in avisynth, with dgindex 1.4.0, input in vdubmod looked like this
http://img385.imageshack.us/img385/3518/vdubmod9ct.jpg
input in vdub 1.6.0 looked like this
http://img385.imageshack.us/img385/3217/vdub16105gv.jpg
With dgindex 1.4.2 both look like the first one.
With DGIndex now having capability to tackle mpg1 and the excellent decoder,i am trying to make some of my vcds look better. Deblocking, deringing and better deencoding of dgindex with the colourlike simplified correction of color/brightness using refererence video file was making it a breeze.
The video in question is an overbright video-simple brightness correction does not work well-so have been trying out colourlike and have been happy. I have dark videos, oversaturated videos, undersaturated videos, which are getting corrected satisfactorily with one reference video file.
I am uploading this specific file which is just two seconds in length-file name trialdgindex142.mpg

[Guest]

Can you demonstrate a problem that you attribute to DGMPGDec in the absence of ColourLike? You have to strip the process down to the minimum. I am not going to troubleshoot other people's software in this thread, especially when you have two other threads going about the problem.

[mgh]

Does not happen without colourlike. I think it is a colourspace related problem-vdub1.6.10 uses internal yv12 decoder and vdubmod uses helix yv12 decoder on my pc-so it is possible for same input to look different. Problem is only with some videos using colourspace filter, again not with all. So you are most probably right that it is a problem with related to the filter.
Thanks for your patience.

[calinb]

Version 1.4.3 final offers the following changes over version 1.4.0:
2. A scanning bug in reading the D2V file in DGDecode has been repaired.
http://neuron2.net/dgmpgdec/dgmpgdec142.zip
Thanks, Donald!

But perhaps an old bug is back. DGIndex seems unable to load previously saved project files again :(. 1.4.2 and the last RCs appear to be affected.

[Guest]

Here is version 1.4.3:

1. Fixed a bug that caused the Force Film warning
to erroneously appear for MPEG1 files.

2. Fixed improper handling of the right arrow button.

3. Fixed broken Load Project functionality.

Thanks, calinb, for pointing out bug #3.

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

[agilpwc]

Somewhere since version 1.4.0 the following bug has occured.
When I used the CLI and I specifiy the wrong PID, after correctly setting them using the "Detect PID" menu option. The program saves a project with a blank name '.d2v' instead of using whatever I specified on the command line, and it also uses a blank name for the audio files. In version 1.4.0 and earlier it always used the project name specified.

[Backwoods]

2. Fixed improper handling of the right arrow button.

Sorry, that was my fault. I was pretty drunk and the button just looked so good and...



Seriously though, you're awesome for putting so much attention into this program. Thank you.

EDIT: Just curious, but from 1.4.1 to 1.4.3 the EXE was cut in half meg wise. Pretty large change, how come?

[Rockby]

EDIT: Just curious, but from 1.4.1 to 1.4.3 the EXE was cut in half meg wise. Pretty large change, how come?
The Spash Screen has been removed...

[Guest]

The Spash Screen has been removed... The built-in default one was removed. You can still have one if you provide your own BMP file, as described in the DGIndex user manual.

[Guest]

Somewhere since version 1.4.0 the following bug has occurred. When I used the CLI and I specifiy the wrong PID, after correctly setting them using the "Detect PID" menu option. The program saves a project with a blank name '.d2v' instead of using whatever I specified on the command line, and it also uses a blank name for the audio files. In version 1.4.0 and earlier it always used the project name specified. Please provide the exact series of steps I need to perform to duplicate this. Thank you.

[rig_veda]

Did anybody notice a difference in speed going from version 1.4.0 to 1.4.3? I'm not sure why, but the time necessary to save a given project (without audio) went from around 5 minutes to almost four times as much using the same settings. Another weird thing after switching is that i seem to not get any image preview in vdub 1.6.10 while manually scrolling the time line, while I do in vdubmod 1.5.10. weird.. :confused: looking into this

[Guest]

Did anybody notice a difference in speed going from version 1.4.0 to 1.4.3? I'm not sure why, but the time necessary to save a given project (without audio) went from around 5 minutes to almost four times as much using the same settings. I don't see any difference. Are you sure all the conditions were the same?

Another weird thing after switching is that i seem to not get any image preview in vdub 1.6.10 while manually scrolling the time line, while I do in vdubmod 1.5.10. weird.. :confused: looking into this VirtualDub 1.6.10 works fine for me.

[rig_veda]

I'm quite sure that all settings were the same, but the problem seems to be somewhere else in my setup, I think, since I noticed that I'm not able to get a picture in vdub 1.6.10 at all anymore, unrelated to the dgmpegdec version used. The speed issue also wasn't reproducible. Quite to the contrary: with another sample, the faster version this time was 1.4.3, (again by far, which is weird), so it might have been source dependend. Sorry for the trouble.. I hope i find the error in my system.

[fatxy]

a little suggestion for the template feature

instead of

video = mpeg2source("__src__")

it would be cooler if its only the src name without extension

why? =>

video = mpeg2source("__src__.d2v")
audio = MPaSource("__src__.mpa")

you dont have to edit the avs for audio :)


if someone has time to implement it would be great, thanks in advance

fatxy

[Guest]

video = mpeg2source("__src__.d2v")
audio = MPaSource("__src__.mpa")

you dont have to edit the avs for audio :)
That won't work because the audio file name gets decorated with various audio-specific information.

Also, we already have this issue on the development list stickie. One problem is what to do if there are multiple audio tracks.

[fatxy]

That won't work because the audio file name gets decorated with various audio-specific information.

hehe your thoughts are to 'complicated'

a little example of what meant and which should be simple to add:
i do often record via dvb some tv stuff -> .pva -> demux with pvastrumento
ill get a mystream.mpv and a mystream.mpa
drag the mpv in dgindex, create a project and avs via template

current template
...
video = mpeg2source("__src__")
audio = MPaSource("__src__")
AudioDub(video, audio)

this will result in
video = mpeg2source("X:\mystream.d2v")
audio = MPaSource("X:\mystream.d2v")
so i have to edit always the avs again (changing d2v to mpa or sometimes wav)

thats why a src name without fileextension would be useful imo, i guess the ones that use dgindex to demux vobs or similar with ac3 and stuff dont have a audio part in the template anyway
or maybe they decode them to wav and a ___src___ + .wav would be nice too, thats the good part, you can decide the extension yourself


since a likely feature is already sticky on list it shouldnt take so long to expect in further build, should it? :P

[Guest]

DGIndex is written to be consistent with itself, not with third-party applications. If you can't wait for me to get to this feature, please get the source code and do it yourself.

[Guest]

Somewhere since version 1.4.0 the following bug has occured.
When I used the CLI and I specifiy the wrong PID, after correctly setting them using the "Detect PID" menu option. The program saves a project with a blank name '.d2v' instead of using whatever I specified on the command line, and it also uses a blank name for the audio files. In version 1.4.0 and earlier it always used the project name specified. OK, I've duplicated this. Thanks for pointing it out. I'll fix it in the next beta.

[Guest]

Since version 1.4.3 has gone final, this development thread is now closed. Please open new threads for problems or issues. A version 1.5.0 development thread will be created for the next version.