Search the Community
Showing results for tags 'opencolorio'.
Found 3 results
I was working on a file with a custom OCIO 1.0 config that Redshift made for Blender. I decided that I wanted to change to a un-modified OCIO 1.0 config for ACES 1.2. So I repointed Affinity Photo to that config and restarted the app. Upon opening my file I got a crash. I expected it to need to have my OCIO adjustments changed but, I don't get an opportunity to fix them. I went back to my old config and could open the file. I tried to delete all the adjustments and set the file to unmanaged in the 32-bit preview and saved a copy. But even that copy crashed Affinity Photo if I tried to use the unmodified OCIO 1.0 config. So I had to recreate my file to use another config. We will need a way to fix this sort of problem without having to start over with a new file. I hope you can use this file to build a little more robustness in how it handles moving between OCIO configs so that we can at least get back into files and correct OCIO settings. Fortunately, this was just a test file for me and nothing important. This is with Affinity Photo 126.96.36.1995 This also happens if you have a file set to use OCIO but open it on another computer that does not yet have OCIO configured in preferences. In both cases we should get a descriptive error message and an opportunity to change the OCIO config rather than a hard crash of the app. Without better error handling users would not have any idea how to fix it or assume the file was corrupt. AirwolfPos_Test.afphoto
Hi Affinity team I have two small feature requests that will make Affinity Photo and Designer fit really good into VFX, movie and TVC production. 1. My primary request is import and export in the Open EXR file format. Some of the key features of Open EXR is: High Dynamic range, up to 32 bit float. Multiple channel sets (layers / passes). Multiple compression types, both lossless and lossy. Open EXR is used all around in VFX, movie and TVC production. It is supported by, and the preferred image file format of many tools in VFX production (nuke, maya, modo, mari, fusion, scratch, daVinci resolve, etc. and even AE, but it's really bad implemented in PS). 2. The second request is support for motion picture and TV color spaces. Being able to handle Rec709, cineon (LOG), P3, Rec2020, ACES, etc. correctly in Affinity Photo and Designer would be a huge plus. I'm not a developer, but I think it could be done through the OpenColorIO color management solution, which is also widely adopted by VFX production tools. A still image editor is not the primary tool in the VFX, movie and TVC world. But it is always there as a secondary tool for doing quick fixes, converting images and vector files, developing raw files, etc. These requests I mention are weak points/not supported at all with most other image editors, and I think if Affinity Photo and Designer get's it right, it could be a huge plus, and with the very reasonable price tag I can't see reasons to not choose Affinity Photo and Designer. Cheers /johs
bvz posted a topic in Older Feedback & Suggestion PostsHi, I am excited that exr/floating point support is coming. One additional feature that would be extremely helpful for us would be to support open colorIO (vs. ICC profiles). In the visual effects industry, ICC profiles are hardly ever used (and can be a pain in the arse). Open ColorIO is our preferred color management and if we had the ability to natively use the same profiles that we use in Nuke, Mari, and Maya then we would be miles ahead of photoshop with its confusing and annoying color management. As its name implies, it is an open standard. I have no idea how hard it would be to switch between the two different color models, but if it is at all possible it would push Affinity Photo forward in the effects field quite a bit (coupled with your support for floating point file formats).