read error, not always at same place
 

Dialhot wrote: There is no real woarkaround for this error. If this arrive always at the same place, just change a little your script or encode at a lower CQ.

What I'm wondering is, if the error happens at different places? Does this indicate anything?

I used TMPGEnc for a couple years now with no errors and now all of a sudden. Read errors...can't figure it out.

Re: read error, not always at same place
 

Simply that tmpgenc, even if very stable, still is a software that means it has bugs. Murphy's law...

Errors can bring up suddenly, with no apparent reason, simply because you changed a codec, or perhaps a simple dll of windows that is involved in the rendering of a video (thanks windows update).

Note: last time I faced to errors I managed to fix them by changing the prediction method into tmpgenc form "Motion Estimate" to "High (slow)".
Try to change this setting to an other value in your jobs.