So ... you're working with full 4k, not even UHD ... using the heaviest effect next to Warp, being Neat Video Noise Remover, and using RedGiant plugins/effects ... and your media files live on an external harddrive. Without proxies.
Right?
I mean, what could possibly cause a bit of lag/delay/"latency" there ... or perhaps realistically, disable the effects while doing 'editing' work such as trimming and such.
Frankly, I don't think I had any problems with moving in the timeline before, but now for some reason the timeline is responding to me late and if you pay attention, Honestly, I've been using Adobe programs for more than 10 years and I don't recall any zoom in and out delays with the timeline, which I've now learned has been fixed with the newer version. The issue here is not the playback problem. It is the late response of the timeline. I don't expect a 4K project to play in real time, but I think I should at least be able to easily perform operations on the interface.
There have always been 'hiccups' with a few users on about every version. Life Happens, I suppose, when trying to handle nearly every media/effect/workflow/delivery need possible on all hardware that might be used.
Resolve is going the same way, trying to mimic the Adobe suite at being one fit for everything. And along the way, gee, more bugs/stability/un-resolved issues have occurred. Who knew, right? (ha.)
Hoping that the little 'latency' you're getting is fixed with the new build. I do know from what others have posted that what ... 24.5 or something like that? ... had a number of lag/latency issues with several users. But not on my system, and when you can't replicate, well ... you can't always figure out what's the problem.
Hello. The problem is that the video is not understandable because I am not recording the reaction time after pressing the keyboard keys. I assure you that the timeline It is seriously slow when zooming in and out. As you know very well, these delays can be annoying in big projects. No, I haven't tried the Beta version, but I think I'll start using it.