Otto Manuel

Thank you.

Hi, I purchased an Affinty Designer license to give it a whirl. One feature I have enjoyed in vector art applications that I have used in the past is the way overlapping vector strokes can be automatically join into larger simple shapes. Macromedia Freehand and Flash would accumulate brush strokes in into vector outlined blobs and at times this was very convenient. I was hoping that perhaps Affinity Designer might have such a feature. I don't see anything like that. Am I missing it some where? Thank you!

Hi, I am using Affinity Photo 1.7.1.404 on Win 7 Pro x64, with an older Wacom CTE-450 Bambo Fun. The Wacom drivers are the latest available for the device, but at this point are also relatively old. Occasionally my Windows install boots with a dialog "The tablet driver is not running". When this happens left click still works, but I have to reboot to get the full function. Lately , I have also had some issue with updates for the Chrome web browser debilitating the Wacom right click function. Windows 7 doesn't have Windows Ink so I can not utilize the popularly recommended turn it off fix. After a couple weeks of hoping for an update to the updates, I gave up on this and switched web browsers. I have one particular VST plugin, which I use in audio applications, that doesn't recognize my Wacom tablet, but that plugin is developed by a Mac developer who offers poor service so he has not fixed the issue. All the other software products written and sold by that vendor do work with my Wacom tablet so I am sure that the one product he sells that does not work could work if he cared to make it so. All of my other applications seem to still work fine with my tablet, but I anticipate more issues coming up because Win 7 and the Wacom drivers are so dated by computer time standards, so I was curious to see if can replicate the issue you have. On my system the right click function of my tablet pen works 100% ok in Affinity Photo. I hope this is helpful in some way. Thank you!

Hi, I am little surprised that someone at Affinity has not, at the very least, mentioned some awareness of this issue. I understand that this may not seem to effect everyone. For example; I made a fresh RAW photo with my Camera and developed it with Affinity Photo. My Preferences > Color is selected as sRGB etc. When I export that photo as a JPEG the metadata tagging is correctly recognized as sRGB. When I open a photo, that has been converted by Adobe Camera Raw and turned into a .Tiff with ProPhotoRGB, with Affinity Photo and export a JPEG with color space conversion to sRGB and ICC date embedded the tagging is not formatted correctly and the EXIF property is recognized as Uncalibrated. I also switched Preferences > Color to 16bit ProPhoto RGB and re-developed the RAW file into a new .afphoto. When I exported this as a JPEG with color space conversion to sRGB and ICC date embedded the tagging is formatted correctly and the EXIF property is properly recognized as sRGB. Finally, I repeated the test where I created a new blank project using the "Photo" and sRGB option. I painted some colors and then Exported as a JPEG with color space conversion to sRGB and ICC data embedded. The EXIF tagging is not formatted correctly and the EXIF property is not recognized at all. It appears as if the category doesn't have a value. I have hundreds of *final master* photos archived as flattened 16bit TIFFs in ProPhoto RGB format. I use these as the source file when I need to prepare a JPEG for some specific output. If I can not rely on Affinity Photo to resize, convert the colorspace, and tag the colorspace properly then my long term goal of using Affinity Photo to replace my current post processing toolkit is neutralized. The circumstance relegates Affinity Photo to an application which I may be curious about but reluctant to consider seriously. If I just got my first camera, and Affinity Photo was my first photo app, I don't think I would care. Conversely, it seems like there must be a very large number of photographers who share my circumstance, where managing an archive of 16bit deep colorspace images is routine and the ability to use a photo edit application to export examples of that library with proper formatting seems like a basic expectation. This problem seems like it must have an easy solution, but I am disappointed to see that no one at Affinity seems interested in commenting on the issue. I understand the fix may be a low priority in the schedule, but it seems like someone at Affinity should acknowledge that a fix is due. Thank you.

Hi, Thank you for the helpful reply. I just made an overlay with an example of a CR2 conversion made by Affinity Photo on the bottom layer, and an example made elsewhere on top. After aligning the pixels, I can see the narrow strips of additional information at the margins. Nice! Thank you!

Developing a 8688x5792 .CR2 RAW file in Affinity Photo creates a 8736x5856 .afphoto Title says it all. My .CR2 file from a Canon camera is expected to be sized as 8688x5792 pixels, but after opening and developing the data into a .afphoto format the pixel dimensions are 8736x5856. It seems as if the demosaic process differs from that used by Canon, Phase One, DXO and Adobe RAW converters. What is up with that? Win 7 Pro x64 SP1 with latest updates. Affinity Photo 1.7.1.404

As a test I opened a RAW file in Affinity Photo and "developed" it. When I exported the photo as a JPEG it was tagged properly with the sRGB tag. So that seems similar to what you have observed. In all my tests where I open a file that has already been assigned another Colorspace the exports with sRGB conversion and embedded ICC profile are mis tagged with the "Uncalibrated" label.

Hi Chris, You evidently do not understand how logic works. An expectation that sRGB should be tagged properly in EXIF metadata has nothing to do with the fact that Adobe RGB can not be tagged. You are comparing Oranges to Red Herrings. I did not come to the Affinity forum to teach you how to use Photoshop on your Mac. Nevertheless, you may find the answer to your question on page 26: https://www.exif.org/Exif2-2.PDF Re: 4.6.5 B You may also find a special note which answers your question here: https://sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html look for Tag ID 0xa001. HTH. sRGB on the other hand, is specifically intended to be tagged with a "1" in EXIF metadata, and when it is being tagged improperly, as with Affinity Photo's export function, there is an opportunity to fix the issue.

Hi, A colleague suggested that I attempt to edit the meta data of a JPEG produced by Affinity Photo. I used the editor at get-matadata.com to edit the Color Space entry from "Uncalibrated" to "sRGB". I then downloaded that modified file and used a Binary Compare application to see how it differed from the version originally produced by Affinity Photo. The attached screen shot shows the location where the code was changed to indicate that the colorspace is sRGB. Affinity Photo wrote the tag incorrectly and after manually editing the tag the color space is correctly identified. It would seem to be a simple fix to format the file structure in the manner which Adobe does, if someone will have the chance to look into the matter.

Here are readouts from Get-Metadata.com showing the differences between how Adobe encodes metadata and Affinity does: https://www.get-metadata.com/result/cecbba84-218c-4ff7-a8a4-2f256d8e0190 https://www.get-metadata.com/result/b62517a8-3af4-4323-810f-1966e02f1a19 You may notice that Metadata.com can not see the specific form of RGB colorspace info in the Affinity example.

Here is an article about the Windows Property System.Image.ColorSpace https://docs.microsoft.com/en-us/windows/win32/properties/props-system-image-colorspace Which, to the best of my limited understanding, suggests that the "Property" is based upon or extracted from EXIF metadata but is stored elsewhere in the file structure. I did notice that Adobe and Affinity conform to differing EXIF versions: Adobe saves <exif:ExifVersion>0220</exif:ExifVersion> while Affinity saves <?exif:ExifVersion>0221?</?exif:ExifV?ersion>?

Here's another bit of information. I have been reading about how the addition of thumbnails can impact EXIF formatting so I tried another test. I opened the "painting" that I synthesized from scratch within Affinity Photo, changed my Preferences to not embed a thumbnail, and exported a JPEG with the ICC embed option. The resulting file is no longer recognized by Windows Properties Color Representation as "Uncalibrated", now it is simply unrecognized as anything. The field is left blank.

Chris, You are not being helpful. Lecturing about ProPhoroRGB and JPEGs, proselytizing about operating systems, reflecting upon "Windows(sic) Photos", (actually named Microsoft Photos and introduced in Windows 8) which hasn't been part of this discussion until you brought it up, and linking to a Pentax Forum thread where someone who admits he doesn't know what he talking about is answered by people who don't know what they are talking about, is a waste of your time. You may not know you are trolling, and you probably presume that you are trying to be helpful, but you are just interjecting where you yourself have repeatedly admitted a solemn disinterest, and that has been reflected by the content of your posts. Hopefully someone who does want to understand that there is an issue with Affinity Photo and Windows integration will recognize the circumstance and make some useful suggestion that may lead to an improvement. Thank you.

Here are the EXIF exports: Affinity_test_03.xmp Affinity_test_03-saved-by-Photoshop.xmp

Curiously, when I open the jpeg in Adobe Photoshop and save as a JPEG, the Adobe export is able to embed the color space data in such a way that Windows Properties dialog actually recognizes it. In other words, Adobe knows how to save the file with the metadata that Windows Properties expects to see. Here is the jpeg as saved with Photoshop. <?xpacket begin=" " id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c011 66.145661, 2012/02/06-14:56:27 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:xmp="http://ns.adobe.com/xap/1.0/"> <xmp:ModifyDate>2019-07-09T15:25:06-06:00</xmp:ModifyDate> <xmp:MetadataDate>2019-07-09T15:25:06-06:00</xmp:MetadataDate> <xmp:CreateDate>2019-07-09T15:15:48-06:00</xmp:CreateDate> <xmp:CreatorTool>Adobe Photoshop CS6 Windows</xmp:CreatorTool> </rdf:Description> <rdf:Description rdf:about="" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#" xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#"> <xmpMM:DocumentID>xmp.did:0576654CA29011E99356A77601B33F78</xmpMM:DocumentID> <xmpMM:InstanceID>xmp.iid:0576654BA29011E99356A77601B33F78</xmpMM:InstanceID> <xmpMM:History> <rdf:Seq> <rdf:li rdf:parseType="Resource"> <stEvt:action>produced</stEvt:action> <stEvt:softwareAgent>Affinity Photo 1.7.1</stEvt:softwareAgent> <stEvt:when>2019-07-09T15:15:48-06:00</stEvt:when> </rdf:li> </rdf:Seq> </xmpMM:History> <xmpMM:DerivedFrom rdf:parseType="Resource"> <stRef:instanceID>C897CB4C4CD5B1111EFD8F1FBC69C04F</stRef:instanceID> <stRef:documentID>C897CB4C4CD5B1111EFD8F1FBC69C04F</stRef:documentID> </xmpMM:DerivedFrom> </rdf:Description> <rdf:Description rdf:about="" xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"> <photoshop:LegacyIPTCDigest>D41D8CD98F00B204E9800998ECF8427E</photoshop:LegacyIPTCDigest> <photoshop:ColorMode>3</photoshop:ColorMode> <photoshop:ICCProfile>sRGB IEC61966-2.1</photoshop:ICCProfile> </rdf:Description> <rdf:Description rdf:about="" xmlns:dc="http://purl.org/dc/elements/1.1/"> <dc:format>image/jpeg</dc:format> </rdf:Description> <rdf:Description rdf:about="" xmlns:exif="http://ns.adobe.com/exif/1.0/"> <exif:ExifVersion>0220</exif:ExifVersion> <exif:PixelXDimension>900</exif:PixelXDimension> <exif:PixelYDimension>600</exif:PixelYDimension> <exif:ColorSpace>1</exif:ColorSpace> </rdf:Description> <rdf:Description rdf:about="" xmlns:tiff="http://ns.adobe.com/tiff/1.0/"> <tiff:Orientation>1</tiff:Orientation> <tiff:ImageWidth>900</tiff:ImageWidth> <tiff:ImageLength>600</tiff:ImageLength> <tiff:PhotometricInterpretation>2</tiff:PhotometricInterpretation> <tiff:SamplesPerPixel>3</tiff:SamplesPerPixel> <tiff:BitsPerSample> <rdf:Seq> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> </rdf:Seq> </tiff:BitsPerSample> <tiff:XResolution>72/1</tiff:XResolution> <tiff:YResolution>72/1</tiff:YResolution> <tiff:ResolutionUnit>2</tiff:ResolutionUnit> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="w"?>