PetervL

Working fine for me too, HA is on

Transform origin works in another way

2024-04-21 08-22-58.mp4    

Don't worry too much about this guys, in a few years the whole planet will speak English anyway.

A temporary but quick work around would be the Adobe DNG converter. This way your Sony RAW files can be converted to DNG files which are compatible with Affinity Photo.
Success, Peter.
 

The support for RAW images comes from the LibRAW Open Source project, so your camera will be supported after LibRAW has implemented it, and then made it available in their GitHub repository, and Serif has made an update to the Affinity apps to include that level of LibRAW.
Mac users have an additional choice of using Apple's RAW engine, which sometimes supports new cameras sooner, but choosing that engine loses some capabilities such as linked RAW layers.
 

A temporary but quick work around would be the Adobe DNG converter. This way your Sony RAW files can be converted to DNG files which are compatible with Affinity Photo.
Success, Peter.
 

A temporary but quick work around would be the Adobe DNG converter. This way your Sony RAW files can be converted to DNG files which are compatible with Affinity Photo.
Success, Peter.
 

@walt.farrell I'm also not able to replicate this. Not on my desktop (i7) nor on my laptop (R7). Just for your information I'm running windows 11 and MSI/EXE on both machines.

I agree. It's in their interest to always plan mandatory refinements. They should come after the new stuff has been laid down and then it should just be a lengthy period knocking out bugs and working on usability/polish. It's not like there's a shortage of people willing to comment on what best needs/doesn't need adjustment. Most reasonable people expect software to encounter bugs during development. This is fine. As long as it's addressed at some point by the end of that point release's development.

The issue currently is we have to wait for potential future updates for fixes to bug(s) that are breaking/impacting our own workflows. Even if the bug(s) are fixed in a future update, some new bug(s) are introduced that further impact workflow and some go unaddressed. Perhaps it is slightly better than before or maybe it is worse. Either way, the user experience is never really improved for those users as impediments become the norm and they feel unrewarded for their patience. In this way, trust is constantly being chipped away at and leads to chronic complaints. I feel like a refinement cycle would nip much of that in the bud and help build back trust. Hopefully they listen. I generally enjoy using their software (when I'm not encountering the issues) and would like to see how things will progress further.

Honestly, I'd much rather Serif focus on fixing the many new and long-standing bugs in 2.2 before adding anymore features. Having a shiny new blend tool {or insert your feature request here} which will probably add new bugs, while still having to deal with countless existing bugs and workarounds doesn't exactly fill me with anticipation. As it is I keep seeing comments around social media, the forums, and the web on how folks are getting increasingly frustrated with the bugginess of the Affinity suite. You really don't want "buggy" to be the first thing that comes to mind when somebody mentions Affinity.
Serif please focus on getting the next few upcoming 2.x releases into a stable suite of apps that new and existing users can rely on for years to come.

We have now released beta build 2.2.1.2075, which is Release Candidate 3 of the 2.2.1 patch
It includes the fixes listed above and has updated Help files in all languages, but is otherwise the same as 2.2.1.2063.
We think it is important to get these fixes above released as soon as possible, so 2.2.1.2075 is to be treated as a Gold Master (final release candidate) that we hope can be released next week.

Here's a list of some of the bugs which have been fixed in the beta build 2.2.0.2005, which is Release Candidate 3
(fixes since the post above for 2.2.0.1994)
Please only reply in this forum to comment on any fixes which are in this list (in particular to let us know if you notice that something we say is fixed isn't!) To report any new bugs please do that against the relevant new feature post, or if unrelated to new functionality in the Other bugs & issues forum.
Changes/Bugs new to this build
Data Entry: Artboard size is not remembered when using 'Custom', making placing many the same custom size difficult  Crash rotating image in picture frame  Crash when replacing PDF  Crash after unchecking Include As PDF Bookmarks on a document with multiple headings in Table of Contents [AFB-8308] Lock files are not discarded when opening .aftemplate files, preventing others from opening them  Some last minute translation and help file tweaks

To bad it didn't work but did you try to install the msi/exe versions?
These are not sandboxed and more accessible.

I've been testing version 2.1 for three days now and so far I haven't had any problems. The program does not slow down after a long work. I think the problem - for me - has been solved.
Thanks!

Hi @Clau_S,
I've replicated this issue across the three apps on Windows and logged it with the developers. 

Confirmed on Windows 11
It makes no sense to unpin them so presumably it is a bug

I bet this is down to selecting 2 separate layers with 2 separate Transform Origins plus they are both rotated. This may be okay if you Group the two layers.

I'm hesitant to get in the middle of this, BUT I think Serif did the right thing to support its customers; the company deserves congratulations instead of criticism.
They made a decision with good intentions that, in retrospect, didn't meet the needs of users. Based on the feedback they received, instead of digging in their heels and telling users "it's our way or the highway", they shifted gears and released standard Windows installer versions.
Having been an embedded software engineer for 40 years, I can tell you that, although installation packages don't add perceived value (they're just supposed to work!), they can take a disproportionate amount of time and effort to develop and test. So understandably, the updates weren't available immediately.
I purchased version 2 of all three programs while they were discounted. Serif made it clear that they were working on a fix for Microsoft's questionable installation paradigm, so I continued to use version 1 until the updated installers were available. When they were, the updates installed cleanly and work flawlessly.
I appreciate that Serif has made such a capable software package available for such a reasonable price.

In this case the "bug" is the fact that the default grid cannot be changed by the user. For example I need a grid to determine if certain lines in my photos are straight. I have no use for a tiny pixel grid that can only be seen at ridiculous zoom levels 😉 Serif should really reconsider and at least give us the option to set the default grid size to something more useful.

This default behavior is very annoying. The default grid should be something more reasonable like in Affinity Photo 1. There switching on the grid immediately brings up a usable grid size.

This is a good suggestion and something we are working on already, thank you.

Please, add the ability to import preferences and/ or shortcuts that were assigned in the commercial versions. That makes it a lot easier for us users to get up and running quickly to do a few tests of the new features.

@Chris B Thank you Chris for response. There is no doubt the photo is overexposed in highlights but Adobe Camera Raw or free Darktable are able to reconstruct the highlights. Someone wrote that Adobe has a much much bigger budget but it doesn't explain why Darktable has a feature that is able to fix it. 

 

Not necessarily. All of the tools are available in the Photo persona, but you have to keep clicking and switching between them. In the Develop persona you can tweak different values with only one opening click and one saving click.
This comes in handy in one of my use cases, which is editing pictures sent by a client's employees for use on the company's Web site. Each employee's phone or camera is "off" in different ways, but the corrections needed tend to be consistent for pictures taken by each individual device. In other words, a given device will always produce pictures that are "X" percent too warm, "Y" percent overexposed, or whatever. In the Develop persona, all the fixes can be applied in one screen and saved with one click. Multiply the click savings by dozens of images, and it adds up to measurable time savings.
When the reality of your workday is a seemingly unending procession of clicks, reducing the clicks needed to do a repetitive task makes a huge difference in productivity. When I first switched to Affinity Photo, the reason was because it required the fewest clicks to do what I used to do in Fireworks. I've since come to appreciate it for other reasons, but the initial reason was because it won a number of clicks contest.
Richard

FWIW, I used Walt's bat file, for LR. Works fine for me. LR does not allow access/using the photo2.exe file.