Quote from: Joe on March 12, 2019, 10:53:59 AMI do that with the page boxes...hence no need for marks.

But mostly we tell ALL customers to not put any marks on their files because their files are usually wrong so no marks are better than wrong marks. First thing I do with all customer supplied PDF's that have marks ===> Remove Printer Marks action. Then fix the page boxes.

Or fix the page boxes, then remove anything outside the bleed box? Then you can remove art box and redefine the crop, bleed, media boxes to fit whatever standard you used based off of the trim box.

Quote from: Joe on February 18, 2019, 10:53:57 AMYes they can do the restore remotely if it gets screwed up but they will not do the procedure remotely.

Seriously???? oooohhh okay....

Quote from: Joe on February 17, 2019, 07:55:29 PMOnsite service from Kodak? Not going to happen at what Kodak charges for onsite service. If they have to rescue the database they can do it remotely which our support plan covers.

Right, they can do it remotely. Makes for an easy process and decision.

"Back up the existing drive then do the RAID 1 to RAID 5 conversion and boot back up into the LIVE CD and restore the data to that drive and they believe I will be good to go. If not I will have multiple backups that they say they can restore from."

Umm... If they think it will work AND they say they can restore it, then make them do it. Then it's their problem. I have a few years experience with these phrases....

Quote from: Joe on February 15, 2019, 03:37:32 PM

Quote from: mattbeals on February 15, 2019, 12:44:29 PMMigrating RAID 1 to 5? Yeah, no.

Add a 4 drive RAID5 or 6 as a separate volume using a hardware RAID controller. You have a mirror, leave it at all reasonable costs.

The system disk is 2 disk RAID1. Not being touched.

The data disk is a two disk RAID1.

I want to replace the RAID1 data disk as a 6 disk RAID5. That is the jobs drive for Prinergy which also has the oracle database. I lose 1.2 TB of storage space leaving it as a 2 and 4 disk RAID1 and RAID5 and the 2 disk RAID1 is useless as I need everything on one array. And yes it is a hardware RAID. Perc H730 Mini.

Maybe it works, I can't say. But at this point for me, comfort level, get an external RAID array and have the flexibility to expand on demand and have failover drives to brought online when a failure occurs. You.should be able to move the DB there, have the data/jobs, hardware RAID, expandability. Migration and changes like this always make me nervous about time. A new array and a restoration *seems* most expedient and reliable. Your mileage may vary.

Migrating RAID 1 to 5? Yeah, no.

Add a 4 drive RAID5 or 6 as a separate volume using a hardware RAID controller. You have a mirror, leave it at all reasonable costs.

Joe and ABC are dead on. There are people though who will buy and take the chances. If you find one of those, make sure the wire transfer or check clears before delivery.

Having done this, it's a painful process to sell and even more so to collect on.

Quote from: rickself on January 24, 2019, 01:58:07 PM

Quote from: mattbeals on January 24, 2019, 09:22:09 AMYou want the PDF Print Engine, do *NOT* flatten the transparencies. The PDF engine will render the transparencies better/correctly at output. There's a reason to not use a Postscript engine, transparency is pretty much the biggest reason.

Spend the money.

Thanks, Matt, oh Guru of PDF. Been a student of yours for some 20 years.
Knowing that transparency is going to give bad results with a PS engine through the Fiery, is it safe to say the workflow of PDF Engine (in the Fiery?), going to the Ricoh PRO C5200 S SHOULD give the end product we're looking for? Does it matter if the file is printed direct from InDesign into the held que of the Command Workstation or are the results better saving as PDF and dropping into the CWS? Or same one as the other?

Keep the Fiery, it's the best you will find, and add the PDF Print Engine. If you are printing though, like Command+P, then the process is flawed from step 1. For the sake of this conversation, "printing" is dead. PDF though, very healthy and thriving.

Print a plain text email, an email. Anything else? Send PDF 1.4 or higher to keep the transparencies. We can talk about the color conversions and output intent later.

Command/Control+P is your mortal enemy. Anyone telling you differently is lying, or uninformed, or selling you something. PDF Print Engine is the way to go.

Okay, from from workstation on up. Lots of choices that get insanely configurable quickly. Six or 8 cores if nothing else is because of the OS overhead. Sixteen GB of RAM or 24GB. Anything more "now" will be useless. Just make sure it's easy to add another physical cpu with an identical CPU in slot 0. That's the worst part to decide. Everything else is relatively easy until you reach windows license limitations. Start with Windows Server 201x.

I9 processor is great, 8 cores is fairly standard, SSD's are ideal.

Picking hardware is personal taste. Is this desktop grade, workstation grade, server grade?

You want the PDF Print Engine, do *NOT* flatten the transparencies. The PDF engine will render the transparencies better/correctly at output. There's a reason to not use a Postscript engine, transparency is pretty much the biggest reason.

Spend the money.

Quote from: elko on October 19, 2018, 07:47:08 AMmatt: I dissagree. Iit is not smarter for me. There could be same setting for CMYK values and so on as it is in the action in the preflight settings. There could be a button "make it real black" in the navigator (with the preflight results) that should change the collor as the action and the automatical fix do and one doesnt need any collor menu to fix it. The issue is impure black so your aim is the real black one doesnt need more. For the case I shall need more, there could be the smarter and intelligent way of added action.

Bizarre, but if it doesn't work for you then that's fine. Remap color provides a huge amount of flexibility that the built in logic doesn't have. Too many combinations to account for. Even callas and its logic has limitations where using color mapping is more flexible.  You essentially set a range of CMYK colors and have them mapped to separation black, k of cmyk, device gray, etc. And it does it without havin to step through the preflight results; it's just "done'. Much more simplistic and powerful. Your mileage varies.

The flexibility of the preflight action is limited. By using the remap color action and putting it into the preflight profile you make a more intelligent and flexible preflight profile. Down the road this is a smarter way of working.

Using remap color is better because you can add additional RGB black, or even cmyk builds of black and map them to device black, separation black, device, etc. It makes the action more flexible/intelligent.