PROCODER EXPERT NEEDED!!!

[twinegar]

I purchased Procoder 1.5 in Feb. and have done several PAL to NTSC convertsions and they turned out perfect.
I tried 2 different PAL conversions recently and the process was terminated early with an error message that basically stated that it was terminated due to inactivity. When I do get it to work the resulting file is jerky. I installed it to a different machine with the same result.
I purchased Procoder Express to see if that helps. The encode ends early due to buffer underuns no matter what the setting is including the default one.
I can load the video file into TMPGEnc with the 3.2 pulldown setting and get the proper result but I spent a lot of $$$ on Procoder and would like for it to work like it used to.
"Anyone" had the same problem?

[lordsmurf]

Sounds more like a hard drive issue (fragmentation, free space, full recycle bin, etc)

[twinegar]

Procoder 1.5: There is plenty of room on the drive but you might be right about the Defrag especially since I did several conversions before and they came out perfect.
Will a fragmented drive cause the buffer underuns I am encountering in Procoder Express?
I will defrag the drive when I get home a try it again.
By the way, I have Express loaded on 4 machines and it has never completed a conversion without the buffer underuns even with the default bitrate settings. There is no jerkiness but it always terminates early.
I can load the video file into TMPGEnc with the 3.2 dropdown setting and the file is perfect but since I paid a lot for Procoder 1.5 and have the ability to convert the audio and video in one step I would like to get past this.

[choirislife923]

Will a fragmented drive cause the buffer underuns I am encountering in Procoder Express?

if your computer is recent (about 1.5 GHz and up), chances are your PC can recover fast enough on a fragmented drive. my 2ghz athlon xp 2200 is running on 2 HDDs which have never been defragged, and it runs fine. my 633mhz celeron...it'll fail a CD burning at 2x if its fragged

[proxyx99]

call Canopus tech. support, that's exactly what they are for...

[hiptune]

I purchased Procoder 1.5 in Feb. and have done several PAL to NTSC convertsions and they turned out perfect.
I tried 2 different PAL conversions recently and the process was terminated early with an error message that basically stated that it was terminated due to inactivity. When I do get it to work the resulting file is jerky. I installed it to a different machine with the same result.
I purchased Procoder Express to see if that helps. The encode ends early due to buffer underuns no matter what the setting is including the default one.
I can load the video file into TMPGEnc with the 3.2 pulldown setting and get the proper result but I spent a lot of $$$ on Procoder and would like for it to work like it used to.
"Anyone" had the same problem?

Make sure the "field order" setting is correct on input/source. If you get that wrong the finished file can end up jerky. And with PAL some dv files are Upper, and some Lower field first.

As for the process quiting on you, go ahead and defrag (good idea for many reasons), unplug your modem from back of machine, reboot right before encode, and start procoder without doing anything on the machine first.

I had read of some of these tips concerning capture, and since I have never dropped frames, but have had encodes quit, freeze, or crash, I decoded to try these capture tips, but use them for encoding. I am now saving time in failed encodes in both procoder and tmpgenc.

Jeff

[booaf]

The encode ends early due to buffer underuns no matter what the setting is including the default one.

And you won't be able to do a thing about it.
Call Canopus. It's an encoder bug.
ITMT, use TMPGEnc.

Greetings,
Baf