
Claudio60
Members-
Posts
147 -
Joined
-
Last visited
Everything posted by Claudio60
-
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
Hi Mark and thank you for the explanation. However I have about 15.000 old slides saved in jpg and many of them are affected with a color cast and other problems that I want to correct; it often happens that I have to rework them again as my perception of "right" colors change from day to day. In short for my purpose it is very useful to have stored them both in original .jpg than .aphoto format (at least before exporting them in jpg). -
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
I hope you can fix it soon, otherwise I will keep on using 1.6. -
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
Hi, I would like to know when and/or it will be fixed, .aphoto file size from jpg are really too big for backup purpose, Tks for your answer. -
Blemish removal tool possible bug in 1.7.2.471
Claudio60 replied to Claudio60's topic in Photo V1 Bugs found on Windows
Thank you Chris! -
Cosmetic bug in Surface Pro 4 (AP 1.7.2.471)
Claudio60 replied to Claudio60's topic in Photo V1 Bugs found on Windows
Yes, it happens only in Affinity and this happens only using the touchpad, there's a "dot" using the pen. -
Cosmetic bug in Surface Pro 4 (AP 1.7.2.471)
Claudio60 replied to Claudio60's topic in Photo V1 Bugs found on Windows
Hi Chris, No, my Surface Pro 4 has never been connected to an external monitor and it's set to default native resolution 2736 X 1824 and default 200% scaling. Furthermore I noticed that the same weird tool icons size appears also with ap 1.6.5.135, I haven't noticed it before. -
Inpainting brush lag in 1.7.2.471
Claudio60 replied to DMayrshire's topic in Photo V1 Bugs found on Windows
I have the same lag with the inpainting brush tool on my Surface Pro 4 i5 4gb ; I thought it could be caused by the low quantity of ram but I checked my memory usage and it is around 70/75%. Strange is that when I was using 1.6.5.135 (until the day before yesterday) I experienced no lag with the inpainting brush tool. Anyway the lag begins immediately, I mean that when I start painting with the inpainting brush tool the stroke begins after half a second or so and is very stutterly/intermittent/not regular. -
Blemish removal tool possible bug in 1.7.2.471
Claudio60 replied to Claudio60's topic in Photo V1 Bugs found on Windows
Hi dimmageiras, I tried what you suggest me and: 1 In my system if I move the cursor outside the image and back inside the cursor remains as "the hand" 2 If I right or left click inside the image the cursor turns back to a circle. -
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
Hi Patrick, still no fix for reducing the .aphoto's file size generated from jpg? Will it always remain 3 times bigger compared to 1.6? -
DNGs with color cast (AP v1.7.1.404)
Claudio60 replied to AiDon's topic in Photo V1 Bugs found on Windows
Hi Aidon, no color cast in your image, at least in my pc (tested with beta 1.7.2.445 and 1.6.5.135) -
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
Tks Patrick, good job -
1.7.0.380 - Huge file size when saving 1.6 image
Claudio60 replied to hoch's topic in Photo V1 Bugs found on Windows
Hi Patrick, any news about the jpeg file size issue? PS: waiting for a fix, in the meantime I rolled back to 1.6.5.135 -
Hi Stokerg, I have successfully installed (Tks to a Photoshop demo) the Aurora HDR 2018 plugin (Aurora HDR Photoshop plugin is installed from inside the program, only if Photoshop is found in the system); what I have done is find where the plugin has been installed and copy it in: C:\ProgramData\Affinity\Photo\1.0\Plugins. Well, now Aurora HDR 2018 is working as a plugin in AP 1.6.5.135 in
-
Hi Sokerg, I have the same issue (exception not handled) on my Surface Pro 4 too (I discovered it yesterday); it seems to me very strange that this issue occurs on both my notebooks; so I think the culprit could be Win 10 1903 that I recently installed on my notebooks (with 1809 I never had such an issue).