Adding to catalog never completes and causes Develop and Effects to be very slow even with very low CPU usage
A few weeks ago I put a note into one of the other forums discussing problems with On1 performance on my Dell Latitude E7440 after cataloging had been turned on. I was advised to contact technical support which I did. I've had three exchanges that didn't resolve my problem and only provided me with canned answers asking for my system configuration, suggesting I download the latest release, and to verify that I was running the most recent OS and video drivers.
Last night I decided to catalog the same directories but on my desktop system. This is a powerful desktop system built on an i7 processor with 16 cores, 28 GPUs, 32 GB of memory, and two professional grade Samsung SSDs. I'm also using a NVIDIA GeForce GTX 1060 GB card driving a Dell monitor at 3840 x 2160. All drivers are up to date.
I am currently running On1 Photo RAW 2018.5 (12.5.3.5757) on a Windows 10 Pro 64 Bit Windows System. Up until last night I was editing and rating the photos from my trip using directories (no catalogs). On1's performance was great. I could switch from image to image with no delay. If I went into Develop or Effects masking tools were completely fluid. Panning/zooming was also fluid. with no lag time.
Last night after I finished an editing session, I decided to Catalog the two top level directories containing photos of my trips to Germany and Switzerland. After an hour On1 reported that the catalog operation was 99% done. There was one directory remaining that was showing 95% complete. This directory contains 12 images. I left the system running and went to bed.
This morning I sat down to my computer and can see that On1 is still at 99% complete and 95% complete on the same directory. I iconified On1 and sat down to browse the web using Chrome. My system was working as expected (which is a good sign - On1 was only using 5-7% of my CPU). After an hour I opened On1 again to see the exact same 99%/95% complete status in the catalog. I opened one of the directories (not being cataloged) and started editing two photos:
1) Opening the photos was very slow. Panning around the photo encountered 3-5 second delays.
2) Turning already created Effects adjustments on/off also encountered delays.
3) I then opened another image and decided I needed to use the masking bug to darken an overcast sky. The masking bug was almost unusable. I then switched to a bush and tried to mask areas in/out. The mask was 3-5 seconds delayed behind my mouse strokes. This went on for 15 minutes until I gave up.
I tried exiting and re-starting On1 figuring it might be a memory leak, hung thread, etc. There was no change in performance.
The only operation that appears to run quickly is the browse module when I filter using the catalog. Selecting all images in the catalog that meet a given star or color criteria is fast. As I said earlier, if I try to drill in to any of the images that's when things slow down.
At no time did my Process Explorer ever register more than about 10% usage so something inside On1 is causing the delay. Any idea what's going on?
As I said in my earlier post in the general forum and in my emails back/forth with technical support. I am a Software Engineering Manager with many years of experience. I will be GLAD to help you debug this problem. Just tell me what logs, etc you need. I like On1 and want to see you and your team succeed. There is something wrong here that needs to be fixed.
I plan to leave On1 open/running for another 3-4 hours to see if it finally completes the catalog operation. If things don't improve I plan to delete the catalogs again in order to make On1 usable. I need to complete my photo editing this weekend so I can show pictures of our trip to my family next weekend.
I had hoped to use the Catalog feature to help me work on the final ratings to break my photos into small logical groupings that could be extracted and shown to family / friends.
Steve Munyan
-
Steve, I've had this exact problem since Christmas but the .5 update seems to have fixed it for me. My catalogs never seem to finish either, but it's not slowing anything down any more. I'd want to know how many photos you're cataloging. I have about 40,000 and my PC is 1/2 as fast as yours. i had to manually make sure the GPU was being used for On1. I've heard from a few others that their problem was one or more corrupt photos messing up the catalog, but only the support team would know that by checking the logs. I suggest you get back to James with a copy of a new log taken after these problems and see if there is anything new.
0 -
I'll be glad to provide a copy of the directory with all 12 files and the side car files along with the log. I'll zip the files and upload them to my OneDrive directory, and send a pointer to James. It has now been 4 hours. On1 is still stuck in the same place, and still consuming 3-7% of the CPU. Nothing appears to be happening. Time to head out and enjoy the sunshine. I'll upload the files when I get back.
0 -
Sounds like a good plan, let us know how it turns out.
0 -
This evening it looks like On1 finally finished processing that directory. It is now 10 pm east coast time and the catalog is no longer showing 99%/95%. I'm uploading the log and directory to support. Hopefully they can figure out what is going on.
0 -
I won't ever use the "Catalog Folders" feature again unless I actually have a spare computer to test it on first. I went through almost 6 weeks of pure hell, one problem after another, re-install after another......and finally started fresh with no cataloging and this latest 5757 build update and everything is now working mostly smoothly.
The only thing different is I'm not using the cataloging feature.....I'm not even going try using it with this latest update now that I've got things working half way decent.
I'm convinced the catalog feature was the cause of most of my problems the last 6 weeks or so.....
0 -
This morning I booted my system and started On1. The Catalog area is now showing 99%/95% complete again and is stuck on the same directory. Last night I sent a pointer to the zip file to support. Let me know if there is anything else I can do to help you analyze/solve the problem.
0 -
Stephen, the catalogs will always be checking to keep themselves up to date. Even if it gets to 100% it will continue to look for changes and show that it's still working. Right now both of my catalogs are sitting at 99% just as they always do (As I'm typing this, they just switched to 49% and 28% for a few seconds and now back at 99% again).
0 -
Understood. If On1 was moving between directories your comment makes sense. It is now 3:48 pm. On1 is still stuck on the same directory containing 12 images. I think your original theory about On1 getting stuck on a corrupt file is the true culprit.
0 -
Stephen, if that is what you suspect and there are only 12 photos, why don't you move them all out of that folder and see if catalog finishes on an empty folder. If it does, add them back one at a time to see where the problem occurs.
0 -
A couple of things I have noted on the catalog updating thing...
If you have a lot of directories, ON1 does not always put up the progress clock next the the folder unless that directory is put up somewhere on the display. So even though you think it is working on only one directory, it may actually be working on many others at the same time.
Sometimes, particularly when it is sitting at 99% at the top level directory, ON1 never removes this progress clock. At least until you shut it down and start it back up again. Like it is a refresh issue and it just forgets.
A year or two ago, on a much slower hard drive, I could never get it to complete. I would leave it running for several days in a row. I just gave up on that. That was back in ON PR 2017.
If I suspect a corrupt file or something, I will simply reset the browse cache, or empty it.
I have also found that ON1 will go thru ALL of the files in your catalog when you enable the "Apply Lens Correction Automatically to Raw Photos". This can take a long time, but it does pop up and tell you about photos it thinks are corrupt. If you do this and it finds a corrupt file, keep an eye on the disk space on your system drive, or wherever you have the scratch folder set, as I believe there IS a memory leak and two different times ON1 has filled up that drive while still processing. Fortunately, exiting ON1 or resetting the scratch folder location will clear up whatever huge file it has created.
0 -
BTW, I do not use "Apply Lens Correction Automatically to Raw photos", because I think it adds a lot of data to the scratch folder and I have some issues how I think ON1 should deal with some focal lengths on at least one of my lenses. I believe that this Apply Lens Correction is simply for the thumbnails in Browse anyway.
0 -
Sorry, I'm behind reading the forum. It was a busy week. I didn't try removing the files from the directory. I suspect that the corrupt file idea I correct. I created a ticket and uploaded my files for support. I'm waiting to hear back.
0
Please sign in to leave a comment.
Comments
12 comments