Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

P: Split channels on large CMYK files gives glitches when converted to bitmap or saved as tiff

Explorer ,
Mar 31, 2016 Mar 31, 2016

This has happened to me on CS6 and now with CC on OSX running El Capitan. When I split channels on a large CMYK file the resulting files look fine, but when I convert them to bitmap or save them as a grayscale .tiff or .psd I wind up with glitched files. This does not happen if I cut and paste the channel into a new grayscale file, so I think it is a bug in the split channels code. Original CMYK file was 7393x5700 pixels

BITMAPPED WITH A HALFTONE SCREEN




SAVED AND REOPENED AS A GRAYSCALE TIFF


ORIGINAL IMAGE AFTER SPLITTING CHANNELS ( BLACK CHANNEL )

Bug Fixed
TOPICS
macOS , Windows
1.6K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 21, 2016 Jun 21, 2016
Translate
10 Comments
Adobe Employee ,
Mar 31, 2016 Mar 31, 2016
Does this happen consistently (100% of the time) with all files or this particular file?
Translate
Report
Adobe Employee ,
Mar 31, 2016 Mar 31, 2016
I wasn't able to reproduce this creating my own CMYK file, splitting the channels and saving a tiff of each file using the default settings in the Tiff options dialog,
Translate
Report
Explorer ,
Mar 31, 2016 Mar 31, 2016
It only happens if the CMYK file is not flattened and split channels creates a transparency channel. I can create a new file the same size and there is no problem. Double click the background layer to make it Layer0, and the glitch manifests. I flattened the original file and now there is no glitch.
Translate
Report
Adobe Employee ,
Mar 31, 2016 Mar 31, 2016
OK. The sounds like it might be the secret sauce. Let me try that.
Translate
Report
Explorer ,
Mar 31, 2016 Mar 31, 2016
I can also send you the file I used if you can't replicate the bug, but I was able to get it to happen with a file I created in photoshop.
Translate
Report
Adobe Employee ,
Mar 31, 2016 Mar 31, 2016
That was the secret. I have a repro case now. Engineering will look into it. Thanks for your help!
Translate
Report
Explorer ,
Mar 31, 2016 Mar 31, 2016
That's great! Also easy to work around now that I know.
Translate
Report
LEGEND ,
Mar 31, 2016 Mar 31, 2016
Ah, yeah, that is something that wasn't mentioned in previous reports.
And that tells me where the error might be...
Translate
Report
LEGEND ,
Mar 31, 2016 Mar 31, 2016
Yep, those steps (transparency, large image) were both important.
I've implemented a fix for this in the next major release of Photoshop.
Translate
Report
Adobe Employee ,
Jun 21, 2016 Jun 21, 2016
LATEST
Chris fixed this issue fixed fixed this issue in the CC 2015.5 upgrade released today: https://blogs.adobe.com/photoshop/2016/06/adobe-releases-major-photoshop-cc-update-today-and-announc...
Translate
Report