[alex reznick]

When I convert without a batch - manually, file by file -
there is no such glitching.

Sounds the the batch mode stresses the machine over a period of time and
eventually it gitches.

I doubt it: this is a 4-core 2.5 GHz machine. And Samplitude is just
about the most economical DAW out there (about 3 times less CPU than
Sonar). Just one job should not cause any CPU overload. Besides,
wouldn't maxing CPU just delay the job rather than intercepting? The
only exception to that is overheating, but Intel calibrates its
hardware with the way safe margin (20 degrees or so) for this to
become an issue under normal temperature conditions.


Does this mean that batch processing uses dither differently than the main
program?

Not necessarily - the load on the system is different because the batch mode
just bangs away on the machine quite relentlessly.

Of course I will try later today to batch process video material - it
is much heavier than audio - and then run bit by bit comparison of the
files. But I doubt CPU load is the cause.