Jump to content

Saijin_Naib

Members
  • Posts

    80
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It would be great if we could enable the manifest flag to allow the Affinity Microsoft Store Apps to move install location, especially since they grow large in size after time and are fairly heavy.
  2. Yeah, it isn't writing anything out to there. This crash is pretty much instant close as soon as the image is attempted to be loaded.
  3. No, but I'm not certain if the Store version writes them there. All I had was ancient entries from the 1.0 Beta
  4. v1.9.1.979 MS Store Image is nothing funky according to MediaInfo, Paint.NET, MS Paint, MS Photos, et all open it just fine. Image sourced here: ss_969408582d4bdce66c4ccf6d637d56628402693e.jpg (1440×1440) (steamstatic.com) cover.zip
  5. Looks like RLE-encoding is standard, as per-spec, so even if uncommon, Affinity should definitely support it for import as well as export. Truevision TGA, version 1.0 (loc.gov)
  6. The attached TGA causes Affinity Photo v1.9 to crash immediately upon load. It was generated by Paint.NET using RLE compression. terrain.tga The same image uncompressed (without RLE Compression) loads fine. terrain_uncompressed.tga
  7. CPU: i7-6700k (not OC'd) GPU: Zotac GTX 1050TI OC 4GB Driver: 460.20 DCH OS: Windows 10 2004 20221.1000
  8. @Gabe This documentation should help: https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop-executionalias I know the Store versions of Blender, LibreOffice, and InkScape make use of this manifest flag (because I sent them the documentation on this )
  9. Not to derail, but also getting instant close/crash with my GTX 1050TI and driver 460.15
  10. Needed this functionality in my new WFH situation, will have to use LibreOffice instead. +1 to needing Fillable PDF support.
  11. Any update on this? Other programs have made it happen: It would be very helpful if the Affinity suite would register themselves here as well, so they can be called by other programs.
  12. No problem. Any idea on the 1/2/4/32 not rendering, and the 16bit rendering grayscale? Thanks!
  13. GitHub Repo for Sample Data: https://github.com/Saijin-Naib/WIC-GeoTIFF-Testfiles Image Set: Standard_GeoTiff_LZW Issues: 1/2/4 bit images (Unsigned) do not display/render properly at all, only showing transparency grid. Issues: 16bit Image (Signed / Unsigned) display in monochrome unexpectedly NAIP_16s (AP) NAIP_16s (QGIS) NAIP_16u (AP) NAIP_16u (QGIS) Issues: 32bit Images (Float, Signed, Unsigned) do not display/render properly at all, only showing transparency grid. Issues: 64bit Images crash Affinity Photo immediately upon load.
  14. I've been exploring Darktable and a feature that has really wowed me is the Dark Frame library concept. In short, the user dumps whatever number of dark frames from whatever bodies they have at whatever combinations of ISO and shutter speed they can into a folder. Darktable will optionally subtract these darkframe(s) from a RAW that is closest in ISO/shutter when matched to the body in the EXIF. With one dark frame, a very minor reduction in luminance/chroma noise was apparent. Switching to 6 dark frames completely removed my hot pixels and reduced color cast and fine color noise on pushed exposures/high-ISO INCREDIBLY. I'm working towards using the DeepSkyStacker recommended 30x dark frames to see if there is any benefit to that number of dark frames for non-astrophotography exposures. It really cleans up the images wonderfully. Areas for improvement: Folder can't be recursed for subfolders by camera/setting Original RAW files only supported (TIFF/PNG/other lossless raster of equivalent bit-depth or greater should be possible as well) Averaging happens at image load, takes significantly long to open image with 6x dark frames. Generation of averaged/stacked proxy TIFF/PNG would likely speed this process up. No Darkframe Subtraction: 6x Darkframes (averaged) Subtracted:
  15. I'd like to see the RAW Demosaic process improved, somewhat along the lines of how DarkTable handles things. I like Affinity's ease of use, so setting sensible defaults for Demosaic engine, settings, etc., makes total sense. However, there are instances where a user might want to tweak the Demosaic or use an entirely different algorithm. For instance, the Markesteijn+fast produces far superior results for X-Trans data to other algorithms in other engines (typically AMaZE-based). This is crucial for IQ, especially when pushing exposure or sharpening at all, basically.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.