owenr

Members
  • Content count

    250
  • Joined

  • Last visited

About owenr

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

148 profile views
  1. You said you were not experiencing the problem which I've reported. I am not simply assuming something. I methodically tested a hypothesis and drew a conclusion. You earlier admitted (and have demonstrated) that colour management confuses you, so it's no surprise that you are unable to verify my claim. I will look at your points 4 and 5 after returning home tonight. For point 6, if you suspect a bug other than the topic of this thread, shouldn't you be passing that info to the staff in a separate thread and linking to this thread if you think there may be a connection to this bug?
  2. I'll try to help further after I get home tonight, if nobody has solved this in the meantime.
  3. Yes you did. Your first post with images contains two JPEGs. At least one of them has embedded profile "Canon PRO-1 v1-1 new <PT> 1/2/3 Photo Paper Pro Platinum". You even stated that it was a JPEG for printing. My browser answer along with screenshot of my browser demonstrates that colour managed software will display your JPEG correctly because I've shown that that JPEG is an almost perfect match for the displayed document in Affinity in your PNG screenshot. I can open your JPEG in any colour manged software and it is displayed as almost identical to the .afphoto file that you also posted in this thread.
  4. You came here and announced, "This does not happen for me." I had already explained to you in that other thread that the bug reported in this thread was indeed happening to you, but that you were being misled into thinking there was no problem because of your particular app preferences. Here are your file opening prefs: When you open an unprofiled JPEG, there first should be a warning of the working profile being assigned because of no profile in the file, but that warning wrongly doesn't appear in the case of JPEG, and, furthermore, sRGB should not be the assigned profile unless that is your working profile, but sRGB is wrongly being assigned regardless of actual working profile; therefore the bug does happen to you when opening an unprofiled JPEG. Because you have the "Convert opened files to working space" enabled, any file that's opened gets converted from its profile to your working space. An unprofiled JPEG first silently gets assigned sRGB (the bug) and then that sRGB image gets converted to your working space, and you have been misled into assuming all is well because you now have an image with the working space profile. There will be no problem, if the unprofiled JPEG should have had sRGB profile, but if it should have had another profile, such as Adobe RGB, you will now have wrong colours because a conversion from sRGB to your working space has occurred instead of a conversion from Adobe RGB to your working space.
  5. I spent considerable effort in that thread which you reference trying to enlighten you as to why your app preferences, which are different to mine, were preventing you from being aware of the problem that Chris_K has confirmed. Your folllowing me to this thread and again stating "it doesn't happen to me" is inconsequential and, frankly, irritating, now that the problem has been confirmed.
  6. Ctrl+Alt dragging works on a Mac. I don't know the windows shortcut, but it should be in the app's help since it's in the Mac app's help.
  7. Your black paint is opaque, but the white paint is completely transparent, which is having the effect of reducing mask alpha just as if you were reducing mask alpha by painting with black. Solution: put your white paint's opacity to 100% in Colour panel.
  8. Affected apps on macOS 10.12.6: Designer 1.5.5 Designer 1.6 beta 10 Photo 1.6 beta 5 Unaffected: Photo 1.5.2 The attached 32 bpc afphoto file was posted to the forum by another user as part of a query about JPEGs exported by Photo. When I open the file in the affected apps listed above, the document is assigned whichever profile I currently have set as my default 32 bpc profile. I have tested and found that each time I open the file while a different default 32 bpc profile is set in preferences, the document is assigned that particular profile. No warning of any kind is presented by the app! When Photo 1.5.2 opens the file, the doc has the expected profile "Asus Raoul kal 20170323 (Linear)". Here's a screenshot of my warning preferences in all apps, so, if they are unable to read the profile for some reason then I should be getting a warning. P8232446-3.afphoto
  9. Hi Raoul, The JPEGs that you uploaded to the forum are both good - the colours look natural when viewed with colour managed software and a correctly profiled display. These JPEGs have embedded profile "Canon PRO-1 v1-1 new <PT> 1/2/3 Photo Paper Pro Platinum". In colour managed software they look extremely similar to the displayed document in your screenshot of Affinity Photo. Also, when I download your uploaded images and view them in Affinity Photo and other colour managed apps they look good. The terrribly pink images displayed on this forum page are down-scaled preview images (click them to access the uploaded images) and they appear that way because their original profile has been discarded by the software that generated the previews, and browsers present images without profile as if they have sRGB profile. Many browsers ignore embedded profiles, anyway, and will also present your original images with the pink discolouration of the previews. A colour managed browser does present your original images correctly, though. Here is a scaled down screenshot (converted from my display's profile to sRGB to make it look OK in any browser) of Safari browser on macOS displaying an original image to the right of the corresponding forum preview image:
  10. Export a JPEG from an Affinity app - the "More" settings includes a checkbox for embedding the profile, so clear it to get an unprofiled export. Various other graphics apps have same option when exporting.
  11. @MBd and @R C-R The bug has been confirmed:
  12. Here is what I initially said: "JPG has no profile: AP assigns sRGB regardless of the default working colour profile, and does not warn the user!" That seems serious enough to me. You've failed to get the point I made. You've set the preference for the app to convert from whatever the input file's profile is to your current default profile, and to receive a warning that that it has happened. If you open a profiled JPG, the app converts from that profile to your default profile, and warns you of that. Good. If you open an unprofiled JPG, the app assumes sRGB without informing you of that assumption, and converts from sRGB to your default profile, and simply warns you a conversion has been made. You think all is good, but a wrong conversion will have been made if the JPG is missing a, for example, Adobe RGB profile. You may now have the wrong colours. In my case, I have not set the automatic conversion preference, so I am not supposed to, and never do, get a conversion warning. I have set the preference to assign my default profile to unprofiled files, and warn me when that happens, but that warning is failing to appear for unprofiled JPG, the app is assuming sRGB and is assigning sRGB regardless of my default profile. If the file is missing an Adobe RGB profile, it now has the wrong colours and I've had no warning of a potential problem. You don't get it, RCR. I want files to open into a document with the profile of the file so I get the ultimate accuracy for that file. And if a file has no profile, I want to be warned of that so I can investigate the matter instead of potentially unknowingly work with wrong colours.
  13. The not knowing can be a serious problem. If a client gives you an image to work with, they're not going to consider you competent if you ask them to proof work where the colours are clearly different to what they expected and required. If the software at least warns that a JPG is unprofiled instead of silently treating it as sRGB, then you can make enquiries into what the profile should be. Exactly - that lack of warning, despite the preference to receive the warning being set, is the bug I was talking about. So, we are in agreement (maybe for the first time ever :D) that there is a bug. The information that a file has no profile can be valuable, as explained in my previous paragraph.
  14. OK, so you have set your Affinity apps to always convert opened files to working space I do not enable that. I only enable the "Warn when assigning profile to unprofiled files". That explains us getting different results, but you are facing the same problem. I'll try to explain... If your Affinity app opens a non-profiled JPEG, it will be assuming sRGB then converting to default profile and warning you of that conversion. If your non-profiled JPEG does happen to contain colours that were defined in sRGB, then no harm will be done. However, if your non-profiled JPEG contains pixel values that were defined in, for example, Adobe RGB, then the image will be converted from sRGB to default profile, which will create the wrong colours. The app should be warning that there is no profile, but instead it is letting the user remain ignorant of that fact and potentially creating wrong colours!
  15. Hi R-C-R, I just retested after reading your post. This gets slightly weirder at my end with a randomly occuring rare warning of sRGB being assigned. I have JPEGs and PNGs exported explicitly without profile from Adobe RGB docs and Display P3 docs in two apps (one of which is Affinity Photo). So, I test opening the files while default profile is set to Display 3D in my Affinity apps. With non-profiled PNG, the warning about the default profile having been assigned appears, and it persists for about four seconds or until I close it. Correct behaviour every time. With non-profiled JPG, sRGB always gets assigned and, almost always, I get no warning of that. Very rarely, there is a warning that sRGB has been assigned, but that warning vanishes after about one second. I mean, opening a given non-profiled JPEG will occasionally result in the brief warning, but usually there is no warning at all for the very same file. I test again with default profile set to Adobe RGB and then test with it set to sRGB. Always sRGB is being assigned for non-profiled JPEGs. (I will be unable to respond to replies for much of today.)