DGDecode.dll keeps running after close

[fmonroy]

I'm using DGDecode.dll that comes with DGIndex 1.4.0 RC4; the problem is that it keeps running at full processor speed after I close Windows Media Player 6 (mplayer2.exe) or Dr.DivX.

It does not happen with version 1.3.0; is there some new setting that I'm not specifying?

This is the way I'm using it:

LoadPlugin("C:\Program Files\DGMPGDec\1.4.0 RC4\DGDecode.dll")
Video = MPEG2Source("Movie.d2v")

(using P4@3.2 GHz w/ HT)

Thanks in advance.


FM.

[Guest]

I don't understand your report. Are you saying you open the AVS in a player, you terminate the player, and somehow DGDecode continues? How do you know it continues? Please tell me exactly what you are doing so I can try to duplicate it.

[fmonroy]

- After the rip process I start DGIndex, then I open the .vob files.
- I use all defaults for video and I change the audio output method to decode to wav, and then select the audio track number to decode.
- I save the project and it works without errors.
- Then it creates the .d2v and .wav files.
- I want subtitles in the video so I use VobSub to get the .sub and .idx files.
- After this I create the script for Avisynth 2.5:
**********
LoadPlugin("C:\Program Files\DGMPGDec\1.4.0 RC4\DGDecode.dll")
Video = MPEG2Source("Movie.d2v")
Audio = WAVSource("Movie.wav")

AudioDub(Video, Audio)

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\VSFilter.dll")

VobSub("Movie.sub")
**********
- Then it plays good at Media Player; just as a test before the encoding process.
- When I close Media Player, the processor is still working a lot, then in the task manager is the mplayer2.exe process, it can be killed manually.
- I use Dr.DivX to encode to MPEG4 and the program has a simmilar problem: it gets 100% of processor during all encode task (using 1.3.0 usually it happens until half of the movie); and after the end of the encoding the processor is at 100% until I close Dr.DivX.

It first happened on a PC so I changed to another; same results.

I think it behaves like a memory leak; what do you think?

[Guest]

I tried it without the audio and without VobSub and it worked fine, nothing stuck in Task Manager. Please try with just audio and just VobSub to try to isolate the problem.

DGDecode can't run on its own. Some application has to make calls for frames to be decoded.

[fmonroy]

VobSub has the problem.

I re-tested with 1.3.0 with same results; so it's no DGDecode related.

I'm sorry for wasting your time.

Thanks for your help.


FM.

[Guest]

I agree. I just tried with the audio and that worked fine too.

Don't worry about "wasting" my time. It's better to be safe than sorry. I appreciate all feedback, so thank you, it could have been a real problem.

[fmonroy]

I found that DirectVobSub is a lot more efficient and has not the close problem.

Thank you very much.


FM