Jump to content

Search the Community

Showing results for tags '32 bit'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. when developing HDR images there is the danger that with RGB color mode you get color faults, because RGB represents color and luminance in the same value. If Affinity Photo would enable a LAB 32 bit HDR color mode that would solve the problem. Because color and luminance are now separated, the large dynamic range of HDR images are mainly reflected in luminance. This prevents color faults during HDR generation. By the way, I like the way Affinity Photo is adressing HDR development in the workflow. However, because I quite regularly get color faults during development, I can not use it in many situations (see attached image as an example for such a color fault in the sky). In this case I use my LAB 32 bit based HDR development programm (Oloneo), which produces nicer color without color faults.
  2. 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 (1.6.4.104) 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
  3. 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
  4. The retouching tools are useless in 32 bit, all they do is painting grey areas. I've attached screenshots for all the tools (inpainting brush, healing brush, blemish removal brush, patch tool). I first tried to use the healing brush which introduced grey areas (screenshot "Healing_brush_32_bit"). I then tried to remove those grey areas using the inpainting brush (screenshot "Inpainting_brush_32_bit") which only expanded the grey areas. I then tried the blemish removal tool (screenshot "Blemish_removal_tool_32_bit") which painted a circle of grey and last but not least I tested the patch tool (screenshot "Patch_tool_32_bit") which also did nothing more than painting a big grey area. There is also a bug concerning the display of masks in 32 bit files. The preview exposure influences the display of masks. I attached two more screenshots, one with the mask like I drew it. I then increased the 32 bit preview exposure and the grey areas of the mask became white. I really don't think that changing the preview exposure should in any way influence how the masks are displayed.
  5. First post here. I've been working on a composite of images captured during totality & getting some banding artifacts in PS when forced to use 16 bit mode rather than 32 bit for sharpening steps. I'd like to make sure Affinity Photos has the adjustments I need in 32 bit mode. The complete workflow for PS is describe in this tutorial by Russell Brown: PS Spin Blur Eclipse Processing From Photos tutorials, I see there are spin-blur filters, Apply Image: Equations panel & an Equations panel. So maybe everything I node is there but done differently in Photos. The key step I'm unsure about is in one of the equations panels. In PS, a duplicate image is spin blurred & the alpha channel of that image is subtracted from the original alpha w/ an off-set of 128 in the Calculations panel to give a low contrast mid-gray frequency mask. That mask is then Overlayed onto the original. I'd like to confirm that all this can be done in Photos in 32 bit mode? Here is a version of my PS work from 77 images w/ artifacts & a mask. The frequency mask reveals the finer corona detail. Thanks!
  6. Hello Everyone, Does anyone know if Affinity Designer or Photo will be available for 32 bit windows systems? I downloaded a trial and I was unable to install it because I don't have a 64 bit system. Regards, Misstheresa2009 :)
  7. It's nice that Affinity Photo has got such good support of the 32 floating point mode but it is somehow unfinished. There are particularly two things that I desperately miss: 1. The ability to show the 32 bit float color values in the info panel. How should we work accurately with 32 bit float values if they are displayed nowhere? All that I can see are the conventional RGB values from 0 - 255 but these are meaningless in 32 bit float. 32 bit float per definition contains color values below 0 (actually a bad thing) or above 1 (actually a good thing). 2. Please make the curves dialogue zoomable so we can also edit values that exceed the white point of 1. The values beyond the white point are in fact one of the main advantages of 32 bit float.
  8. Request a 32 bit version of Affinity Photo be released for Windows 10. I have an admittedly old PC, but it is a 2.2GHZ, quad processor that I am sure could handle Affinity Photo. Specifically: AMD Phenom 9500 Quad-Core Processor, 2200 Mhz, 4 Core(s), 4 Logical Processor(s) I recently upgraded my Vista system with a clean install of Windows 10 mostly so I could run Affinity Photo. My mistake for overlooking 32 vs. 64 bit. I am running Affinity Photo on my laptop and would prefer to run it on my desktop also.
  9. Hi, My desktop PC runs Windows 10 Home on 32 bit system (X64 processor). It has 4Mb RAM. Display card is NVIDIA Geforce 8400GS with DirectX runtime version 11. Will Affinity Photo run on this system? Regards Barry Brotherton
  10. I know it's an option for HDR, but i would really like to have this option for the png file extension.
  11. 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).
×