Skip to main content

REAL system requirements for on1 2024 RAW

Answered

Comments

15 comments

  • Keith Neff

    First, don't be alarmed, your system may be just fine.  I've been running 2024 for a while now and there could still be an issue now and then.  When it is running does everything seem good?  16 gig works fine, if your video card worked well with 2023 it should also work with 24.  Keep at it and see how it goes.

    0
  • Iain Sloan

    Same here just closed no reason 3 times now hopefully it will be sorted soon

     

    0
  • Brian Lawson Community moderator

    I believe there is a memory leak in the Keyword AI process which gets kicked off in the background when you launch the program. When first run 2024 will start scanning ALL your Cataloged photos again looking for new useless (IMO) keywords you'll just have to remove later. Once that process has finished doing its thing the crashing stopped on my system.

    The crashes can happen at any time while browsing or editing or even while it is just sitting there running but not being used.

    0
  • Keith Neff

    I'm with you on that Brian.  When Keyword AI came out as a standalone program I tried using it and it would hang and crash frequently and, like you said, seems to be memory related.

    0
  • NaturalEnquirer

    I had not noticed that it was adding AI keywords. Is there no way to turn that off?

     

    0
  • NaturalEnquirer

    BTW, I don't feel that my original setup questions have been answered yet.

    0
  • Adalberto Hernanddez

    Well, my ON1 Photo RAW MAX 2024 won't past the first screen when trying to display the thumbnails of the default folder, it just crashes.  My system configuration is:

    DELL Precision Workstation 7720

    Processor: Intel(R) Xeon(R) CPU E3-1535M v6 @ 3.10GHz   3.10 GHz 4.20 GHz max turbo. (4 cores and 8 threads, 8MB cache and 8GT/s bus speed)
    Installed RAM: 64GB
    OS Version: Windows 11 64bit
    Display Adapter: NVIDIA Quadro P5000, 16GB RAM (none shared) With latest driver (10/26/2023) from manufacturer. DirectX 12, DirectML and WinML capable according to manufacturer.
    Installed on: 1TB SSD Drive with more than 50% free space

    I guess I have to wait until next bug free release...

    1
  • Brian Lawson Community moderator

    Adalberto, it is my opinion that there is a memory in the Keyword AI process which gets kicked off in the background whenever the program is launched. I reported this during testing. Memory usage would climb until there was none left and the program would crash regardless of what it was doing — browsing, editing, just sitting there running in the background. Once that process finally finished the crashing problems stopped.

    0
  • Brian Lawson Community moderator

    NE, I'm not a Windows expert anymore so I don't feel qualified to answer your hardware concerns as well as some of the Widows folks around here.

    As for the Video Card Strength slider, I keep mine at 100% unless I need to change it temporarily. The GPU is used for both rendering our edits onto the screen and for tracking the mouse movements while brushing mask and moving the image around when viewed at a size larger than the screen. That slider controls how much time the GPU spends on each task. Moving it to the left gives more weight to tracking movements; moving it to the right means faster, better quality rendering at the expense of possibly lagging or event stuttering brush movements.

    The company recommend leaving the Processor setting at Auto letting the program decide based upon the hardware in use.

    HOT TOPIC : Changing AI Processor Preference Can Cause AI Models to Fail to Produce Results

    It does appear to me that you've got it configured properly.

    1
  • Adalberto Hernanddez

    Thanks Brian,

    Then is safe to say anytime soon the folks at development will come out with a fix to that Keyword AI memory issue. I wonder if it could be a way to temporarily disable beforehand some of the AI features such as Keyword AI which is not essential for a typical workflow.

    I will be patiently waiting for this update.

    Best!

    0
  • christophe ducrocq

    Hi
    I would recommand 32 GB RAM instead of 16. My memory usage raised from 6 to nearly 11GB only by displaying a 45 Mpix image and going to 100% view in Browse.
    During AI initial Keyword scan, it took more than 10 GB the whole time (would say around 15). Quite memory intensive.
    Next plan for me will be to replace my "old " ryzen 2700x by a brand new 14xxx (still hesitating between 600/700 or 900, but new 14700 has 4 more cores vs 13700 ) cpu, with 64 GB (for the future) since I noticed on 2023 that  the more you have cpu cores the faster it reacts (despite bettering from 2023 version, it is still too slow for culling in 2024 with my configurtaion). To give an idea, aroud 10 to 15 seconds to show a picture in full screen for Browse 2023, now up and around 5 seconds in 2024 (way better but varies depending if you already applied some settings).
    Comparing with browse 2023 on a laptop with I7 12800HX (24 Core 8x2+ 8 Ecores)+3070ti and 32 GB , displaying was instantaneous.
    Best regards.

    1
  • NaturalEnquirer

    Thank you for your comments Chris.

    One change I just made which actually did make a marked difference in my case was to disable the paging file and then re-enable it. It actually made a difference in my case. I expect my paging file had gotten fragmented over time and needed refreshing.

    If you have a Windows 10 system (I'm sure it's similar in Windows 11) and want to try this, it may or may not improve your performance, but you have nothing to lose by trying this:

    • Go to Advanced System Settings: Type in Advanced System Settings in Windows search and select "View Advanced System Settings" OR right click on This PC, select properties, scroll down to and select Advanced System Settings
    • Select the Advanced Tab.
    • Select Performance Settings box.
    • Select Advanced Tab.
    • Select Change Virtual Memory.
    • Uncheck Automatically manage paging file size for all drives (make a note of your current settings just in case)
    • Select OK and close out all the dialog boxes.
    • Reboot.
    • Go back to the Virtual memory page and Check Automatically manage paging file size for all drives again.
    • Say Ok and close the dialog boxes and reboot one more time.

    Hope this helps at least one other user.

    0
  • Adalberto Hernanddez

    I want to share with you all how I solved my problem with ON1 Photo RAW MAX 2024. I realized that I had installed the New Features Branch driver from NVIDIA, which is experimental and unstable. Therefore, I uninstalled everything, including the ON1 Application Manager, and downloaded the Trial version of MAX 2024 again. Then I installed the Production Branch driver from NVIDIA, which was newer in release date and more reliable (although it is older in version number thab the one from the New Features Branch). Now ON1 Photo RAW MAX 2024 works fine, even with multiple files open in Photoshop (as a plugin), and also standalone.

    I hope this helps anyone who has a similar issue.

    1
  • Brian Lawson Community moderator

    Adalberto, I can't say how long it will take to get them fixed. I imagine it is a pretty high priority as crashes are never a good thing. There are settings now to disable KAI but they are not working. Rick just posted a topic here not too long ago showing them all.

    Thanks for sharing your find.

    0
  • NaturalEnquirer

    UPDATE: I am happy to report that on1 2024 is finally working (with occasional glitches) as it should on my existing system although it probably is pushing the limits of my system. It is actually cataloging the files and previews. Yea!

    I have finally sorted out why on1 was crawling and non-responsive on my system. My case is unlikely to affect anyone else, but I mention it here just in case.

    In order to access a Lightroom catalog on a network drive per article at https://github.com/kgorlen/lightroom, I had created a symlink to a network directory and had created a junction link to that network directory. Worked fine for Lightroom, but it caused havoc with on1. Once I deleted the symlink and junction link, on1 was back to normal.

    Thanks to all for your suggestions.

    0

Please sign in to leave a comment.