Rotate cursor missing - also delays in updating Lightroom migrated images
Sorry to lump these together; I'll separate them into different posts if necessary, but they're both kind of small things. As I noted in my last post, I've migrated my Lightroom catalog and am in the process of cleaning up the settings and workflow in Photo RAW. The workaround to fix photos which are not editable has worked flawlessly; thanks again to those who walked me through the process of solving this. So far, everything is going well but I've seen a couple of things which have slowed me down a little:
The Rotate cursor in Develop sometimes disappears when I select Crop mode. You can still rotate the image by placing the mouse in approximately the right spot outside the crop rectangle and clicking, but the cursor never changes - so you have to estimate where the hot spot is. The only way I've been able to restore it is to quit the app and restart. Switching to Browse and back doesn't fix it. Just an annoyance, but it seems like a bug. I'm running OS 10.13.6 and my graphics card is fully supported by the OS.
Also, I have migrated many thousands of Lightroom edited images. The good news is that if the edits were processed at all, they seem to work very well and maintain the non-destructive state properly. However, even though I waited carefully till the migration was totally done in Lightroom before quitting it, I still have a lot of images which retain the little "LR" tag in Photo RAW. Browsing to the folder and letting the Photo RAW app "sit" there for a while, I see the photos start to update with LR edits and cropping; selecting one of the photos also forces the update. I had thought this might be a background process, but it only seems to affect the current folder. CPU usage eventually drops dramatically, but there doesn't appear to be any processing going on. Switching to a different folder kick starts the process and ramps up CPU usage again. Am I going to have to select the folders one at a time to finish the migration? These folders are cataloged by Photo RAW already as far as I can tell, but they don't seem to have fully processed somehow.
-
I have to refer you to tech support on this. I don't have Lightroom so I can't speak to the migration process or any possible problems with it.
The rotation cursor is sensitive to where you have the pointer located and to the crop you've chosen. I'm currently looking at an image I've cropped with the Freeform option. The crop fills the image horizontally but I've brought it in from the top and bottom. Along the top/bottom edges I see the rotation pointer as long as I'm close the to crop marks and outside of them. Along the left/right edges I have to be a little further out from the crop marks or it won't show.
0 -
I will probably submit tech support requests on both. The cursor just doesn't appear, whether I'm a few pixels away from the edge or a hundred or so, on any of the 4 sides. It doesn't matter whether I've already resized the crop rectangle or not. Nevertheless, Photo RAW recognizes my cursor position, as when I put it in the right area, I can easily rotate the image by clicking and dragging. Even then, the cursor doesn't change. The "right area" on my 27" screen is about 20-30 pixels outside the crop rectangle and is repeatable whether the rotate cursor is displayed or not.
The hardest thing about this will be figuring out what triggers the behavior; it's worked for an hour at a stretch with no problems, and failed rather soon on other edit sessions...
0 -
I've seen some other weird cursor behavior at times too. Sometimes the proper tool cursor isn't shown, others it is but the regular mouse pointer is superimposed over it making it very hard to use with small brushes. So far I haven't found any particular trigger either. For now I'm assuming it may have something to do with running under Rosetta emulation.
0 -
I've submitted a support request for that one. I am running an Intel-based machine under 10.13.6 so in my case it's surely not an emulation issue. I will try it on my Mojave testing machine as a sanity check as well.
I'm doing more testing on the Lightroom migrate thing, but will probably submit another request tomorrow if I can't sort it out.
0 -
I've always had problems getting the cursor arrows to light up using crop mode, the hot spots must be really tiny, but as you say the rotate cursor symbol is very hit and miss but appears to operate anyway. Be good if it were improved.
0 -
I entered a support request about the cursor and got a prompt reply. Unfortunately, their suggestions haven't gotten me any closer to the solution. One of them required restarting the app, which always clears the problem temporarily, so I'm waiting for it to recur (or not) before I can follow up. One thing I noted before quitting the app was that the cursor just doesn't change at all; in other words, I don't even get the magnify cursor when that should be active. It stays with the pointer no matter what mode I'm in. That seems to be to be a real issue; unfortunately, now I have to wait for it to start happening again before I can do more problem isolation.
I did take time to figure out where the "hot spot" was, and on my monitor it seems to be from roughly 20-80 pixels outside the crop rectangle, all the way around, so it's not too hard to hit without a visual cue. Just annoying.
The migrate/process issue is still bugging me but I'm not quite ready to submit a detailed request yet; I'm still gathering info. It seems to randomly update the edits on individual photos while it's running. Sometimes it will chatter away in the background updating who knows what for hours (verified by Activity Monitor showing lots of CPU and disk on Photo RAW); then it will stop and go back to an idle state. Once it pauses, it's completely idle (often for hours) until I switch folders, and then it starts thrashing the disk again.
Leaving a folder open in the browser or in Develop sometimes causes it to update photos inside the folder, and sometimes not. The only thing that will force the updates for sure is to select the photo in Develop mode, and within 10 seconds or so it will apply the edits and change the "LR" icon to the "+/-" icon. I really would rather not have to select each photo in my library and wait for each one. Mass selecting all the photos in a folder doesn't cause it to act on them. I'm not too bothered by this behavior, actually, because I don't often go back and re-edit older shoots; it's just that Photo RAW randomly spinning up and eating CPU slows down the app's response when I'm trying to edit new photos from the current round of shoots, and I don't see any benefits occurring.
0 -
Finally, 6 days after restarting the app, the cursor problem appeared again. As I thought, it locks the cursor into the arrow state, and nothing will change it to Text, Brushes, Magnify, or anything else. Quitting the app is the only thing I've found which restores proper cursor operation. Interestingly, when I choose a brush, the brush tip appears, but it's still at the end of the arrow cursor. I have followed up with ON1 support and provided additional data.
The Lightroom processing issue continues. Most of the time, I have to select the photo in Edit mode before it will update the settings/crop; but sometimes even that fails to cause the image to update. It changes the "LR" badge to a "+/-" badge but does not update the settings. It has, however, stopped eating CPU when sitting idle. I think I have enough data now to submit a support request on this, though it is far less bothersome than the cursor issue.
0 -
That's what I've seen too Greg. Things still work OK but it's a pain when you need precise placement and there are two different mouse pointers glommed together.
0 -
Support feels it's related to leaving the app running for an extended period:
Hello,
It sounds as though this issue is caused by a caching and RAM issue by leaving the program open too long.
We would recommend closing ON1 periodically to avoid this issue happening in the future.My interpretation of this is: memory leak. After 6 days (longer than I would usually leave an app open except when doing a migration) memory climbed to 25GB on a machine which has 32GB of physical RAM. I think this is probably a hint. Unlike Lightroom, Photo RAW only takes a minute to open or close, so this is an acceptable workaround - and frees up RAM periodically. Hopefully they'll address this in the future because it could affect other behaviors in the app.
0 -
I think it would be nice if On1 would release any un-needed memory when the program is minimized to the taskbar to allow other programs to use it. Maybe that data could be cached and read back when the program is maximized again.
0 -
I've suspected for some while that there is a memory leak associated with cataloguing, I may have mentioned it a couple of times. I'm in the habit of closing ON1 when I'm not editing or when things slow down, slow export is usually an indicator that the program needs resetting. Leaving it open for any length of time can ultimately lead to a freeze or crash.
0 -
Yeah, it's a mixed bag - eventually the disk thrashing stops, but other things slow down or stop too (apparently). After restarting the app I'm watching to see if the post-processing of Lightroom edits picks back up in the background.
0
Please sign in to leave a comment.
Comments
12 comments