Jump to content
You must now use your email address to sign in [click for more info] ×

laurentia

Members
  • Posts

    161
  • Joined

  • Last visited

Everything posted by laurentia

  1. Hi Julie, Unfortunately, I do not have good news for you ... I tried with your photo without result. Then I tried to reproduce the issue with one of my lenses that does not appear in the lensfun database, a Nikkor 28-105 AFD zoom. I get exactly the same problem as you (with darktable using the same lensfun file, I could recognize it)! I deduce that this procedure is inoperative on Windows, the video being made with Mac OS. At this point, only a developer can trace the problem. It should also be known that the maintainer of the lensfun base has big problems of disponibility and because of this, lensfun is updated with big delays and the procedure is quite forbidding. In addition, in lensfun, your Sigma lens has been tested with a Sony and not a Canon. The APSC crop factor for Canon is 1.6 while it is 1.5 for other brands. As a result, the distortion values would be a bit distorted. There is also a conflict in your image at the level of the exifs and the maker notes, in these last appears the zoom 75-300 Canon while it is the Sigma which appears in the exifs ... Sorry for not being able to help you ... the hand is to the developers.
  2. Hi Julie, there must be a difference between the name of the lens in the exifs and in the lensfun file ... Can you give me a link to a raw so that I can see what is possible to do?
  3. Hi, what version of lensfun did you download? Are you sure your 18-300 sigma lens is in the slr-sigma-xml file? I see it in the latest version of lensfun 0.3.95 downloaded from the site lensfun and not that of github.
  4. Hi Mark, My monitor is a Dell U2711 wide gamut. The profile is the last one I created, close to the Adobe RGB.
  5. Hello, the use of .8bf files is the reason for being compatible with Photoshop plugins. That said, launching the .exe would not be heretical, that's what Lightroom does ...
  6. Hi IndigoMoon, Thanks for the link but the macro does not work with the latest version of AF Photo. The real problem is that of colors.
  7. Hi, I seem to see a difference in behavior of Viveza when called from AF or PS. It is true that when the image is 100%, the colors are good but it is no longer usable, while everything is fine when the call is made from PS. In addition, I noticed the appearance of a button "Brush" when Viveza is called from PS, button that does not appear when the call is made from AF. How to explain this difference in behavior? (In the screencopy of PS, the image is without cross processing ...)
  8. Hi, the issue of colour profile is well fixed for DFine 2 (many thanks for that!), but it still does not work for Viveza 2.
  9. Hi, at home, no Affinity software is listed ... (C1 12.1.1, Win 10 updated)
  10. I tested with afphoto and tiff files. Jpeg is 8bits, I did not have time to test other bit depths. I have to do it ... I now remember having tested a few years ago Paintshop Photo X6 which presented different renderings of the same image in 8 and 16 bits!
  11. Hi, Unfortunately! There is no change. In the Nik suite, only Color Efex 4 and Analog Efex 2 work well. I presume you only work in sRGB ...
  12. Hi, I use an old version of FastPictureViewer WIC odec Pack 1.67 (the last free version) and AF Photo works fine.
  13. Hi, Of course, not all plugins work. But, in the suite Nik by DxO with W10, Analog Efex 2 and Color Efex 4 work well with a good color management. HDR Efex responds to a different calling sequence (with PS, it's available in the automation menu!) and does not work effectively but without freezing AF Photo. The other Nik plugins work with the color problem. In addition, DxO Viewpoint and Filmpack plugins cause a shutdown without error message and Portrait Pro freezes AF Photo without shutdown. I have not tested other plugins.
  14. Hi Chris B, Mark's reply is explicitly about color management when going into plugins. This issue is still pending (except Analog Efex 2 and Color Efex 4). But here it's about plugin not working anymore or not. It's not the same thing. This also includes the DxO Viewpoint and FilmPack plugins that cause a crash without error message.
  15. Sorry, but a zoom factor of 33% or more does not solve the problem. On this screencopy, the zoom at 50% remains the same as what I showed above and the zoom to 100% gives what you see there! I do not think it's good ... I also trust that Affinity will find the solution.
  16. @Asser82, a printscreen copy is always without profile. You have to assign one profil at openning.
  17. Hi Mark and thanks, DxO support is usually very responsive, and as a developer, it should make things easier. I'm currently rebuilding a new PC, I will not be able to test before 2 or 3 days ... (Sorry, I do not only that)
  18. I confirm this issue with a TIFF file in sRGB and Prostar RGB within Viveza 2 : Strangely, it's correct within ColorEfex 4 ...
  19. @Mark For this test, my image is developed in Affinity Photo with Prostar (same gamut as ProPhoto and TRC L*) as output color space, then reloaded in persona module for applying filters. In this case, is the profile embedded in the "afphoto" file when he is saved ? You say that you have tested viveza 2 with an ok result, how explain my second screencopy ? My two monitors are wide gamut and correctly calibrated in L*. My usual wokflow is: development in Capture One Pro then passage in PS for corrections and filters that C1 can't do. In this cases, all works correctly.
  20. Hi Mark, Like WMax70, it works well with ColorEfex 4, but it still does not work with DFine 2 and Viveza 2 ... (file in ProPhoto)
×
×
  • Create New...

Important Information

Terms of Use | 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.