RGB Fail

[Joe_UrbanStudio]

Hi,
I am using Enfocus Switch Spring 2024. I have a workflow that delivers files to a GMG ColorProof system.
I would like to preflight for RGB files and have them fail and go into the problem files folder.
We do have RGB workflows on the GMG so I want to fail RGB files where the file name has a certain suffix. (ex: _Gr2013, _F39)
How would I configure something like this? I have set up an RGB Pit Stop Preflight profile to fail RGB. I am thinking an action set that will see the suffix and fail the file, but let the RGB without those suffixes get through.

[freddyp]

I would not let the job end up in Problem jobs, because you still want to continue with it, you just want to do different things.

The first thing you do is preflight the file for RGB. If it fails, it follows the error connection out of PitStop Server into a folder, and from that folder you add 2 outgoing connections to 2 other folders. On one of the connections you add a "Condition with variables" that checks for:
[Job.NameProper:After="_"] equals Gr2013
OR [Job.NameProper:After="_"] equals F39
OR etc.
and on the other one you use "All other jobs".

Instead of using multiple conditions, you can also use just one with a regular expression:
[Job.NameProper:After="_"] matches Gr2013|F39|etc

[Joe_UrbanStudio]

Thank you. What I am hoping for is that eventually I will put a Slack app in and it will slack the channel that there was an RGB file dropped. The producers would then convert the file to the proper color space and redrop the file.

I have set up the Preflight profile, and it fails RGB.. I just do not how to to filter.
We use _ARGB so that when GMG picks it up it applies the correct RGB proof Standard. So any RGB file that doesn't contain _ARGB would fail and _ARGB would go on.

I still need cmyk files with Gr2013|F39|etc to go through.

[freddyp]

Screenshot 2024-12-05 at 10.02.52.png (24.85 KiB) Viewed 15241 times

The CMYK files come out of PitStop Server through a different output than the RGB files, if you set the "Output level" correctly of course.
The condition for the "bad" RGB files is from the folders RGB to Not OK for GMG, and the connection from RGB to OK for GMG has to be set to "All other files".

[Joe_UrbanStudio]

Thanks for your help. My workflow is a little more complicated and I think this may be over my head for the time being.
We are dropping both PDF and tiff files. We are using Image Magic to put a "PDF Wrapper"
on them so that Pitstop server can do certain things to them (Like resizing).

[loicaigon]

Hi

I am interested in knowing more about those TIFF files. We recently extended input file to images so that PNG and JPG files can be sent directly to PitStop Server. We considered TIFF for a future release. Would be nice to see how interesting it would be for you.

Let me know

Loic

[Joe_UrbanStudio]

What would you like to know? We generally output PDFs or Tiff files. The Tiff files go through ImageMagic to get a PDF wrapper so that Pitstop Server can process them.I just cant figure out how to fail RGB files that the name doesn't include _ARGB in the file name.

[freddyp]

I just cant figure out how to fail RGB files that the name doesn't include _ARGB in the file name.

That is exactly what the flow illustrates of which I added a screenshot: PitStop separates files with RGB from files without RGB by using the output level of the outgoing connections, and then the RGB files with certain characters in the file name are separated by files that do not by using conditions on the outgoing connections from the folder named "RGB".

doesn't include _ARGB in the file name

means the condition should be:
[Job.NameProper] Does not contain _ARGB