Jump to content

Search the Community

Showing results for 'ROMM RGB'.


Didn't find what you were looking for? Try searching for:


More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 144 results

  1. I exported from darktable a 16Bit tif in linear prophoto rgb colorspace. I opened this document in AP (first attachment as screenshot). AP seems to be crushing the blacks with a purple cast in the shadows. I've opened the same file in several other programs (Capture One, Capture NXd) and the file seems to be rendered much closer to what it does in darktable. Then I convert the file to ROMM RGB and it seems to lighted the shadows and remove the color cast (second attachment as screenshot. Is it possible that AP is not recognizing the tif file color space properly, i.e., it doesn't recognize linear prophoto rgb as ROMM RGB? I've also attached the 2 tif files. DSC_2409_Prophoto.tiff DSC_2409_ROMM.tiff
  2. Walt, thank you for you quick response. You make an excellent point. When it comes to colorspace and profiles, I am out of my depth. I'm not sure linear profiles are limited to 32 bit. At least that doesn't seem to be the case for darktable's raw processing. Nonetheless, the only built-in Prophoto profile in darktable is linear. It would appear that AP isn't recognizing this profile. I am not able to locate the linear prophoto profile in the darktable installation files in order to provide it to AP. As a work around, I have taken the ROMM RGB profile from AP and loaded it into darktable as a new output colorspace. This seems to have done the trick. This seems to give the same result as converting the file to ROMM RGB within AP. I am also able to convert from linear prophoto to ROMM in ACDsee and Krita. However, Krita seem to be able to recognize a correctly display the linear prophoto profile. In the end, I am unlikel to work in ROMM very often, but wanted to be able to in there was a need. Thanks again and Happy New Year.
  3. Hi, even it says/reads sRGB there it should be operational an unbounded space, so usually a full-float linear RGB working space, thus with a gamut (color space) similar in wide to ProPhoto (ROMM) which goes much beyond Adobe RGB. Comparison of sRGB/Adobe RGB/ProPhoto gamuts ... Typical color projection in L*a*b* ...
  4. Hello, I played with conversion from different color spaces in Affinity Photo and have found that it seems strange. I have made test file in ROMM RGB color space and tried to correctly convert one to sRGB color space with all four existed methods. I wanted to see difference between Perceptual , Relative colorimetric, Absolute colorimetric, and Saturation methods, but I cant see difference and it seems for me strange especially for perceptual method. I have made video and atteched here my test file. Could somebody explain me is it normal or not. Excuse me for bad English. Color_conversion.mp4 ProPhoto_RGB.afphoto
  5. Thank you for your replies. I have just a couple of queries: 1) The setting I’m referring to is found in Edit: Preferences: Color: RGB Color Profile. In the drop-down menu are numerous options, including sRGB, Adobe RGB, ROMM RGB, and my specific monitor profile. So am I correct in thinking that I should (a) set this to Adobe RGB, and (b) output my TIFFs from DxO PhotoLab with an attached Adobe RGB profile? 2) It is my understanding that it is best to upload JPEGs to the internet with sRGB profile attached to avoid problems with others possibly seeing incorrect colours. If so, why is it not better simply to use sRGB (with its more restricted colour range) throughout the editing process? Would this approach not give me a more accurate idea, as I make editing decisions, of the colours that other people who view these images on the internet would be likely to see in the finished result? (Sorry if I’m being a bit dim here)
  6. I can reproduce this if I'm using ROMM RGB. But that's true of the retail version wich doesn't have OpenCL. OpenCL seems to give me the correct render when using ROMM RGB as if I use the retail and set ROMM RGB I get the green cast. The first part of the video shows what I'd expect to see when OpenCL is on. The second part of the video, when you turn it off shows the green cast and looks wrong to me.
  7. Both of these freeze Designer completely on New: In Program Files > Affinity > Designer > Resources > icc there are 17 files. All appear to have been installed when I un-installed and re-installed 1.8.5 Directory of C:\Program Files\Affinity\Designer\Resources\icc 10/28/2020 01:33 PM <DIR> . 10/28/2020 01:33 PM <DIR> .. 08/12/2020 06:01 PM 560 AdobeRGB1998.icc 08/12/2020 06:01 PM 552 AppleRGB.icc 08/12/2020 06:01 PM 557,120 CoatedFOGRA27.icc 08/12/2020 06:01 PM 654,352 CoatedFOGRA39.icc 08/12/2020 06:01 PM 560 ColorMatchRGB.icc 08/12/2020 06:01 PM 548 Display P3.icc 08/12/2020 06:01 PM 557,168 JapanColor2001Coated.icc 08/12/2020 06:01 PM 557,168 JapanColor2001Uncoated.icc 08/12/2020 06:01 PM 557,172 JapanColor2002Newspaper.icc 08/12/2020 06:01 PM 557,164 JapanWebCoated.icc 08/12/2020 06:01 PM 564 ROMM RGB.icc 08/12/2020 06:01 PM 654,140 UncoatedFOGRA29.icc 08/12/2020 06:01 PM 557,168 USSheetfedCoated.icc 08/12/2020 06:01 PM 557,168 USSheetfedUncoated.icc 08/12/2020 06:01 PM 557,168 USWebCoatedSWOP.icc 08/12/2020 06:01 PM 557,164 USWebUncoated.icc 08/12/2020 06:01 PM 654,140 WebCoatedFOGRA28.icc 17 File(s) 6,979,876 bytes 2 Dir(s) 131,918,311,424 bytes free Note that "Display P3.icc" and "ROMM RGB.icc" do not appear in Chris B's list. All the others do appear. Here is Windows > System32 > spool > drivers > color Directory of C:\Windows\System32\spool\drivers\color 10/26/2020 10:03 PM <DIR> . 10/26/2020 10:03 PM <DIR> .. 05/17/2012 12:00 AM 329,328 CNBBLDB0.ICM 05/17/2012 12:00 AM 329,340 CNBBLKB0.ICM 05/17/2012 12:00 AM 329,340 CNBBLKC0.ICM 05/17/2012 12:00 AM 329,328 CNBBLMB0.ICM 05/17/2012 12:00 AM 329,328 CNBBLMC0.ICM 05/17/2012 12:00 AM 329,328 CNBBLNA0.ICM 05/17/2012 12:00 AM 329,328 CNBBLNB0.ICM 05/17/2012 12:00 AM 329,328 CNBBLNC0.ICM 09/26/2005 12:00 AM 17,552 CNBJPRN3.ICM 05/28/2012 10:31 AM 216,160 CNFRC2.ICC 12/07/2019 03:08 AM 1,058 D50.camp 12/07/2019 03:08 AM 1,079 D65.camp 12/07/2019 03:08 AM 797 Graphics.gmmp 12/07/2019 03:08 AM 838 MediaSim.gmmp 12/07/2019 03:08 AM 786 Photo.gmmp 12/07/2019 03:08 AM 822 Proofing.gmmp 12/07/2019 03:08 AM 218,103 RSWOP.icm 12/07/2019 03:08 AM 3,144 sRGB Color Space Profile.icm 12/07/2019 03:08 AM 17,155 wscRGB.cdmp 12/07/2019 03:08 AM 1,578 wsRGB.cdmp 20 File(s) 3,113,720 bytes Note that none of these has been modified later than 2019 and up until a few days ago Designer 1.8.5 was working. If Designer is pulling a bad color profile from its Resources\icc, how it could survive a re-install? If from spool\drivers\color what changed? Still sad but appreciate the support, J.Michael
  8. @Chris B Thanks for your reply and taking the time to test this on your system. Automatic conversion is on, but since the profile of the file and my Working-RGB-Profile are both ROMM RGB, there is nothing to convert. Perhaps you may want to try again with the RGB-Profiles set to ROMM RGB? Thanks in advance.
  9. Expected behavior: In Affinity Photo, apply a scanner profile to a raw scan with no profile, then convert to a working space such as ROMM RGB. 1) Results should be very similar to doing the same steps in an external app (I don't expect that they'd be pixel-perfect, but any differences should not be perceptible). 2) There shouldn't be any visible color casts in the result. Actual behavior: Results are perceptibly different between Affinity Photo's result and argyllcms' cctiff. Given a scanned IT8/7.2 target with the profile applied and then converted to ROMM RGB (once in Affinity, and then once with cctiff on a copy of the image), for Affinity Photo the dark grey rectangles in the image have a reddish color cast to them, whereas the output of cctiff has those squares as a neutral grey. Repro steps: To generate the Affinity Photo output: Open the unprofiled image ("raw0010_2019-5-20-downsampled.tiff"). Document->Assign ICC Profile... then Assign the desired scanner profile ("2019-10-27_qh_as_u"). Document->Convert Format/ICC Profile... then Convert to the desired working space profile ("ProPhoto RGB"--see Note 1). Rendering Intent is Relative Colourimetric. Black Point Compensation is on (it also repros with BPC off... doesn't matter). Observe that the grey rectangles at the bottom of the image have a reddish color cast to some of them, #19-21 in particular. (The RGB values confirm that there's more red present.) To generate the cctiff output (can use GIMP instead--see Note 3): Install cctiff. I downloaded the source code, v2.1.1, at https://www.argyllcms.com/downloadsrc.html and compiled it on my Mac. Run cctiff like so: ~/Argyll_V2.1.1/imdi/cctiff -e ~/Argyll_V2.1.1/icc/ProPhoto.icm -ir /PATH/TO/2019-10-27_qh_as_u.icc -ir ~/Argyll_V2.1.1/icc/ProPhoto.icm /PATH/TO/raw0010_2019-5-20-downsampled.tiff /PATH/TO/2019-5-20-downsampled-output_of_cctiff.tiff Observe that the grey rectangles at the bottom of the image are all neutral grey. Notes: ProPhoto.icm (which displays as "ProPhoto RGB" in Affinity Photo) is argyll's included ProPhoto color profile (which I imported into Affinity's color profiles by just opening some existing file that already had that profile embedded). However, this still repros if I instead convert to the included ROMM RGB profile in Affinity. The scanner profile was generated by argyll separately (scanin and colprof). (I actually used this exact raw image to generate the profile.) I can also generate the expected output (i.e. no reddish color cast in the dark greys) with GIMP (it's using argyllcms under the hood). Just apply the scanner profile, then convert. I don't have Photoshop so I can't do this experiment there. I'm on Affinity Photo 1.8.3, but this repros on 1.7.x as well. I've also attached the output of Affinity Photo's Preferences->Color menu, just in case those settings matter. ProPhoto.icm 2019-10-27_qh_as_u.icc raw0010_2019-5-20-downsampled.tiff 2019-5-20-downsampled-output_of_affinity_photo.tiff 2019-5-20-downsampled-output_of_cctiff.tiff
  10. Hey @jomaro, hopefully this should give you enough info to work with.. Looks like you have an OCIO configuration set up, and your EXR file is appended with "acescg"? So Photo will convert from ACEScg to scene linear because it's found a matching profile. It's just the way 32-bit linear in Photo works—everything is converted to scene linear, then the colour space is defined either by traditional display profile conversion (ICC) or via OCIO. You choose which using the 32-bit preview panel (View>Studio>32-bit Preview). Bear in mind that if you plan to export from Affinity Photo as a gamma-encoded format (16-bit, 8-bit JPEG/TIFF etc), you need to preview using ICC Display Transform. So just to clarify, the document's colour profile (e.g. sRGB, ROMM RGB etc) is arbitrary and only applied when using ICC Display Transform—then the scene linear values are converted and bounded to that profile. If you choose Unmanaged, you'll be looking at the linear values. OCIO Display Transform will convert the scene linear values according to the view and device transforms that are mandated in the combo boxes. You would need to install a given ICC profile for that to show up. However, I suspect you probably want to be managing with OpenColorIO. Looks like you've already managed to set it up, but here's a reference video just in case: Within the 32-bit preview panel, you will want to choose OCIO Display Transform (it will be enabled by default with a valid OCIO configuration). Then you set your view transform on the left and device transform on the right. The OCIO adjustment layer is for moving between colour spaces within the same document—you might want to do this for compositing layers with different source colour spaces, for example. You can also bake in colour space primaries if you wish to do that as well (typically go from scene linear to whichever colour space you require). Yes, Photo can convert to profiles on import/export by appending the file name with a given colour space. For example, if you imported a file named "render aces.exr", it would convert from the ACES colour space to scene linear. Similarly, if you append "aces" to your file name when you export back to EXR, it will convert the document primaries from scene linear back to ACES. Hopefully the above all helps? Let me know if you have any further questions!
  11. @AiDon I know - Serif calls it ROMM RGB. https://en.wikipedia.org/wiki/ProPhoto_RGB_color_space Why did you mention this? None of your postings in this thread refers to the Color-Profile your are using. I just wanted to explain, why I chose ROMM RGB.
  12. Hi, Assuming I'm trying to load in AP TIFF files that are tagged as sRGB but with no embedded profile. My AP working color space is ROMM RGB (Prophoto). In that case, the sRGB profile should be assumed (W3C/ICC). But AP is obviously displaying the wrong oversaturated colors. If I change the working color space to sRGB, there's no problem. I'm not aware of any other application having this problem. All the image handling applications/viewers/browsers I'm using are displaying these files with the correct colors. Attached are the AP version and the PS version (same file, correct colors). I get the same result with all other applications/viewers/browsers as in PS. Same result if I disable the “Convert opened files to working space” option.
  13. Edit > Preferences > Misc > Reset Default Text Styles The file i uploaded previously still freezes the UI solid when clicking Text Styles. The "beta" file modified by Old Bruce still freezes the UI in the same way. I have two folders in %AppData% > Affinity > Designer called 1.0 and 1.0 (beta). Renamed both to 1.1 Restart Designer without a system restart. Designer asks me to sign in and recreates 1.0 (beta) so the app reset was successful. The file i uploaded previously still freezes the UI solid when clicking Text Styles. Sigh! Here is the log file from the new 1.0 (beta). There's an error at the end: "Failed to create tablet context". (Note that I'm running on a PC not a tablet.) Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: Intel(R) UHD Graphics 620 Primary: Yes Has user profile: Yes Profile name: sRGB Color Space Profile.icm System Found 10 system profiles (parsed 10) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): sRGB Color Space Profile.icm Loading colour profile (system): RSWOP.icm Skipping colour profile (system): Proofing.gmmp Skipping colour profile (system): Photo.gmmp Skipping colour profile (system): MediaSim.gmmp Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Found 10 user profiles (parsed 10) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): sRGB Color Space Profile.icm Loading colour profile (user): RSWOP.icm Skipping colour profile (user): Proofing.gmmp Skipping colour profile (user): Photo.gmmp Skipping colour profile (user): MediaSim.gmmp Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Installed Loading colour profile: AdobeRGB1998.icc Loading colour profile: AppleRGB.icc Loading colour profile: CoatedFOGRA27.icc Loading colour profile: CoatedFOGRA39.icc Loading colour profile: ColorMatchRGB.icc Loading colour profile: Display P3.icc Loading colour profile: JapanColor2001Coated.icc Loading colour profile: JapanColor2001Uncoated.icc Loading colour profile: JapanColor2002Newspaper.icc Loading colour profile: JapanWebCoated.icc Loading colour profile: ROMM RGB.icc Loading colour profile: UncoatedFOGRA29.icc Loading colour profile: USSheetfedCoated.icc Loading colour profile: USSheetfedUncoated.icc Loading colour profile: USWebCoatedSWOP.icc Loading colour profile: USWebUncoated.icc Loading colour profile: WebCoatedFOGRA28.icc Imported -- 691.7638ms Wintab: Failed to load Wintab32.dll Wintab: Failed to create tablet context Attempting to create Direct3D device on default adapter Setting screen DPI to 71.1725119738834 (scale = 1.145833) Exit
  14. I just updated to Affinity Photo 1.7 In the previous version of Affinity Photo in Develop Persona you had the option of choosing romm RGB Profiles in the pull down menu. What happen to it? Do you have to reload it some other way? Never mind....I was able to load the ROMM RGB into Develop Persona Profiles
  15. @anon2 Thanks for your reply. Based on that I tried the following: no convert the final panorama but convert the individual images and then make the pano from them. first I re-enabled the "Convert opened files to working space" - Option then I opened all images individually, (they are auto-converted from sRGB to ROMM RGB) and saved them again (ROMM RGB). after that I used the panorama-tool again with those converted images and the result was fine. To me, this is evidence that you are right ("..just assigns the ROMM profile without converting the pixel values..") and makes me more secure that no color-information is lost during the panorama-stitching since the ROMM-RGB gamut is wider/bigger than sRGB. Thanks. Fritz
  16. well, that´s in fact the same which I do - I just added some explanation about the conversion to another Color-Profile (ROMM RGB)... I do this to make sure that elements like e.g. the sky have enough "color-space" available during stitching to avoid color-clipping.
  17. I use to use ProPhoto RGB as my working space. Should I choose ROMM RGB now at Preferences>Colour (AFF.Photo)? Thank you.
  18. Embedding the ICC profile is one of the More... options when exporting a PNG from Affinity. If PNG files can't have an embedded color profile, perhaps that should be removed? Next, the Color Preference in Affinity is to warn when assigning the working profile to "unprofiled" files. It is unclear to me whether this means: FIles without an embedded color profile; or Files without a color tag. #2 seems more likely to me, as a file can be tagged as, e.g., sRGB ISO-whatever or as ROMM-RGB whether or not it has the profile actually embedded. Or it can be untagged. Only in the case where it's untagged would Affinity need to assign a profile, unless the user's Color Preferences also included "convert to working space".
  19. I looked in the forums and google but i couldn't really find a solid answer. Im working on an album cover and normally for all my work (regardless of if i plan to print or not i) just set it to "print" when i open a new document. I may have fiddled a bit with the profiles in the past but i cant remember what the default is. does it make any difference?
  20. I'm creating a panorama in Affinity Photo (version 1.8.3 at the moment) from DNG files. These files are the native format of my Pentax K-3 II camera. The program will always create a panorama photo in RGBA/16 with the sRGB color profile. Therefore highlights and shadows are easily clipped and I'm wondering if I can make Affinity Photo to create a panorama photo with a wider color space. I have set the ROMM color profile for both RGB and RGB/32 photos in the settings (I'm on Windows 10 btw). It doesn't seem to have an impact on the panorama creation process, because I end up with an sRGB photo all the time. I know I could process my RAW photos before stitching, then export them as TIFF files with a color space of my choice. Then Affinity Photo would end up creating a panorama picture with the same color space. But I often want to see first, how well the stitching will work, before investing too much time into editing the photo. I would also prefer to stitch the DNGs in Affinity Photo, export the result as TIFF and import it into Lightroom for further management and editing (unless there are edits I need Affinity Photo for). Does anybody know, why Affinity Photo ignores the wider color space of DNG files when creating a panorama? Is this a defect?
  21. @SPaceBar So AfftiyPhoto 1.8.5 runs great with my my XP-Pen Monitor in low precision. But once I change to high precision is where the same issue occurs. Here is the log as you requested. Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: NVIDIA GeForce GTX 1060 6GB Primary: Yes Has user profile: No Profile name: QuickGammaProfile20191226.icc Name: Generic PnP Monitor Adapter: NVIDIA GeForce GTX 1060 6GB Primary: No Has user profile: No Profile name: sRGB Color Space Profile.icm Name: S230HL Adapter: NVIDIA GeForce GTX 1060 6GB Primary: No Has user profile: No Profile name: sRGB Color Space Profile.icm System Found 18 system profiles (parsed 18) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): sRGB Color Space Profile.icm Loading colour profile (system): S230HL.ICM Loading colour profile (system): RSWOP.icm Loading colour profile (system): QuickGammaProfile20191226.icc Skipping colour profile (system): Proofing.gmmp Skipping colour profile (system): Photo.gmmp Loading colour profile (system): perv550r.icc Loading colour profile (system): perv550f.icc Skipping colour profile (system): MediaSim.gmmp Skipping colour profile (system): Graphics.gmmp Loading colour profile (system): ewsrgb.icm Loading colour profile (system): ewrgb18.icm Loading colour profile (system): ewgray22.icm Loading colour profile (system): ewgray18.icm Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Found 18 user profiles (parsed 18) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): sRGB Color Space Profile.icm Loading colour profile (user): S230HL.ICM Loading colour profile (user): RSWOP.icm Loading colour profile (user): QuickGammaProfile20191226.icc Skipping colour profile (user): Proofing.gmmp Skipping colour profile (user): Photo.gmmp Loading colour profile (user): perv550r.icc Loading colour profile (user): perv550f.icc Skipping colour profile (user): MediaSim.gmmp Skipping colour profile (user): Graphics.gmmp Loading colour profile (user): ewsrgb.icm Loading colour profile (user): ewrgb18.icm Loading colour profile (user): ewgray22.icm Loading colour profile (user): ewgray18.icm Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Installed Loading colour profile: AdobeRGB1998.icc Loading colour profile: AppleRGB.icc Loading colour profile: CoatedFOGRA27.icc Loading colour profile: CoatedFOGRA39.icc Loading colour profile: ColorMatchRGB.icc Loading colour profile: Display P3.icc Loading colour profile: JapanColor2001Coated.icc Loading colour profile: JapanColor2001Uncoated.icc Loading colour profile: JapanColor2002Newspaper.icc Loading colour profile: JapanWebCoated.icc Loading colour profile: ROMM RGB.icc Loading colour profile: UncoatedFOGRA29.icc Loading colour profile: USSheetfedCoated.icc Loading colour profile: USSheetfedUncoated.icc Loading colour profile: USWebCoatedSWOP.icc Loading colour profile: USWebUncoated.icc Loading colour profile: WebCoatedFOGRA28.icc Imported -- 367.6756ms Wintab: Failed to get tangent pressure info TabletContext::Create: original queue size is 32 TabletContext::Create: new queue size is 128 Attempting to create Direct3D device on default adapter Setting screen DPI to 84.8139130434783 (scale = 1.0) Exit
  22. Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: Intel(R) HD Graphics 620 Primary: Yes Has user profile: No Profile name: sRGB Color Space Profile.icm System Found 10 system profiles (parsed 10) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): sRGB Color Space Profile.icm Loading colour profile (system): RSWOP.icm Skipping colour profile (system): Proofing.gmmp Skipping colour profile (system): Photo.gmmp Skipping colour profile (system): MediaSim.gmmp Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Found 10 user profiles (parsed 10) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): sRGB Color Space Profile.icm Loading colour profile (user): RSWOP.icm Skipping colour profile (user): Proofing.gmmp Skipping colour profile (user): Photo.gmmp Skipping colour profile (user): MediaSim.gmmp Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Installed Loading colour profile: AdobeRGB1998.icc Loading colour profile: AppleRGB.icc Loading colour profile: CoatedFOGRA27.icc Loading colour profile: CoatedFOGRA39.icc Loading colour profile: ColorMatchRGB.icc Loading colour profile: Display P3.icc Loading colour profile: JapanColor2001Coated.icc Loading colour profile: JapanColor2001Uncoated.icc Loading colour profile: JapanColor2002Newspaper.icc Loading colour profile: JapanWebCoated.icc Loading colour profile: ROMM RGB.icc Loading colour profile: UncoatedFOGRA29.icc Loading colour profile: USSheetfedCoated.icc Loading colour profile: USSheetfedUncoated.icc Loading colour profile: USWebCoatedSWOP.icc Loading colour profile: USWebUncoated.icc Loading colour profile: WebCoatedFOGRA28.icc Imported -- 636.1729ms
  23. First of all: I am honored that "Professor, Dr. Mr. Photo himself" Ritson answered my question :-) "...you must take into consideration how this affects all imagery you bring into Affinity Photo." OK, .... so why is there no visible color-shift when opening the images individually? To me that means: the images are converted from sRGB (Xiaomi) to my working profile (ROMM RGB) without noticeable issues. "...Convert opened files to working space option—could you check your own preferences?" done; as expected you are right. Changed that option: issue gone. "If you open a single JPEG image, what does the colour profile entry read in the top left?" the Metadata-Panel shows sRGB, top-left info too. (after having changed the settings as you suggested) My thinking was/is: ROMM RGB offers more colors. OK. That feature is needed for HDR etc. and may also be useful when working with panoramas since the stitching will merge multiple sources, each contributing its own range of used colors (depending on the contents of the picture..) into one final image. Therefore my guessing is: having a wider range of colors "available" may prevent losing color-information. (Before you answer: I know: such detailed thoughts on one hand and using a cheap smartphone on the other does not match: true. Usually I do not use a smartphone to take pictures, but it was a lucky situation to see this location with hardly any people around (#Corona)...) kind regards Fritz
  24. @SPaceBar To be clear you want me to do this with the new Customer Beta\Designer.exe\ that works not the old one that was crashing (1.8.4.693 ). Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: NVIDIA GeForce GTX 1060 6GB Primary: Yes Has user profile: No Profile name: QuickGammaProfile20191226.icc Name: Generic PnP Monitor Adapter: NVIDIA GeForce GTX 1060 6GB Primary: No Has user profile: No Profile name: sRGB Color Space Profile.icm Name: S230HL Adapter: NVIDIA GeForce GTX 1060 6GB Primary: No Has user profile: No Profile name: sRGB Color Space Profile.icm System Found 18 system profiles (parsed 18) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): sRGB Color Space Profile.icm Loading colour profile (system): S230HL.ICM Loading colour profile (system): RSWOP.icm Loading colour profile (system): QuickGammaProfile20191226.icc Skipping colour profile (system): Proofing.gmmp Skipping colour profile (system): Photo.gmmp Loading colour profile (system): perv550r.icc Loading colour profile (system): perv550f.icc Skipping colour profile (system): MediaSim.gmmp Skipping colour profile (system): Graphics.gmmp Loading colour profile (system): ewsrgb.icm Loading colour profile (system): ewrgb18.icm Loading colour profile (system): ewgray22.icm Loading colour profile (system): ewgray18.icm Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Found 18 user profiles (parsed 18) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): sRGB Color Space Profile.icm Loading colour profile (user): S230HL.ICM Loading colour profile (user): RSWOP.icm Loading colour profile (user): QuickGammaProfile20191226.icc Skipping colour profile (user): Proofing.gmmp Skipping colour profile (user): Photo.gmmp Loading colour profile (user): perv550r.icc Loading colour profile (user): perv550f.icc Skipping colour profile (user): MediaSim.gmmp Skipping colour profile (user): Graphics.gmmp Loading colour profile (user): ewsrgb.icm Loading colour profile (user): ewrgb18.icm Loading colour profile (user): ewgray22.icm Loading colour profile (user): ewgray18.icm Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Installed Loading colour profile: AdobeRGB1998.icc Loading colour profile: AppleRGB.icc Loading colour profile: CoatedFOGRA27.icc Loading colour profile: CoatedFOGRA39.icc Loading colour profile: ColorMatchRGB.icc Loading colour profile: Display P3.icc Loading colour profile: JapanColor2001Coated.icc Loading colour profile: JapanColor2001Uncoated.icc Loading colour profile: JapanColor2002Newspaper.icc Loading colour profile: JapanWebCoated.icc Loading colour profile: ROMM RGB.icc Loading colour profile: UncoatedFOGRA29.icc Loading colour profile: USSheetfedCoated.icc Loading colour profile: USSheetfedUncoated.icc Loading colour profile: USWebCoatedSWOP.icc Loading colour profile: USWebUncoated.icc Loading colour profile: WebCoatedFOGRA28.icc Imported -- 319.9821ms Wintab: Failed to get tangent pressure info TabletContext::Create: original queue size is 32 TabletContext::Create: new queue size is 128 Attempting to create Direct3D device on default adapter Setting screen DPI to 84.8139130434783 (scale = 1.0) Exit
  25. Hi @Fritz_H, the issue is not related to a 10-bit panel, wide gamut display, anything like that. I simply think it's your colour preferences and how your workspace colour settings are configured. I appreciate you want to work in ROMM RGB for more intense colours, but because you have changed the default colour profile (rather than changing it on a per-image basis whenever you develop a RAW file), you must take into consideration how this affects all imagery you bring into Affinity Photo. Normally, with panorama stitching, the colour profile will be inferred from the images you provide during the stitching process. For example, if you are stitching JPEGs tagged with Adobe RGB, the final panorama document will be in Adobe RGB. This is true, even if your default RGB Colour Profile in Preferences>Colour is different. However, there are circumstances when your RGB Colour Profile choice will be used: if the images do not contain any colour profile tagging (you will typically receive a message in the top right explaining your image has been assigned a colour space), or if you have explicitly enabled Convert opened files to working space in Preferences>Colour. The only way I could reproduce your issue with panorama stitching is by going to Preferences>Colour and enabling the Convert opened files to working space option—could you check your own preferences? If that option is enabled, disable it, then see if your colours are correct. Note that it is disabled by default, so at some point I suspect you may have manually enabled it? Hopefully that will solve your issue. However, do be aware that I'm unsure as to whether your Xiaomi smartphone JPEGs are intended to be in sRGB or a wider colour space—similar to iPhones and how their images are tagged with Display P3. If you open a single JPEG image, what does the colour profile entry read in the top left?
×
×
  • 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.