XMF & Prinergy to Spinjet hot folder stops folder

[Nivin]

We have both a Prinergy Workflow and an XMF Workflow. If we send a proof from XMF to the Spinjet, the hot folders no longer function for Prinergy proofs and we need to reboot the proofer front end.

The output files are going to different hot folders on the Spinjet. Prinergy sends a PDF and XMF sends a TIFF (the reason for different hot folders).

Has anyone else seen this and solved this problem?

Thank you!

[Ear]

Two full workflows!? This is like a prepress version of "First World Problems"  


I kid, I kid... but seriously, I only have one XMF. I do have two EFI Fierys and they are both a PITA.

[Farabomb]

I have a printdrive rack parked not 50 ft away from my prinergy server.

The rack holds my switches. The boxes haven't been on in years.

[DCurry]

I can't answer your specific question, but I don't like the idea of having Prinergy send PDFs to the proofer (unless that PDF is fully rasterized by Prinergy, but I kinda doubt that's what is happening). By sending a PDF to the proofer, you are asking the proofer's RIP to interpret and rasterize the PDF and if it interprets differently than Prinergy would, you could end up with proofs that don't match plate.

I would prefer to send rasterized TIFF from any workflow to the proofer - that way, the same engine that creates 1-bit tiff for plate is the same engine creating 8-bit tiff for proof. No surprises this way.

Sorry I can't address your initial question!

[Ear]

I agree with DCurry. I send rendered tiffs to my Spinjet and they are bulletproof. I send PDF to my Epson with the Fiery but only to get a color correct proof, and I don't 100% trust it as a content proof.

[Nivin]

I talked to XMF hoping they would have an idea of what might be causing this. They came up with a virus program might be causing it. And when opening a window to see what's happening to a file, the act of the thumbnail being created may lock the file.

[Nivin]

In case this may be helpful to anyone else . . . I think we have solved the problem. It seems when Prinergy actually "talks" to the proofer front ends is when everything locks and we need to reboot. So we created a HOLD folder into which we print the Prinergy proofs and then manually drag them into the correct output folder on the proofer front end. Seems to have solved the problem.

[David]

could you not put a delay on the hot folder to give the file time to finish writing before it starts to process?