Jump to content

thkl

Members
  • Content Count

    6
  • Joined

  • Last visited

About thkl

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    Germany
  1. Hi there. I am pretty disappointed. Version 1.4.2 is released and this issue is still unresolved. It would be very nice if there would be an information update from the developers on an estimated fix date...
  2. Is there any news on this issue? At the very moment Affinity Photo is unusable for me: - no native support for new Fuji RAW-Format (manageable with workaround) - EXIF-Data missing/removed on raf-file and jpg-export (see https://forum.affinity.serif.com/index.php?/tags/forums/AFP-791/) I have reverted to darktable. Would really like to see some progress here...
  3. Hi Sean, thanks for that workaround. I wil give it a try! Didn't even know one could change the RAW engine used...
  4. Hi there, Fuji has recently released the firmware 4.0 for its X-E2 model. Now Affinity Photo crashes when I'm trying to open a RAF-File. This is not related to one file, but to all files, it can be reproduced with every single RAF-file from the camera. Prior to the firmware update Affinity Photo worked fine. Link to file (dropbox): https://www.dropbox.com/s/kzi1o44gh0t5s1j/20160204-7859.raf?dl=0 Additional info: it seems that dcraw and RawTherapee suffer from the same problem. Maybe some library that needs updating? Exiftool reports RAF Version: 0400 Excerpt from crash report: Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000014 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x14: --> __TEXT 000000010a3af000-000000010a445000 [ 600K] r-x/rwx SM=COW /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 liblibpersona.dylib 0x0000000119b7cc2a DevelopTool::Start(Kernel::Counted<Tool>) + 2218 1 com.seriflabs.libcocoaui 0x000000010b2f0bdf -[Document setCurrentTool:] + 1247 2 com.seriflabs.libcocoaui 0x000000010b6501f3 -[DocumentView setCurrentTool:] + 67 3 com.seriflabs.libcocoaui 0x000000010b64a6a4 -[DocumentView setDocument:] + 516 4 com.seriflabs.libcocoaui 0x000000010b780260 -[NotificationsController handleNewDocumentNotification:] + 2560 5 com.seriflabs.libcocoaui 0x000000010b77deb3 -[NotificationsController handleNotification:] + 1571 6 com.seriflabs.libcocoaui 0x000000010b77d5fb -[NotificationsController receiveNotification:] + 1115 7 libdispatch.dylib 0x00007fff942c7871 _dispatch_call_block_and_release + 12 8 libdispatch.dylib 0x00007fff942bc33f _dispatch_client_callout + 8 9 libdispatch.dylib 0x00007fff942cfc1d _dispatch_main_queue_callback_4CF + 1685 10 com.apple.CoreFoundation 0x00007fff99051cd9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 11 com.apple.CoreFoundation 0x00007fff9900cd3d __CFRunLoopRun + 1949 12 com.apple.CoreFoundation 0x00007fff9900c338 CFRunLoopRunSpecific + 296 13 com.apple.HIToolbox 0x00007fff87d96935 RunCurrentEventLoopInMode + 235 14 com.apple.HIToolbox 0x00007fff87d9676f ReceiveNextEventCommon + 432 15 com.apple.HIToolbox 0x00007fff87d965af _BlockUntilNextEventMatchingListInModeWithFilter + 71 16 com.apple.AppKit 0x00007fff8d8ae0ee _DPSNextEvent + 1067 17 com.apple.AppKit 0x00007fff8dc7a943 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 18 com.apple.AppKit 0x00007fff8d8a3fc8 -[NSApplication run] + 682 19 com.apple.AppKit 0x00007fff8d826520 NSApplicationMain + 1176 20 com.seriflabs.affinityphoto 0x000000010a3b0d84 0x10a3af000 + 7556 Hope that helps. I hope you can fix this soon. If you need any more information, I will try to supply it. Thank you, thkl
  5. Hi Leigh. Thanks for the reply. I think I'll be patiently waiting (for lens profiles and eventually for the Leica Q). And of course for batch editing as every image of the "I want one"-Leica would need the correction applied. (Seems Affinity Photo just saved me some money...) I have been able to get my hands on some DNGs from the Leica Q and played around a little bit. Using the lens correction in Affinity does indeed correct the barrel distortions from the Leica lens but the result looks slightly different from the DNG opened with Adobe's CameraRaw. From what I see in the pictures the correction in Affinity is working very well at the image borders and does overcorrect the image center. The transformation matrix for the Leica lens seems to be less uniform, so to say. The corrected image gets a somewhat unnatural look in the centre, unfortunately. Tom.
  6. Hi there! I am new to this forum and a new user of AffinityPhoto as well. So far I have tried it on my various images (Fuji X100, Fuji X-E1, Canon D7000 and numerous tiff-files from scanning my negatives from my camera collection) and I am extremely happy that I gave Affinity a try. (Not to mention that I do not endorse Adobe's switch to rental software). As of this moment I am considering buying a Leica Q. I do know that Leica embeds a lot of lens correction information into their DNGs and Lightroom is interpreting this information when opening the file. So with Lightroom the distortions from the 28mm lens get corrected automatically. I won't comment on the design decision from Leica that their lens on the Q needs some software correction, the camera is stunning and the images are snap sharp, and I want one :D So the question is: has someone here tried to develop Leica DNG files with Affinity? And what are the results? Or, put it another way: Does Affinity Photo read and interpret lens correction information that is embedded in DNG files? Unfortunately I can't get my hands on a Leica Q DNG file that is unaltered, so I cannot test it by myself. If anyone could help it would be greatly appreciated. Tom.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.