Jump to content

plobnop

Members
  • Content count

    9
  • Joined

  • Last visited

Everything posted by plobnop

  1. Hi, Is it possible to convert an image to 32bit from 8bit/16bit without converting to linear? I need to be able to preserve the numerical values of the pixels and save as an EXR. An example of why I might want to do this: I have an 8bit normal map and a 32bit normal map. Both are correct as far as pixel values go. Now I want to mix them together, I'm finding there is no way to convert the 16bit image to 32bit without linearizing the image. I don't care about preserving the look of the image, I care about preserving the numerical values of the pixels.
  2. Hi @GabrielM, just to be clear (and maybe a little nit-picky). I'm not looking for a non-linear 32-bit profile; I'd like for it to still be linear. I would like to have the option for AP to not perform a gamma correction to my image when switching to 32bit. A concrete example that I have just run into. I have a 16bit normal map. I am currently trying to convert all my images to EXRs in the ACEScg colorspace for consistency. Now, If I was in Nuke I'd set my read node to Utility - Raw then save it as an EXR (and still work with the image in a linear colorspace). The pixel values did not change and the image went from 16bit to 32bit with no gamma correction. In AP there is no way to open a 16bit image and save it as an EXR without a gamma correction. This makes saving images (originally 16bit) like displacement, normal, spec, etc. as EXRs impossible in AP as the gamma correction destroys the integrity of the images. After conversion I'd like the profile to still be linear, I don't really care if the image looks different when converted to linear. Hopefully this makes the use case for this feature a little clearer.
  3. It looks like AP, when viewing an image with the 32-bit Preview OCIO Display Transform checked, is using the monitor profile for Display 1 on Windows 10. In 1.6 of AP it seemed it was incorrectly using the monitor profile of the Primary Display for both ICC Display Transform and OCIO Display Transform. Now, with 1.7, ICC Display seems to be correctly choosing the monitor profile of the display AP is being shown on. However, OCIO is still incorrect but in a slightly different way than it was in 1.6.
  4. Hey Chris, sorry it has taken so long to reply... got busy and forgot to check back. Monitor/Profile Configuration: So, I'm using a BenQ and a Dell monitor for my two displays. The way in which these monitors are calibrated are very different. The BenQ uses sRGB color profile for windows color management and has a calibrated LUT on the monitor hardware to provide color calibration. The Dell has a calibration profile selected at the OS level. ICC behavior: If I open an 8bit image in both AP and Photoshop (sRGB color space) they match when displayed on either monitor. When I move it from one monitor to the other I can see the the color in the image change when the proper profile is applied (in both AP and Photoshop). OCIO behavior: Convert 8bit sRGB image to ACEScg (Equivelent to Nuke: Read (Output - sRGB)) Open 8bit sRGB image. Convert to sRGB Linear 32bit. OCIO adjustment layer Source: Utility - Linear - sRGB Destination: ACES - ACEScg OCIO adjustment layer Source: ACES - ACEScg Destination: Utility - sRGB - Texture OCIO adjustment layer Source: Output - sRGB Destination: ACES - ACEScg When compared to the original 8bit sRGB image (Photoshop and AP) the above 32bit image in ACEScg should be indistinguishable. In AP 1.6 on my primary display they do match. With AP 1.7.0.209 they do not match. So, OCIO is displaying the image differently than the original. Originally I thought AP was using the profile of the primary display. However, If I set the color profile of my second monitor to the profile of the primary (So, AP will use that profile for the ICC displayed image) ICC and OCIO still display differently. So, all I can say at this point is OCIO is displaying oddly on a second monitor. On my primary display OCIO and ICC display exactly the same. Additionally, I'm using an OCIO 1.0.3 config. Hopefully this makes things clear.
  5. Hey everyone, I'm running into an issue with how Affinity Photo chooses a monitor color profile on Windows. I'm using a BenQ and a Dell monitor for my two displays. The way in which these monitors are calibrated are very different. The BenQ uses sRGB color profile for windows color management and has a calibrated LUT on the monitor hardware to provide color calibration. The Dell has a calibration profile selected at the OS level. The problem is that Affinity Photo only uses the primary display profile so the colors are accurate on only the primary display. Photoshop will automatically switch depending on which monitor it is on. Is there any way I can choose which profile Affinity Photo is using?
  6. Hi Walt, since you mentioned this issue possibly being fixed in the 1.7 beta I went ahead and installed it. I can confirm as of 1.7.0.209 AP correctly chooses the monitor's color profile when it is moved between windows when using the ICC Display Transform in 32-Bit preview. However, when using the OCIO Display Transform the problem seems to persist. Looks like I need to submit a bug report for the 1.7 beta for the OCIO Display Transform.
  7. Hi, HVDB, that's for setting the default color profile for images not the applicaiton. That does not allow me to choose the monitor profile AP is using. AP has to choose which monitor profile it uses to display colors correctly in addition to the profile used for the image. As it is right now, AP is using the monitor profile of the primary display.
  8. Hey everyone, is it possible to turn off thumbnail generation in the "New Batch Job" dialogue for your sources? I have over 1 thousand images I need to process and it takes forever to generate the thumbnails. For me, and I imagine others, the thumbnails are not necessary to see (I know what folder I'm in and what images I'm selecting) and add a significant amount of time to getting the a batch process going. I can see this being a nice safety feature to see what images you loaded. However, it would be nice to have the option to disable thumbnail generation (if it does not already exist). EDIT: There were 6min 21sec between adding my sources and being able to click "OK" to start the batch process. It kind of defeats the purpose of automation if you have to stand around and monitor your computer.
  9. I would love to see floating point numbers in the info palette when working in 32bit. I'm beginning to do a lot of work in the ACES colorspace and work with a ton of HDR sphericals. So, it is important to be able to check values well above one. I also do a lot of work in Nuke and have really grown accustomed to mousing over pixels to see their values.
×