Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Claudio60

Members
  • Posts

    147
  • Joined

  • Last visited

Posts posted by Claudio60

  1. 2 hours ago, Chris B said:

    Quick update - the slow raw loading is due to us applying noise reduction on open as opposed to doing it after the raw has opened. This will be reversed.

    Tks Chris, I already noticed it and reported in my previous post, see: 

     

     

    but raw loading time is still doubled compared to v1 even with noise reduction set to off in develop assistant. Any ideas?

  2. Hi all, I'm evaluating AP v2 (trial mode) for eventually upgrade and I noticed that opening a raw file (.orf) takes from 13 to 16 sec. in V2  and only 3-4  sec. in V1 (hardware  acceleration OFF in both AP versions); my old Alienware notebook  is running win 10 21h2, i7-3610QM, 12gb ram, crucial m500 sd, radeon 7970m 2gb with no hardware acceleration capability  and no chance  to update the drivers as my graphic card is not more  supported by AMD.   Any ideas about this poor  performance?

     

    I made the same test on my Surface pro 7+ with i5, 8gb ram, Iris xe, win 11 21h2 and with this machine there's only a  little  difference between v1 and v2 when opening a raw file (hardware acceleration ON); is it something changed in the raw engine? Because the very poor performance that I have with v2 is limited only when opening raw files and not jpeg.

     

  3. 11 minutes ago, R C-R said:

    On my Mac, I can duplicate that if in the Develop Assistant I change the Tone curve setting from Apply tone curve to Take no action.

    If I leave it set to apply the curve I get the same result as @v_kyr posted.

    You are right, on my pc the tone curve setting was set to take no action, changed the setting to apply tone curve reveals all the details and contrast of the photo.

  4. 1 hour ago, wolboe said:

    Danke für den Hinweis – aber ich bin kein Profi und habe Bedenken, dass der Intel-Originaltreiber mit dem Chipsatz des Herstellers nicht richtig arbeitet.

     

    Thanks for pointing this out - but I'm not a professional and I am concerned that the original Intel driver will not work properly with the manufacturer's chipset.

    Wolfgang

     

    👍

  5. 2 hours ago, wolboe said:

    Hello Alan,

    Danke für den Link, hat aber bei mir nicht funktioniert, weil mein Treiber die Hersteller-Version und nicht direkt  Intel kommt.

    Thanks for the link, but it didn't work for me because my driver comes from the manufacturer's version and not directly from Intel.

     

    Wolfgang

    Original Intel DCH drivers can't install over OEM drivers if the OEM drivers are old and not "signed/certified/WHQL"  (you'll get an error); if this is your problem first you have to uninstall all Intel drivers related to your graphic card until you see "Microsoft Basic Display Adapter" in device manager, reboot, then install the latest Intel drivers from their web site. Hope it helps

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.