Jump to content

- S -

Members
  • Content count

    602
  • Joined

  • Last visited

About - S -

  • Rank
    Set *.tif Free

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If in the Microsoft Store app it says "You own this app", rather than "This product is installed", then it's possible that it isn't actually installed. What does the button on the right-hand side say? If it says "Install", then although you own the app, it isn't actually installed. Perhaps it needs re-installing again, as originally it was a beta extension.
  2. See my below posts from last year: https://forum.affinity.serif.com/index.php?/topic/62259-cannot-save-files/&tab=comments#comment-323174 Or the shorter version: If you're running Windows 10 1809 onwards (the below screenshots are from 1903, so may be slightly different), either click the Windows Notification Centre message that appears in the bottom-right corner when something has been blocked by Controlled Folder Access—which will take you directly to the Windows Security settings. Or go to [Windows Security > Virus & Threat Protection > Manage Ransomware Protection > Block History], which will take you to the same place. You can then select ‘Allow on device’ under the ‘Actions’ drop-down menu. Alternatively, you can go to [Windows Security > Virus & Threat Protection > Manage Ransomware Protection > Allow an app through controlled folder access > Add an allowed app > Recently blocked apps]. You can then add an allowed app from the list.
  3. That's likely because you're using a Mac—where you can use the Apple Core Image Raw engine. The SerifLabs raw engine itself doesn't yet support .CR3 files. The link below contains a list of cameras officially supported by the SerifLabs raw engine. The 6D Mark II (which was announced 2017Q3) is on the list, however the M50 (which was announced 2018Q2—and the first Canon to use the new .CR3 raw format), isn't yet supported. SerifLabs Supported Raw Cameras (1.7.x) & Lens Correction list: https://forum.affinity.serif.com/index.php?/topic/73699-seriflabs-supported-raw-cameras-17x-lens-correction-list/
  4. If you're running Windows 10 with the May 2019 update (1903), you can download the Microsoft 'Raw Image Extension' from the Microsoft Store. This will display thumbnails and metadata in Windows File Explorer and the Photos app for most cameras—although it doesn't currently support Canon .CR3 raw files at the moment. https://www.microsoft.com/en-us/p/raw-image-extension/9nctdw2w1bh8
  5. - S -

    [Solved] Unable To Save

    I think you're misunderstanding my post. The first part where I quoted Patrick was to do with Controlled Folder Access. The second part was in reply to your comments. I was pointing out that if you open a read-only *.tif file, the error message Affinity Photo produces is also a little non-descript, occurs at a fairly poor moment and it tells you half way through the first write that actually it's not going to let you use that file after all (it force closes the file without saving). Therefore I think it's also something that needs addressing if you're currently in the process of improving error reporting for file write errors. I wasn't suggesting 'Overwrite' for files and folders protected by Controlled Folder Access, but 'Overwrite' and 'Save As' for read-only files; instead of the error message as displayed in my first screenshot above, which just has a 'Close' button.
  6. - S -

    [Solved] Unable To Save

    I've previously posted about 'Controlled Folder Access' in the below thread: https://forum.affinity.serif.com/index.php?/topic/62259-cannot-save-files/&do=findComment&comment=323174 When Controlled Folder Access has been enabled and it blocks writing to file, in addition to the File Explorer error and Affinity error, it should also display a Windows notification in the bottom-right of the screen and also keep the notification in the Windows Action Centre. I'm not sure why it hasn't in the OP's case. Without derailing the thread too much, if you open a read-only *.tif file, Affinity Photo also does this. I've reported it a couple of times before (for example HERE), and although it now shows 'Read-Only' in the title bar, Affinity Photo still doesn't handle the file properly (see below): I like how VS Code handles this. When you open a read-only file and try saving it, it tells the user that it's read-only and gives four options: Overwrite - Removes the read-only file attribute and allows the user to overwrite the file in place Save As - Brings up the 'Save As' dialogue and allows the user to save it as something else Discard - X -
  7. Similar to what Walt suggested, I would go right-back to basics to try and isolate where the issue lies from there. Assuming you've already installed the latest version of Affinity Photo (1.7.1.404), try doing the following: 1) Go to [Edit > Preferences > Colour] and set the settings to the same as in the below screenshot: 2) Go to [File > New] and open a new blank document using the same settings as in the below screenshot (pay particular attention to the 'Colour Format' and 'Colour Profile'). In this case the document is using a 'sRGB IEC61966-2.1' document colour profile: 3) Does the red show correctly (red, not orange) in the colour panel, like the following screenshot? 4) Go to [File > New] and open a new blank document using the same settings as in the below screenshot (pay particular attention to the 'Colour Format' and 'Colour Profile'). In this case the document is using a 'ROMM RGB: ISO 22028-2:2013' document colour profile: 5) Does the red show correctly (red, not orange) in the colour panel, like the following screenshot? 6) If in both cases above (I.E. using either a 'sRGB IEC61966-2.1' document colour profile or a 'ROMM RGB: ISO 22028-2:2013' document colour profile) the red is still not showing correctly, then it's possible there could be an issue with your monitor colour profile. In which case, go to [Windows Control Panel > Colour Management > Devices tab]. Make a note of what colour profile is set for 'Display 1'. Also make a note of what colour profile is set for any other displays as well—if you have more than one display (I.E. 'Display 2' in the drop down menu). Then temporarily set the monitor profile for the monitor(s) to use the generic 'sRGB IEC61966-2.1' ICM colour profile as the default profile for your monitor(s). This will use a generic 'sRGB IEC61966-2.1' colour profile instead of your monitor's colour profile. 7) Try from Step 2 again and see if red shows correctly in the colour panel now when using a generic 'sRGB IEC61966-2.1' colour profile instead of your monitor's colour profile. 8) If the colour shows correct when using a generic 'sRGB IEC61966-2.1' colour profile instead of your monitor's colour profile, then that would indicate there's some sort of issue with the monitor colour profile. In which case, you may be able to see if your monitor manufacturer has drivers on their website that contain a different ICM profile that you can try, or maybe see if you still have the discs that came with the monitor and get them from that, however these will possibly be the same as the ones you're already using. If you know someone with a monitor hardware calibrator, you could also try creating a custom monitor profile with that and using that profile in Windows Colour Management.
  8. Serif's insistence on forcing their users to use *.tiff is my number one issue with Affinity Photo. If one of their developers likes *.tiff for some odd, bizarre reason, then that's their choice. However, to force that choice on all their users is illogical and unacceptable. Everyone else uses *.tif, so I have no idea what they were smoking when they came up with this decision. It's possible to manually change the file extension, but firstly *.tif files still aren't visible in the file explorer from within Affinity Photo when saving, and secondly if you deal with a lot of TIFF files, it makes it a real PITA to work with. Users shouldn't have to fight the software to use *.tif. I've complained multiple times to allow us to use *.tif instead of *.tiff, but it always gets ignored; so I'm not sure what else we can do. I'm now at the point of wondering whether I should just use some other software instead.
  9. Sometimes the Paint Brush tool 'Wet Edges' setting turns on by itself after using the Erase Brush tool, even though the settings for both the Erase Brush tool and the Paint Brush tool are set to 'Set wet edges off'. It also happens in reverse too—where the Paint Brush tool 'Wet Edges' setting turns off by itself after using the Erase Brush tool, even though the settings for the Paint Brush tool are set to 'Set wet edges on'. After manually toggling the 'Wet Edges' setting in the context tool bar, the problem disappears for a while, only to return later. I think the issue is caused due to a discrepancy between the 'Wet Edges' setting in the brush context tool bar and the 'Wet Edges' setting in the brush settings. Steps to reproduce 'Wet Edges' turning on by itself: Wet Edges 01.mp4 Steps to reproduce 'Wet Edges' turning off by itself: Wet Edges 02.mp4 ----- Windows 10 - 1903 (18362.207) Affinity Photo - 1.7.1.404
  10. It's likely because your original document is using a ProPhoto RGB (ROMM RGB: ISO 22028-2.2013) document colour profile. Then whatever you're viewing the exported PNG file with is probably ignoring or stripping the ROMM RGB colour profile and assuming that the document colour profile is sRGB. For this particular document try clicking the 'More' button in the PNG export settings, setting the 'ICC Profile' to 'sRGB IEC61966-2.1' and ticking 'Embed ICC Profile'. This will try to export it as sRGB as best as possible—however it will still likely be different to the original. It would better to start off with the document colour profile set to 'sRGB IEC61966-2.1' when you first create the new document.
  11. Updating the post with steps to reproduce Issue 1, as this is a similar issue to THIS post regarding the Macro panel. Steps to reproduce the issue below: Asset Steps.mp4
  12. I think the issue is in part due to the length of the visible macros names when the program is closed. I've also updated THIS post regarding the similar issue with the Assets panel. Steps to reproduce the issue below: Macro Steps.mp4
  13. I've been trying to reproduce this issue for a while now on different browsers, but no matter what I try, I've been unable to corrupt the file download. Therefore I'm not sure what's causing the browsers to sometimes say that the file download is complete, when it isn't. Can you confirm that this was with Edge that is built into Windows, and not the new Chromium-Edge beta? Also, do you have any third-party antivirus software installed on the machine that is possibly doing HTTPS man-in-the-middle inspection?
  14. Right-click the Affinity Photo installer file (affinity-photo-1.7.1.404.exe) and go to 'Properties'. Then follow the below steps: Then post a screenshot of the two below tabs:
  15. In your original screenshot there was a problem with the digital signature. It was showing "Publisher: Unknown Publisher". It should say "Verified Publisher: Serif (Europe) Ltd". Try re-downloading the Affinity Photo installer file from the Serif website link below and see if you still have the same issue: https://store.serif.com/en-gb/update/windows/photo/1/
×