Jump to content

Search the Community

Showing results for tags 'icc Profile Conversion'.



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 1 result

  1. Hello! I watched the Affinity-Tutorial "ProPhoto cs sRGB" some days ago and started to try this for my workflows. The first obstacle to overcome was, that on my mac there was no prophoto icc-profile. In this forum i found a post about that, where is was shown, that the ROMM RGB Profile should be the same. This profile is on my mac, so I gave it a try! But one thing about the ROMM-Profile I didn´t understand. In the forum-post was a link to the ICC-website to download the ROMM.icc file. I also downloaded the profile (unless the romm was on my mac) just to compare the one on my mac with the one downloaded from ICC. The one on my mac is dated with 2015 or so and the one freshly downloaded was dated with about 2006!? The settings shown via the color-sync app on my mac are also not the same... so is the ROMM on my mac still the same profile than the one from ICC? And are those really the same like the prophoto?? After my try on one of my actual projects - I tryed the same workflows than in the tutorial videos - I got stuck with some troubles... - converting my sRGB Image to the ROMM was as expected. And in some details the result of my project changes quite positively. I could really see that the bigger gammut gave some adjustment- and filter-layers more room to work. - then i tryed to export the project - like on the tutorial - via the export dialog as an jpg with an sRGB profile again. But the result was not the same, then. The color shift wasn´t the problem! The sharpness of my foto got lost? What I couldnt understand. Exporting a jpg directly from my original project file (in sRGB, not converted to ROMM) looked much better, sharper, like it should look like! So the jpeg out of the "sRGB-aphinityfile" and the jpg out of the "ROMM-aphinityfile" look enormous different, but not like the nice differences I could watch via the profile-conversion. The third and last issue on that is about the soft proof. Because my actual projects will be printed on fine art paper I use the soft proof from the producer to check the gammut. after the romm-conversion it is much more difficult to get rid of the "black" surfaces the gammut check shows. What is expected, because the romm have a much greater gammut. But maybe you can give me some tipps to handle this better, because even in my sRGB projects it is quite difficult to reach the gammut of the producer (the fine art paper) - can it be, that the gammut of this fine art paper is rather small compared with sRGB (and smaller compared with romm)? I watched the tutorials about soft proofing, but on my projects it seems much harder to reach the soft proofed gammut. Thanks for help! the icc profile for my soft proof is attached, as well as the two romm profiles, the one from my mac and the one from ICC. (Wasn´t allowed to upload the icc files) Thanks!! Andreas
×

Important Information

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.