Jump to content
You must now use your email address to sign in [click for more info] ×

marcus.fehse

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. does „by design“ mean it’s an elaborated decision because of something unalterable? i want to apologize for insisting but – with my little knowledge of coding – i would think the function which adds the metadata to the default slice could doubtless be called while exporting any other slice too.
  2. just to explain, why other slices than the default slice could be important: imagine one retouched a photo. the client needs the image in full resolution and a 1:1 version for social media or a somehow cropped version for his website or a PRINT version with some margin around or ... in my workflow i would cascade the MOTIF inside a masked group. my default slice always points to a legacy copy of the document for coworkers who ask for .PSD-files. the second slice would contain the CROP the next the MOTIF and so on. my workaround for now is clipping the canvas before exporting through the default slice to different file formats needed for the MOTIF and then clipping the canvas again to the cropped version with another file format preset for the CROP and so on. it’s much better than restoring all the lost metadata with some tool of your choice. but it’s not as convenient as it could be. wouldn’t it be much easier to have the metadata preserved by the raster graphics editor – as i would definitely expect? ober!schöne grüße, marcus.
  3. hi. as i learned these days: the export persona of affinity photo embeds all the metadata of a document in the default slice only. for all the other slices all metadata – especially CAMERA and GPS data – is lost. it’s not the right place to ask: why? please preserve the metadata through all slices of export persona unless they are checked off. thank you. ober!schöne grüße, marcus.
  4. exactly. thank you for investigating further, @- S -. (i’ve never read this tooltip info inside export persona. my bad.) is there any idea or logical explanation why one would want this behaviour? i’m often exporting my work to different sizes and formats (incl. different colour spaces) for different needs. in most cases CAMERA- and GPS-data is not so important. my personal info, title and subject are added afterwards via an exiftool based script. but loosing all CAMERA- and GPS-data unintended would be no option to me. hence: the tooltip info inside export persona tells me it’s a „feature“. i should definitely place a feature request.
  5. as i wrote before: it is basically the same image exported either via export persona or file > export. after this both exported files got their additional EXIF-data via a script using exiftool written by phil harvey. EXIF-data of the camera and GPS-data is not touched (neither added nor deleted) by this. it’s just used by the script to make some cryptic – or for some software hidden – info human readable like in IPTC:Keywords where the altitude above mean sea level, the camera direction relative to north and the gimbal pitch is noted. any processing prior to the export should not be interesting.
  6. hi. while developing some photos in affinity photo [v2.1.1/macos] unfortunately all EXIF- and GPS-information was lost, after exporting some different formats via the export persona. yes, the „embed metadata“ checkboxes are all checked! to preserve the EXIF- and GPS-information i had to export every slice to every format „by hand“. is there a special setting i’m missing? ... or is this just another BUG? you might check the metadata of both images – one saved with export persona and one with file > export. ober!schöne grüße, marcus.
  7. is there any chance to see this improvement in the near future? i see others also fighting with this strange sub-pixel behaviour since V1.
  8. the files are on their way. my workflow: the aerial was developed in DxO and saved as 16-bit data in sRGB IEC61966-2.1 colour space. the renderings are HDR saved as 32-bit linear openEXR files. in most cases i add some layers for ambient occlusion or a depth layer and group them with a alpha-mask before pasting this to the photo. but even the unedited openEXR file colour- or gamma-shifts when pasted to the 16-bit document. my workaround at the moment is to change the colour space before pasting – either the aerial to 32-bit HDR or the rendering to 16-bit. but this is not intended, isn’t it?
  9. i understand. thank you for keeping this problem in your mind and bringing this issue up again. hej, @serif did you notice the annoying „colour management broken while pasting“ BUG? =;^)
  10. as already mentioned here: not helpful too. you might know a lot about graphics, bit-depth and colour spaces but not enough about respectful behaviour. if a user reports a bug (or what feels like a bug at least) the intention is to help the developers to improve their product. „You should really preprocess ...“ is an advice based on your opinions. you should really ask yourself if someone who reports a bug with the conclusion „in photo1 inserting these layer(s) gives the expected result.“ – which doesn’t sound like a first-time user – wants to hear it’s her or his fault. itIsYourFault again, @NotMyFault! just think about it. ... and sorry to all the others for getting off-topic! i just hope my comment improves the quality of conversation in this part of the affinity-forum a bit.
  11. hej @NotMyFault, let’s get serious! i understand your intention to help. but it definitely did not in this case – at least for me. ... and i did not ask for some help. we are in the bug reporting section of this forum. if someone tells me, it’s not a bug, it’s intended, and asks for „one of the source files, and screenshots of the export settings to check if this causes the seam in your case“ with a royal „We would need ...“ on top newbies like me could expect to interact with an official or at least a freelancer. just to be funny: itIsYourFault! ask yourself if this is the right way to communicate. to be honest: the upsizing vectors to a high resolution explanation gave me an idea of why one could decide to rasterise AFTER resizing at least – resulting in a new feature request at the end. so long and take care, m.
  12. thanks @,,,. it’s a bit more complicated at the end, if you work with different, partly nested groups of layers and slices in export persona. but for a direct export via menu or shift+opt+cmd+S it’s a reasonable workaround.
×
×
  • Create New...

Important Information

Terms of Use | 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.