Dealing with screened 1 bit tiffs in ArtPro to Nexus

[schenkadere]

I'm curious how anyone is dealing with this. I usually go back to the supplier and ask for a hi res pdf, but there are times they are reluctant.

We do all our stepping in ArtPro and print to various Nexus workflows.

I saw in one post that someone uses DotSpy to combine the tiffs and create a link...good idea...does this work out ok? Any other creative solutions?

 

[Toweri]

Theoretically it sounds a viable option. DotSpy generates an EPS link file that can be utilised on S&R.
One must make sure, though, that the resolution of the 1-bit Tiffs is obeyed on your Nexus workflow. Otherwise the 1-bit files will be interpolated to the new resolution, causing Moiré that is hard to notice on single separations - but will definitely show up on print...

 

[schenkadere]

Theoretically it sounds a viable option. DotSpy generates an EPS link file that can be utilised on S&R.
One must make sure, though, that the resolution of the 1-bit Tiffs is obeyed on your Nexus workflow. Otherwise the 1-bit files will be interpolated to the new resolution, causing Moiré that is hard to notice on single separations - but will definitely show up on print...

Ok...but will Nexus recognize the combined, screened tiff as a hi res? I have used links to OPPO, but never tiff.

 

[Toweri]

Ok...but will Nexus recognize the combined, screened tiff as a hi res? I have used links to OPPO, but never tiff.

I am not a specialist in PS program code, but to me this appears to be quite similar to the Nexus Link files you refer to.

The file DotSpy generates, is not a merged hires file (and you don't even need to 'Merge Windows' on DotSpy.) The EPS generated by DotSpy is quite like a regular Link file generated by your Nexus WorkFlow.

See this code snippet from the EPS link file I created on DotSpy from a set of Nexus 1-bit Tiffs as a test:

%PCCProxyType: Separated TIFF
%PCCLink: (Cyan) (J31P001_R_Cyan.tif)
%PCCLink: (Magenta) (J31P001_R_Magenta.tif)
%PCCLink: (Yellow) (J31P001_R_Yellow.tif)
%PCCLink: (Black) (J31P001_R_Black.tif)
%PCCLink: (PANTONE 192 C) (J31P001_R_PANTONE 192 C.tif)
%PCCLink: (PANTONE Reflex Blue C) (J31P001_R_Reflex.tif)
%SSiBoundingBox: 0 0 1842.510 1417.320
%%CropBox: 0 0 1842.510 1417.320
%%EndComments
{
/PCCReplaceImages where {pop PCCReplaceImages} {false} ifelse {
    <<
        (Cyan) (J31P001_R_Cyan.tif)
        (Magenta) (J31P001_R_Magenta.tif)
        (Yellow) (J31P001_R_Yellow.tif)
        (Black) (J31P001_R_Black.tif)
        (PANTONE 192 C) (J31P001_R_PANTONE 192 C.tif)
        (PANTONE Reflex Blue C) (J31P001_R_Reflex.tif)
    >> PCC_Separated_TIFF_Helper
}

The references to the separation 1-bit Tiff files (J31P001_R_[separation].tif) are relative paths. So the hires files must be moved to the Nexus "Pages" folder, as selected in Nexus Preferences. Nexus will then detect the image replacement function in the link file, and insert the hires Tiff data into the PostScript stream - just as it does with the OPPO files.

I tested this with DotSpy 4.5 rev 1, ArtPro 9.6.3 and Nexus 9.5.5 on Mac platform and it works just fine!
Please be aware, this doesn't seem to work with any flavor of PDF exported from ArtPro and Nexus PDF Rip. (Or I just didn't know how to do it properly... )

(Here I feel I must include my motto and Standard Disclaimer(tm) : "I have been known to be wrong." If any of you PS gurus out there disagree with any of this, please feel free to correct me!)

 

[schenkadere]

I am not a specialist in PS program code, but to me this appears to be quite similar to the Nexus Link files you refer to.

The file DotSpy generates, is not a merged hires file (and you don't even need to 'Merge Windows' on DotSpy.) The EPS generated by DotSpy is quite like a regular Link file generated by your Nexus WorkFlow.

See this code snippet from the EPS link file I created on DotSpy from a set of Nexus 1-bit Tiffs as a test:

%PCCProxyType: Separated TIFF
%PCCLink: (Cyan) (J31P001_R_Cyan.tif)
%PCCLink: (Magenta) (J31P001_R_Magenta.tif)
%PCCLink: (Yellow) (J31P001_R_Yellow.tif)
%PCCLink: (Black) (J31P001_R_Black.tif)
%PCCLink: (PANTONE 192 C) (J31P001_R_PANTONE 192 C.tif)
%PCCLink: (PANTONE Reflex Blue C) (J31P001_R_Reflex.tif)
%SSiBoundingBox: 0 0 1842.510 1417.320
%%CropBox: 0 0 1842.510 1417.320
%%EndComments
{
/PCCReplaceImages where {pop PCCReplaceImages} {false} ifelse {
    <<
        (Cyan) (J31P001_R_Cyan.tif)
        (Magenta) (J31P001_R_Magenta.tif)
        (Yellow) (J31P001_R_Yellow.tif)
        (Black) (J31P001_R_Black.tif)
        (PANTONE 192 C) (J31P001_R_PANTONE 192 C.tif)
        (PANTONE Reflex Blue C) (J31P001_R_Reflex.tif)
    >> PCC_Separated_TIFF_Helper
}

The references to the separation 1-bit Tiff files (J31P001_R_[separation].tif) are relative paths. So the hires files must be moved to the Nexus "Pages" folder, as selected in Nexus Preferences. Nexus will then detect the image replacement function in the link file, and insert the hires Tiff data into the PostScript stream - just as it does with the OPPO files.

I tested this with DotSpy 4.5 rev 1, ArtPro 9.6.3 and Nexus 9.5.5 on Mac platform and it works just fine!
Please be aware, this doesn't seem to work with any flavor of PDF exported from ArtPro and Nexus PDF Rip. (Or I just didn't know how to do it properly... )

(Here I feel I must include my motto and Standard Disclaimer(tm) : "I have been known to be wrong." If any of you PS gurus out there disagree with any of this, please feel free to correct me!)

Yes...that makes sense. I attempted to create a link using Nexus, but obviously, it created individual links. I imagine the only way to succeed in his workflow is to have DotSpy, giving me the ability to merge the tiffs to map the colors so that the link .eps will collect that information. I guess I'll need to purchase a seat to simply to map the individual tiffs and export a link. Does that sound correct? It does to me, LOL.

 

[Toweri]

I guess I'll need to purchase a seat to simply to map the individual tiffs and export a link. Does that sound correct? It does to me, LOL.

I would agree. Currently it may be your best option.
While you could merge the 1-bit seps on Photoshop (depending on the compression used), it would produce huge uncompressed composite file, making working with it quite tough and slow...

I wish you success.

 

[schenkadere]

I would agree. Currently it may be your best option.
While you could merge the 1-bit seps on Photoshop (depending on the compression used), it would produce huge uncompressed composite file, making working with it quite tough and slow...

I wish you success.

Yes...the Photoshop option doesn't always work because of the compression and that it is ridiculously huge, slow and cumbersome.

DotSpy it is!

Thank you for your help!

 

[schenkadere]

Order processed.

 

[schenkadere]

Works perfectly...DotSpy was the answer. Stick the individual tiffs in the Links &Pages, step the .eps link from DotSpy in ArtPro and print to the queue...voila...piece of cake. No more 1 bit tiff problems.

 

[Toweri]

Glad to be of assistance!

 

[colinobrien]

it is possible to merge the tiffs, apply their original colour and resave it as a composite PDF with out the Artpro expense.

Screens Master File Editor and Truflow. it takes about 5 mins to generate one.

 

[schenkadere]

it is possible to merge the tiffs, apply their original colour and resave it as a composite PDF with out the Artpro expense.

Screens Master File Editor and Truflow. it takes about 5 mins to generate one.

We've had an ArtPro/Nexus workflow for many years, so it was no big shake...DotSpy was a good fit...one seat everyone can share with the new licensing...it's a handy tool.

I am curious about the products you mention though. We don't currently have a software to step PDF's, as we use ArtPro for all our step and repeat.

 

[david]

Swiss Knife for 1 bit TIFF files

Swiss Knife for 1 bit TIFF files

You might find some interesting capabilities with TIFF Pager. It has the ability to combine TIFF files into a variety of production formats - including PDF and online Zoomable Proofs.

PDF files will have the screened data present and set to the correct color space. Take a moment and check out some of the many features


avid Lewis

 

[Rock Lobster]

I have tried this, merging files with DotSpy, stepping the Link EPS in Artpro and ripping with Nexus, but it always seems to be re-screening the TIFFs!!! How have you gotten around this?

 

[schenkadere]

I have tried this, merging files with DotSpy, stepping the Link EPS in Artpro and ripping with Nexus, but it always seems to be re-screening the TIFFs!!! How have you gotten around this?

That's never been an issue...just point the workflow to the hi res tiffs on your Nexus server and it will pull the screened data.

 

[Rock Lobster]

I'm not sure what I'm doing wrong... it must be a workflow thing. I'm pretty sure that it is pulling the high-res tiff data, since the edges are not all bitmappy and staircased like they would be it it was getting preview-resolution date, but it is definitely rescreening. I'm attaching a before-and-after screen capture.
Any thoughts? I'm thinking Nexus wants to rescreen because it is seeing these as EPS and not as 1-bit TIFF, but I don't see anything in the workflow that would tell it otherwise.

 

[Rock Lobster]

Actually, I think I figured it out. Earlier in this thread someone mentioned about matching the resolution. That seems to be the case here. It rescreens it if there is a resolution mismatch.
Also, it only seems to work using the "Assemble Separation" task rather than the "Assemble Screened TIFF" task. They look pretty much identical, though.
Thanks for the quick response.

 

[schenkadere]

Actually, I think I figured it out. Earlier in this thread someone mentioned about matching the resolution. That seems to be the case here. It rescreens it if there is a resolution mismatch.
Also, it only seems to work using the "Assemble Separation" task rather than the "Assemble Screened TIFF" task. They look pretty much identical, though.
Thanks for the quick response.

I use Assemble Screened TIFF without a problem...but the yes...the mismatch sounds like your issue...glad you figured it out.

 

[pp411]

Whenever we have gotten Copydot files, which is pretty much the same as a 1-bit tif., what I have done in the past is place each tif in Adobe Indesign. I make sure to color the tiff the appropriate color (Cyan, etc.), and set it to overprint. Then I either print directly to a Screened WF, where it assembles the screened tifs, which produces a link for me. If you can't print directly to Nexus, you can always save to a postscript file. Dotspy is of course ideal, but this does in a pinch if you don't have it.