Tom Lachecki
-
Posts
121 -
Joined
Posts posted by Tom Lachecki
-
-
We had to change the data path for the EXE installations in 2.1, and when this button is disabled it means the release installation wasn't found.
You should find that the EXE installations can be migrated-from after 2.1.
-
-
-
-
-
Shortcuts will be migrated as of the next beta.
-
On 3/18/2023 at 10:34 PM, spiderpod7d said:
It Left behind my short cuts and my plugins.
This has now been fixed in our code; might not appear in the very next beta, but it'll appear.
-
Custom lens profiles are loaded from:
- ~/Library/Application Support/Affinity Photo 2 Beta/LensProfiles
- ~/Library/Application Support/Affinity Photo 2/LensProfiles
I don't think these are being migrated at the moment. We'll make that change.
-
On 3/18/2023 at 10:13 PM, spiderpod7d said:
Back Again
I had to Also copy the from the release version 2.04 the ~user/library/group container/user folder from the release V2 folder to the V2 Beta folder to get my lens processing presets
Are you referring to custom XML Lens Profiles?
-
-
27 minutes ago, md_berlin said:
Does not seem to work for me. Could it be because my purchased version 2 is from the Mac App Store? Here the preferences are in >Library>Containers ... . Or should it still work?
It should.
-
9 minutes ago, debraspicher said:
This is helpful for y'all as well because if we import everything instead of cherry-picking imports, it will offer as much opportunity to showcase bugs across various use cases. So while it's a bother, do add in as much portability as feasible. One of us will have some weird setup that will cause mayhem... no doubt... (edit) so while the convenience is very welcome, it makes our day-to-day usage in beta much more realistic...
Yes indeed
-
13 minutes ago, garrettm30 said:
However, I have found shortcuts do not seem to have been migrated when I clicked the “Copy Settings & Content From Release App”
We'll check into this.
-
11 minutes ago, garrettm30 said:
Curiously, the message that popped up stating “additional disk space required” showed a different amount. The first time, it showed around 176 Megabytes, while the second time it showed 916.8 MB.
The amount of space currently used by your beta content, which will be deleted, is taken into consideration for this calculation.
-
As I say, this is really more of a Photoshop & Camera RAW setting (and you can turn it off in Camera RAW) for any file that has, at some stage in its past, already been touched by such software.
But we'll consider an addition to our "Embed Metadata" checkbox to allow you to strip out only the Camera RAW metadata from exported JPEGs, so that you can stop this Adobe feature from being triggered.
-
The unsandboxed app data paths have changed in the 2.1 beta so it's possible there's a bug here in not picking up the original 2.0 paths from an unsandboxed installation.
-
The migration option is just for content (assets/brushes/etc) and data like document presets. It won't be able to migrate studio layout.
-
Hi @Ldina,
Photoshop opens processed files in Camera RAW by default if an XMP sidecar file is present.
So one thing to check is that you don't have a sidecar in the same directory, left over from your work with the DNG in your Adobe software.
If that doesn't solve it, it is possible that Photoshop is picking up on some Camera RAW develop metadata in the JPEG; if so, it may be appropriate for us to start automatically stripping that out on export, but it's something we'll need to investigate further.
You can also change your Camera RAW settings to "Disable JPEG Support" entirely.
-
We currently have no plans to implement it in reverse - this would be problematic in many cases. But I appreciate it would be useful!
-
28 minutes ago, MikeTO said:
This is minor but for brand new panels like Cross References, this migration feature sets them smaller than their minimum height and their position to something other than the default.
Thanks Mike that's interesting; could be a data file got missed out. Which platform is this on?
-
26 minutes ago, footeg said:
This option is greyed out in Affinity Photo. Windows 11 latest update. Do I need to have all the beta apps installed to see this option?
Theoretically it should be available if any v2 release app is installed; it doesn't have to be the same app.
-
On 1/4/2023 at 3:48 PM, Nats1 said:
Ctrl Alt Down (to move text lines closer) turns my entire screen upside down.
I use Ctrl Alt Up to fix it.This is a common shortcut with some graphics drivers to alter the rotation of the screen; it isn't Affinity doing that
I recommend checking your nVidia/AMD/etc settings.
-
It will be fixed in a forthcoming update.
The reason it appeared to work in Affinity Photo 1 is that we did not have a proper date/time widget with user input until Affinity Photo 2. We were just showing the timestamp without any timezone information at all. It would appear to be correct, but if you went on holiday you'd soon realise that your computer local time was not being taken into consideration properly then either.
Times in exported data would also have had the offset.
It's just much more obvious now: the user input is interpreted as being in local time for convenience, so the whole widget must be timezone-aware.
-
Thanks - it's not setting the EXIF timezone information, but it's setting some data in the Makernotes we can start using.
.png.9908ebf07d8b1a670e4a58f026e33d50.png)
Canva
in Affinity on Desktop Questions (macOS and Windows)
Posted
Off topic but I couldn't help but giggle at the translation of my boss's first name to "Freixo"