Search the Community

Hi, I searched quite a bit, but couldn't find a way to partially modify the exposure in a 32-bit image to create a, none tone mapped, HDRI to be used as lighting in 3d software. In a nutshell: I want to create a 32-bit HDRI and increase the exposure within masked areas to different values, pretty much like the Exposure control in Photoshop. The exposure adjustment layer would require me to paint the influence mask after applying, but it does not seem to be able to increase the exposure value in a way necessary for IB lighting. Using the Develop Persona allows me to increase the exposure value for the whole image, but requires me to calculate color values in advance to, e.g. create a grey background with "lights". Am I missing something or should this go into a feature request? TIA, Erik

If I create an HDR image using HDR Merger, or load a 32-bit .exr file I cannot get the 32-bit Preview pane to appear. I go to View -> Studio -> 32-bit Preview and select it, but nothing happens. If I go back to that menu there's no check mark next to it, so that confirms nothing is happening.

When stitching 32-bit HDR panorama from previously HDR merged OpenEXR source the panorama "persona" in Photo 1.6.6 does not offer the 32-bit preview panel, this can impede identification of stitching artefacts

Summary: The image is 4988 x 2814px, 14.04 MB, 7 layers: 1 background pixel layer, 5 masked curve adjustment layers, 1 B&W layer in RGBA/32 (HDR), ProPhoto RGB (Linear). Using Document, Color Format to convert this image in 32-bits to 16-bits RGBA/16 - ProPhotoRGB takes over 8 minutes of processing time on a relatively well-spec'ed machine. Adobe Photoshop CS6 using the same image in 32-bits, similar number of layers and same color space to 16-bits in same color space takes about 5 seconds. Affinity Photo takes an inordinately long time that is not acceptable for the workflow. Details: The machine: Windows 7 Professional 64-bit up-to-date per Windows Update Service Pack 1 Processor: Intel Core i7-3770 CPU @ 3.40GHz 32.0 GB RAM Windows Experience Index 7.7 (on a scale of 1.0 to 7.9) Graphics card: GeForce GTX 970 version 385.69 NVIDIA Control Panel reports (see attached PNG) More details on machine in attached PNG. Disk C: is a SSD and has both Affinity Photo and Adobe Photoshop CS6. The software: Affinity Photo 1.6.1.93 RAM Usage limit 25,599 MB Renderer: Default (NVIDIA GeForce GTX 970) Adobe Photoshop CS6 64-bit, using the NVIDIA GeForce GTX 970) Using Photo Affinity's Document, Color Format, RGB 16 bit it takes slightly over 8 minutes to have hourglass disappear and the RGBA/16 - ProPhotoRGB to appear. During this time Windows Task Manager reports (see attached PNG's). CPU utilization by Affinity Photo is essentially 100% during this time. Trying 32-bit to 16-bit conversion on the same image in the beta version 1.6.1.93 (Beta) does not result in Task Manager reporting "Affinity Photo (not responding)" but if anything the conversion takes even longer at about 8 minutes 55 seconds. Doing this 32-bit to 16-bit conversion of same image and same color spaces in Photoshop CS6 takes about 5 seconds of processing time. Machine Info 1.pdf

After having used the 32-bit modes almost exclusively now since we had them available I noticed some issues with OCIO configurations and maintaining them. What I'm suggesting is a more global config file. I've attached a YAML example. YAML because it's easy to read, duplicate and modify. It can be easily exchanged when working in groups. Download project config from Shotgun, merge with own config and use it right away. Affinity currently has a config switcher that doesn't switch configs. This way it would work and it would be easy for the user to manage. The ICC part is for Affinity to determine which profile is used for converting OCIO data to ICC data for delivery use to devices and services that don't use OCIO (print shops for example). ocio affinity.yaml

I need to add on to a matte painting but the new version doesn't let me work on objects larger than approx 300 x 500 px. Everything else gets cut to that with a soft circular feather. New layers that I add when painting in other apps and placing in AP are impossible to select. The blue layer frame only gets displaced to the same max dimensions. When I try to select it, the selection gets applied to the layers below it. This all was possible in 1.5.1. In 1.5.2 this probably got messed up with the 32-bit fixes. So I need a way to get back to the App Store version 1.5.1 to be able continue to work before this gets fixed.

Is thre a way to open a 32-bit exr file, withou applying the alpha channel to all the layers in the file? When opening a rendered file from 3ds max everything in the windows is just transparent pixels.

Hi, I was SO looking forward to playing with the Windows Beta, but I don't have a 64-bit install and don't really want to go through a clean install. Too much risk for potential problems on my Parallels Mac/Windows set-up. Is there any chance at all that there will be a 32-bit version of AD Windows later? Or do I have to buy a brand new 64-bit PC? Thanks, Sheila P.S. Congrats on the beta release! :)