ronnyb

Thanks for looking into it @NathanC That’s odd as the performance degradation wasn’t noticeable for a while with that layer active…. I guess as the file got more complex it uses up more resources…. I’ll keep a copy of that image+live filter deactivated in backup layers group, and simply Merge that filter with the image in the working layer… Again, much appreciated 🙏

Thanks @NathanC I just uploaded the .package file This is a client file. Please delete after use...

That’s clever @MikeTO i bet you have a lot of these kinds of tips and best practices…

Yes @GarryP Yes @MikeTO but mainly for performance. My M1Max is crawling slowly with my latest files and I need all the performance I can get… maybe it is a memory leak issue, I will have to reboot and see if it helps… but my layouts use quite a bit of FX, blend modes, transparency, etc… @Return can you give a little more insight as to how you would set up States for performance? I set up 2 Captured States that toggle the image objects on and off…

It would be very beneficial if Publisher and Designer enabled tagging placed files of any type as FPO (for position only) and have the apps display a translucent FPO visual overlay / icon type / etc on said placed (linked or embedded) files. Publisher, could offer more granular control by enabling user-defined tagging categories, so assets could also be designated a step within a user-defined, multi-step production process, and assets can be tracked along that progression. This would prevent many mis-steps in the production process by visually indicating what assets are not finalized —and in Publisher, with finer control, where along the user-defined production process each assets stands... For example, FPO is a general category that indicates the asset is not ready for final output. Within that category, the asset can be tracked along a user-defined production process via tagging. If it's a photo, it usually has to be cleaned up, color corrected, approved, etc before it can be Green Lighted for final output/production. The Red, Yellow, Green light metaphor would be great visual metaphor for tracking that process. Thanks for your consideration and everything you do!

For the sake of working with image-heavy documents and for visual simplicity when doing rough layouts with said heavy images, it would be great have a View Mode similar to Hide Effects called Hide Images that would simply display images as a 50% grey. Thanks for your consideration and all you do!

I can send files to a private upload link for you to check out... it was taking about 5 seconds to redraw changes to screen...

SVG format developed as an onscreen vector format, so it has no reference to units beyond pixels....

Oh no! Not the Logs of Perdition! (where bug reports wonder aimlessly in eternal damnation....)

Yes, any changes to the object works in forcing the re-render, except actually changing the content of the Art Text object....

Affinity's display rendering doesn't work/update in the canvas when changing the text inside and Art Text object inside a Subtract Compound Object (Live).

My Godox studio lights have a color temperature range I can set, from 2700° which is very warm/yellowish white to 9000° which is cold, blueish white...

This is confusing and counterintuitive. In the photo context, lower K = warmer COLOR temp and higher K = cooler COLOR temp. Its called COLOR temperature, not energy or heat temperature, for a reason… I took astronomy courses in college back in the day, and in fact, stars that burn (HEAT) cooler in Kelvin temp have LOWER color temperatures (warm color tones) than stars that burn HOTTER in temperature and emit cool color tones (blues). This is backwards in Affinity. No need to reinvent the wheel….

It’s funny, I thought we were using a photo RAW Developer to edit COLOR temperature, not a “physics simulator” adding heat temperature to an image…. In the photo context, lower K = warmer COLOR temp and higher K = cooler COLOR temp. Its called COLOR temperature not energy or heat temperature for a reason. @Ron P. When I took astronomy courses in college back in the day, we learned the stars that burn (HEAT) cooler in Kelvin temp have LOWER color temperatures (warm yellowish color tones) than stars that burn HOTTER in temperature and emit cool color tones (blueish whites). This is backwards in Affinity. No need to reinvent the wheel….

We don’t need to get into astrophysics or anything other than your camera’s white balance setting, or your light’s color temperature. It’s ALWAYS warmer light is lower degrees kelvin, and cooler lights are higher degrees. We are not running a physics simulation, I just want my RAW developer sliders to match my light’s and cameras color temperature settings… Maybe a preference/Setting for the Raw developer ?

When using Sony .ARW files, the white balance slider is incorrectly displaying degrees Kelvin; it shows cooler temperatures having lower Kelvin values than warmer temperatures. This is backwards. Lower temperatures are warmer/yellower than higher temperatures, which are bluer, colder. Thanks for taking a L👀k at this and all you do!

Never a good idea to build on shaky foundation....

I don’t want to see any new features in future updates until basic bugs like these are resolved…. It’s not like Sony is some obscure camera brand……. 🤷‍♂️

@Old Bruce Maybe we can get the bug bumped in HQ’s CQC (Central Quantum Computer) after the pilot/trailer of Walt wearing Apple Vision Pro headset and an Ironman Jet-suit while analyzing with JarviSiri AI the bugs that should have been fixed months ago….?

@walt.farrell: [RADIO STATIC] Operator, this is Zenith Phoenix number 43781, I picked up some unresolved activity in the beta forums, swooping in for recon; seeking permission to engage if necessary, over...." Nottingham/Australia HQ: [RADIO STATIC] Permission to engage and neutralize with all disposable assets granted, Zenith Phoenix 43781. Send them on their way, over...."

Thanks Walt, that was quick! I sorta imagine you as a high flying drone, keeping watch over the forums... 👁️ 🛰️ 👁️

Still not resolved for Sony A7Cii........

And Sony A7Cii

When I drag 2 .HIF images into latest AD beta, it ignores the portrait orientation and doubles up part of the same image as landscape, almost as if it's confused by the first image's orientation...? 2 sample .HIF files attached below. This is what the error looks like: Finder Quickview on left, ADesigner on right: DSC01524.HIF DSC01536.HIF

Nice workflow, and thanks for circling back and sharing your discovery and use case with the community!