Jump to content

Recommended Posts

Posted

TIFF files can't be read by Topaz Sharpen AI with Beta 1.7.0.250. I get an error - "ImageImport::Wrong input image". I tried with several different images. This doesn't happen with the latest official version of Photo (1.6.5.123).

Aleksandar Mitov
www.renarvisuals.com CGI and 3D rendering services
email: office@renarvisuals.com

Affinity Photo 2.5.5  Windows 10 Pro x64 ver. 22H2  AMD Ryzen 9950X 16-core + 96 GB DDR5  GeForce RTX 3090 24GB + driver 565.90

Posted

As I recall, 1.7 changed to using a different TIFF compression algorithm, though it was supposed to be one that is compatible with more applications than the former LZW compression algorithm.

-- 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 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

Why not give the user the ability to chose the compression method and have a warning appear when choosing the new one as being potentially incompatible? Wouldn't that be better? The overwhelming majority of graphics software I've used gives you that ability.

Aleksandar Mitov
www.renarvisuals.com CGI and 3D rendering services
email: office@renarvisuals.com

Affinity Photo 2.5.5  Windows 10 Pro x64 ver. 22H2  AMD Ryzen 9950X 16-core + 96 GB DDR5  GeForce RTX 3090 24GB + driver 565.90

Posted

I have never seen one that shows a choice of the compression algorithm, but most I've used have allowed a choice of compressed or uncompressed.

-- 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 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

Remember it is a Beta product and there may be issues so therefore it should never be used for anything except testing, remember Sharpen AI works as a Plugin from AP both PRD and Beta.

Both PC’s Win 11 x64 System
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 ASUS ProArt  PZ13 - Snapdragon X Plus X1P42100 (8 CPUs), 16GB RAM
- Neural Processor - Qualcomm® Hexagon™ NPU up to 45TOPS 

- GPU 1: Qualcomm Adreno Graphics, 

 

  • Staff
Posted
20 hours ago, Alex_M said:

Why not give the user the ability to chose the compression method and have a warning appear when choosing the new one as being potentially incompatible? Wouldn't that be better? The overwhelming majority of graphics software I've used gives you that ability.

I think this was mentioned in passing. We ought to add a checkbox in the More export dialog to allow for LZW compression. I found some other apps that don't work with the new Adobe compression (Epson Print Layout to name one of them) so we need to make sure we don't break compatibility for anything or anyone else on release. 

Unfortunately, it sounds like this is also affecting Topaz :(

Posted
19 hours ago, walt.farrell said:

I have never seen one that shows a choice of the compression algorithm, but most I've used have allowed a choice of compressed or uncompressed.

There is at least Photoshop and darktable ...

487047412_Compressiontiff.jpg.0f4af29b22e509f7ac537887d0ebcbc1.jpg

1556788250_compresstifdt.jpg.bbc622a89cdfca2068edd9243ad2edb3.jpg

Note that the LZW compression of a 16-bit image frequently generates a larger file than the same image without compression ... in this case, ZIP compression is preferable.

On the darktable screenshot, deflate means ZIP compression.

 

  • Staff
Posted

Hi @Alex_M

We've just added some TIFF compression options in the macOS version. I believe this should be available in the next Windows beta build. 

When this build is available, could you please go to File > Export > Tiff > More > Compression and change it from ZIP to LZW and let me know if this fixes the compatibility issue you were having with Topaz.

Posted

As Sharpen AI is a very new product in the interim you can open the image in A photo and then call Sharpen AI using the plugin interface.

Both PC’s Win 11 x64 System
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 ASUS ProArt  PZ13 - Snapdragon X Plus X1P42100 (8 CPUs), 16GB RAM
- Neural Processor - Qualcomm® Hexagon™ NPU up to 45TOPS 

- GPU 1: Qualcomm Adreno Graphics, 

 

  • Staff
Posted
15 hours ago, KARILIYATSI said:

TIFF files can't be read by Topaz Sharpen AI with Beta 1.7.0.250. I get an error - "ImageImport::Wrong input image". I tried with several different images. This doesn't happen with the latest official version of Photo (1.6.5.123).

 

We changed our TIFF compression in the beta. There is now an option on macOS to change the TIFF compression to LZW which should resolve this. We're just waiting for the fix to come to Windows.

We're also on build 258 now so you might want to consider updating from build 250
https://forum.affinity.serif.com/index.php?/topic/80813-affinity-photo-windows-customer-beta-170258/

 

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