Not at all. (Sorry, this is long)
Well, that part at least you can do in Onyx, in what back then was called 'Preflight' and what is now called 'Job Editor.' You do have to specify to open the file that way, however. Not that that's any big deal, but you do have to know to do it.Oh, one more thing came to mind. It's been years, so maybe my memory is a bit fuzzy, but I recall that the onyx would rip a file when it was imported. Another reason we liked the Fiery XF was it would import a job, and before it would process the file it would allow us to manipulate it. Then, once we hit print, it would raster and print the file(s).
This is one of the things I'm curious about. For years, it was pretty common practice when setting up RIP's to set the vector rendering intent to Relative Colorimetric, and the raster rendering intent to Perceptual.With the Altona test suite as well as our own in house work we found that it couldn't handle more than one rendering intent per file, transparency over spot colors would draw bounding boxes around text and shift color...
In a PDF/X3 file that has various elements, each graphic within can have it's own rendering intent. I don't know the science behind all of this, all I know is when it comes to PDF/X files, the efi can do what the onyx couldn't. I suggest you look into the Altona Test Suite. It's built to show you what your rip can handle.Are you saying that you can set differing rendering intents for vector and raster elements of an image and not get this? If so, that would be a handy tool to have back.
We use a strict PDF/X workflow. Regular images and PDF's will print just fine. Not to sound like a broken record, but the Altona test will show you everything I'm talking about.As far as all the other issues you had, well, I wasn't there so of course I can't know. I've never had any of them come up with any RIP, to be honest. Set up properly, Fiery works okay, and it does have a leg up on Onyx, and Caldera, and anybody save maybe GMG when it comes to proofing. But set up properly, I'd expect any RIP to be able to process the workflow you describe. (Although I do agree the remote stations is a nice feature.)
I'm not sure what you mean by "fall down", but they were helpful. They did everything they could, the rip just couldn't digest PDF/X files. They broke every time, and it was because Jaws couldn't deal with it. We got our fiery support from chromaticity. They were incredibly helpful. No bad words for them at all. I've had good experiences with both onyx and efi. It's just that onyx couldn't fix what was wrong with their product at the time without a big update. I wasn't upset with them, we just had to find a rip that could do what we needed. But aside from PDF/X, the Fiery can also print just about anything we throw at it. The greatest relief from the switch is that there are no unexplainable anomalies we have to waste time trying to figure out, and our clients trust us again.Interestingly, while you obviously had Onyx tech support fall down for you, and I've heard others tell of them falling down as well, my personal experience with them has been not all bad, while EFI tech support has been gawd-awful. For my money, they're not even worth calling.
You should run the Altona test files then, and see if everything works. I'd say we got everything we need with the Fiery.Obviously an experience like that has left me no doubt biased, but my personal reason to this day for preferring Onyx is that to me, the main purpose of a RIP is to gain control of the printer; to gain control of the printer so as to get maximum use of every bit of machine capability out of each and every print, on each and every print, each and every time.
What tools again? For what it's worth, I haven't found it to lack anything we've needed so far. I am curious though about the tools you say it is missing.Now you have to look for those tools in Onyx, and then once you find them, you have to know how to use them, but they are there. Second to Onyx, I would put Caldera. And any biases I may have aside, in Fiery, those tools are simply are not available.
Specifically the ability to have full control of ink splits, and multi-dot generation -- both of which can be pretty important on the SureColor.What tools again? For what it's worth, I haven't found it to lack anything we've needed so far. I am curious though about the tools you say it is missing.
Actually, I recall using this (preflight), but the only part that was a bummer was having to open it in a separate "app", manipulate, then send it to the queue, and then back to preflight for any more edits, etc. We did know it was there (used for tiling, etc), but all the round trips and layers made it cumbersome. So with the EFI, jobs were queued as usual, but if you needed to edit them, you could do so instantly since it wouldn't process the file until the moment you hit print. Huge time saver.Well, that part at least you can do in Onyx, in what back then was called 'Preflight' and what is now called 'Job Editor.' You do have to specify to open the file that way, however. Not that that's any big deal, but you do have to know to do it.
I'm not Mike, but I've never noticed a difference. It seems that the rip always just streams data to the printer regardless. We've had HP DesignJets with onboard PS rips, and without, and there was no difference between them performance wise that I could tell. We've used various quantities of the HP 5000, HP 5500, HP Z6100, HP Z6200, Epson 11880, Epson 4900, Epson 9900, Epson S70670, FujiFilm Frontier DL600, FujiFilm Acuity Advance Select, and Durst Lambda76. All seemed to operate equally well in regards to being driven by the rip.Mike,
Thanks for the advice, I use Onyx every day and I love it.
One question, do you see a difference in reliability between printers with HDD's used by RIP's?
Although the autonomous car is not quite ready, a lights out print operation is something you can do right now if you have a comprehensive Print MIS (Management Information System). The advantages can put money on your bottom line. So what’s your next step? Link to Article