< Previous | Contents | Next >
The Blackmagic cloud library
Optimization and Performance of a Cloud Project Library
Before learning about how to create and manage cloud project libraries, it’s worthwhile addressing server lag and optimizations. The project library is a database of all the edits, clip metadata, visual effects, color corrections, and audio engineering applied to your timeline. This project library is queried and updated constantly as you use DaVinci Resolve. When the project library is local to, or on the same network as your workstation, these updates happen more or less instantaneously. However, when the project server is half-way around the world on the internet, the speed of light and internet routing start to insert perceptible lag time.
Luckily the majority of the changes required to mitigate this have been done by the DaVinci Resolve team. They have re-written the underlying project library code over a period of several months to optimize it for internet performance, and in most cases the responsiveness will be indistinguishable from using a local project library. However, these types of processes involve intensive and persistent project library operations, and some lag will become apparent when:
— Changing cloud project libraries
— Loading a project from the cloud project library
— Backing up and restoring cloud project libraries
It’s important to keep in mind, that once loaded, actually working in DaVinci Resolve will still be as fluid and responsive as you are used to working with local libraries.
TIP: The major optimization that the user can make in cloud library performance is to decide where to physically locate the server. The best performance will be found closest to the city where the team is working. In some cases, the team will be working in multiple cities and countries around the world. In those cases, the server should be hosted in the region of the person who uses the project library the most, and that person is the editor.
In the Edit and Cut pages, the project library is written to whenever the user releases the mouse button, while on the Color page the project library is only written to when you select a new clip. So for the best performance, you want to host the server location as close to the editor as possible.
TIP: The major optimization that the user can make in cloud library performance is to decide where to physically locate the server. The best performance will be found closest to the city where the team is working. In some cases, the team will be working in multiple cities and countries around the world. In those cases, the server should be hosted in the region of the person who uses the project library the most, and that person is the editor.
In the Edit and Cut pages, the project library is written to whenever the user releases the mouse button, while on the Color page the project library is only written to when you select a new clip. So for the best performance, you want to host the server location as close to the editor as possible.
TIP: The major optimization that the user can make in cloud library performance is to decide where to physically locate the server. The best performance will be found closest to the city where the team is working. In some cases, the team will be working in multiple cities and countries around the world. In those cases, the server should be hosted in the region of the person who uses the project library the most, and that person is the editor.
In the Edit and Cut pages, the project library is written to whenever the user releases the mouse button, while on the Color page the project library is only written to when you select a new clip. So for the best performance, you want to host the server location as close to the editor as possible.