Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags '32bit'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 12 results

  1. Data: Affinity Photo 2 (just installed) - Windows 10 Pro 64 bits Note: this bug has a very simple workaround, but quite cumbersome in repetition if you work with several 32bit images (and OCIO) at the same time. Description of the bug: When working with OCIO in the "32-bit preview" implementation, while having more than 1 image/tab open, the view-transform appears to almost (but not quite) "duplicate" itself at the point of switching tabs. What's happening it's likely that at the point of switching tabs, it's applying the ICC transform + the OCIO one. For example (video attached), I have a Linear-709 image loaded being visualized with an OCIO transform, everything looks fine. I load another one (in this case an identical re-export of the first); the view appears broken. This has a really easy workaround solution: simply switch back and forth the selected transform on the 32-bit Preview panel, and it resets back to looking fine. But as you can see in the video, this step is required every single time you switch tabs/projects. How to replicate: - Load a 32-bit linear image and use OCIO "32-bit Preview" as your preferred visualization method, with any ocio.config of your liking setted up. - Then, load/open another image (also 32 bit, so that it uses the OCIO preview as well). - Switch back and forth between their tabs. If you wish to use the same image I did (its CC0 made by myself, but I tried with other images too with the same bug present): https://github.com/jkierbel/CC-Skull-Test-Image If you wish to use the same OCIO configuration I used for this test (I also tried with other ones with the same bug present): https://github.com/sobotka/filmic-blender/tree/all-views Video showcasing the issue (and it's workaround) attached 20-11-2022-14-29.mp4
  2. Hey All, Got a question about OCIO and Blender's Filmic profile in AP. I'll preface this by saying I'm no expert in color/gama spaces and profiles, so go easy. Here's my situation. I'm running some tests with 32bit OpenEXR renders out of Blender and compositing them in AP. Up until last week, admittedly, I did this in PS, but PS on the Mac can't open OpenEXR files, and I do like working on my M1-Max. I digress. Back on point... When I open these renders in AP, I get the same exact export output whether I use the ICC Display Transform or OICO Display Transform so long as I have the layer setup as show in the video put out by James Ritson, of Affinity Photo, i.e. OCIO, LUT, OCIO. It's identical on export out to TIFF or JPEG. Can anyone explain what is happening, or what I'm missing... or has AP just been updated since James made his video? Video is linked here. Thank you!
  3. Hey guys, I found this weird problem, while importing 32bit .tif files. Photoshop and Windows can preview them normally, but Affinity is adding white boarders around the white areas. Hope to get help here... Any idea what I am doing wrong? Thank you Jonny
  4. Hello, With a custom OCIO config, with 32-bit Linear document in ACEScg color space, with a display management set to OCIO Display Transform and custom display LUT, with several documents open at the same time (all 32-bits ACEScg), we found that the 32-bit display is deactivated when swithing from a document to an other. We have to click on 'Unmanaged' or 'ICC Display Transform' then on 'OCIO Display Transform' to finally see the correct display. Whereas this is not critical, we are always able to bring back the correct display with a few clicks, this is really annoying and perturbing for the artists. This is with Affinity Windows 10. Thanks.
  5. Hello Stacks and panorama both output in RGBA 16 bit. Is it not possible to output into 32 bit? It would be good to have the extended flexibility obtained when using RAW as base files. With panoramas it is within reasonable bounds to pre-process individual frames but that is often somewhat excessive for stacks. All goes otherwise very smoothly Michael
  6. Hi, I do not know if is it some bug or I my lack of knowledge but since I've once changed in develop assisitant option for "RAW output format to RGB 32bit HDR" all my files are always opened in 32bit even thought that I reset this option back again to output in 16 bits. I cannot find in any other place option to change this and due to the fact that my computer is not so fast developing in 32 bits almost ruins my machine's resources. I hope that this can be fixed somehow.
  7. Hi, I've been working on a document in 32 bit mode, then started to add filters then this artefact appeared but this disappeared when downgraded to 16bit. I presume it is software bug? Kind Regards C Wolland 2017-03-16 artifact.afphoto
  8. Greetings! I love the power and control that using the Tonemapping persona provides with single image editing. But I'm concerned that it is so slow to go into the persona that it hinders my workflow. Once it gets into the module it moves quickly but it lags again horribly when applying the change. I'm using The files I'm using are from a Canon 5DSR, and I go to 32bit Adobe RGB straight from the raw engine. The System is an i7 8700k 3.7-4.5GHz CPU with 16GB 3200 speed DDR4 RAM. NVIDIA GeForce GTX 1080 Ti 11GB GDDR5X GPU . Running windows 10pro. The performance monitor shows it is spinning at 16% (1 core 4.5GHz) and not using any disk. Are there plans to improve the parallelism and overall performance of this wonderful feature? Thanks!
  9. Quite everything is in the title, but to be more contextual, I'm working with 32bits linear .exr (3D renders). To have a proper non destructive workflow I use OCIO layers to convert from linear space to color profil spaces, then I use creative LUT (or do manual adjustments). Exemple: OCIO layer to convert from scene linear to Slog, then a creative Log LUT to have my look, and export to final 8bits format. The problem is at the end of the process, when exporting an image there is an ICC profile apply on top of my stack, so it add an aditionnal transfer curve wich altered my work. I don't talk about how to view my work how it's exported, I know that, but I want my work not to be altered with additionnal transform. I know a cheap way of doing what I want but it's not satisfying. So, is there a way of disabling ICC profile during the export? Or is it planned to add the option in a future release?
  10. 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.
  11. Hi, it seems the "artefacts on 32bit images" bug is still around. I used the Vignette filter on a 32bit HDR stack and got a grid that's also visible in the exported image (see attached screenshot). Cheers, Henning
  12. Absolutely gutted that Affinity doesn't support Windows 32 bit. There a many photo enthusiasts (as opposed to professionals) who can't easily justify (to their partners!) endless expense on gear and it is often forgotten that the computer is just another item in a fairly long list that must be funded. I run a quad Xeon that is plenty fast enough for my needs, but manufacturers keep forcing me upgrade (which I can't afford) or I must forget about the most recent software, which seems to be all 64 bit. My question: Can Affinity be compiled for 32 bit or does it use hardware/OS features that 32 bit machines/OS don't have? If the former, then please do it! If the latter, can you consider a 32 bit version? Here's hoping, because I used Serif years ago and quite like the company ethos. I ran with Photoshop for several years then swapped to Corel but to be honest I dislike them both and have been looking for a viable alternative for a long time.
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.