Jump to content


  • Content Count

  • Joined

  • Last visited

  1. @carl123 There is a difference between "REGEDIT4" and "Windows Registry Editor Version 5.00" .reg files. The first use single-byte Windows character encoding (typically Windows-1252), the latter use UTF-16 (characters represented using code points taking 16 bits or more). In notepad the first one is called ANSI (which is a terrible name, as it has nothing to do with ANSI), the second one - Unicode (which is not as precise as it could be, but well, Microsoft...). So I suspect that during saving you did not set Unicode, that's why it wasn't working properly for you, so you did the change yourself in regedit, exported and shared it afterwards in the thread.
  2. On the mentioned "Transport Layer Security (TLS) best practices with the .NET Framework" we can also read: So I think AP should simply set TLS 1.2 if it detects it runs on Windows 7. I believe it's a pragmatic solution.
  3. Thanks, Mark. I also confirm that editing registry as suggested in link provided by carl123 workarounds the issue. Thanks! There is a useful tidbit there that I wasn't aware, which is worth quoting explicitly here. Basically adding following stuff in registry is sufficient to make Unsplash work in AP: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 I call it a workaround, because I think it should be fixed in AP without need for changing user's registry. Even if TLS 1.2 is disabled by default in Secure Channel (schannel) as configured in Windows 7 out-of-the-box, it remains supported, so it should be possible to enable it in programmatic way from any application that needs it.
  4. I gave a quick look with Wireshark into this issue and it seems it may be old TLS version used to setup secure connection. AP sends: TLSv1 Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 119 Handshake Protocol: Client Hello AP receives: TLSv1 Record Layer: Alert (Level: Fatal, Description: Protocol Version) Content Type: Alert (21) Version: TLS 1.0 (0x0301) Length: 2 Alert Message Level: Fatal (2) Description: Protocol Version (70) I suspect there is some difference in how you setup secure connections in Win 7 and Win 10. There are no reports of Win 10 users having this issue, right? In practice you shouldn't use any TLS < 1.2.
  5. I'm also always getting "Connection failed" for Unsplash in Stock tab in latest Photo, just like I was getting it in previous Photo (BTW this stock thing is a really nice addition among other features added in 1.7!) EDIT: Forgot to mention that in the web browser searching using https://unsplash.com/ works fine.
  6. Recently I've grabbed my old Panasonic again. [Leica lens, 5MPix (2560×1920), 12x opt zoom, f/2.8] Nothing stellar by now, but still acceptable camera. The problem is: Automatic lens correction does not work for its photos in Affinity Photo. But according to http://lensfun.sourceforge.net/lenslist/ it should be supported. I've tested trial version of PTLens.on Windows and darktable on Linux and both handle the photos correctly. Tested with latest stable AP on my laptop. Tomorrow I'll confirm the bug with latest beta of AP on my desktop. I really hope it can be fixed before releasing upcoming AP 1.6.
  7. I wasn't checking betas for some time, but I'm fixing my behaviour right now: P1. The bug mentioned half year ago in topic 100% zoom clips off edge pixel is still here. WYSIWYG aspect of image editors is quite important, so it would be great if someone finally tackled the problem. P2. I'm baffled that simply zooming in and/or out the image a few or several times (most conveniently using Ctrl + mouse wheel) leads to freeze of AP, i.e. it's become unresponsive for about 5 seconds. (The used image is a simple one as in my post from above mentioned topic.) I'm using AP beta version on other machine now (Athlon 64 X2 4600+, 4 GB RAM, GTX 460) than the one I used to work with release version (details in the footer), so it's not your top rig, but it's still ok for a lot of things, definitely including 200x200 images. Anyway, thanks for working on AP to make it even better. It's all really appreciated. Those pesky bugs are simply extremely annoying.
  8. I really hoped it would be fixed for upcoming AP 1.6, but it's still not. I tested recent beta and there is slight difference, so I'll show up-to-date screenshots. 100% http://imgur.com/WdwXsal 150% http://imgur.com/lcPXToj 200% http://imgur.com/5L0bBKc The difference from 1.5.x is that now even in 150% zoom edges are clipped.
  9. Unfortunately problem still exists in AP I haven't checked new AD yet.
  10. Blending-related wish list: Adding "Use beneath layers as initial Destination" button in Apply Image filter.Such button would allow for typical use case when you want to perform custom blending. Nowadays you have to: temporarily hide the layer "S" you want to blend, Merge Visible, unhide the layer "S" and move it below new merged layer "D", switch to layer "D", Apply Image and drag layer "S" onto its dialog window to use it as Source. Supporting presets for equations in Apply Image.It's obvious enhancement for better automation. Defining custom blend mode via Adjustment Layer (possibly called Blend Adjustment).It would work for such layer only when it is a child layer. Presets here are also crucial. Defining custom global (accessible in all documents) or local (accessible in current document) blend modes.The most robust solution for users performing repeatedly their own custom blending. In Blend Mode Manager there should be a way to see (in a read-only manner) already existing blend modes with equations (for blend modes expressable in plain equations). Blend mode definition should be performed using equations where:S (Source) = current layer [aka Active or A] D (Destination) = beneath layers [aka Background or B] In case of Blend Adjustment source would be the parent layer. Example of custom blend mode: Remove DR=(DR-SR*SA)/(1-SA) DG=(DG-SG*SA)/(1-SA) DB=(DB-SB*SA)/(1-SA) DA=DA(It doesn't make sense for truly opaque layer, of course.)
  11. There are cases when value in #(RGB) input box differs from what is shown in R, G or B. The difference equals 1. Go to Colour panel and set "RGB Hex" in Colour Model Selection. Use mouse to set any slider until you notice that value shown in input box next to the slider differs from #(RGB) input box. Example: I set R to 50 using mouse, but #(RGB) displays 510000. EDIT: Same thing happens for many colours chosen from RGB Spectrum. Affinity Photo, Windows 7 Pro x64, non-HiDPI laptop display [1600x900]
  12. I found quite serious bug that makes Levels unusable for non-Master channels. Layer > New Adjustment Layer > Levels Adjustment [Ctrl+L] Change channel to anything but Master. (Colorspace doesn't matter) Change any value (Black Level, White Level or Gamma) using slider or input box. (After inputting value you have to lost focus from the current input box, e.g. by clicking mouse outside the input box or by pressing Tab.) You're seeing unwanted switch to Master channel. Affinity Photo, Windows 7 Pro x64, non-HiDPI laptop display [1600x900]
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.