• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

LRT user interface unresponsive

Offline
#1 jorn-t
Hi!

Started editing a new time lapse project and updated to 5.7 a couple of weeks ago. I'm experiencing heavy lag / unresponsive user interface.
Applies to 5.7.1 as well.

If I, for instance, try to edit the exposure of a key frame in LRTimelapse, I click/doble-click to edit a cell in the Exposure column, and often/almost every time, nothing happens!
And, when the edit field eventually turn up, it is not possible to drag/edit for a long time. Changing to a different timelapse sequence, often does not work either.
It is like the mouse clicks not are working half of the time. Dragging the slider on the visual previews, clicking the save button, what ever, half of the time nothing happens. Has to wait typically 10 seconds, and sometimes, the mouse clicks I did previously kicks in after all, often making unwanted things to happen.

Running Windows 10 on a intel i9-9900K, Asus Z390, 64 GB, M.2 system drive, 4x16 TB RAID-5 storage.

Could also be a problem with my setup, just recently upgraded Premiere, Lightroom, Bridge, Photoshop and so on to v. 2021, and then right after to v. 2022. But it feels like LRT 5.7.x has got a built in "onMouseClick() { justDoNothing(atLeastHalfOfTheTime); }
Just wanted to hear if others experience the same problems, before I reinstall everything..

Tested the new Lightroom masks a bit and that part seems to work perfectly.
"Select Sky" mask opens up a new world - works perfectly on stationary sequences, i.e. camera on a non-moving tripod.
Moving sequences (rotating, dolly, hyperlapse) I guess has to be treated the same way as before, with linear gradients?
Offline
#2 Gunther
Could you provide the log after the in responsiveness happens? Info menu / show log
Subscribe to: LRTimelapse Newsletter, Youtube Channel, Instagram, Facebook.
Offline
#3 jorn-t
Nothing unusual in the logfile as I can see. At least, nothing that indicates the problems I experience. Even trying to open the log file window, and scrolling up/down in that dialog, is unresponsive from time to time (I would say, most of the time).

LRTimelapse and some Adobe stuff is also drawing some CPU resources when idle, i.e. when finished rendering/loading/whatever. Not much, but 2-3% all the time, sometimes 10-20%.

If noone else are experiencing the same problems, I guess it could be a local problem after the last Adobe updates.. I could try a full reinstall of Windows and everything.

Code:
[2021-11-03 22:58:51] DEBUG: Pass 1 with 577 frames to deflicker.
[2021-11-03 23:02:54] DEBUG: Pass 2 with 550 frames to deflicker.
[2021-11-03 23:06:47] DEBUG: Pass 3 with 387 frames to deflicker.
[2021-11-03 23:09:33] DEBUG: Pass 4 with 249 frames to deflicker.
[2021-11-03 23:11:28] DEBUG: Pass 5 with 98 frames to deflicker.
[2021-11-03 23:32:07] INFO: --- Loading directory: G:\Timelapse\2019\2019_04_USA\2019_05_02_Black_Canyon_Gunnison\2019_05_03_Black_Canyon_Rock_Point_Pano
[2021-11-03 23:32:07] DEBUG: Loading sequence properties from G:\Timelapse\2019\2019_04_USA\2019_05_02_Black_Canyon_Gunnison\2019_05_03_Black_Canyon_Rock_Point_Pano\.lrt\lrtsequence.properties
[2021-11-03 23:32:07] WARN: Sequence properties-file not found.
[2021-11-03 23:32:07] ERROR: Could not create snapshot dir!
[2021-11-03 23:32:22] DEBUG: Finished loading XMP data in 15 sec.
[2021-11-03 23:32:22] DEBUG: NEF sequence with 382 images loaded.
[2021-11-03 23:32:22] DEBUG: Memory: [max|54144] [used|3203] [free|50941]
[2021-11-03 23:32:22] DEBUG: Buffer size for ExifTool: 38
[2021-11-03 23:32:32] DEBUG: Sequence shot in auto mode
[2021-11-03 23:32:32] DEBUG: Timestamp Data complete!
[2021-11-03 23:32:32] DEBUG: Sequence is new or was processed with LRT < 4.0
[2021-11-03 23:33:29] DEBUG: Done loading previews.
[2021-11-03 23:33:29] DEBUG: Memory: [max|54144] [used|4059] [free|50085]
[2021-11-04 12:20:31] INFO: Reloading XMP only...
[2021-11-04 12:20:31] DEBUG: Loading sequence properties from G:\Timelapse\2019\2019_04_USA\2019_05_02_Black_Canyon_Gunnison\2019_05_03_Black_Canyon_Rock_Point_Pano\.lrt\lrtsequence.properties
[2021-11-04 12:20:31] DEBUG: Detected a Masks 2.0 sequence.
[2021-11-04 12:20:37] DEBUG: Done loading previews.
[2021-11-04 12:20:37] DEBUG: Memory: [max|54144] [used|2337] [free|51807]
[2021-11-04 12:20:38] DEBUG: Buffer size for ExifTool: 38
[2021-11-04 12:20:48] DEBUG: Sequence shot in auto mode
[2021-11-04 12:20:50] DEBUG: Detected a Masks 2.0 sequence.
[2021-11-04 12:20:50] DEBUG: Checking and fixing XMP values
[2021-11-04 12:20:51] DEBUG: Done loading previews.
[2021-11-04 12:20:51] DEBUG: Memory: [max|54144] [used|3919] [free|50225]
[2021-11-04 12:20:52] DEBUG: Calculating Auto Transitions
[2021-11-04 12:20:52] DEBUG: Buffer size for ExifTool: 0
[2021-11-04 12:20:53] DEBUG: Sequence shot in auto mode
[2021-11-04 12:20:58] DEBUG: Successfully saved 382 XMP files.
[2021-11-04 12:24:28] DEBUG: Launched worker with 8 threads.
[2021-11-04 12:24:28] DEBUG: Starting multipass deflicker with 5 passes.
[2021-11-04 12:24:28] DEBUG: Pass 1 with 309 frames to deflicker.
[2021-11-04 12:26:26] DEBUG: Pass 2 with 293 frames to deflicker.
[2021-11-04 12:28:14] DEBUG: Pass 3 with 213 frames to deflicker.
[2021-11-04 12:29:26] DEBUG: Pass 4 with 150 frames to deflicker.
[2021-11-04 12:30:20] DEBUG: Pass 5 with 78 frames to deflicker.
Offline
#4 Gunther
So you are on Windows. Good to know...
It's not a problem others repirt, so I can only guess.
I'd try updating the graphics driver. Don't think, it has anything to do with the Adobe programs.
Please try and let me know.
Subscribe to: LRTimelapse Newsletter, Youtube Channel, Instagram, Facebook.
Offline
#5 Gunther
Since I didn't hear back, I'm moving this to General Questions.
Subscribe to: LRTimelapse Newsletter, Youtube Channel, Instagram, Facebook.

...also check out: