Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

Hi Affinity beta!

 

Steps to reproduce:

- open a New Batch Job from the File menu.

- add the attached .HEIC file

- set the output to .JPG with 100% quality

- start the conversion

 

The resulting file will miss the 'Date taken' property from the .HEIC file - see the second attached file here.

I did not check the other properties...

 

From my observations, it occurs only with big files - like the attached panorama from my iPhone.

 

Best regards,

Martin.

IMG_4015.jpg

IMG_4015.HEIC

Posted

Welcome to the Serif Affinity forums. 

Are you using the current 2.4.2 Beta of Photo? And what OS do you use?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop 1:  Windows 11 Pro 24H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 26.0, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1

  • Staff
Posted

An issue raised in this thread ("HEIC loses Date Created data after Batch Job") has now been reported to the developers by the testing team (Ref: AF-2625). Thank you very much for reporting this issue to us.

Posted
46 minutes ago, Chris B said:

Hi Martin,

I can see info in EXIF Tool, however, it looks like it might be a general import issue in Affinity as it's nuking a lot of the info even on File > Open...

Hi Chris,

thanks for the analysis - i can only confirm, that i tried it in the 2.2.1 and it is the same - so, very probably, we found an older bug....

  • 2 weeks later...
  • Staff
Posted

The issue "HEIC loses Date Created data after Batch Job" (REF: AF-2625) has been fixed by the developers in internal build "2.5.0.2392".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

×
×
  • 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.