Live filters messes with file size.

[GabrielR922]

Hello everyone! 

I have a file with multiple brightness/contrast, gradient map and hsl shift filters.
For some reason some of them are just huge in pixel size.


Whenever i have to do something that changes the file pixel size, it's extremely slow, also, I can't export usign selection only.
Also another issue:
Select Lower Framing -> ctrl + c -> file - new from clipboard.
Pixel size will be the size of the layer.

Any way to clip/resize/crop this ?
 

bigpixelsize.afphoto

[NotMyFault]

A rasterize and trim applied to the pixel layer (bottom) solves the issue.

Do you remember the exact steps how you created this file?

The wrong export (when using selected area option) seems like a bug.

Did you use the move tool to stretch the pixel layer (or reduce its size after painting)?

[carl123]

3 hours ago, GabrielR922 said:

Select Lower Framing -> ctrl + c -> file - new from clipboard.
Pixel size will be the size of the layer.

If you copied your adjustment layers from a much larger document to the current one, this will cause the effect you are seeing

Not sure if that should be considered a bug or not

[NotMyFault]

3 hours ago, carl123 said:

Not sure if that should be considered a bug or not

Definitely a bug in my view. The adjustment layers have no inherent mask, and rasterizing the pixel layer solves the issue (despite not being stechend).

Affinity has more bugs where layers „remember“ wrong DPI or size/position data and start to act erratic. 
If this is not rated a bug I don’t know what criteria are used.

[HCl]

.

[GabrielR922]

4 hours ago, NotMyFault said:

A rasterize and trim applied to the pixel layer (bottom) solves the issue.

Do you remember the exact steps how you created this file?

The wrong export (when using selected area option) seems like a bug.

Did you use the move tool to stretch the pixel layer (or reduce its size after painting)?

Hello!
No, it doesn't solve the issue, if you follow your steps and copy the group and do a new from clipboard, the result is exactly the same.

Parts of this file/filters were created by another person, I just bought the asset pack and used parts of it. Just checked the original file and the live filters layers are in range of the image size.

The pixel layers were probably resized down a bit.

[GabrielR922]

13 minutes ago, Return said:

Workaround:
Drag the pixel layer outside of the group and have it be under the adjustments group.
Choose selection area instead of selection only in the export settings.
Or create a (vector) mask for the pixel layer>keep this selected and use selection area in the export settings.

Thanks for the workaround, yet selection area is not a good option imo.

The best workaround, or maybe right way to make it at all ?
Go from this:

To this:

To achieve this you have to drag the live filter layers IN the group layer.

This actually solves ALL the issues I had.

If you select the live filter and try export just it (for debug reasons), it still shows an insane high number though:


So I do believe this is a bug.

Edited November 7, 2024 by GabrielR922

[NotMyFault]

18 hours ago, GabrielR922 said:

The best workaround, or maybe right way to make it at all ?

That does not solve the issue. I still get a wrong export size, just smaller than 32000 px so it is faster and does not trigger the warning.

But you are right that the HSL adjustment layers is the culprit.

it has a stretched DPI in x direction by factor 4. this might happen if it was pasted from another document where wrongly memorized size values (no longer visible in UI as inherent mask is clears/filled).

• add a new pixel layer, paint a stroke of defined size e.g. from top bot bottom 
• repeat with a new pixel layer, but this time nest the HSL layer in child position
• use Move Tool and inspect x/y size of layers. The size in x position differs severely 

so nuke the HSL layer and create a fresh one. This is the only way to solve the issue

[NathanC]

Apologies for the delayed reply, I can confirm i've replicated and logged this issue with the developers.