What is Your Davinci Resolve Startup Time?

Hiii Guys!!!

What is your Davinci Resolve Startup Time (from double-clicking the Resolve icon to the opening of the Project Manager)?

I'm just curious.

And, are your startup times increasing or decreasing with each new version?

Thanks!

33 seconds. 16.2.6, windows 10.

Feels about the same for each version.

About 30 seconds here, with an SSD System drive.

Studio 16.3b2 for Windows

I have over 90 seconds with SSD system drive. It's been the same since I first experimented with 16 Beta last year, and hasn't really changed + or - although first impressions with 16.2.6 suggest slightly longer, almost 2 minutes

Hi Guys,

I should have given my startup numbers at the beginning of this topic. Sorry for that. My Resolve startup time to project manager is 57 seconds.

35 Seconds, but since I stopped using it for anything before I built this new computer (just installed it to have it there, for completion) the project, etc. database is empty.

On my laptop it takes about 8 more seconds, but that's a weaker machine.

Both have NVMe SSDs though (Samsung Evo Plus) for the OS and Applications (incl. Resolve Studio).

In any case, when I brought this up a while back, I was told that Resolve does a lot of things in the background when starting up. This is why the start-up time is long. The idea is probably "once you boot it, you shouldn't have to "reboot" it - barring an application or system crash/restart."

31 seconds on a 8 year old computer....

About 26 seconds, with NVMe system drive and separate NVMe Temporary Files folder and Resolve Scratch disk.

33 sec. System specs below, The Resolve project drive is a 2-SSD Raid 0 that has a R/W speed of 970mb/s. Also have a Resolve Keyboard that may need some time to handshake.

2016 mbp 15”, 19.5 seconds until the splash screen expands into the project manager for 16.3 Studio Beta.

Good Luck

DVR 16.2.6

Mac Pro 2013 26 seconds
iMac 27" 2017 22 seconds

But a lot of plugins are installed and DaVinci has to load them. (BorisFX, Ignite, Waves, iZotope, etc.)

29 seconds booting from a 7200 rpm spinner system drive.

DVR 16.2.6

Mac Pro 2013 26 seconds
iMac 27" 2017 22 seconds

But a lot of plugins are installed and DaVinci has to load them. (BorisFX, Ignite, Waves, iZotope, etc.)

I'm pretty sure most applications have a binary Plugin Cache, at least for VST Plugins. So, those don't really add much of anything to the load time of the application.

The only time this factors in, is when it has to scan new plugins (or something triggers a full rescan), however this is a background process which does not affect boot times for the NLE itself

I've never experienced OpenFX plugins causing the NLE to load much slower, either. If there is an effect, it is negligible.

Even on a clean system, I don't gain back much of anything in Resolve "boot times."

29 seconds booting from a 7200 rpm spinner system drive.

I don't think drive type factors in much, unless the spinner is bottlenecked when you are loading the application (i.e. doing a virus scan while loading the Resolve application, or loading it while you're forcing a defrag on the HDD).

DVR 16.2.6

Mac Pro 2013 26 seconds
iMac 27" 2017 22 seconds

But a lot of plugins are installed and DaVinci has to load them. (BorisFX, Ignite, Waves, iZotope, etc.)

I'm pretty sure most applications have a binary Plugin Cache, at least for VST Plugins. So, those don't really add much of anything to the load time of the application.

The only time this factors in, is when it has to scan new plugins (or something triggers a full rescan), however this is a background process which does not affect boot times for the NLE itself

I've never experienced OpenFX plugins causing the NLE to load much slower, either. If there is an effect, it is negligible.

Even on a clean system, I don't gain back much of anything in Resolve "boot times."

I have the opposite experience. E.g. Final Cut Pro 7 shows how plugins load and if there are a lot of them, the boot application takes more time.

21 seconds with the free version.
CPU: Ryzen 3900x with Sasmung 970 EVO Plus NVME.

I don't think drive type factors in much

I expected Resolve to start up much faster after moving to an SSD. (Most other software does.)

Not so much with Resolve, though.

It's good to start a new database every once in a while. As they grow in complexity, performance degrades. Whatever database you last used when you quit Resolve will be the one that opens at startup, and if it has a lot of projects in it, it'll take longer to start up. Also, complex projects take longer to load than simple ones, if that's not obvious enough.

But 27 seconds for me on my most recent working disk database.
and 22 seconds opening the postgresql database that only contains the fairlight sound library.

Hi.
The startup time depends if it is the first time I start Davinci Resolve after I turn my PC on.
The first time is 45 seconds...
The second and subsequent times the time is 35 seconds.

My PC is really old but works surprisingly well (11.5 years... yes! Eleven and a half years old!).
I have a lot of audio plugins. Three Sata SSD drives (Sata III drives Sata 6 Gb/s) but with a Sata II (3 Gb/s) interface and one HDD.

13 seconds on my new desktop from 1 month ago and database transferred from old system with Resolve on the M.2 NVMe SSD.

102 seconds from click on davinci until project manager loaded.

and + 56 seconds my working project starts

2 min and 38 sec
its too much. how can i decrease this time? program is on ssd. should i recreate the database?

Hi Guys!

Looks like around 30 seconds is the average startup time, and it depends a lot on the amount of memory and graphics card power that you have.

My Vegas 15 opens in about 11 seconds, but it doesn't have to load effects/color grading modules like Resolve. So, maybe 30 seconds is reasonable for loading all of those tools so you have everything accessible to do any type of chore.

Have a great week!

I had create new database not on disk, but via postgre. my old DB had many wrong audiofile in audio DB and stuff. now my project manager works faster.

Load from click to project manager = 58 sec and + 20 sec my working project opened.

Total time = 1 min and 15 sec against 2 min and 38 sec on old DB nice result.

i use old gtx 970 graphic i think when i will buy 3060 loading waveforms will need less time.

Studio 16.2.6
first start 13 sec, then 11,5

R7 3800x, RTX2060 super, 32GB, nvme boot drive, OS Ubuntu 20.04

27 secs on Windows 10 and DR Studiio 16.2.6

I get 20.19 seconds from a dead stop to the Project Manager in Resolve on a 2019 Mac Pro with 256GB of RAM. Actually opening up a project depends on the project -- one recent one took another :10 seconds.

There's a ton of code in there, but I know the BMD engineers are working tirelessly on getting it more efficient and streamlined whenever they can.

roughly 18 seconds with the hardware listed in my sig, my system drive is a samsung 512gb 950 pro.

27 sec.s

13 sec to project manager in Centos 7.6. System is threadripper 3960X, 128GB RAM, Corsair MP600 nvme drive.

13 sec to project manager in Centos 7.6. System is threadripper 3960X, 128GB RAM, Corsair MP600 nvme drive.

That's very fast!

13 sec to project manager in Centos 7.6. System is threadripper 3960X, 128GB RAM, Corsair MP600 nvme drive.

That's very fast!

Not sure if it is a linux thing or just the system. From above, kobayashi also has 13 from Ubuntu. Capthook on the other hand has win system and also 13... It goes through stuff like hot knife through butter though, Nuke for example launches in 2 sec, which includes getting floating license through network.

26 seconds, but starting a new database drops this to 21

30 seconds if everything works normally but usually on the first, cold start-up of the day, DR will hang on either "Looking for control surface" or "loading Fairlight page". If it hangs, sometimes if you wait it out for as long as 5 minutes it will eventually load. Most times, it is Task End only and then try again until it will load. Usually, by the 3rd try, it will load and then load normally the rest of the day.

If Resolve dosnt hang 39.5 seconds. to project manager and from there, 7 seconds. to timeline.

My Lightworks 2020.1 takes 1.3 seconds startup to project manager and from there 0.7 seconds to timeline.
(The fastest NLE on the planet)

About 30 seconds... which is fine. I only start Resolve once and then I use it all day before shutting it down when done. DR15.3 never crashes on me so start-up time is a very, very tiny percentage of my up-time.

I have over 90 seconds with SSD system drive.

My mistake: that's just the delay during the 'looking for control surface' phase. It takes a total 3 minutes until the Project Manager appears. Then about 2 minutes to open an (empty) project

26" and some times a few seconds faster

on all of my 10 years old mac pros

I was looking to ask this, glad someone else did. I timed it today, I was on the "searching for control surface" screen for 50 seconds. I have an i9-9900K, WD 500GB Black SN750 NVMe M.2 Internal SSD, 32Gb RAM, GTX 1060/6GB VRAM. This is pretty typical since I built this PC 6 months ago. Is it something about the control surface that I can turn off?

I was looking to ask this, glad someone else did. I timed it today, I was on the "searching for control surface" screen for 50 seconds. I have an i9-9900K, WD 500GB Black SN750 NVMe M.2 Internal SSD, 32Gb RAM, GTX 1060/6GB VRAM. This is pretty typical since I built this PC 6 months ago. Is it something about the control surface that I can turn off?

Hi Evildad!

You would think i9 cpu with 32gb ram and a M.2 hard drive would be kicking with Resolve. 50 seconds is longggg! My i5 with 8gb ram and SSD drive has the "searching for control surface" timed at 22 seconds.

I mentioned, in a previous forum post, about having a setting to not search for control surfaces (i.e., Resolve Panels) because I don't use any Resolve panels. But,the answer I was given is that "searching for control surface" does more than just look for Resolve Panels. I wish the startup statuses were a little more detailed.

Have a great week!

Hi,

mine takes 37 seconds. Also sitting at "Looking for Control Surface" for quite a bit and then at "Loading Waveform Monitor".

It's definetely the slowest starting software i have. On a ususal work day (where everything goes well) it doesn't matter because Resolve runs quite stable. But there are days where it chrashes quite often. Then it gets annoying.

But, honestly, the switching time between timelines is MUCH more annoying. I have a project where i work on 25 eposides, 2 long form and several intros etc. So over 30 timelines. It took about 10-20 seconds to switch betwen timelines. Totally killing the workflow and you need to take a deep breath in between...

I created a new disk database on a separate SSD, removed my VST audio plugins (iZotope RX7). That brought it down to 8-10 seconds. But that is still a lot when you have to switch constantly.

I think there would be a lot to be gained in productivity when improving that.

I had delete all trash OFX plugins and reinstall DVR. startup time = 20 seconds instead of 50+

- From a clean boot with Outlook and Edge running: 40 sec

- Running Outlook, Chrome, Edge, Visual Studio, Skype and Microsoft SQL Management Studio: 50 sec

- Running all the above + Photoshop: 58 sec

All combinations work fine with my version 17.6 installed. No crashes with this version so far. I also have a USB sound card, a USB headset and 2 USB disks and a Phone connected to my computer.