abra100pro Posted November 14, 2024 Posted November 14, 2024 I get this message everytime I update the JPG and AD syncs with the updated, linked file. The update itself works. AD 2.5.5 / Sequoia 15.1 Quote
Hangman Posted November 14, 2024 Posted November 14, 2024 Hi @abra100pro, So far, I've not been able to replicate this using Sonoma... Is the JPEG in question located on your internal Hard Drive, an external drive or in the Cloud? Are you using Edit Image in Designer to make changes to the JPG file or editing in directly in Photo or a third-party editor? Can you upload the JPG file in question so we can test it? Quote Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
abra100pro Posted November 14, 2024 Author Posted November 14, 2024 Hi @Hangman It is a JPG I export from a PSD in Photoshop, each time I change it. It's on my internal drive and linked to in AD. (Should I mention: copyrights apply). Quote
Hangman Posted November 14, 2024 Posted November 14, 2024 Hi @abra100pro, Thanks for clarifying, I'm wondering whether this is a Sequoia issue... I don't have Photoshop installed but I'm not seeing any issues when editing the JPG in a couple of other image editors on Sonoma... Hopefully, someone else running Photoshop on Sequoia can also test to see if they see the same issue and if so the team at Serif can log it accordingly... Quote Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted November 14, 2024 Posted November 14, 2024 Is the folder that is on your computer managed by a cloud service? If so, and that service is configured to remove files and keep them primarily in the cloud, then it is possible that: You update the JPG file Affinity is notified of the update Affinity tries to read the changed file, but as it is trying to read it your cloud service is moving the file off the machine, and Affinity gets a truncated version of the file and cannot recognize its contents. Old Bruce and Callum 2 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.