Asser82

Members
  • Content count

    116
  • Joined

  • Last visited

About Asser82

  • Rank
    Advanced Member

Recent Profile Visitors

83 profile views
  1. Yes please. Lightroom seems to use them too. If this is going to be fixed, please ensure that the before and after jpegs are shown under the same lens name in LR when the user filters by lens. I do not know, what else depends on maker notes and which workflows are broken by striping them away. Thx.
  2. Done, hope this helps.
  3. When I am at home I will try to use the exiftool to restore the metadata. Should be something like that: exiftool -X -b -makernotes -all a.jpg > a.xml Work with Affinity Photo exiftool -tagsfromfile a.xml -all:all a.jpg Perhaps -all arguments can be removed, if the problem lies in makernotes only. If this works, I will write a batch automation application while this is not addressed.
  4. It might be the Makersnote, but the delta seemed to be much greater. I would not expect the metadata to be changed at all, except maybe the modification date and the creator tool. Lets discuss this in the bug forum, so we do not have two places to look at. Goto here:
  5. Hi, I have written this in the question forum and read to late that this topic is now handled here. I wanted to tell that I have also this problem. I import my Canon RAWs in Lightroom, which is used as DAM, and develop the JPEGs in DxO PhotoLab. The lens information produced in the JPEGs is OK at that point, because Lightroom combines the CR2 and the JPEG under the same lens filter (EF-S 18-135mm f/3.5-5.6 IS STM) after DxO export. Now I want to remove red eyes inside the exported JPEG in Affinity Photo. What comes out is a JPEG with broken metadata. DxO can no longer find the lens that belongs to the Photo, Lightroom assigns the Photo under an own Lens Category (18.0 - 135.0 mm) which is different from the one of the RAW. Parsing the Affinity modified JPEG with "ExifTool" reveals that many of the Canon specific metadata tags have been lost. This is a serious bug and makes AF photo unusable in environments, where tools must work together. If the before after JPEGs are still needed, I can provide them.
  6. I have this problem also: I import my Canon RAWs in Lightroom and develop the JPEGs in DxO PhotoLab. The lens information produced in the JPEGs is OK at that point, because Lightroom combines the CR2 and the JPEG under the same lens filter (Canon EF-S 18-135mm f/3.5-5.6 IS STM) after DxO export. Now I want to remove red eyes inside the exported JPEG in Affinity Photo. What comes out is a JPEG with broken metadata. DxO can no longer find the lens that belongs to the Photo, Lightroom assigns the Photo under an own Lens Category which is different from the one of the RAW. Parsing the Affinity modified JPEG with "ExifTool" reveals that many of the Canon specific metadata tags have been lost. This is a serious bug and makes AF photo unusable in environments, where tools must work together.
  7. I have started with Lightroom 6 + Affinity also. But the created TIFF sizes were to much for me, so I have changed my workflow further. I just do not want to spend >100MB on each photo.
  8. This is also the reason btw. why Adobe can do what they want. They just have "locked in" all their users, because the users do not want to loose their edits while switching to another tool. Even if the develop results are bad compared to others tools. As long at there is not a standard raw format and develop process defined by IEC or something and as long as all camera manufacturers have their own format, nothing will change. So you have to make a hard break at some point, where you use Lightroom for your "before 2018" catalogs and create new catalogs or workflow within a new tool.
  9. I can answer this more precisely. As in any RAW development tool the non destructive edit operations are stored only in the catalog of the tool or in a XMP or similar sidecar file next to the RAW on disc. This depends on your lightroom settings. However the information in such a file has only a meaning to the tool which produced it, at least in full extent. There are parts like star ratings or embedded previews which can be reused by other tools, but the other settings like "Clarity" or your local adjustments cannot be used by other tools 1 to 1 because the underlying RAW engines are different. This is the reason why Lightroom produces a "pre developed" TIFF when it transferes the image to another tool via "Edit In". Another tool just does not understand the Lightroom language and even if it understands it, it has not the code to reproduce the same results. What this means is: 1) If you use "Edit In" you automatically generate large additional files, which consume up your disc space. Additionally your image manipulation process becomes destructive at this point. You just cannot change your Lightroom edits afterwards and reapply the external editor's changes. 2) If an external editor has to use the RAWs directly instead of generated TIFFs, then a Lightroom plugin must be provided by the external tool, which passes the selected RAWs to the external tool. But again the RAWs are provided as they were imported from the camera. Your Lightroom edits stay in Lightroom. This is not Affinity specific.
  10. If the develop module covers your needs, you don't needed it. My needs are not covered, because I need non destructive raw processing with sidecar files integrated into a photo management software where the developed changes can be previewed. The tool must support body and lense profiles and auto correct photos according to these.
  11. Highlights, shadows, midtones and blacks can be adjusted with the selective tone panel globally. Dxo 12 (PhotoLab) has now also non destructive local adjustments with gradient masks, smart masks with edge detection or nik like u-points.
  12. For what do you need layers in a raw development tool? If you use dxo, you do not need Affinity Photo's develop persona. Layers, retouching, photo combining (panorama, stacking, ...) is the domain of Affinity Photo (for me).
  13. This was one of the reasons for me in addition to raw development quality and lens support to buy Dxo PhotoLab this week. This constelation works really great: 1) Lightroom 6 as DAM (Import+Library) 2) Dxo PhotoLab Elite for RAW (Develop) 3) Affinity Photo (Post Develop) No software renting. 2) and 3) are developed in future. For 1) I do not need further development because the DAM part is complete for me.
  14. You do not have the MSI Afterburner or the RIvaTuner Statistics Server (RTSS) running when your NVIDIA GPU is active? I have experienced problems with the way how this tool hacks itself into the process.
  15. performance
    -

    OK, tested everything and could not achieve improvements. Tested: - Disabling XMP - Disabling Hyperthreading - Deleting and reinstaling Affinity (including AppData and Registry entries) To verify that the system works fine I ran cinebench and aida everywhere with the expected results (everywhere better than 6700k and very good memory throughput). Really do not know what is wrong with Affinity on my PC. What I have noticed is that at 5:40 the progress bar disappears and the Affinity window goes into a non responsive/inactive state, displaying a different title bar for the next 5-6 minutes. So maybe this should not happen...would be interesting to know, whether this happens on other Win 10 machines also.