p01 Kansas City Southern
Skip to main content

Recent Topics

xx

xx
New Windows 10 PC
by Slappy
November 16, 2018, 09:41:00 PM

xx
Dieline Question
by Tracy
November 16, 2018, 05:12:37 PM

xx
Lotem 800 punches
by Mark2
November 16, 2018, 04:47:57 PM

xx
Add filename without extension
by Joe
November 16, 2018, 01:56:07 PM

xx
Apple releases new Mac mini
by seratne
November 16, 2018, 10:22:20 AM

xx
The Future of business cards
by Omegared86
November 15, 2018, 05:16:59 PM

xx
Business Card order
by Omegared86
November 15, 2018, 05:14:13 PM

xx
Pantone Color Finder
by Joe
November 15, 2018, 12:57:07 PM

xx
Pitstop 2018
by Tracy
November 13, 2018, 06:03:12 PM

xx
Remember Client Password
by seratne
November 12, 2018, 05:11:05 PM

angry
mac rage
by wonderings
November 12, 2018, 04:18:06 PM

Topic: DCS2 file using vector workflow (Read 4687 times) previous topic - next topic

DCS2 file using vector workflow

We do not have support so I am reaching out to this forum in the hope that someone here can lead me in the right direction. Currently running Nexus 9.0.3. I have 2 workflows that create DCS2 files, one raster and the other vector. Problem I am having is the vector workflow does not hold the spot color, but the raster the raster workflow does. The Assemble DCS and Merge DCS modules in each workflow are identical. The raster workflow only creates the DCS2 file. The vector workflow also creates a PDF (high and low res), Artpro file and PSTI files along the DCS2. All the other files produced in the in the vector workflow retain the spot color. If I highlight the Assemble DCS and Merge DCS modules that the actual file is going through it still shows the spot color listed in the separations, but ultimately the spot color converts to process in the DCS2. Any clue where this may be going wrong?

Re: DCS2 file using vector workflow

Reply #1
Why use DCS files at all? Modern workflows do not require postscript, so my question to you would be, why not use PSDs with spot channels? If you do the research, you will find a multitude of problems with DCS and DCS2 files with any software newer then 10 years or so. Maybe I'm not understanding your problem.
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: DCS2 file using vector workflow

Reply #2
Using DCS2 because that is what the printer requires, trapped DCS2. They will not except any other file format.

Re: DCS2 file using vector workflow

Reply #3

Using DCS2 because that is what the printer requires, trapped DCS2. They will not except any other file format.
Switch it to multichannel and save as .eps
"I'm not addicted to cocaine. I just like the way it smells."
– Richard Pryor

“Always do sober what you said you'd do drunk. That will teach you to keep your mouth shut.”
― Ernest Hemingway

Re: DCS2 file using vector workflow

Reply #4


Using DCS2 because that is what the printer requires, trapped DCS2. They will not except any other file format.
Switch it to multichannel and save as .eps


I doubt that will work, either. It used to, but modern software today usually does what he described above.

A printer that requires trapped DCS2 files? Who's running that place, Fred Flintstone?
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: DCS2 file using vector workflow

Reply #5
If it's raster art and it's a duotone, does it really need trapping? I think not... maybe if it had objects butting up against one another that were all of one color it should trap... but a true raster image shouldn't need trapping.
"I'm not addicted to cocaine. I just like the way it smells."
– Richard Pryor

“Always do sober what you said you'd do drunk. That will teach you to keep your mouth shut.”
― Ernest Hemingway

Re: DCS2 file using vector workflow

Reply #6

We do not have support so I am reaching out to this forum in the hope that someone here can lead me in the right direction. Currently running Nexus 9.0.3. I have 2 workflows that create DCS2 files, one raster and the other vector. Problem I am having is the vector workflow does not hold the spot color, but the raster the raster workflow does. The Assemble DCS and Merge DCS modules in each workflow are identical. The raster workflow only creates the DCS2 file. The vector workflow also creates a PDF (high and low res), Artpro file and PSTI files along the DCS2. All the other files produced in the in the vector workflow retain the spot color. If I highlight the Assemble DCS and Merge DCS modules that the actual file is going through it still shows the spot color listed in the separations, but ultimately the spot color converts to process in the DCS2. Any clue where this may be going wrong?



A printer that requires trapped DCS2 files? Who's running that place, Fred Flintstone?
Maybe I misunderstood as well. Is this a buy-out (subbed to another shop) or is it your imagesetter/workflow that requires this kind of file? It sounds really old school, like you're going to output high-quality lasers and shoot it to film... but a good cameraman can spread for trap when shooting to film.
"I'm not addicted to cocaine. I just like the way it smells."
– Richard Pryor

“Always do sober what you said you'd do drunk. That will teach you to keep your mouth shut.”
― Ernest Hemingway

Re: DCS2 file using vector workflow

Reply #7
Using today's methods, I don't really know how to get a DCS2 file to run properly in almost all apps. Believe it or not, Quark is about the only one that would handle DCS2 files correctly, however, that was back in version 5. PSDs are about the only way to maintain spots out of Photoshop, any other way is archaic and does not work like it used to, multichannel or not.
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: DCS2 file using vector workflow

Reply #8
in Prinergy world, DCS2 = output and refine using OPI
Does not answer the question I think, though.
vdp donkey
gmc inspire • sarcasm while you wait

Re: DCS2 file using vector workflow

Reply #9
Does anyone still use OPI? What would be the need with RIPs being as fast as they are today?
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: DCS2 file using vector workflow

Reply #10

Does anyone still use OPI? What would be the need with RIPs being as fast as they are today?


I only use it with DCS2 placed art as it does not come out correctly without - at least I've never been able to get it to work.  Co-worker dezinger uses it for big graphics heavy books as it gets the application finished with export a lot quicker, letting the rip do all the file moving. Net processing time is slower but he's out of the file and into another one quicker because the export goes quicker. I suppose not much of an issue with cs5+ but that's what he do.
vdp donkey
gmc inspire • sarcasm while you wait

Re: DCS2 file using vector workflow

Reply #11
Is his name Fred Flintstone? :laugh:
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: DCS2 file using vector workflow

Reply #12

We do not have support so I am reaching out to this forum in the hope that someone here can lead me in the right direction. Currently running Nexus 9.0.3. I have 2 workflows that create DCS2 files, one raster and the other vector. Problem I am having is the vector workflow does not hold the spot color, but the raster the raster workflow does. The Assemble DCS and Merge DCS modules in each workflow are identical. The raster workflow only creates the DCS2 file. The vector workflow also creates a PDF (high and low res), Artpro file and PSTI files along the DCS2. All the other files produced in the in the vector workflow retain the spot color. If I highlight the Assemble DCS and Merge DCS modules that the actual file is going through it still shows the spot color listed in the separations, but ultimately the spot color converts to process in the DCS2. Any clue where this may be going wrong?


Does the original file have transparency in it? It could be when it is flattened it converts the spots to process. Old processes like this really do not understand a combination of transparency and spot colors. I haven't used Nexus for a couple of years now so I'm not going to be much help. G-Town will probably chime in tomorrow. I think he is about the last Nexus user around here.
Mac OS 10.12 Sierra | Prinergy 7.5 | Adobe Creative Cloud 2017 | Two Luscher XPose 160 CTP units

Prepress: One who does precision guess work based on unreliable data provided by those of questionable knowledge.

Re: DCS2 file using vector workflow

Reply #13


We do not have support so I am reaching out to this forum in the hope that someone here can lead me in the right direction. Currently running Nexus 9.0.3. I have 2 workflows that create DCS2 files, one raster and the other vector. Problem I am having is the vector workflow does not hold the spot color, but the raster the raster workflow does. The Assemble DCS and Merge DCS modules in each workflow are identical. The raster workflow only creates the DCS2 file. The vector workflow also creates a PDF (high and low res), Artpro file and PSTI files along the DCS2. All the other files produced in the in the vector workflow retain the spot color. If I highlight the Assemble DCS and Merge DCS modules that the actual file is going through it still shows the spot color listed in the separations, but ultimately the spot color converts to process in the DCS2. Any clue where this may be going wrong?


Does the original file have transparency in it? It could be when it is flattened it converts the spots to process. Old processes like this really do not understand a combination of transparency and spot colors. I haven't used Nexus for a couple of years now so I'm not going to be much help. G-Town will probably chime in tomorrow. I think he is about the last Nexus user around here.


Hey it's not like I'm still rocking a Scitex VIP rip  :whip:

DHG upload your workflow to sendfile, or sendspace or one of them damn places and I'll take a look.