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 9 results

  1. Hi all, I'm fairly new with Affinity (loving it so far), but I can't find a way to see the values of an 32-bit image in the Color Sampler Info panel. No matter what mode I use it seems to always clip to 255 which is not the case of my image. Cheers, Juan
  2. Hi all, I have noticed that the Intensity Slider in the color chooser for 32-bit documents jumps from 0 to +20 or -20 but I'm unable to choose any intermediate values. Here is a short video: Cheers, Juan
  3. Hi folks, anyone noticed the colour change when converting down from 32-bit to 16-bit? Searched the forum for a while and it doesn't come up. I'm working with 32-bit EXR render and at some point you need to convert down to a lower bit depth and when you do any editing on the scene, it changes the colour. Do the same in Photoshop and it stays correct. You can try it with anything: Exposure or Curve to make it visible. Set up the exact same settings in both AP and PS and convert down to 16 bit and then compare both images. Or even just do it in AP. Have your layer stack in full 32 and change the format down to 16 and then switch back and forth to see the difference. I think this is a huge drawback. Whatever is handling the conversion in the background, somethings off. Cheers, Bo
  4. 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
  5. bgreenstone

    32-bit Preview not working

    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.
  6. 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
  7. 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
  8. 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.
  9. 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.
×