Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for 'ROMM RGB'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. Thanks. My research indicates that ROMM is basically ProPhoto RGB; gamut covers almost every reflected color humans could see; only possible weakness in specular reflections. Oddly, when I use the Develop Persona, if I choose the ROMM Profile, even with the Develop Assistant set to RGB 32 (HDR), Photo assigns the RGBA/16 color model (and ROMM profile) to the image. Why the 16 instead of the 32?
  2. Affinity Publisher crashes right after startup. This is a fresh installation. The log file looks like this. What is the problem here? AppData\Roaming\Affinity\Publisher\1.0 [DXCore] Error 0x80004002 (298): Failed to create adapter factory! [DXCore] Error 0x80004002 (298): Failed to create adapter factory! [DXCore] Error 0x80004002 (298): Failed to create adapter factory! 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 Name: Generic PnP Monitor Adapter: Intel(R) HD Graphics 620 Primary: No 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.4796ms
  3. Thanks for the reply. Yeah, I only imported the JPEG to determine whether it wasn't Preview that was screwing up, figuring that, if the program that generated it didn't display it as I expected, it was indeed the program that was at fault, not other programs that might display it. I did export in TIFF-16, PNG-24, etc., but they all looked similar in Preview to the JPEG. The only thing that worked was TIFF-16 with layers, but only when I imported into Affinity Photo and found that all the adjustment layers and live filter were there. So apparently the TIFF format allows arbitrary "stuff" to be occur in the file, and applications that can't do anything with it at least don't choke on it. I was pretty careful with the profiles, telling Develop to use the ROMM RGB: ISO 22028-2-2013 (Linear) profile, ensuring that, in the Photo Persona, the document colour format was set to RGB (32 bit), and even checking in Preview what profile was embedded in the files exported from Affinity Photo. I can't imagine that a modern program like Affinity Photo, or, for that matter, any of the Apple programs, has problems with profiles. On a Mac, applications needn't worry about monitor profiles, as that is handled by the OS. Apps just worry about app-specific profiles. So juggling different profiles, since support for the monitor profiles comes from macOS, not from each application. So Affinity Photo only has to worry about, in this case, ROMM RGB: ISO 22028-2-2013 (Linear). In fact, I did do the exact same work, starting with the NEF and specifying sRGB IEC61966-2.1(Linear), then, first thing in the Photo Persona, setting the document color format to RGB (16 bit) and proceeding to recreate the same workflow of adjustments and live filters. I could not get a result that was the same as the other, but I got one that was good, exported in various formats, and was still not satisfied. Maybe it's just me. The problem with using an external exporter is, as far as I understand, none of them understand .afphoto files, so I have to export something out of Affinity Photo, and I haven't been satisfied with any of the export formats. As I said, when I flattened the layers I found that the resulting pixel layer was a less than faithful rendition of the original. I assume that any export must go through a flattening phase before the specified sampling is performed and the result formatted for the required file type.
  4. After I updating all three Affinity products for windows from 1.85 to 1.9.0 (successfully), none of them can be started. All I saw was a couple of seconds of splash window, then nothing appeared. I have manually updated my Graphics drivers and set the Graphics preference as High performance. None of them helped. The info from %AppData%\Affinity\Publisher as below: [DXCore] Found 2 adapters Intel(R) HD Graphics 515 Version: 27.20.100.9168 IsHardware: Yes Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_8086&DEV_191E&SUBSYS_38120000&REV_07 LUID: 0xE254 Microsoft Basic Render Driver Version: 10.0.19041.546 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xE608 Now I cannot run/use the latest version. I am able to run the older version after I uninstalled the 1.9 and reinstalled 1.85. I am running Win 10 with the machine: Lenovo Miix 700-12ISK (ideapad) - Type 80QL with serial number PF0E9611 Additional info: I could install and run 1.90 version on my another older computer. The info from %AppData%\Affinity\Publisher\1 as below: [DXCore] Found 2 adapters Intel(R) HD Graphics Version: 8.15.10.2900 IsHardware: Yes Supports D3D12 Feature Level 12.0: No HardwareID: PCI\VEN_8086&DEV_0046&SUBSYS_031C0000&REV_12 LUID: 0x10C62 Microsoft Basic Render Driver Version: 10.0.19041.546 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0x10E2A [OpenCL] Not available [OpenCL] Not available [OpenCL] Not available Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: Intel(R) HD Graphics Primary: Yes Has user profile: No Profile name: sRGB Color Space Profile.icm System Found 11 system profiles (parsed 11) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): U28E510D.icm 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 11 user profiles (parsed 11) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): U28E510D.icm 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 -- 4234.5388ms Wintab: Failed to load Wintab32.dll Wintab: Failed to create tablet context Attempting to create Direct3D device on default adapter Setting screen DPI to 106.387434554974 (scale = 1.0) Exit It seems that my newer computer failed to load colour profiles. Not sure what should I do in order to run the new version on my newer computer which is the one I'm using to do most of my work.
  5. [DXCore] Found 3 adapters AMD Radeon R5 330 Version: 8.17.10.1404 IsHardware: Yes Supports D3D12 Feature Level 12.0: No HardwareID: PCI\VEN_1002&DEV_6665&SUBSYS_90F10000&REV_83 LUID: 0xC883 Microsoft Basic Render Driver Version: 10.0.19041.546 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xC85D Intel(R) HD Graphics 530 Version: 25.20.100.6446 IsHardware: Yes Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_8086&DEV_1912&SUBSYS_2B470000&REV_06 LUID: 0xC413 [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO Loading colour profiles Monitors Name: HP 24ea Display Adapter: Intel(R) HD Graphics 530 Primary: Yes Has user profile: No Profile name: HP_24ea.icm System Found 13 system profiles (parsed 13) 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 Loading colour profile (system): HP_24ea.icm Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Loading colour profile (system): CNFRB6.ICC Loading colour profile (system): CNBJPRN3.ICM Found 13 user profiles (parsed 13) 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 Loading colour profile (user): HP_24ea.icm Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Loading colour profile (user): CNFRB6.ICC Loading colour profile (user): CNBJPRN3.ICM 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 -- 667.8987ms
  6. [DXCore] Found 3 adapters AMD Radeon R5 330 Version: 8.17.10.1404 IsHardware: Yes Supports D3D12 Feature Level 12.0: No HardwareID: PCI\VEN_1002&DEV_6665&SUBSYS_90F10000&REV_83 LUID: 0xC883 Microsoft Basic Render Driver Version: 10.0.19041.546 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xC85D Intel(R) HD Graphics 530 Version: 25.20.100.6446 IsHardware: Yes Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_8086&DEV_1912&SUBSYS_2B470000&REV_06 LUID: 0xC413 [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO [OpenCL] Found 2 platforms: Name: AMD Accelerated Parallel Processing Vendor: Advanced Micro Devices, Inc. Version: OpenCL 2.0 AMD-APP (1800.12) Name: Intel(R) OpenCL Vendor: Intel(R) Corporation Version: OpenCL 2.1 [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing: AMD Radeon R5 330 Vendor: Advanced Micro Devices, Inc. Version: OpenCL 1.2 AMD-APP (1800.12) (Skipping unsupported device) [OpenCL] Found 1 devices for platform Intel(R) OpenCL: Intel(R) HD Graphics 530 Vendor: Intel(R) Corporation Version: OpenCL 2.1 NEO Loading colour profiles Monitors Name: HP 24ea Display Adapter: Intel(R) HD Graphics 530 Primary: Yes Has user profile: No Profile name: HP_24ea.icm System Found 13 system profiles (parsed 13) 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 Loading colour profile (system): HP_24ea.icm Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Loading colour profile (system): CNFRB6.ICC Loading colour profile (system): CNBJPRN3.ICM Found 13 user profiles (parsed 13) 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 Loading colour profile (user): HP_24ea.icm Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Loading colour profile (user): CNFRB6.ICC Loading colour profile (user): CNBJPRN3.ICM 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 -- 641.6558ms Wintab: Failed to load Wintab32.dll Wintab: Failed to create tablet context Attempting to create Direct3D device on default adapter Setting screen DPI to 92.53889943074 (scale = 1.0) Exit
  7. Same result after Clear. Here is the Log.txt : Loading colour profiles Monitors Name: Generic PnP Monitor Adapter: AMD Radeon HD 8550G Primary: Yes Has user profile: No Profile name: sRGB Color Space Profile.icm System Found 27 system profiles (parsed 27) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): WebCoatedFOGRA28.icc Loading colour profile (system): USWebUncoated.icc Loading colour profile (system): USWebCoatedSWOP.icc Loading colour profile (system): USSheetfedUncoated.icc Loading colour profile (system): USSheetfedCoated.icc Loading colour profile (system): UncoatedFOGRA29.icc 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 Loading colour profile (system): JapanWebCoated.icc Loading colour profile (system): JapanColor2002Newspaper.icc Loading colour profile (system): JapanColor2001Uncoated.icc Loading colour profile (system): JapanColor2001Coated.icc Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Loading colour profile (system): ColorMatchRGB.icc Loading colour profile (system): CoatedFOGRA39.icc Loading colour profile (system): CoatedFOGRA27.icc Loading colour profile (system): CNFRCB.ICC Loading colour profile (system): CNBJPRN3.ICM Loading colour profile (system): AppleRGB.icc Loading colour profile (system): AdobeRGB1998.icc Found 27 user profiles (parsed 27) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): WebCoatedFOGRA28.icc Loading colour profile (user): USWebUncoated.icc Loading colour profile (user): USWebCoatedSWOP.icc Loading colour profile (user): USSheetfedUncoated.icc Loading colour profile (user): USSheetfedCoated.icc Loading colour profile (user): UncoatedFOGRA29.icc 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 Loading colour profile (user): JapanWebCoated.icc Loading colour profile (user): JapanColor2002Newspaper.icc Loading colour profile (user): JapanColor2001Uncoated.icc Loading colour profile (user): JapanColor2001Coated.icc Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Loading colour profile (user): ColorMatchRGB.icc Loading colour profile (user): CoatedFOGRA39.icc Loading colour profile (user): CoatedFOGRA27.icc Loading colour profile (user): CNFRCB.ICC Loading colour profile (user): CNBJPRN3.ICM Loading colour profile (user): AppleRGB.icc Loading colour profile (user): AdobeRGB1998.icc 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 -- 11664.192751ms
  8. I have some Kodak Gold negatives that I want to scan, then develop in Affinity Photo. Is there any point in scanning these negatives so I can open them as 32-bit ROMM-RGB files? (My scanner is capable of producing 48-bit DNG files.) i.e. Would I get any more detail from such a file than from a 16-bit TIFF scan? In other words, I'm not sure how much dynamic range is in a colour negative.
  9. Take also a look at and the https://en.wikipedia.org/wiki/Color_space conversion of color spaces, the mapping of one color from one space into a color of another space. Wider color spaces as sRGB (like Adobe RGB, ProPhoto/ROMM) do have and offer colors you can't directly/exactly map 1:1 into lower color spaces, since the lower color space might not contain that color at all. Thus also look at the different gamut sizes (color space sizes) shown there in the above link. - BTW, ProPhoto RGB and ROMM RGB are (or should) be nearly the same, since it's usually just another name for the same child. Also if you initially create the images in Adobe Animate, what color space do you use there (sRGB ?) and do you embbed the used profile from there into your exported PNG images or not? Meaning do you save the PNG with an reusable embedded color profile or not?
  10. Thank you all for your replies and contributions. The document was indeed intended for a professional printer, hence the CMYK setting. The company that is going to print the (A0) document is using EPS as their standard document type. I managed to get the desired output by first changing the document from RGB to CMYK, while using the appropriate profile, ISO coated V2. Then I exported the document to EPS. I then used undo to get the RGB document back, and did the procedure again, but now with the PSO Coated V3 profile. When that was done, I used undo once again. If I understand this correctly, I can use the 16 bit RGB setting combined with the ROMM profile for the maximum colour information. If I export such an image to JPEG and embed the colour profile, then such a picture should show up fine on any PC, assuming the PC has a colour profile setting attached to the monitor. The colour information will be recalculated from the embedded profile to the display profile. Printing is another matter. I have no colour profiles for my printer, and as far as I know I would need to set them up for different paper types and print qualities. The Fuji profiles came from a photo book producer, who publishes them on their web site, so you can use them if you want.
  11. I have a color cast issue, in Affinity Photo 1.7.1.404, that I am trying to explain, in terms of the cause. I use Nik Silver to generate B&W pixel layers. Most of the time I am using RGB16, ProPhoto. I was working on an image and noticed green and red in a layer that should be grayscale! I have two computers, with dual monitors - all calibrated with Xrite. I used the color picker to confirm that the RGB values are the same, so the areas are gray, but the display is not! The layer is the output from Nik SilverFX, without any toning applied. I changed the pixel layer to grayscale, then the color bands disappeared. I then tried various color spaces. Strangely, the color cast that manifests in ProPhoto is removed if I switch to sRGB: I then gave ROMM a shot, but the color cast returns: I then tried LAB16 and HDR32 - no color cast (I didn't upload the HDR32 example): I am trying to understand what's going on, and how to explain the display output, at least to myself. But, I can't since I don't really know what's at issue. I also exported the file, about 572 MB, as a PSD, then opened it in PS CS6. I don't see the color casts, banding of red and green in PS. So, I am inclined to conclude that: -it's not a hardware issue, as the banding shows up on two different computers (Nvidia or Intel graphics; Windows 10 Pro; four different monitors - all Xrite calibrated, recently) -is a software issue, probably related to Affinity Photo or Nik, since the color space does impact the display within AP. ProPhoto and ROMM seem to have the same issues. Output files (JPG, PNG, TIFF) do not show the color issues. I generally Develop into ProPhoto 16-bit, to start, and only switch to sRGB and/or 8-bit on export. I searched the forum content and could not find a similar color space issue. Perhaps I don't know which terms will produce the similar issues? Thanks for any suggestions, Greg
  12. Why is it not possible to get a romm-rgb output from stacks? The s-rgb is rather limiting with what one can then achieve with manipulation.
  13. Hi @Murfee, Thanks for moving your posting here. As a matter of fact, when I first began using Affinity Photo, having previously used nothing, not even the ubiquitous products from Adobe, I did everything in 32 bit mode with the ROMM profile, i.e., development and editing. That seemed to be the cause of a curious effect that I can only describe as looking at my work in Affinity Photo and exported JPEGs as if through a veil, or dirty window. The colors were muddy, not clear. For a time I thought I just needed to add a tone curve, and I was satisfied until I began using DxO Photo Lab 2. The colors seemed deeper, clearer. I put the question to one of these forums, whether it is possible to produce something comparable to the output from PL2 with AFP, and one person took a crack at it and produced a .afphoto that compared favorably. I noticed that the output of Develop was 16 bit, and I questioned him about that. Then I reconfigured AFP to produce 16 bit from Develop and never turned back ... until now. I created a 32 bit workflow from a RAW file that I had previously developed, edited and printed in 16 bit using the ROMM profile. The veil phenomenon, which I had never experienced in 16 bit mode, was back, and everything was darker on the display than with the 16 bit file. When I printed the 32 bit workflow, including a curve adjustment to clear up out--of-gamma areas, but excluding the soft proof layer, I saw on the thumbnail in the print dialog that a recolor adjustment that I was using for bringing texture in rock and wood (cf. James Ritson's tutorial https://player.vimeo.com/video/150884324/ from the beginning until about 1:40 min.) was going to be printed much to orangey, even though the orange color was hardly visible on the display. So I had to reduce its saturation the opacity until the thumbnail displayed properly! The resulting printout was OK, but it was much brighter than on the display. In contrast, when I work with 16 bits the printout agrees tolerably well with the display. I've uploaded the files to Google Drive (I think!). Here's a link, I think it allows downloading: https://drive.google.com/drive/folders/1zkX5qqe1shqc2igAalTTEVzNNefsDwZc?usp=sharing . .NEF is the Nikon RAW file. "36" in the filename denotes the 32 bit workflow, resp. the JPEG export. What display and printer are you using? I have a BenQ SW271 calibrated to Adobe RGB, gamma 2.2, 100 cd/m² and 5800K, and am printing on a Canon Pro-1000 using Canon Photo Paper Plus Glossy II and the printer profile for that paper supplied by Canon.
  14. Hello, i have no begin of reply to my pots, i'm going crazy, i just can't work on a raw since the introducing of 32 bits ; raws are supposed to be displayed thru a RGB space, or ROMM, not really clear for me, but for sure, it needs a color space to display some colors, i understand this profile is internal to develop persona, i don't need and i can't choose by myself, i have just to open my raw and develp persona displays it with colors thru a RGB space ; but in my case it displays a totally black pixeled picture like if i attempt to display a document with no profile in photo persona ; if i assign a profile by clicking on develop or making an hdr, then return to develop, it also displayed with color, but the original raw without profil in it of course is displayed as a black picture . So something is missing somewhere ? a profile in an affinity library ? in my color sync profiles, i 've download ROMM and putted it with over profiles and verified all library and profiles, and found a CAMERA RGB PROFIL in system/frameworks/ICAdevices, so in case i have added ROMM in it and import it into photo, but ... i found no solution with profiles ; then i turn myself to 32 bits , on my mac if i choose 32 bit output, or if i make a hdr, the picture is displayed totally black until i check the button "unmanaged" in the 32 bits preview, so in develop persona this possibility doesn't exist, and there is no preset for that, perhaps this explain that ; so this point should be considerer as a missing feature ?! i have watched many tutorials many times, i have read and read again, checked the posts, used translator to understand, token mass of aspirin, i have tried to find something in the propertylists any where in the mac, and now the rest for me is to inspect the threads on the "console" hoping i will find something, it's crazy !!!!! i have a software with witch one i just can't work ???? could someone scream to a moderators ??? pleaaaaaase !!!!!!
  15. As enlightening as the comments have been, I am still plagued with the problem that full-sized exports are not very good, even when comparing with the preview in Affinity Photo at full size. The problem I have is, the exported files are much too dark. When previewed in Affinity Photo, the structure on a large tree trunk is very clearly visible, even though the tree is in the shade and hence dark. (Actually, the previewed document is much too light for my taste and purpose.) I can supply the .afphoto (601.2 MB) a JPEG export 100% quality, bilinear sampling (30.9 MB) a TIFF-16, Lanczos 3 sampling (174.4 MB) As the files are very large, I don't want to upload the last two unless somebody really wants to take a crack at this. (I just tried to upload the JPEG, but the upload failed.) Further to the problem: My Apple Thunderbolt 27" display is calibrated using basICColor display and an Xrite i1 Display Pro as follows: When working in the Photo persona the document Colour Format is RGB (16 bit) and I see this in the upper left corner: I assume that means that Affinity Photo is using ROMM RGB: ISO 2028-2-2013 to display the previews. Does anybody know this for sure? When exporting the files I have checked to use the document profile and to embed it in the export. I view the exported files with Preview, a macOS app. Preview shows me that I assume that Preview is using the named profile. Does anybody know this for sure? As I said, when displayed at full size in Preview and when previewed at 100% in Affinity Photo, the former is noticeably darker. I imported it into Graphic Convert, a third-party app for the Mac. It is somewhat lighter than in Preview, but still not nearly as light as in Affinity Photo. I really cannot explain the discrepancy but I am getting criticism from a teacher that the photos that I upload to a web site for critique are too dark. I suppose the problem could be the way her monitor is calibrated. Perhaps her's uses a tone response curve, while mine is calibrated to L*, and that, presumably, is what "(linear)" means in "ROMM RGB: ISO 22028-2:2013 (linear)," the output profile that I selected in the Develop persona. Does anybody know for sure what profile Affinity Photo is using when it generates profiles? What about how Preview honors embedded profiles? Should I upload the files? Thanks
  16. 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
  17. Hi @ijustwantthiss**ttowork OK, so my suspicion is that the blade.icc profile is deficient—out of curiosity, is this the Razor Blade laptop? Can I ask where you got the blade.icc profile from, did you download it from a website or did it come preinstalled with the laptop? So if you switch the colour profile to the sRGB device profile, everything looks fine inside Affinity Photo? No issues, and when you export to JPEG/TIFF etc with an sRGB document profile everything looks good with an external image viewer etc? This is expected, as Affinity Photo needs to restart to colour manage with the newly chosen profile if you change it on the fly. Definitely don't do this! The reason it looks OK if you use blade.icc as your document profile is because you're matching the document profile with the display profile, negating colour management entirely—the document numbers are being sent to the display with no alteration. It might look OK for you, but it won't for anyone else. Colour managed applications are supposed to use the display profile to translate the colour values in the document as they're sent to the display. This is especially important for wide colour profiles beyond the scope of sRGB. The thing that seriously isn't working has to be the blade.icc profile—not sure where you got it from but it's defective as regards compatibility with colour management. We've seen this a lot with various monitors that people are using, Windows Update seems to push specific display profiles that just don't work with colour management solutions at all—in the article that was linked above you'll see I invited people to search for "whites are yellow" in relation to apps like Photoshop because it's not just Affinity Photo that is affected. Have you got access to a colorimeter, e.g. i1Display Pro, Spyder, ColorMunki etc? If so, I would download either the manufacturer's profiling software or DisplayCal and use that to profile your own monitor—any profile created by the software will be valid and work correctly with Affinity Photo. If you can't profile the display by yourself, the best solution is simply to use the sRGB display profile rather than this factory-calibrated blade profile—when you say factory calibrated, that instantly makes me sound very skeptical. Again, this all points to the blade profile being incompatible with colour management. Not many applications are actually colour managed—to be honest, I've lost track of whether Windows Photos/Photo Viewer/whatever it is in Windows 10 is colour managed or not. I think web browsers by and large should be colour managed by now, but there's no guarantee there. The fact that things look different in Affinity Photo is a clear sign that it's performing colour management based on your active display profile, but unfortunately if that display profile is incompatible then everything is going to look whacked. As I just mentioned above, unless you can create your own accurate and compatible profile with a measuring device, I think your only solution here is to use the sRGB display profile. From your screen grabs, you haven't touched Affinity Photo's default document colour profiles (they're left on sRGB) which is good—just avoid using blade.icc as your document profile altogether and stick with standardised device profiles like sRGB, Adobe RGB, ProPhoto/ROMM RGB etc. If you do use a wide profile like Adobe RGB, don't forget to convert to sRGB on export if you're going to view it in other applications that aren't colour managed—the article explains how to achieve that. Hope all the above helps! [Edit] From a bit of searching, I found someone had posted their Razer Blade 2019 profile that they had created with DisplayCal here: https://drive.google.com/file/d/1l07D8CtFjXYVsDpeTAyLBEkZpELNomYo/view (from this Reddit discussion: https://www.reddit.com/r/razer/comments/ase96x/razer_blade_15_2019_color_profile/) I definitely wouldn't recommend using it for professional/production work (I'd seriously advise getting a colorimeter and creating your own profile to the standards you require) but it's worth installing and switching to it just to see if it helps. It could go either way, since if that person's display is wildly different to yours it will still look terrible, but it could also produce a much better result than the blade.icc profile you're currently using..
  18. Further consideration is with the Photo Personae and the document sizing. I can figure that the current method is to re-sample the image when changing the DPI and yet retaining the original or cropped size by changing the pixel quantities. But I do not need to do this operation in the Photo Personae. All I want is to edit the image from a digital camera and then do the re-sizing or resampling at Export. I use an RGB monitor that claims about 97% of the Adobe RGB (1998) colour space and have set this colour space in preferences and in the Develop Personae as Adobe RGB colour space for all editing. I could use the ROMM RGB (ProPhoto) colour space if I require to do so. Printing images in these colour spaces direct from the Photo Personae is not an option as I am in a larger colour space and the prints come out with the wrong shades and with colour shifts. When exporting the image is then re-sized if required and then set to the SRGB colour space and saved at the appropriate size and this is what I use to print and the colours and tones are excellent and using a fully calibrated monitor the screen colours very nearly match the print colours. Still will be a slight difference as the monitor is backlit and prints are reflected light and have to viewed under daylight for any real comparison. In the Photo Personae all that is required is to be able to choose the appropriate ppi (DPI) to resize the image. Edit the size in the CROP tool to an absolute size (a specific dimension) move the crop grid around the image for effect. (Rule of thirds etc) and crop away the pixels I do not require to be part of the new image. Can then rasterize if I wish and if I have no intention of returning to the original pre-crop size. Then export the image at say 8 bit and SRGB colour space at a specific size for the type of image I want to print or use elsewhere. It is only at Export that I need to resize or resample an edited image. I want to retain all the image/pixels or edited image/pixel sizes in the .afphoto file format in case I come back to either re-print via export or revise my edits and then export.
  19. 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!
  20. 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.
  21. 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
  22. Ok, so I started by resetting Windows Colour Management to sRGB as per @- S -'s linked post. Opened Designer and created a new document. The colour profile was set for ROMM RGB!!?? Checked Designer prefs and the RGB Colour Profile is set for sRGB. Closed that doc and started fresh again resetting the colour profile to sRGB in the new doc dialogue. Then I took @firstdefence's advice and used the RGB sliders at 0,0,0 to draw a lovely black box, added a new layer, set the sliders to 256,256,256 and did a little scribble. Now that is black & white! Re-opened my org chart thingy and now it looks the same in Designer as in the exported PDF. Just for giggles I went back to my scribble, changed to the HSL wheel, dialled in a red and then upped the luminosity to 100. Looks the same as my 256 RGB. So it appears the issue was Windows Colour Management all along. I vaguely remember trying a profile from somewhere off the web for my cheap-ass Acer but I thought I'd reset that ... obviously not! All seems to be good now. Thank you all for your efforts in helping me track this down.
  23. To clarify, the general Develop process is done in sRGB float—this includes the initial conversion from the camera's colour matrix to a designated colour space. However, the colour data is processed in ROMM RGB which produces enormous benefits for some type of imagery, particularly low light images with lots of artificial lighting sources. Despite this, the document is in sRGB and so this is the colour profile used when converting to the display profile. As the pipeline is in float, this does mean that you can convert to a wider colour profile on output and avoid clipping to sRGB, which is the recommended course of action for now. Do you mean the final developed image? This isn't my experience—choosing an output profile of ROMM RGB and then using adjustments and tools within the Photo Persona allows me to push colours right up to the limit of P3.
  24. If I remember correctly APh Develop Persona uses a ROMM RGB like mathematical color space when processing RAW files, though some former forum member then showed/proved in the past, that only the sRGB gamut seems to have been used always instead. But I don't know if in the meantime things have been fixed or changed here in this regard during APh version updates. - However, since RAW images do not have color info at pixels and so are not in any color-space (instead they have color primaries corresponding to the wavelengths that the Bayer filter on each pixel defines), using an RGB based color space (even a wider gamut one) in/during RAW development limits the overall possible and theoretical available color spectrum. Thus RAW -> LAB should offer more possibilities than RAW -> RGB -> LAB here from the beginning.
  25. Unbeknownst to myself, I now realise that when I you open a RAW file in Affinity Photo it's processed in a working pixel format of 32-bit float, which is unbounded. This would appear to be normal. This prevents values outside the range of 0-1 from being clipped and discarded, and allows for highlight recovery. Colour operations are processed in ROMM RGB (ProPhoto), which helps colour fidelity even if the intended output colour space is sRGB. You are essentially working in the highest quality that is reasonable. I did not have the above ICC profile selected but since I activated it, the transfer to the Photo Persona is exactly as it was when I clicked the Develop button. Furthermore, Affinity Photo converts by default, the file to 16-bit pixel format. And since I have Adobe RGB set as my colour profile in preferences, everything now is honky dory. Thanks to all for responding. William
×
×
  • Create New...

Important Information

Terms of Use | 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.