Jump to content

Search the Community

Showing results for tags 'exr'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Questions (Mac and Windows)
    • Feature Requests, Suggestions and Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Support
    • Photo Beta on iPad
    • Designer Beta on Mac
    • Designer Beta on Windows
    • Photo Beta on Mac
    • Photo Beta on Windows

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 19 results

  1. Dear Serif Team and Affinity Photo users, I'm a VFX Compositor & Matte Painter and I'd like to move from PS to AP. I hope you can help me with some questions regarding the Implementation and proper use of ACES and 32-bit. My background plate is exported from Nuke as an ACES - ACES2065-1 16-bit EXR file. The import into AP ( works fine - the file get's recognized as an ACES file and I get the same result using OCIO. But there are a few things I can't get my head around yet: How do I pick and paint high color values? Using the exposure slider in the 32-bit Preview I see that there are high values. If I pick and paint them back in, the result is way darker. (Changing the exposure doesn't effect the false picked color) picked in Nuke for comparison I moved from PS because there is a 16Bit limitation and I had to work with ACEScc files (log encoded) and use an ICC profile to check my work. I hoped to get around this using AP. Those threads are dealing with the same issue but the information is contradictory and I can't reproduce the method quoted first. https://forum.affinity.serif.com/index.php?/topic/49815-hdr-raw-pixel-values/ https://forum.affinity.serif.com/index.php?/topic/19787--/ What is the proper workflow of importing and edit JPGs in an ACES setup in AP? Unfortunately there's no way of assigning an IDT during import (as in Nuke) but I can reproduce Nukes behavior with OCIO Adjustment Layers, which seams pretty inconvenient. (Windows Photo Viewer as comparison) Bottom left: Two OCIO nodes in sequence [ACES2056-1 to Utility - Curve - sRGB] followed by [Output - sRGB to ACEScg]. Bottom right: Two OCIO nodes in sequence [ACES2056-1 to Utility - Curve - sRGB] followed by [Utility - sRGB - Texture to ACEScg]. This post deals with the question of the right IDT for JPGs in general. I guess going the Utility - sRGB - Texture way is better, isn't it? My color settings: If you need further information or I haven't made my questions clear enough please don't hesitate to ask. I'm glad about any help or further learning resources! Thanks a lot
  2. I'm writing with an issue I've noticed for importing RAF files from a Fujifilm X-S1, which employs the EXR-CMOS, which has a non-traditional orientation, similar to the SuperCCD layout. Affinity Photo imports my 12MP RAF files as 6.11MP (2848x2144 RGBA/32) instead of the native 12.00MP (4000x3000 RGBA/32) it should be. These same RAF files are read properly by Win10 Photos and SilkyPix (Fuji's bundled RAW software). Thanks! X-S1_RAF_JPEG_Sample.7z
  3. I explain myself, After 2 days of trials, watching tutos, topics on the forum, I finally managed to have a fonctional 32bits linear workflow in place. I've tried tones of LUTs, OCIO layer and 32bits preview configs but, the better I had was a good viewing and a crap export. Finally I've found a way, perhaps not a good one, but a way. I've read @Frank Jonen talking about a gamma issue on a spécific question so I've tried the transfer fonction trail. It lead me to add an S curve shape on top of my layer stack and this time my LUT worked as expcted and the export too. But why do I need to do something approximative to have all working? Infos: -working with 32bits EXR float (full) linear render -OCIO layer to convert from linear to LOG -LUT layer to apply a creative Log base look -S curve shape on top -ICC or OCIO 32bit preview @troy_s welcome to the discussion
  4. Hi there, I've got a problem exporting a CG render. The source is an .EXR 32bits linear, I've applied an OCIO, LUT... everything is correct in affinity (right contrast) but when I export it, it looks like there something wrong with the color profil (not sure). The image looks dull. i've tried different export format, color profil but always the same problem. I'm on windows with Affinity Photo
  5. Hello, When i open an EXR file into Affinity Photo, I dont get the transparent background, all i get is a solid black background, im pretty sure the file has transparent background, becouse when I open the same file using photoshop, i get nice white transparent background. what am i missing here? is that a bug? pls help me!! original EXR FILE above!!! test_renderxdd.exr
  6. Hi guys I mainly work with 32bit rendered EXR files. When I'm comping rendered objects into backplates, I need to be able to have coloured masks. This is to ensure shadows that are in alpha (masked), creates the correct tone on the backplate. A coloured mask can for example produce a blueish shadow, where a grey scale mask will produce a grey shadow. Is there perhaps a setting I'm not seeing? Whenever I convert a layer to a mask, it goes greyscale!
  7. Hi Affinity team. During the last days I tested the Windows version of Affinity Photo 1.5.1 and checked out those parts most important to me: RAW processing, HDR/Tone mapping and stitching Panoramas. (The video tutorials are great for newbies concerning your software.) I am happy to see all these features under a common hood and working reasonably well (although there are issues like the wrong histogram displayed in Develop persona which will refrain me from using Photo as default RAW software for now.) What I want to achieve: For years now I'm accustomed to create HDR images from a single RAW file instead a series of JPG or RAW files. The benefit is that there are no problems with motion (and thus ghosting) in the image, and no softness as a potential side-effect of the automatic alignment of handheld shots. Today's DSLR cameras create RAW images which can easily compensate 3 EV steps. (Depending on sensor size and ISO, the downside can be higher noise in dark areas, but that's acceptable for me.) My conventional approach is to develop 3-5 differently exposed JPG images (usually with different noise reduction settings) and then creating the HDR from these. This approach is very cumbersome with Affinity Photo, which does not even remember the RAW conversion settings I last used by default. Once a RAW file is developed, the Develop persona is closed and I have to start over for the next exposure. (In contrast to a dedicated raw converter like Canon's DPP or Nikon's NX-D where this is a no-brainer and easily done.) But maybe Affinity has a better approach? What if you could develop the raw file and apply a tone mapping without JPGs inbetween? Lets see, Photo Persona works in 32 bit, and RAW files can be developed to 32 bit HDR. Sounds promising. 1. I import the RAW file, disable applying the tone curve and leave the exposure-related settings untouched. 2. Then I put the developed 32 bit image into the Tone mapping persona -> Voilá, a developed HDR image. And what if I have a panorama of single RAW images which needs HDR processing? 1. You can start a "New batch job", select the RAW files to process and choose EXR as output format. 2. Then you can continue creating the panorama with "New panorama" and select the EXR files as shown in the HDR panorama video tutorial. 3. After the panorama has been stitched, it can be tone mapped in the Tone Mapping persona. Cool - this is a real time saver and more flexible regarding adjustments compared to my previous workflows which would mean first tone mapping every HDR image and then stitching the (hopefully equally exposed) JPGs together. Matthias.
  8. Hi I’m having some difficulty converting files exported from Lightroom. With the latest versions of Lightroom mobile you can make full 32bit HDR files with your iPhone. However, Lightroom can only export those files as DNG files... I want to use the photo’s in a 3D rendering application where the data in those files are being used to light 3D objects and scenes. Therefore I need the full range that’s inside of the DNG. That’s why I want to use the Affinity Photo to open the DNG file and save it out as an 32bits floating point EXR file. Iv’e been trying many ways to get this to work but I just keep getting clamped values in the resulting file. Could anyone help me out? Thanks!
  9. Good evening everyone, I've a little question because I'm new to Photo and I cannot understand if I'm doing something wrong or if it's an Affinity Photo problem. I'm opening a Multichannel OpenEXR generated by Blender that contains all my render passes (I've check that with a compositing software and all the passes are there) but Photo only show me into the layer tab the RGB "beauty" channel and the alpha one. I don't understand why that's happen because as far as I know Photo should support Multichannel OpenEXR without any problem. I'm missing something or I've found a potential bug/issue? Thanks for the help N.
  10. anon1

    EXR view hiccups

    took a look at the image provided in this other bug report https://forum.affinity.serif.com/index.php?/topic/46305-retouching-tools-useless-in-32-bit-mask-display-flawed/&do=findComment&comment=232066 and saw some display glitches as shown in the video: 32bit.mov another issue arises using HDR he exposure is just way to high hdr32.mov cheers other display bugs that have not yet been accepted: https://forum.affinity.serif.com/index.php?/topic/46073-affinity-photo-customer-beta-165-beta-5/&do=findComment&comment=230647 https://forum.affinity.serif.com/index.php?/topic/46268-hide-left-studio-moves-canvas/
  11. hi, tried to make a batch conversion from .exr to png but when i try to add multiple files (more than 1) affinity 1.52.69 and newest beta instantly crash it works when i add the files one by one - but thats kinda annoying... for 600 files... unhandled exeption on beta 0xE06D7363 also sent crash reports hope you can fix that soon though as i need it for job today i guess not that soon... thanks in advance
  12. Here's my scenario I have a lenovo laptop running win10 with an i7 quadcore 2.6ghz cpu, 16g ddr4 memory and a nvidia gforce graphics card with 4g of memory. After watching the youtube tutorial on hdr panoramas, on the Affinity channel, I attempted one of my own, merging 7 raw files to hdr with no tone mapping and repeated the process on one additional image. Exporting both files as open exr documents using the default settings. I then attempted to stitch these two files as a panorama but instead i am greeted with a dialog box that says panoramas not found. (file attached) i am not sure what i am doing wrong. Please help. P.S. on the video i noticed all the files in the dialog have thumbnail images with the filename before they are stitched, my dialog box only shows the affinity logo.
  13. When exporting EXRs from Affinity Photo, the Alpha channel is being exported as unassociated. Opening in other apps I have to convert it to pre-multiplied. Is there an option on Affinity to export EXRs with Associated alpha (premultiplied)?
  14. Hi guys, I'm a 3D artist and quite interested in buying Affinity Photo. But I want to know how does it perform and work with 32 bit images like HDR and EXR. This is a huge weakness in PS and I hope AP can fulfill this gap for me. So, here are my questions: -Can AP create layers, blending modes, apply filters, masks and whatever I can do with standard 8bit images, so I can work non-destructively? -Is there any tone mapping tool in AP? Something on the lines of Camera Raw in PS? Does it work non-destructively too? -Does it have a Lens Blur so I can use ZDepth to apply DOF in post? To me it's very important to have non-destructive workflows as much as possible. Thanks in advance, -Eugenio
  15. Hi Guys! It's great to see Photo can work with .exr files out of the gate :) In my line of work (3D), I work with .exr files a lot. This can be single channel (layer) files, or .exr files containing multiple channels (layers). If I open a single channel .exr in AP, I get a RGB layer and a separate alpha layer. This could be helpful, if only the RGB layer had a 'cut out', so no black bg where the alpha should be. It's the same for .exr files with multiple channels, have all channels imported with the alpha being transparant on each layer if it's there. This is a plugin I use for PS that does more or less the same thing, but has some nice additonal options when importing: http://www.exr-io.com/ Especially the option to split (or not) the alpha channel, and the option to add alpha to all layers when importing is extremely useful imho. I would be nice to see this behavior to change in the future, as it would eliminate one step when the 3D object has no background. PS can import with a transparant bg, but looses the extra matte layer (after years of nagging at Adobe btw.....) And thanks for releasing Photo to Windows!! :) rob edit: I cannot seem to upload a file, so here's a linked file ;)
  16. 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.
  17. 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
  18. Hi, 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).
  19. Are you planning to get 32 bit images like EXR