Blackmagic Forum

Yes, it starts up quicker but it still takes a long time to open the project database. All of it is not really a problem. However, I found that editing and playback on the very same project (originally created in 17.1) is much more sluggish. It literally takes nearly 1/2 of a second from a mouse click to action and playing back stalls consistently between clips processing a transition. With 17.1 (after removing and re-installing) everything is going smooth and fast again.

Is there a configuration change that I am missing?

Btw: I am running Windows 10 (latest) on a rather fast computer (14 core i9 overclocked 64Gb and Nvidia Titan xp all ultra fast solid state storage drives)

In my case from double clicking the Resolve desktop icon to the Project Manager opening is 9 seconds. From click open on a 22 minute project to it being fully open 13 seconds. I know that these timings are dependent on the number of projects in the database and their complexity. No problems with dissolves or response to mouse clicks, etc.
Have you checked the usual culprits like GPU driver version and whether a Windows update has changed the GPU setting to OpenCL rather than CUDA?

I'm seeing my startup times cut in half, with even snappier responses once the project is open.

Studio 17.2 for Windows.

Startup time is blazing fast here (to be fair, I didn`t mind having to wait 30 seconds for all subsystems to load and initialize before), funny enough quitting takes longer now, by about double.

Loading projects is pretty snappy, although I can`t say it was noticeably slow before.

Thor

Roamer105 wrote:It literally takes nearly 1/2 of a second from a mouse click to action and playing back stalls consistently between clips processing a transition. With 17.1 (after removing and re-installing) everything is going smooth and fast again.

Is there a configuration change that I am missing?

I think auto-save/"live save" is turned on by default now.

If your project file or database is on a slow drive, that could be what's causing delays every time you make a change.

I second Jason's diagnosis. Please check which databases the project manager lists - and whether they are on external or network drives.