Can't get DGIndex to work properly

[iTayb]

You're right - it's memory problem. Avisynth crushes when MPC's process gets to beyond 1.5GB RAM.

Then I'll have to create 4 or 5 files, and then combine them all together?

[poisondeathray]

You're right - it's memory problem. Avisynth crushes when MPC's process gets to beyond 1.5GB RAM.

Then I'll have to create 4 or 5 files, and then combine them all together?

I don't know, that sounds like what you might have to do if you choose this route... You could encode to a lossless intermediate with 5-10 clips at a time , for example. Then join those in a script finally encoding to your end goal format. That's a clunky way to do it.

Ideally you could make a single MPEG2 file, but I also tried videoredo, and quickstream fix etc...no luck with the pixellation on those test files. tsmuxer doesn't seem to work on those, even with extension renamed

You should check the HV20 forums, maybe there is a better workflow, because this seems a very convoluted way to get what you want...

[poisondeathray]

Running each indiviudal file through videoredo's quickstream fix, and then appending them with videoredo seems to work (no pixellation at the cut/join sites). (But appending clips first , and then quickstream fix didn't work). I only have 2 test clips that I copied a few times, so you might want to try it out on a bigger sample. I don't know if videoredo has a batch quickstream fix

[jagabo]

I got this when I opened the sample m2t with mpeg2cut2:

[iTayb]

Running each indiviudal file through videoredo's quickstream fix, and then appending them with videoredo seems to work (no pixellation at the cut/join sites). (But appending clips first , and then quickstream fix didn't work). I only have 2 test clips that I copied a few times, so you might want to try it out on a bigger sample. I don't know if videoredo has a batch quickstream fix

You are right, after using VideoReDo quickstream fix's function - the output .mpg files are fine, no pixellation at all.

There is a batch quickstream fixing, I'll try it tomorrow's morning.

I got this when I opened the sample m2t with mpeg2cut2:

Hehe. So it seems HV20 produces defective files.

By the way, thank you very much, poisondeathray, jagabo and manono. You're all being a great help.

[jagabo]

Was the sample file a full clip directly from the camcorder or did you trim from a larger file?

[iTayb]

It was a full clip directly from the camcorder.
When I captured the footage with Vegas, and it seems that Vegas had trimmed the input video into scenes, which are actually the multiple m2t files. The sample clip I've uploaded is a full clip/scene/m2t file.

[poisondeathray]

I wonder if vegas is causing those errors?

Some people use hdvsplit for their hdv captures

[iTayb]

HDVSplit was producing choppy and pixellated video (not only an join sites), whether it was with Scenes Trimming mode and whether not.

In any way - I don't have the tapes anymore, so I'll have to deal with this buggy files.