dke Posted March 9, 2019 Posted March 9, 2019 (edited) When I try to open tiff files saved by DxO Photolab 2.2 AP Beta 1.7.0.258 crashes (it simply disappears). The problem is new. I could open the same files in Beta 1.7.0.256 and I can open them in the official version 1.6.5.135. My system is Windows 7 Home Premium 64-bit. Regards, dke Nanzdietschweiler_270219_02_DxO.tif Edited March 9, 2019 by dke attached file
Staff MEB Posted March 9, 2019 Staff Posted March 9, 2019 Hi dke, Do you mind attaching a sample TIFF saved in DxO Photolab 2.2 for us to check/fix this please? Thanks. A Guide to Learning Affinity Software
dke Posted March 9, 2019 Author Posted March 9, 2019 29 minutes ago, MEB said: Hi dke, Do you mind attaching a sample TIFF saved in DxO Photolab 2.2 for us to check/fix this please? Thanks. Sorry MEB, file attached in my first posting.
Rick G Posted March 9, 2019 Posted March 9, 2019 I grabbed your TIFF and it opened right up in the latest beta ... nice shot BTW Affinity Designer 2.2.2075 & beta 2.3.1.2212 Affinity Photo 2.2.2075 beta 2.3.1.2212Affinity Publisher 2.2.2075 & beta 2.3.1.2212 Windows 11 Pro Version 22H2 OS build 22621.1928 Processor Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz Installed RAM 16.0 GB (15.7 GB usable) System type 64-bit operating system, x64-based processor
laurentia Posted March 9, 2019 Posted March 9, 2019 5 minutes ago, Rick G said: I grabbed your TIFF and it opened right up in the latest beta ... nice shot BTW And me too ...
David Quail Posted March 9, 2019 Posted March 9, 2019 Your Tiff works great on my Beta 258 Asus ROG Strix G713 Notebook: AMD Ryzen 7 5800H 3.80 GHz with Radeon Vega Graphics | 32GB DDR4 3200mHz RAM Nvidia GeForce RTX 3060 Ti 8GB Gfx | 2x 2TB SSD NVMe PCIe M.2 3x4 | Windows 11 Version 23H2 Build 22623.870
dke Posted March 9, 2019 Author Posted March 9, 2019 Thanks people. My problem still persists. I cannot open tiff files saved by DxO Photolab with AP 1.7.0.258 beta. In the meanwhile I found crash reports (see attached file). 6d26a781-c77b-4568-be28-15ba58273232.dmp
Mark Ingram Posted March 9, 2019 Posted March 9, 2019 2 minutes ago, dke said: Thanks people. My problem still persists. I cannot open tiff files saved by DxO Photolab with AP 1.7.0.258 beta. In the meanwhile I found crash reports (see attached file). 6d26a781-c77b-4568-be28-15ba58273232.dmp I haven't checked the crash report yet, but this might be a locale thing. @dke, what is your Windows system language set to?
Gnobelix Posted March 9, 2019 Posted March 9, 2019 Again, no problems opening the attached TIF file. Windows 10, language German. Cheers Affinity Photo 2.5: Affinity Photo 1.10.6: Affinity Designer 2.5: Affinity Designer 1.10.6: Affinity Publisher 2.5: Affinity Publisher 1.10.6: Windows 11 Pro (Version 24H2 Build (26100.3037)
Uwe367 Posted March 9, 2019 Posted March 9, 2019 I tested too and there are no problems, no crash or similar things. I use Win 10 Home, newest updates, language german. BTW.... very nice picture and a good camera with a good lens Have a nice day. Ich wünsche einen schönen Tag.
dke Posted March 9, 2019 Author Posted March 9, 2019 Thanks. I unstalled Beta 1.7.0.258, deleted manually the directory 1.0(Beta) under user/appdata/roaming/affinity/photo and installed Beta 1.7.0.258 completely new, but the problem persists. I cannot open most tiff files saved by DxO Photolab and I cannot open nef files of my D7200 and my D7000. It is strange.
Mark Ingram Posted March 9, 2019 Posted March 9, 2019 53 minutes ago, dke said: Thanks. I unstalled Beta 1.7.0.258, deleted manually the directory 1.0(Beta) under user/appdata/roaming/affinity/photo and installed Beta 1.7.0.258 completely new, but the problem persists. I cannot open most tiff files saved by DxO Photolab and I cannot open nef files of my D7200 and my D7000. It is strange. I think I know what this is - does the path of the image contain unicode (non-ascii) characters? Perhaps in your username if you're loading from Documents or Desktop? There's a problem with the current version that metadata is failing to load for paths that contain non-ascii characters. This will be fixed in the next version.
dke Posted March 9, 2019 Author Posted March 9, 2019 No, that's not the reason for my problems. When I copy a nef file into the base directory of drive C I still cannot open it.
walt.farrell Posted March 9, 2019 Posted March 9, 2019 5 minutes ago, KARILIYATSI said: The problem is new. I could open the same files in Beta 1.7.0.256 and I can open them in the official version 1.6.5.135. Are you saying that you can't open dke's file, either? -- 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
dke Posted March 9, 2019 Author Posted March 9, 2019 My problem has to do with EXIF data. When I delete the EXIF data from the attached tiff file in my first posting everthing is OK.
Mark Ingram Posted March 9, 2019 Posted March 9, 2019 Thanks @dke, I've just tried it on my laptop here and it opens fine. We'll analyse it next week when we're back in the office to see if there is any extra info we can discovered about the problem. PaulAffinity 1
dke Posted March 9, 2019 Author Posted March 9, 2019 I tried older betas and must correct myself: The problem already existed in version 1.7.0.256 beta. With version 1.7.0.251 I could open all nef and tiff files. Tony77 has the same problem as I:
Recommended Posts