Jump to content

Patryk

Members
  • Content count

    25
  • Joined

  • Last visited

About Patryk

  • Rank
    Newbie

Recent Profile Visitors

313 profile views
  1. Patryk

    Build 112 Meta Data / EXIF / GPS

    For sure I uploaded this file shown in the sreenshots. Feel free to play around. I just tested it also with raw files from my GX80/85 where the problem does not occur. But also in the earlier built it wasn't a problem with the G9 RAWs.
  2. From the latest release thread: Actually this is a big mess... When I load .rw2 files from my Panasonic G9 the meta data from this file are completely destroyed... Lens information will be deleted and automatic lens correction won't work anymore. Further GPS data are removed. Showing in my screenshots the EXIF from Apple preview and AP Beta Build 112 ... Any comments on this?
  3. You are hearty welcome. That's what this forums and betas are for. Actually it seems to be just a little thing. Any idea when 1.7. is going live?
  4. Dear MEB, thanks for the swift reply. Actually yes, the lens correction is enabled and the picture looks exact the same like with disabled lens correction. Find below some Screenshots and a RAW file from GX80 attached. Here we see loading the .rw2 file to AP 1.6.7. with enabled Lens correction. Below screenshot like regular fisheye without correction (in beta 1.7) Sorry everything is in German but actually I can assure that lens correction is enabled. Maybe you can try out and actually restore the bug? Best regards Patryk _1110949.RW2
  5. Dear Team, actually I downloaded the newest beta as I recognised Version 1.6.7. was not capable to handle my RAWs für Panasonic DC-G9 with the Serif Labs RAW Engine. Actually loading a picture was completely desaturated and modifying simple contrast was really extreme. Anyhow this is not the topic. I faced the solution using Apple Core RAW Engine but as I want to go with the Serif Labs Engine due to Lens correction which was outstanding also for the Olympus 8mm Fisheye I downloaded the latest beta. And what shall I say. I just cannot await to get this Version 1.7. live because the improvements are huge especially recognising much faster loading time on my old MacBook. Unfortunately it seems that the lens correction which was fabulous in 1.6.7. is not applied yet to the beta? Is this right? Best regards Patryk
  6. Hey MEB, yeah I've reported this earlier but did not get reaction on this. Thank you for an appropriate feedback. Actually I need to modify hundreds of files manually which is quite annoying but as you mentioned there are silver linings on the horizon. Best regards.
  7. Dear Affinity Team! I have following problem with the Affinity Photo App for Mac since a while. During trips I capture all my GPS data with my iPhone and write it to the files on the cam every evening to have the GPS tag directly saved to the EXIF. This works brilliant and is a simple solution to atomise the geotagging of photos. The Jpegs and the RAWs have exactly the geotag where the picture is taken! When I load my RAW file to Affinity Photo and make all the adjustments to the picture in the develop persona and finally develop the image I finish it up in the Photo Persona and finally export it to a jpeg to load it to my photos app on my Mac to have it in my library. The problem is that the final JPEG has not the same geotag than the original out of cam JPEG and the RAW. Now I explain what happens and what you need to fix: While developing the RAW file the Develop Persona kills the "-" in front of the values of degree of longitude and latitude in the EXIF what switches the GPS Tag from Northern to Southern latitude or from Western to Eastern Longitude. Kindly find attached a RAW (with the GPS coordinates: 51°30'47,262" N ; 0°8'19,89" W) file for testing. After my regular workflow and exporting to JPEG with AP the geotag switches to 1°30'47,262" N ; 0°8'19,89" E whites actually right in the middle of the river Thames. I actually do not have a file with a southern latitude actually but I think the failure will be the same. I would appreciate a short reaction! Best regards Patryk _1110464.RW2
  8. Hey folks, this problem with "f*ckin up my gps data" while developing raws with gps data inside affinity photo destroys my motivation editing my pictures with AP. Doesn't matter if I take the last release built or the newest beta. The problem is like described above: GPS Data in the RAW file is correct after editing with affinity photo the GPS Data is switched from Western to Eastern longitude. So all the pictures now are relocated from Costa Rica right to the middle of the bay of Bengal between India and Sri Lanka. Is there any chance to fix this soon?
  9. Actually these aren't real solutions. Did you get any feedback from the develop team or shall I buy Photoshop Essential or something similar?
  10. By the way: Is it possible to reset AP to 1.5 again to continue working ?
  11. Yeah you are right, actually there are files that are "failing" and files that are not touched by the issue. This seems quite weird. Anyway it would help me more if I could use Serif labs Engine in the future without the purplez
  12. Hey Chris, I am referring to this topic but I think/hope the dev team is in charge
  13. Just tried quite swiftly the beta download if something improved but unfortunately nothing change in the develop persona concerning the issues that are blocking my work atm. Fringing still occurs with the Serif Labs Engine This curious splitting is still there with Apple Core Image RAW.
  14. Actually the issue seems to be fixed with the last update (beta 1.6.7) but unfortunately the other things are still not solved..
  15. Hey folks, Actually I'm using AP 1.6.6 on a MacBook with macOS High Sierra 10.13.1 I have problems that Affinity Photo freezes when I try to open multiple (>5) jpegs at once (did it quite often with version 1.5 without problems when I want to rescale picture for web) The program freezes and does not give any reaction anymore. Only possibility is to kill the program and restart it open less files at once. Hope somebody can give me hand solving this issue
×