SLOW User Interface in Windows 10 on GTX1060 6GB Xeon 4GHz
The whole reason for migrating to ON1 RAW is to speed up my workflow from LightRoom.
Unfortunately On1 is very slow... even on my NVidia GTX 1060 with 6GB and a xeon cpu running at 4Ghz.
Can anyone help or I just need to give up and get my refund?
btw: This article didn't help https://on1help.zendesk.com/hc/en-us/articles/115000138471-How-to-Update-Video-Card-Driver-and-Set-Default-GPU-Open-GL-3-3-Error-Windows-Only-
Can I suggest to move this statement to the top of the article??? There was no reason for me to go through this whole article to find out it doen't apply to me.
"Windows machines that have both a dedicated GPU (from AMD or NVIDIA) and the built in Intel Graphics are the only machines that need to be configured to run off of one GPU."
The post in General Discussions “Setting up ON1PR 2019/2018 to used NVIDIA Graphic Card” may help0
I wasn't able to locate this post through the search function... do you have a link?0
I believe the link is located in the initial post above0
In the category of "it can't hurt", I would update my nVidia drivers to the Nov. 2018 release. I mention this as I had another newly released GPU-heavy application that failed without user intervention that was fixed by updating the nVidia driver.
A side note, "windows update" reports "all drivers up to date" and does not find this driver. Instead, you need to manually go to directly to the nVidia website.0
I have a very similar problem to you with a very similar spec machine.
I wish I knew what the magic was to fix it. If there is indeed any magic0
If you install the NVIDIA GeForce Experience app (along with the NVIDIA Control Panel), it will monitor for NVidia driver updates and put a little exclamation mark next to it's icon on the right side of the Windows taskbar.
This will always keep you notified on updates and they do come out about once a month or so. I have never had an NVidia driver update cause any problems. Ever.0
I guess maybe I should have been more clear ....
I tried upgrading the drive and doing the things in that first article.
It doesn't help.
the UI is still slow, too slow to use. Something is very wrong.0
I am now apparently in the same place. I have been running 2019 since it was officially released on a Nvidia 1080. No problems. Until today. And today I installed the DXO Nik Collection (over top of the Google free addition). I also downloaded about 180 photos into a new subdirectory in my catalog.
Now my machine goes into "total consumption of all resources" for 5 to 6 seconds at a time. No mouse movement, no taskbar updates, etc. I am moving and reseting all of the ON1 cache and scratch files now. At one point I believe it overheated my CPU and did a Hard reboot.0
Is it updating catalogs on those 180 photos?0
It was. I have been trying to determine what is beating the machine to death. I changed from Accurate to Fast. I had a common preset on all of them. That is where I suspect the problem was. All of them being updated to accurate with the presets. I reset the presets. I have changed the system usage to 40%, I have set the priority to Low and that seemed to help a lot too. No mouse movement is a sure sign of a program running wild.
I am going to undo things slowly and see what happens.0
Well, my problem seems to have gone away. So here is what I did...
I had the task manager up.
I opened up a catalog directory where I had put 130 (24MB each) photos. I had applied a preset to all images. There is about 5 filters and a LUT in the preset. I had the browse view set to largest so I was getting 3 image in each row. I would scroll down a couple of rows and the machine would freeze for 5, 6 7 seconds. No mouse trails, no task manager updates. It would unfreeze for a 1/2 second and I could get a mouse trail, then it would freeze for another 3 to 4 seconds. Finally after that it would become normal. ON1 was still running in the high 90% of all 6 cores. But I had multi-tasking.
I would then scroll down some more in browse, maybe a few rows and it would happen again. Same symptoms.
I am pretty sure the catalog was being updated during all of this and it took awhile.
So I did the following:
I reset all of the images to clear the preset. I lowered the system resource sliders in ON1 down from 60% to 40%. I reset, emptied and moved the cache and scratch folders. I use SSDs with one SSD dedicated to the cache and one to the scratch folder. I have evme drives for the OP sys drive and another evme for my images. I switched the raw preview from accurate down to fast. I used the task manager to set the ON1 PR executing priority down to LOW.
At some point the catalog update finished.
ON1 ran normally (which is not saying a whole lot, but more than usable for me)
So I undid all of the things I did, except I left the cache and scratch folder where they were, as they ended up in clean folders on the SSDs.
So for whatever all that is worth, at least it gives a list of things to try for those of you who cannot get your 2019 ON1 running in a usable condition.0
The catalogs are still a pain when they update. After my On1 reinstall earlier this week and rebuilding catalogs I had the same problem. That's why I was using Process Lasso that I mentioned in the other thread. It kept On1 from maxing the CPU so that I could still use the PC while the catalogs rebuilt.0
I can appreciate that. I saw that bit about Lasso, but since I had not seen this sort of lockdown... I know it took well over 12 hours to build the catalogs when I first installed 2019. But I let it run overnight and just ignored it.
I suspect that as long as you do not attempt to actually do anything in ON1 while the catalogs are being built, you may not need Lasso. At least I did not see the lockdown until I tried to make ON1 multitask itself.0
Well, on my PC when catalogs are building and CPU is maxed I can't do anything else. I can't use a browser properly, cursor freezing sometimes the screen goes blank for a minute or two. It's not pretty.0
Those are the exact same symptoms I also posted in a different thread. It seems that this is becoming fairly common with PR2019. The difference in my case is that I am not building any catalogs and my GPU is only a 2gb GFX 860M. In my case the computer will basically lock up for several minutes at a time with 90-100% cpu and 10+gb ram being used. I think my issue is related to trying to build previews for tier 2 raw files (unfixed bug from PR2018). Haven't heard back from support lately with anything new to try. Hopefully they will come out with some patches soon.0
Update... Process Lasso was installed and I see that it is throttling back ON1 PR at times. However, it has not solved my horrendous lockdown. I did see the screen go completely black on both of my monitors today as well as all mouse movement. In the process I actually used Task Manager to set ON1 PR's priority all the way down to Low and that did nothing. I even set the affinity. I tried half of the 12 processors (on my machine), just a couple of processors, the first half, the second half. All that did was allow me to actually move my mouse when things lockdown. But the mouse was moving in an extremely jittery fashion and nothing else worked. No browsing, nothing. I told Lasso to throttle down I/O. Nothing.
I even started ON1 PR from the cmd line with only 4 processors, thinking that perhaps they do something on program startup and it screws with the affinity changing. Starting it with only 4 processors did the same jittery mouse thing and was a waste of time. So whatever ON1 is doing, they are doing it extremely badly.
The only time I really noticed the lockdown was when I was working in a directory that had 130 images. If I scrolled down in browse with 3 images in each row, it would always go into lockdown after a few rows. So I decided to set the image sizes in browse to the smallest possible. OMG, I could have taken a two hour nap. I hit the ALT/F4 key (which is a program exit) and waited for ON1 to see that and shut itself down. That was horrible.
So then I decided to break the catalog directory into two directories. I put half of the images in each. That was SO MUCH BETTER. I could not believe it. There was a small lockdown, but only for a few seconds. and only once in each directory.
Lets hope they are on top of this problem and as Peter said, come out with some patches soon.0
Although my system is working... OK... the idea of better performance always triggers my OCD.
I started poking around in the manual section about preferences and saw this:
Preferences > System > scratch folder location >
"This setting lets you move or reset your memory cache, which helps speed editing operations while you’re running Photo RAW. This is helpful if your system drive has limited space and wish to use a faster external drive as a cache. This cache information is purged each time you quit the application."
I focused in on "...helps speed editing operations..."... it also says it is purged each time you quit the application..."
It got me to thinking about what happens if the application dies instead of a graceful close... I was hoping the application may clear the directory when the program is first opened. Well... mine wasn't cleared. This seems to suggest there may be leftover vestiges that may interfere with On1 (although, I have no way to know for sure)
So I did 2 things... I manually cleared the directory... Further, I did not like the default location in the programs directory , so I moved it to a location that does not need admin access (I created "C:\temp\On1_usercache").
YMMV, but it seemed to make things a little smoother for me.0
Kevin, changing the affinity and priority didn't help me either, but lasso did keep my PC from locking.
BTW, in a few days Lasso will start giving you nags to register. It will still run for free, but you have to close the window each time.0
quick question guys,
how long it takes for you to load a raw file? i have i7 cpu with 16gb of ram and gtx, ssd cache
d800 files, to load 1 raw is 5-6 seconds
d610 files around 4 seconds
and the pain is when i export, around 3-4 images per minute
other then that i like this software alot, but still is so slow0
A 14 bit D610 file opens in Develop module in 3-4 seconds for me. A D300s 14 bit raw opens in 1-2 seconds. 12 bit D610 files are a different story - they take 10-12 seconds - I assume because they are defaulting to the tier 2 raw engine.
An export from either 12bit or 14bit D610 raw with only Develop adjustments and most export options (resize, watermark, jpg/100%, etc) included takes about 15-20 seconds0
why i don`t understand, if indeed it uses the gpu, why only 10%? i am curios if someone has i9 processor or amd ryzen treadripper what times have....
overall is slow, lightroom took around 3-4 second to export one image :~(0
also, i noticed just now, when i switch from current image to the next image, the processor load is average, when it could be 90% is just around 20-30%, if somehow this could be increased i think the load times will be shorter!0
Machine: Similar configuration to Sebatian
D500 and D810 files; RAW file from Browse to Edit
The second time viewing the file; Less than what I can manage to click the start/stop on the stopwatch.
The first time viewing the file; maybe 1 a second; I think it takes time to write the first On1 file and cache the image.
Across the network, maybe 2-3
I also like to work with TIFs (~120M), maybe 1-2 seconds (seems to load in two steps)
3-4 per minute if I export TIFFs from .onone to a local drive that is also doing cloud backups
4-7 per minute if I export JPGs from RAW files to a location on local drive that is not cloud enabled
FWIW, I too find this a bit slow as compared to other tools.0
i made more inspections, and it seems this software is doing the basic conversion very slow, for example if i load with capture nx a raw file is much faster then with this software, i really like this software for what it has to offer, but the performance of it makes me wonder if i should make a step back, on the long run i will be very pissed if i need to wait such long times :(
too bad because the ability to stack luts is really unique in photo realm
few more days and i will know if i jump ship (again)
This has helped me a little bit.
Not solved it all but has helped.0
nice ideea i will try it Jeremu, meanwhile, i noticed if u convert to raw, resize a bit like 20mp, load times are 2seconds with effects on from 6-7seconds, i check your post now come back with results0
That method seems that have some improvement 10%-15%! great find Jeremy
(Regarding that tutorial the only important thing after u made all that u need to start the scrip from performance monitor window, which he did not mentioned)0
Take a look here and see if this post has anything in it that helps. Especially the catalog removal part. I have already submitted a ticket.
For me the issue with the software is that is very slow working with raw files, i changed my workflow as this:
capture nx convert to 16bit tiff with a flat curve, then i process the files with on1 pro, speed is much better, for the moment i am happy like this0
Please sign in to leave a comment.