DGIndex problem in Staxrip

[invy]

[copy and pasted from my original post in the "Staxrip Discussion" thread]

omg finally I can post a message.... I waited 5 days.

Ok I have a problem here with Staxrip concerning DGIndex. I searched these forums hard in those 5 days I had to wait and didn't find anything to read about it.

My problem is whenever I load a file, then it starts transcoding okay, but after that part when it's DGIndex's turn to process the mpeg2 file, it doesn't actually process anything and just stalls. DGIndex's window just pops up and its black, and my cpu usage at 0.00% which means nothing is processing.

However, I can manually go to Open > File in DGIndex and pick a m2v, but I notice the side effect of doing so. The effect is that the last 10-20% of whatever the file's length is will be glitched and corrupted.

Anyone experience that problem with DGIndex not wanting to process automatically?

I noticed it only happens with SMALL files around 1.5 GB or less. If the file is 2 GB or more, then DGIndex will do work just fine!

The filetype is an uncompressed 12Mbit MPEG2 stream that my Hauppauge WinTV-PVR150 outputs... i'm really wishing someone could help me.

[burfadel]

I have seen this problem too! are you using the latest Staxrip and DGindex? (newer than the recommended version). With that combo I haven't had the problem... just remember if you do install a newer dgindex to copy the dgdecode.dll file over the one in the avisynth directory, and any files ready to process will have to be reindexed. The corruption at the end is interesting though, although I have to admit sometimes it seems a bit, um, off?

The new version if 1.4.9, but use only the release verison. Its available from neuron2.net :)

[invy]

my staxrip version is 1.0.0.1, and my dgdecode file version was 1.48. when I update through the external updater thing, it doesn't give me 1.49.

is it possible for me to send you a sample mpeg2 file to see if it works ok for you?

Although, I had this problem on 2 different computers...

And what do you mean i'm a bit off when I said it corrupts the file? It may not be an exact number but it's a rough estimation.