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

AP overwrites 32-bit tiff with 16-bit tiff when saving


Recommended Posts

If I load a 32-bit tiff in AP, make a trivial change (like applying an adjustment then undoing it) and save the file, AP saves it as a 16-bit tiff. This seems like a bug to me...

Is there a workaround? Image export is not viable, because I need to save over the original file, not create a new one.

I'm using AP 1.10.5.

Thank you.

Link to comment
Share on other sites

You can Export, and overwrite the original. You merely need to supply the proper file name and location, and accept the warning that you're going to overwrite it.

It would, of course, be much more convenient for it to work automatically. Personally, I prefer not to overwrite my originals like that, but if you want to I see no reason it shouldn't work so that does feel like a bug.

-- 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:  Windows 11 Pro 23H2, 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 17.7, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.6.1

Link to comment
Share on other sites

8 hours ago, walt.farrell said:

You can Export, and overwrite the original.

Even if this works in this specific case, as you mentioned this is a dark bad pattern, and should be avoided under all circumstances to avoid bad patterns sneak into your „muscle memory“. It is especially dangerous as Affinity requires read access to opened files at any time. Tiffs could be (mis-used) as containers of affinity files, including linked files etc. 

Exporting over the current opened file is a good recipe for potential data loss. On top, the Windows and MacOs version differ in how files are saved or exported. On Windows, Affinity tends to create a temp file on c:drive, i could not find this on MacOs.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

3 hours ago, NotMyFault said:

Tiffs could be (mis-used) as containers of affinity files, including linked files etc. 

In that case, though, Export is required. You cannot (as far as I know) Save a TIFF file that contains Affinity layers; that's only an Export option.

-- 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:  Windows 11 Pro 23H2, 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 17.7, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.6.1

Link to comment
Share on other sites

9 hours ago, walt.farrell said:

In that case, though, Export is required. You cannot (as far as I know) Save a TIFF file that contains Affinity layers; that's only an Export option.

I suppose if you work with affinity files directly this simplifies the situation, however afaik affinity files have no direct interoperability with anything outside the affinity ecosystem (hence my other post requesting a file format sdk so devs can start supporting it).

Link to comment
Share on other sites

33 minutes ago, Michael Allman said:

I suppose if you work with affinity files directly this simplifies the situation, however afaik affinity files have no direct interoperability with anything outside the affinity ecosystem

The same is true of TIFF files exported with Affinity Layers. Only Affinity can read them. Essentially it is a TIFF with an embedded .afphoto, similarly to Photoshop producing a TIFF with a PSD embedded.

-- 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:  Windows 11 Pro 23H2, 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 17.7, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.6.1

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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