I've been doing some experimenting and stumbled across this odd problem. I made a file from a video capture and thought to find out if I could take that processed file and reprocess it. Why? Well, I've been reading about MPEG and how one company's product makes MPEGs one way and another makes them another way -- but still other programs won't accept either (out of specs? whatever).
So, I was thinking, just how good is TMPGEnc (or, for that matter, any piece of software in the entire KVCD process)? Can it take it's own product without choking? So took the KVCD file I made using AviSynth (2.0.8 under WinNT4) and TMPGEnc (2.5.20) and made a simple AVS file to feed it through again:
Code:
# using MPEG2DEC_nic.dll
mpeg2source( "tmpgenc_KVCD.mpg" )
Usually, before I do any TMPGEnc'ing, I'll simply run the AVS file with Windows Media Player to see what it looks like. THAT is where it got stuck. When the AVS file is run, MPEG2DEC first creates it's D2V file. But it's a bad file - no list of information beyond the header info - and WMP locks up. There's what I get:
Code:
DVD2AVIProjectFile
1
35 tmpgenc_KVCD.mpg
Stream_Type=1,0,0
iDCT_Algorithm=2
YUVRGB_Scale=1
Luminance=128,0
Picture_Size=0,0,0,0,0,0
Field_Operation=0
Frame_Rate=25000
Location=0,0,0,0
9
FINISHED
This indicates that whatever TMPGEnc produces, MPEG2DEC doesn't like. (BTW, TMPGEnc has no problem processing the actual KVCD file itself. However, everything stops when it's fed in via AVS -- the MPEG2DEC problem again.)
Anyone ever notice this? Is there a bug in the MPEG2DEC file, or some other file (like DVD2AVI)? Is it the same with AVS 2.5.x version files or other versions of TMPGEnc? Just an inquiry ...