![]() These ColorSync AppleScripts can be saved as an application, then all you need to do is drag and drop the c2 embedded files onto the application to process them. Prepression: ColorSync AppleScript Archive I personally prefer the options below, as one does not have to open and resave the JPEG data (lossy), one can hopefully work directly on the ICC metadata without affecting the image data.Ī Mac OS approach could be to use an AppleScript ColorSync to process the JPEG files, either removing the ICC profile or embedding sRGB instead of the offending c2 ICC profile: ![]() One could then use a script or action to batch process the files selected in Bridge. In Adobe Bridge, you can do a “find” command and use the following criteria “Color Profile Equals c2” and “Document Type Equals JPEG file” with a “Match if all criteria are met” result. ![]() There are numerous work arounds if this is not a script related issue: By the time the operator goes to place the JPEG, the problem should not be there.Īnurag, on CS6 Mac OS 10.9.5 I don’t have a problem placing a Facebook JPEG with an embedded “c2” ICC profile – so I don’t know what the difference is with this unknown script. The beauty of using a ColorSync AppleScript and a Folder Action (watched/monitored folder) is that the Mac OS will remove or assign a different profile to the image automatically when the image is in the folder, without operator intervention. Either at the server level or local workstation level. If you don’t have a colour server or other process normalising the colour content upstream, then ColorSync AppleScripts and Automator Folder Actions are a great entry level solution. Have you looked into colour settings, perhaps turning off RGB profiles in colour management policies to see if this has an effect? Do you get the same issue when manually placing or updating – or only when using your unknown script? I can place a JPEG with c2 profile or place say an sRGB JPEG and then relink to a C2 profile without issue, however this is using the GUI – your script may be doing something else. You can send me a PM and I can look offlist at one of your images with an embedded c2 profile in CS6, however that will not really resolve anything at your end if you use CS5 and CC14/15. ![]() I was hoping someone on the forums (particularly someone at Adobe) had some thought on it. ![]() Since we don't really understand the root cause that causes AI to fail on C2, we can't really fix the bug at source and having to explicitly edit color profiles out of images seems like a clumsy solution. I also don't know if facebook has used different versions of c2 over time, but any time we encounter this problem, it can be directly traced to the c2 profile. Doing a pre-screen in illustrator using javascript may be an option, but we'll have to do it using exiftool or imageoptim since opening the image in illustrator is enough to cause the : It is interesting that you are able to open it in CS6 (which I have not tried yet). Doing it in photoshop is far more painstaking.ĭoing a pre-screen for the C2 is really the only option that remains, but we have a complex image import pipeline (before it gets to the illustrator step) and adding a step to it has met with some resistance. We get rid of the profile on all the images in batch using something like ImageOptim or exiftool on the command line. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |