News:

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - DCurry

#1546
Adobe Photoshop / Re: Photoshop User
October 24, 2007, 08:45:51 AM
I sell mine on eBay every year or so. I have a bunch from the past year that I haven't listed yet if those are what you are looking for. I can check which issues they are tonight.
#1547
Adobe Acrobat / Re: Distiller Question
October 18, 2007, 04:51:08 PM
Maybe I'm misunderstanding something here, but if you are outputting the images at 600 from Quark, then yes it will downsample in Distiller because it it above 450.
#1548
Fonts / Re: Fonts and the legal standpoint
October 17, 2007, 07:09:37 AM
Quote from: david on October 17, 2007, 07:03:08 AManyone know the number for 911?

I can't find the eleven on my phone!
#1549
Quote from: NinjaPB_43 on October 10, 2007, 09:27:45 AMI STILL am not seeing that..   when I have no links highlighted in the links pallette, the "update link button" is grayed out.  only option is to click "relink button"..   and then you have to tell each link individually which file to relink to...

I see - it is grayed out because there are no links that require updating (if a link needs updating, it has the yellow triangle/exclamation point icon). Yes, relinking each instance of a repeated graphic is a pain.
#1550
Quote from: NinjaPB_43 on October 09, 2007, 03:43:04 PMI have to still update individually..   :'(

The trick is to make sure nothing is selected in the Links palette, then hit the Update Link button either at the bottom of the palette or from the flyout. If you have a link selected, only the selected link will be updated.
#1551
Never mind - I think I figured it out. I believe it was the "Allow Trapping" checkbox for Black Lineart  under the Overprint button.
#1552
(This is for PS/M 8 users, but anyone with a Brisque can chime in, too because it does the same thing)

I recently upgraded my rip from PS/M 7 to 8.1. I rarely allow the RIP to automatically do my trapping - instead, I prefer to rip the job, then open it in PressTouch and make my trapping decisions and frame it there. Since the upgrade, whenever I open my Decisions to look at how it is going to trap the file, I get a bunch of colors in the Constraints tab that all say "Don't Frame" - anywhere from 1 color to a list of a dozen or more. Some of the colors in this list are just Registration, which is fine, but other times it lists colors that I do need to trap, so with every job I have to delete the list before I let it make the decisions. No big deal, except that on the few occasions where I actually want to just let it trap automatically (like when it is only LW in the job), it doesn't trap some color pairs that obviously need it.

I never had this happen in 7, so obviously there is something different here. As far as I can tell, all my rip settings are the same as before unless I'm missing something. All FAF settings are identical (I don't think it is an FAF setting issue anyway because I can rip the same file on PS/M 7, 8.1, and Brisque 4 and 7 does not protect these colors) I've experimented with all the RIP settings and haven't gotten anywhere.

So how do I get my RIP to not protect these colors?
#1553
Kodak Preps / Re: Indy CS3 ps page offsets
October 07, 2007, 08:32:07 PM
I only use Device Independent when I am intending to place the postscript directly into Preps. If I am intending to distill a PDF, I use the Acrobat Distiller PPD.
#1554
Kodak Preps / Re: Indy CS3 ps page offsets
October 07, 2007, 09:00:46 AM
Hmm, I've not had Quark drop any type (yet)! I've narrowed the type-dropping CS3 issue down to Preps 5 - the single postscript will rip fine by itself - it is only when it is being stepped off in Preps 5 that type starts to drop, and it is not on every instance of the page that is repeated (some pages wil be fine.) I'm talking about 1 page stepped multiple times on a template, just to be clear.
#1555
Kodak Preps / Re: Indy CS3 ps page offsets
October 07, 2007, 06:08:04 AM
Quote from: frailer on October 07, 2007, 03:43:37 AMBTW, did they happen to be Identity-H fonts[double byte].

I don't know because it was a postscript, so I couldn't look at the font encoding. I was able to open the same file in CS2 and make a postsript and it was fine. My standard op for CS3 now is to make postscript and then Distill (also have issues with direct export from CS3).
#1556
Kodak Preps / Re: Indy CS3 ps page offsets
October 06, 2007, 07:08:07 AM
Quote from: pspdfppdfx on October 06, 2007, 06:36:33 AMI have the same problem with Quark  7 ps in preps.

Me, too. My solution is to export PDF from Q7 - has worked well so far for every job.

I don't have offset problems with INDD CS3 - my problem there is that Preps will drop type from the CS3 postscript.
#1557
Adobe Photoshop / Re: digital camera corpses
October 03, 2007, 04:01:53 PM
Sounds like the wrong profile was used as a source when converting. If there is no embedded profile, try sRGB first, then compare with AdobeRGB and see which one looks better, then convert to your 4-color profile.
#1558
Quark Xpress / Re: anyone getting Quark 7 files?
October 01, 2007, 10:23:28 AM
We have quite a few customers who have upgraded, thus forcing us to as well. It's biggest problem is a lack of Flattener Preview or something similar. No way to analyze transparency to look for potential issues.
#1559
Macintosh / Re: Do you still use OS 9 or lower?
October 01, 2007, 10:20:05 AM
Until recently, my RIP was running on an OS 9 machine, and we had Preps 4.2. I got a new Intel Mac, upgraded the RIP to PSM 8 (OS X compatible), then shifted my old production to become the new RIP. Also upgraded to Preps 5, so now we only use Classic for Q4 & Q5 jobs - I'm still afraid to open them up in newer versions. Everything requiring OS 9 runs under Classic in my shop.
#1560
Macintosh / Re: Classic launches, but apps won't
September 26, 2007, 12:40:05 PM
Actually, some apps do need extensions - BarCodePro needs something, as does Transmit (I know because during my troubleshooting they gave me an error about a particular extension being required to run.) Otherwise, good to know!