-
Content count
10 -
Joined
-
Last visited
About whizzrd
-
Rank
Newbie
-
whizzrd started following Tonal Selections Ignore Child Filters
-
This just happened to me too, I intuitively expected "Select > Tonal Range" to apply to the selected layer as displayed on screen after applying adjustment layers. When no layer is selected the "Select > Tonal Range" does not select anything. The behavior may be "by design" when a layer is selected, but I suggest re-designing such that when no layer is selected the selection applies to image as displayed on screen.
-
whizzrd liked a post in a topic: Can't Open PSD from Apple Photos Extension
-
Hi Affinity team, sorry to bother you with yet another problem. Short description When using Affinity Photo as an extension to Apple Photos, PSD files from the Apple Photo's Library cannot be opened User story As a user of both Affinity Photo 1.6.6 and Apple Photos 2.0 (3161.4.140) on Mac OS Sierra I'd like to be able to perform iterative edits to developed RAW files larger than about 1 MegaPixels. Problem 1 Apple Photos seems to apply a limit of 16MB to adjustment data of Photo Editing Extensions, so round-tripping is effectively only possible with raw files up to about 1 Megapixels; larger files will result in the message 16MB change limit exceeded - document will be flattened and saving only the JPEG into the Apple Photos Library Problem 2 Affinity Photo does not allow saving a copy in its native .afphoto file format when editing a file named "Apple Photos Document.afextensiondocument" (the File -> Save As... menu option is greyed out) but it does allow exporting a PSD document in this case. Attempted work-around I've tried to work around these limitations by exporting a PSD and reimporting the PSD in Photos. (.afphoto files can not be imported into Apple Photos unless they are saved as adjustment data by the Photo Editing Extension AND the file size if below 16MB) Perceived bug However when trying to edit the PSD using Affinity Photo as Photo Editing Extension the following message is displayed in Affinity Photo: Failed to open file [...]/6LVTQB9699.com.seriflabs.extensions/intermediates/Apple Photos Document.afextensiondocument The file type is not supported. Additional information Testing revealed that Affinity Photo CAN open the file when a .psd extension is appended to the file name. [edit] More testing revealed that the document type contained in .afextensiondocument file can be recognised by the "file" tool (file-5.31 as of macOS Sierra) - when editing OpenEXR files (can be opened by Affinity Photo) $ file -b "Apple Photos Document.afextensiondocument" OpenEXR image data, version 2, storage: scanline, compression: zip, dataWindow: (0 0)-(4944 3274), displayWindow: (0 0)-(4944 3274), lineOrder: increasing y - when editing PSD files (can not be opened by Affinity Photo) $ file -b "Apple Photos Document.afextensiondocument" Adobe Photoshop Image, 4945 x 3275, RGB, 3x 32-bit channels
-
whizzrd started following Can't Open PSD from Apple Photos Extension
-
JoanKauai liked a post in a topic: Affinity Photo Customer Beta (1.6.7 - Beta 2)
-
whizzrd liked a post in a topic: Develop exposure slider does not reflect applied value
-
whizzrd started following Develop exposure slider does not reflect applied value
-
When developing a RAW (NEF) file in Photo, having an EV value above 2 and "Apply exposure bias as initial state" set in the develop assistant, the exposure slider and text-box do not reflect the exposure bias applied by Photo. In this (extreme) case the EV value set in camera and applied by develop assistant was +5 but the exposure slider and textbox show a maximum value of +2. Preferred fix is to expand the range of the exposure slider, alternatively (as expanding the range could make exposure adjustments by slider too coarse) allow setting higher exposure values via the textbox and spinners/steppers.
-
whizzrd liked a post in a topic: Location (map) Panel unavailable
-
whizzrd started following Location (map) Panel unavailable
-
The Location (map) panel is not available in Develop persona in Photo 1.6.7 - Beta 2 Will this feature be removed ?
-
whizzrd liked a post in a topic: Migrate adjustments
-
whizzrd liked a post in a topic: Affinity Photo feature roadmap
-
whizzrd liked a post in a topic: What exactly do the Clear User Data options clear?
-
Found the answer to the preference storage part, please move this topic to Feature Requests as request for UI to import/export develop settings
-
whizzrd started following Develop Presets Export/Import
-
Hi, i'm new to these forums and the Affinity suite, please forgive me if this has been brought up before, a cursory search did not return relevant posts for me. I'm looking for a way to synchronise presets in the develop persona between computers and Affinity Photo and Affinity Photo Beta. There seems to be no UI for this, but perhaps these presets can be synchronised between preference storage, where are the develop presets stored on macOS?
-
whizzrd liked a post in a topic: .aftonemap files not associated with Affinity Photo
-
whizzrd changed their profile photo
-
Tone Mapping Preset files (.aftonemap) are not associated with Affinity Photo 1.6.6 and can not be saved in the Affinity Photo folder in iCloud Drive. Please add aftonemap to CFBundleTypeExtensions
-
whizzrd started following .aftonemap files not associated with Affinity Photo
-
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
-
whizzrd started following 32-bit Preview in Panorama Persona
-
whizzrd started following Retain EXIF on Share > Add to Photos
-
EXIF data is lost when sharing images to Apple Photos from Affinity Photo 1.6.6 using File > Share > Add to Photos, please retain this data.
-
whizzrd liked a post in a topic: Affinity Photo feature roadmap
-
Thanks for making Affinity Photo more awesome! Just a quick question: is the new (and hopefully improved) shadows / highlights algorithm implemented in the Tone Mapping persona as well?