Soln Posted November 16, 2022 Share Posted November 16, 2022 ... not present in Photoshop as it should be (both seen on 30-bit display). So is there 16-bit support in AP2 as advertised, or not? Try youself with greyscale gradient RGB 64/64/64 to RGB 96/96/96 (with the 8-bit sliders) in 16-bit RGB mode. Quote Link to comment Share on other sites More sharing options...
Soln Posted November 17, 2022 Author Share Posted November 17, 2022 Please, anyone? Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted November 17, 2022 Share Posted November 17, 2022 1 hour ago, Soln said: Please, anyone? Its an open bug: Affinity is unable to render open documents utilizing more than 8 bit color depth in RGB/16 format. The documents and exported files are fine - you can check this with other apps. RGB/32 documents can utilize higher bit depth. Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
cgidesign Posted November 17, 2022 Share Posted November 17, 2022 And it seems to be related to the zoom level? At around 25% zoom there is severe banding visible. At 100% it is better. In my opinion 10bit display output is another one of those basic things which professional graphics software should do correctly these days (when were 10/12bit monitors introduced to the marked - 10 years, 15 years ago?). [EDIT]: It is also borked with 32 bit documents. Gray_16bit_V2.afphoto Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted November 17, 2022 Share Posted November 17, 2022 Your file is color format grey/8. at least you should use gray/16. Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
Soln Posted November 17, 2022 Author Share Posted November 17, 2022 Thanks for the link. @NathanC Let's hope there will be a fix for that very soon! It's mid of november and V2 has been released in the meantime with the same bug as in V1... WTH? Please make a statement regarding this issue in V2 ASAP, because I only can get a refund for two weeks. Quote Link to comment Share on other sites More sharing options...
cgidesign Posted November 17, 2022 Share Posted November 17, 2022 27 minutes ago, NotMyFault said: Your file is color format grey/8. at least you should use gray/16. Sorry, wrong file name while testing all variants in V1 and V2. Gray_16bit_V2.afphoto Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted November 17, 2022 Staff Share Posted November 17, 2022 14 minutes ago, Soln said: @NathanC Let's hope there will be a fix for that very soon! It's mid of november and V2 has been released in the meantime with the same bug as in V1... WTH? Please make a statement regarding this issue in V2 ASAP, because I only can get a refund for two weeks. This problem is also logged against V2 and is still with the developers, I've added your report for consideration however I can't provide an ETA on when a fix version will be available. Quote Link to comment Share on other sites More sharing options...
cgidesign Posted November 17, 2022 Share Posted November 17, 2022 @NathanC I just now saw your reply. I already made a new bug report for V2. Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted November 17, 2022 Staff Share Posted November 17, 2022 19 minutes ago, cgidesign said: @NathanC I just now saw your reply. I already made a new bug report for V2. No problem, I'll include another report of the issue based on your thread. Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted November 17, 2022 Share Posted November 17, 2022 There is a second issue in the area of 16—bit color depth (and 8 bit color depth) in case of using gradients, Affinity applies a forced dithering. the forced dithering may reduce/limit color bit depth for RGB/16 documents For rendering (in Photo, while using the App) you can deactivate dither gradients in preferences/performance For export, no such option exists. Even if disabled for rendering, exported to raster formats will always be forced-dithered (affecting gradient tool, applied to all layer types e.g. vector, pixel, mask) There is a (unofficial) trick to deactivate forced dithering, including export: add a layer fx, color overlay, 0% opacity. there are very old feature requests to allow disabling forced dithering. Add your vote there. cgidesign 1 Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
cgidesign Posted November 17, 2022 Share Posted November 17, 2022 2 minutes ago, NotMyFault said: There is a (unofficial) trick to deactivate forced dithering, including export: add a layer fx, color overlay, 0% opacity. Preferences - dithering I knew. But not the export trick. Thanks! Quote Link to comment Share on other sites More sharing options...
Soln Posted November 24, 2022 Author Share Posted November 24, 2022 @NathanC Please make a offical statement regarding this issues in V2, because otherwise I would like to get a refund ASAP. Can we expect 16-bit support in AP as advertised? This would include correct 16-bit rendering. Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted November 24, 2022 Staff Share Posted November 24, 2022 3 minutes ago, Soln said: Please make a offical statement regarding this issues in V2, because otherwise I would like to get a refund ASAP. Can we expect 16-bit support in AP as advertised? This would include correct 16-bit rendering. As per my previous post, this issue with 16 bit rendering to display in Photo is currently logged with the developers, I can't provide an ETA on when this will be fixed as it is not in my direct control. If you wish to make a refund request please contact affinityreturns@serif.com Quote Link to comment Share on other sites More sharing options...
Soln Posted November 24, 2022 Author Share Posted November 24, 2022 @NathanC Sorry but bug logging is no statement. You could ask a lead programmer and s*he could answer: Oh yes, we definitly have to fix this asap, because there a people actually working in 16-bit mode (at least try to...). Or s*he could anwer: Oh no, rendering now is sufficient enough, we don't plan to fix this. Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted November 24, 2022 Share Posted November 24, 2022 Affinity consistently expressed that no ETA will be given to all such requests, neither for bug fixes, feature requests, roadmaps, release dates or whatever. Affinity will publish new versions when there are available, in the News section of the forum. If bug fixes are available, the individual threads will be updated. No swearing, bribing, or use of force will change that. Unless you are Elon M. and succeed in buying the company. As Serif is privately held and no stocks are listed, even this option is next to impossible. loukash 1 Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
Soln Posted November 24, 2022 Author Share Posted November 24, 2022 I don't want an ETA but an assurance this will be solved in V2. Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted November 25, 2022 Share Posted November 25, 2022 You will not get that information at the time a fix is available, not before. Even if Affinity would give such assurances: how will you know if Affinity can deliver? Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
cgidesign Posted February 13, 2023 Share Posted February 13, 2023 @NathanC The issue is still there in V2.0.4 Even worse - gradients in 32 bit files are also dithered. Can you please fix this ? 32bit 16bit gradient-16bit.afphoto gradient-32bit.afphoto Quote Link to comment Share on other sites More sharing options...
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.