B4Print.com

Workflows => RAMpage => Topic started by: JARRIGO on September 18, 2014, 12:57:59 PM

Title: FILE CANT RIP?
Post by: JARRIGO on September 18, 2014, 12:57:59 PM
Here I am again trying to Rip a file.
The size is oversize but I have done similar files without an issues. any thought on what this error means or how I can fix it? or make it work
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 12:59:27 PM
I hate to go backwards but my go-to trick for lame files is to: Open in Acrobat, save as Postscript and re-distill.

Proper PDFs aren't a problem but not all PDFs are done correctly.
Title: Re: FILE CANT RIP?
Post by: Farabomb on September 18, 2014, 01:03:33 PM
I'm with ear on this one. It's a last resort but redistilling has sorted some files out.

Even just opening it and doing a save as has sorted things.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 01:08:00 PM
Postscript is old but solid for non-cooperative files. Anytime I receive a file from Publisher, I will PS and distill back to a flat PDF. It removes transparency, which is good for sub-par programs.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 01:11:17 PM
... and make sure you hit the "settings" button and give it a quick once-over before saving as Postscript. Also, be sure you establish a good, current Distiller preset. Press Quality is a good start but I always change compatibility to higher than Acrobat 8 and change output to "Do not color manage". Anything below PDF v1.4 will be trouble too.
Title: Re: FILE CANT RIP?
Post by: JARRIGO on September 18, 2014, 01:14:37 PM
Thanks!
 looks like it's going to work as .eps double checking to make sure when I saved it we didn't have any issues with photos fonts ect.
of course its a rush job!
 
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 01:20:31 PM
To be clear, I would go with PS over EPS. (Postscript vs Encapsulated Postscript). .eps was good for things like Illustrator files and images with clipping paths but never supported proper font embedding and multiple document pages like Postscript.

Glad you got it to work but next time, try straight Postscript.
Title: Re: FILE CANT RIP?
Post by: DigiCorn on September 18, 2014, 01:25:58 PM
He's on Rampage.

Rampage syncs up with your platesetter and gets the absolute end size from that; any file with dimensions larger won't RIP. Sometimes you can "trick" Rampage by rotating the artwork 90 degrees, and then rotate it back when impoing; that's what I do.

I have a few files that I have to crop down to smaller than plate size before RIP to make them work.

For posters that output to our Epson proofer, I created a second output device with a max size of 99 in x 99 in and I don't have size issues.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 01:30:17 PM
Nerverackin. Sounds like a Harlequin.

My plate size is dictated as a media size in the stripping templates. Marks, pages, etc... are dealt with as live objects that are confined to the media you start with. You can change anything on-the-fly, until you release the platesetter tiffs. It is ridiculously fast.
Title: Re: FILE CANT RIP?
Post by: DigiCorn on September 18, 2014, 01:40:46 PM
It's really stupid too. Our plates are basically 26 x 22 and Rampage reports it from the Screen as 26.496 x 22.008 but the maximum image I can RIP is roughly 25.8 x 19 or so. I have several jobs that are 25.5 x 11 so with bleed and crop marks, they won't RIP, even rotated. I usually crop them to 25.75 x 11.25 and then do the RIP 'n' Rotate trick. Then, when I impo in Preps, I have to spin them back into proper position for proper stripping. I'm so used to it, it doesn't even bother me anymore.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 01:43:48 PM
It would bother you if you got to take a new RIP for a spin. Similar to how I liked my Chrysler up until a week ago, when I test drove a new Mercedes. Now the Chrysler seems like a POS.  :laugh: :undecided:

Title: Re: FILE CANT RIP?
Post by: DigiCorn on September 18, 2014, 01:48:44 PM
Understood. I have a webinar scheduled for Apogee in the near future; I'm not excited.

I'm not a Kodak fan, but I understand Prinergy is da shiznit. I would also be interested in XMF. But we probably have to get Apogee because we'll be working out a deal with Agfa/Pitman and that will work out best for the bottom line of the shop.
Title: Re: FILE CANT RIP?
Post by: Farabomb on September 18, 2014, 01:56:42 PM
Apogee was horribly, horribly expensive and they wouldn't budge on price. Kodak came down to where we needed to be and XMF just wasn't ready for prime time when we were looking.

I ran 2 Apogee systems and they weren't horrible. Hell I have one here but it's not a PDF RIP so it's really not a step up.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 02:02:52 PM
I'm actually Running Sierra, which is a rework of XMF. And from what I can tell, XMF (Sierra) are comparable to Prinergy in everything but virtual proofing. I didn't care so much about the virtual proofing a few years ago, but a lot of clients are asking about it. I see an upgrade in my near future. Hopefully Sierra has upped their VP game.
Title: Re: FILE CANT RIP?
Post by: Farabomb on September 18, 2014, 02:14:42 PM
Virtual Proofing?

Send them a link to the hamster dance, they'll approve it. We all know customers don't look at proofs.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 02:15:51 PM
This is true.
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 02:50:26 PM
Virtual Proofs in Prinergy, known as VPS, are screened composite proofs. Customers never see them....at least not here anyway. We use the VPS internally for prepress only. Customers look at PDF's within Insite either through Smart Review with all of the fancy preflight and annotation tools or with Preview which is like a 3D Flipbook with the pages in order...hopefully.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 02:57:16 PM
hmm... well I guess that really isn't any better. XMF has a fine VPS style viewer built in. And it will export a 3D proof, but you have to use a .jar reader, which sucks.

I can have clients look at PDFs, but they aren't rendered and that makes me nervous. Nothing beats the good ol spinjet composite proof for content accuracy.
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 03:13:25 PM
We've never had an issue with the viewed files in Insite not matching the output of the plates. The biggest problem we have is customers uploading files and approving them without looking at them. I just love calling customers at 1:00 am and telling them they approved a page earlier that evening that was blank...which matched exactly what they uploaded. And then they get pissy because they have to get out of bed, get dressed, and drive 45 minutes back to the office.
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 03:20:06 PM
 :evil: That's like taking drunk dialing to a whole new level.
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 03:26:38 PM
Quote from: Ear on September 18, 2014, 03:20:06 PM:evil: That's like taking drunk dialing to a whole new level.

My sig on my work email, below my name and title has the words, "Check your files carefully after uploading...and then check them again just to be sure". Does anyone pay attention to that? No. Another favorite is a 72 page book and they only upload 71 pages. Never check to make sure everything is there. Go home. Then get pissed at me when they have to get out of bed, get dressed, and drive 45 minutes back to the office. Lather...rinse...repeat. It's like everyday is groundhog day. It's been going on as long as I can remember...approximately 1979 for me but I'm sure it was happening before that. David? Frailer? Hotmetal? Tap?
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 03:40:19 PM
I started kindergarten 1979.  :grin:
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 03:45:16 PM
So in 1979 you were dealing with more intelligent life forms than I was. :laugh:
Title: Re: FILE CANT RIP?
Post by: Ear on September 18, 2014, 03:53:31 PM
 :laugh: And they had some tasty glue in the 70s. nom nom nom
Title: Re: FILE CANT RIP?
Post by: David on September 18, 2014, 03:55:14 PM
... about the word "approved"...

it is just a way of keeping the file on the server until they find a better one.

for some reason most of my Insite custys love to approve all the pages and then call me so I can reject pages for them, you know they really need to make that tracking change, cause it just bugs the bejesus out of them after they stare at it for a while.  morons
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 04:05:21 PM
Quote from: david on September 18, 2014, 03:55:14 PM... about the word "approved"...

it is just a way of keeping the file on the server until they find a better one.

for some reason most of my Insite custys love to approve all the pages and then call me so I can reject pages for them, you know they really need to make that tracking change, cause it just bugs the bejesus out of them after they stare at it for a while.  morons

A daily occurrence here too. Just had two of them since I got here an hour and a half ago.
Title: Re: FILE CANT RIP?
Post by: David on September 18, 2014, 05:37:07 PM
maybe they need a new word on Insite...   "can't decide".

either Reject, Approve, or Can't Decide
Title: Re: FILE CANT RIP?
Post by: Joe on September 18, 2014, 05:39:28 PM
Or "Approved with the option to change my mind later". :sarcasm:
Title: Re: FILE CANT RIP?
Post by: Farabomb on September 19, 2014, 07:37:45 AM
I thought customers always had that option.

Custy: I'm rejecting the job because I don't like the color.

Me: Ummm... you picked that PMS color.

Custy: I don't like it, it doesn't look right.

Me: We had ink drawdowns and the ink was custom made to your specs.

Custy: It doesn't pop enough.

Me: We went through 3 different ink formulations. Here's your signoff on the final mix.

Custy: It just doesn't make me feel inspired.

Me: <to self> I NEED some of the shit you're on. Can't you share?<?self> You were here on the presscheck. We held the press for 2 hours because you were late. Then you took another 2 to approve the color.

Custy: I'm rejecting it because we can't use them.

Me: Okay, my driver will be over to pickup the job.

Custy: That's okay, we'll throw it out.

Me: No, really we will come and take the job back. No need for it to clutter up your warehouse since you can't use it.

Custy: Well, there are a few pieces.

Me: That's ok, you probably needed a few to show management to find out if it was good or not.

Custy: No like there are only a few left.

Me: The order was for 10m, how many are left?

Custy: 100

My boss: That's ok, we'll rerun it at no cost.

Me: WTF.  :hangme:
Title: Re: FILE CANT RIP?
Post by: DigiCorn on September 19, 2014, 07:59:57 AM
Quote from: Ear on September 18, 2014, 03:40:19 PMI started kindergarten 1979.  :grin:
holy shit! I thought you were older than me. I started in '76. Yes, I remember the bi-centennial. I was on the beach in Portland, and we got a Chinook stuck on the beach.
Title: Re: FILE CANT RIP?
Post by: JARRIGO on November 11, 2014, 07:48:25 AM
Hey Guys!
I am trying to get this 4 up 8.5x11 S-W perfector to register in rampage. I think it has something to do with the preps settings but when I view it in Rampage its cropped off the image... When I view it in preps its proper. Suggestions on how this file should be output from preps and ripped into rampage?

:-\
Title: Re: FILE CANT RIP?
Post by: mwc on November 11, 2014, 09:16:38 AM
I would check your preps config Rampage setup. Sounds like something is amiss (plate dimensions, rotation, tiling)? Check the Rampage documentation for proper Preps configuration.
 (ALSO, are you placing the full-res single page data.... or (hopefully) FPO-EPS files, or JDF FPOs?)
Title: Re: FILE CANT RIP?
Post by: JARRIGO on November 11, 2014, 10:15:19 AM
@MWC Thanks for the response. I deleted the job and re-register everything from my FPO to preps sig an bodabing it worked! I think rampage was acting up. I was confused on why the hell it would be making an issue over something super simple and thought it had to be operator error.