Jump to content

Search the Community

Showing results for tags 'colorspace'.



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 & Discussions
  • 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 4 results

  1. I have selected adobe 1998 as the colorspace in my SonyRX10M4 which is also set to give me raw data .ARW files. When I import them as a batch job to Affinity for processing into .tif files and then save them back to the original folder the colorspace changes to the, less desirable, sRGB 1996 colorspace. I can't find any way of making sure that the colorspace I chose in my camera remains the same the saved .tif file after Affinity has processed it. HELP
  2. Is it possible to work in L*a*b* colorspace, to at least 16 bit depth, with layers and masks functioning? If not, this is first on my wish list.
  3. Hello Affinity, I'm a Photoshop user testing Affinity using the trial. In photoshop I setup custom proof setup to quickly emulate Sgray using CTRL+Y Is this possible to setup in Affinity? This video explains exactly what I'm looking for: Thanks!
  4. Hi Forum, I shoot in Adobe RGB and have likewise set color space in AP to Adobe RGB. However, whenever I open an image in AP a get a prompt saying the file was converted to Adobe RGB. Is this a bug or intentional? Thanks
×