Jump to content

MarvinR

Members
  • Content Count

    78
  • Joined

  • Last visited

About MarvinR

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Ormond Beach, Florida

Recent Profile Visitors

955 profile views
  1. Thanks for the feedback @Gabe. You are absolutely right, the GPS bug is fixed. I ran the wrong copy of the app on my second test. My apologies for taking up your time with this. Beta 1.9.1.221 - RC1 fixed the problem. Peace Marvin
  2. @Gabe, my apology. I just ran the test again and it works completely fine in the Beta. When I did the Export I bet I hit the wrong icon and ran the release that had the bug. Sorry to have taken up your time. Peace
  3. I had submitted a report for GPS Location Data Lost in Affinity Photo Processing a short while back in the forum for report Affinity Photo Bugs on the MAC. @Gabe had told me it was going to be worked on. When I saw the note that one of the fixes in this release was related to reading a TIF file I thought maybe it would be the fix for the GPS Location Data. I left the same note for Gabe in that forum as what follows. However, after I thought for a minute I thought since this was a release candidate I should post the information here too. My apologies if posting in both places turns out to cause any sort of problem. Any below is the information. Gabe will get the same as written below. @Gabe, looks like this is fixed by Affinity Photo Customer Beta (1.9.1.221 - RC1). Tested the copy I had submitted with the bug report and it worked fine. GPS data was in the exported JPG and also appeared when in the metadata when I looked at the JPG in Affinity Photo Customer Beta (1.9.1.221 - RC1). Gabe what I wrote above was after I had tested using the Batch Job option to generate the JPG. EDITED: @Gabe I tested this GPS not being read problem using Affinity Photo Customer Beta (1.9.1.221 - RC1). It works fine when the JPG is created using the File--->New Batch Job option. The resulting JPG shows the GPS data when I open it back into Affinity Photo. However, after I did that test and was very pleased to see the results, I thought I should test by using the File--->Export option. The JPG generated using the File-->Export option did not contain any GPS data. Additionally, if you look at the .TIF file in Affinity Photo you can see that the GPS data is there. I would guess the code used by File--->Export to generate the JPG file needs to be modified as it appears the code for File--->New Batch Job was modified. In the attached zip file are the TIF file, the JPG file generated by the Batch process, and the JPG file generated by the Export process. The file names for the JPG files indicate if the file was created by Batch process or Export process. Hope this helps. Peace Marvin Archive.zip
  4. @Gabe, looks like this is fixed by Affinity Photo Customer Beta (1.9.1.221 - RC1). Tested the copy I had submitted with the bug report and it worked fine. GPS data was in the exported JPG and also appeared when in the metadata when I looked at the JPG in Affinity Photo Customer Beta (1.9.1.221 - RC1). Gabe what I wrote above was after I had tested using the Batch Job option to generate the JPG. EDITED: @Gabe I tested this GPS not being read problem using Affinity Photo Customer Beta (1.9.1.221 - RC1). It works fine when the JPG is created using the File--->New Batch Job option. The resulting JPG shows the GPS data when I open it back into Affinity Photo. However, after I did that test and was very pleased to see the results, I thought I should test by using the File--->Export option. The JPG generated using the File-->Export option did not contain any GPS data. Additionally, if you look at the .TIF file in Affinity Photo you can see that the GPS data is there. I would guess the code used by File--->Export to generate the JPG file needs to be modified as it appears the code for File--->New Batch Job was modified. In the attached zip file are the TIF file, the JPG file generated by the Batch process, and the JPG file generated by the Export process. The file names for the JPG files indicate if the file was created by Batch process or Export process. Hope this helps. Peace Marvin Archive.zip
  5. No problem Gabe. You all do a great job with the Affinity Photo. Really like the positive steps each release has made. Peace
  6. @Walt.farrell, I did have "Embed Metadata" selected in the More...options when I did the export. I just zipped the JPG and am attaching it here. Thanks for checking it. D3200_ShellsOnTable_02-07-2021-999_1345_DxO.jpg.zip
  7. The workflow that is involved is: (1) GPS location data added to .NEF file in NeoFinder software; (2) .NEF file edited in DxO PhotoLab 4 and exported as a .TIF file; and (3) .TIF file processed in Affinity Photo and exported as .JPG file. I checked the exported .TIF file and the GPS location data was present in the file. I checked the .JPG file and the GPS location data was not present. So, it looks like the GPS location data was lost during processing in Affinity Photo. To simplify things I repeated the test and this time in Affinity Photo I simply exported as a .JPG without making any adjustments at all. The results were that the GPS location data was not present in the .JPG that was produced. I am attaching both the .TIF file and the .JPG file I am writing about so you can see what I mean. For me this isn't a critical problem because I can use NeoFinder to copy the GPS location data from the .TIF to the .JPG. But, others maybe surprised as I was to find the final product did not contain any GPS location data. Thanks. UPDATE: Running on Mac mini M1 16GB RAM 1TB HD Big Sur 11.2 D3200_ShellsOnTable_02-07-2021-999_1345_DxO.tif
  8. I am using Affinity Photo 1.9.0 on Mac mini M1, BigSur 11.2, 16GB Memory, 1TB HD The version of DxO Nik Collection I am using is Nik Collection 3 the 25th Anniversary Edition. This is the latest version available. I tested the Nik Collection apps that I normally use and this was the results I got. Color Efex Pro 4: No problem experienced HDR Efex Pro 2: No problem experienced Silver Efex Pro 2: No problem experienced Viveza 2: Affinity Photo crashed when returning from edit (tried both 8 and 16 bit files with same results) Define 2: No problem experienced Analog Efex Pro 2: No problem experienced When the crash occurred a crash report was created by the Mac OS. I copied the contents of that crash report and put it in the document attached. Now Affinity Photo did not produce a crash notification of any sort. When I started Affinity Photo after the crash it started up and displayed the file that I was working on. Hope this report will contain some information that can help identify the cause of the problem. Viveza Crash.rtf
  9. Merry Christmas and a healthy and happy new year. Peace
  10. Patrick, using Affinity Photo Beta 1.9.0.869 selected Luminance brush pack and they downloaded and installed with no problem.
  11. No, I didn't rotate the canvas. I had only made some standard edits on the Basic tab and Lens tab. After reading your post I went back to the same file made some changes on the Basic tab settings and the Lens tab settings. In fact on the Lens tab settings I even tried settings beyond what I did previously. Still everything on the Display tab worked fine and without error. I can only assume that there was a glitch in my system or I did something and failed to realize it. But, both yesterday and today I cannot repeat the problem. If it occurs again and I can repeat it then I will add to this post. But, at this point I feel what ever the problem was I experienced was not a problem generated by Affinity Photo. I do appreciate the responsive support received. Peace Marvin
  12. When I followed your directions for the "Can you try this?" I was able to use both the tablet pen and the mouse and everything worked as it should on the same file I experienced the problem with yesterday. I have no unusual mapping set. And, the Tablet Input Mode is Low Precision. After I ran the test with the pen and the mouse and everything worked fine, I went back and renamed 1.0 to 1.0.goodtest and renamed 1.0.backup to 1.0. I reran the test again on the same file using both the pen and the mouse and again everything worked fine. Gabe and Mark, I really don't know what cause the situation but everything with Affinity Photo 1.8.5 appears to be fine. The problem must have been some conflict on my end. My apologies for taking your time away from other things. Peace Marvin
  13. Tablet Input Mode is Low Precision Added: Mark, please see my response to Gabe immediately below. Peace Marvin
  14. In the Develop Persona in the Overlay area: 1. Click on the gradient tool icon. 2. Create a gradient by dragging from top to bottom. Result: Gradient appears as coming across from the right edge of the image. Re-tested and this time drew a gradient from the left edge into the image and the result was a gradient was created from top to bottom. Windows 10 Version 2004 OS Build 19041.450
×
×
  • 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.