Memory could the issue.
But as I mentioned we are using a TCP protocol call OrbitLink on
our RIPs, Outmanger and Imagers. It's job is to coordinate the multiplexing
of jobs.
It looks like when two composite pages are being sent to the same Imager
from two different RIPs one page is imaged and one put on hold.
The one that is paused, until the first page is finished imaging is the page
that only outputs one of the three plates..
Has anyone heard of or use this Orbitlink ?