Jump to content
You must now use your email address to sign in [click for more info] ×

Tom Lachecki

Staff
 View Profile  See their activity

  • Posts

    121

  • Joined

 Content Type 

Everything posted by Tom Lachecki

  1. Tom Lachecki
    Off topic but I couldn't help but giggle at the translation of my boss's first name to "Freixo"
  2. 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.
  3. Tom Lachecki
    This thing is scary...
  4. Tom Lachecki
    We do support "use". This particular document is technically invalid SVG due to the circular reference on #s, but it seems many apps silently ignore it and proceed anyway, so that's what we'll do
  5. Tom Lachecki
    The next version
  6. Tom Lachecki
    Yes - I'll look into that. Update: Found the oversight - should be fixed in the next build
  7. Tom Lachecki
    Shortcuts will be migrated as of the next beta.
  8. Tom Lachecki
    This has now been fixed in our code; might not appear in the very next beta, but it'll appear.
  9. Tom Lachecki
    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.
  10. Tom Lachecki
    Are you referring to custom XML Lens Profiles?
  11. Tom Lachecki
    We'll strip Camera RAW metadata on export to raster formats (e.g. JPEG).
  12. Tom Lachecki
    It should.
  13. Tom Lachecki
    Yes indeed
  14. Tom Lachecki
    We'll check into this.
  15. Tom Lachecki
    The amount of space currently used by your beta content, which will be deleted, is taken into consideration for this calculation.
  16. Tom Lachecki
    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.
  17. Tom Lachecki
    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.
  18. Tom Lachecki
    The migration option is just for content (assets/brushes/etc) and data like document presets. It won't be able to migrate studio layout.
  19. Tom Lachecki
    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.
  20. Tom Lachecki
    We currently have no plans to implement it in reverse - this would be problematic in many cases. But I appreciate it would be useful!
  21. Tom Lachecki
    Thanks Mike that's interesting; could be a data file got missed out. Which platform is this on?
  22. Tom Lachecki
    Theoretically it should be available if any v2 release app is installed; it doesn't have to be the same app.
  23. Tom Lachecki
    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.
  24. Tom Lachecki
    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.
  25. Tom Lachecki
    Thanks - it's not setting the EXIF timezone information, but it's setting some data in the Makernotes we can start using.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

 Accept Cookies  Reject Cookies