Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjustment Layers Inconsistent Export #159

Open
IgoSplashman opened this issue Aug 18, 2021 · 1 comment
Open

Adjustment Layers Inconsistent Export #159

IgoSplashman opened this issue Aug 18, 2021 · 1 comment

Comments

@IgoSplashman
Copy link

IgoSplashman commented Aug 18, 2021

In my projects I often use adjustment layers as top layers with a bunch of groups below them, and I was hoping that your script would automatically apply them to the groups while exporting.
However, I noticed that only certain types of adjustment layers get applied, while others get exported as separate images. Example: "Curves" and "Levels" layers get applied, while "Vibrace" does not.

I made a few tests and here are my results:

Color Fill: separate image
Gradient Fill: separate image
Pattern Fill: separate image

Brightness/Contrast: applied
Levels: applied
Curves: applied
Exposure: separate image

Vibrance: separate image
Hue/Saturation: applied
Color Balance: applied
Black & White: separate image
Photo Filter: applied
Channel Mixer: applied
Color Lookup: separate image

Invert: applied
Posterize: applied
Threshold: applied
Gradient Map: separate image
Selective Color: applied

I was wondering, if the rest of these layers could get implemented into the exporting process as well, or is it due to a Photoshop limitation that it doesn't work?

@IgoSplashman IgoSplashman changed the title Adjustment Layers Exported Inconsistent Adjustment Layers Inconsistent Export Aug 18, 2021
@antipalindrome
Copy link
Owner

Thanks for this bug and all the information you provided. I don't know off the top of my head where this limitation is coming from or why Photoshop is handling the cases like this. My assumption is that it has something to do with how it classifies layers under the hood.

I'm unsure how complicated of a fix this might be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants