установите сервер postgresql выбрав соответствующий параметр в установщике davinci resolve
BlackMagic DaVinci Resolve
Компания BlackMagic выпустила бета версию программы для цветокоррекции и грейдинга DaVinci Resolve 8.2 для платформы Windows.
Сертифицированные рабочие станции: HP Z800 Workstation, Supermicro SuperServer 7046GT-TRF. Видеокарты: NVIDIA GPU для GUI (NVIDIA Quadro 600 и NVIDIA Quadro 4000) и NVIDIA CUDA (Quadro 4000, GeForce GTX 580, Quadro 5000, Quadro 6000).
Программа также поддерживает работу с двухголовыми видеокартами GeForce GTX 590. Драйвера: NVIDIA driver 280.26.
Поддержка работы на операционной системе: Windows 7 Professional 64 бит.
Объем загрузки: 410.5 Мбайт.
Также доступна для скачивания с официального сайта бесплатная облегченная версия: DaVinci Resolve Lite 8.2. Функционал бесплатной Lite версии DaVinci Resolve урезан относительно полной версии программы. Но имеет в своем арсенали достаточное количество полезных функций: высококачественный оптический ресайз, грейдинг с помощью кривых, импорт и экспорт XML, работу в 32-х битном режиме, процессинг YRGB, многослойный таймлайн, стабилизацию, оконный трекинг, инструмены первичной и вторичной цветокоррекции, работу в реальном времени, захват и воспроизведение с контрольной панели, поддержка нода цветокоррекции, совместимость с панелями от сторонних производителей и многое другое.
Ограничения Lite версии: нет поддержки стерео, шумоподавления, трекера, проекты только с разрешениями HD и SD, поддерживается один GPU и одна карта RED rocket. Для нормальной работы потребуется достаточно мощная конфигурация компьютера: большой объем оперативной памяти, видеокарта GeForce GTX 580.
Рассмотрим процесс установки программы DaVinci Resolve 8.2 для платформы Windows. Рекомендованные драйвера NVIDIA driver 280.26 и выше, ставим последние WHQL драйвера с официального сайта:
Запускаем инсталлятор DaVinci Resolve Installer и выбираем компоненты которые будем устанавливать:
Можно выбрать частичную установку компонентов если что-то из предложенного уже стоит в системе. Нажимаем на кнопку: Install. Начнется установка Nvidia CUDA Toolkit v4.0 (64bit):
Далее, установка PostgreSQL 9.0.4.1.
Медиа плеера QuickTime 7.70.80.34.
И соответственно запустится программа установки приложения DaVinci Resolve, нажимаем на кнопку Next.
Принимаем лицензионное соглашение. Next.
Выбираем директорию установки. Next.
И для начала установки нажимаем на кнопку: Install.
Запустится процесс установки приложения DaVinci Resolve.
Лучше при установке отключать антивирусы и брандмауэры, чтобы не завис установщик при всплытии подобных сообщений:
По окончании установки, нажимаем на кнопку: Finish.
Последний компонент установки: Blackmagic Design Desktop Video 8.6.1.0.
Так как версия Бета, различных ошибок в установке и запуске хватает:
Ошибка: Not licensed возникает при установке полной версии, поэтому можно попробовать бесплатную облегченную DaVinci Resolve Lite 8.2.
Зависает установка Blackmagic Design Desktop Video:
Также при загрузке программы, если конфигурация ПК не соответствует рекомендуемой, появляются следующие сообщения:
Для создания оптимальной рекомендуемой конфигурации, нам предлагают обратиться к документу DaVinci_Resolve_Windows_Config_Guide.pdf.
Делаем двойной клик по ярлыку программы на Рабочем столе:
Запустится заставка программы DaVinci Resolve:
Или заставка программы DaVinci Resolve Lite:
В окне Database Manager если не собираемся создавать базу данных, нажимаем на кнопку: Cancel.
В версии программы Lite в интерфейсе часть опций просто недоступны. Создаем новый проект: File > New.
И импортируем XML документ, с помощью команды: File > Load XML/AAF. Выбираем файл в окне Choose a file to import и нажимаем на кнопку Open.
В окне Load XML. оставляем настройки по умолчанию и нажимаем на кнопку: ОК.
How to Add Sound Effects to a Sound Library in DaVinci Resolve 15
The new Sound Library browser in DaVinci Resolve 15 makes it much easier to find that perfect audio clip. Here’s what you need to know.
One of the many new features in DaVinci Resolve 15 is the new Sound Library browser. This gives you a searchable database of all your connected sound libraries, accessible from the Edit and Fairlight pages.
This makes finding and adding the perfect sound effect much easier than scrolling through folders, highlighting specific files, or trying to remember which “Whoosh” file is the best one.
In this article, I’ll walk you through everything you need to know to get started with the Sound Library.
(When putting this post together, I encountered a problem with PostgreSQL (which we’ll get into). If you see “No Library Connected” when you open the Sound Library browser in DaVinci Resolve 15, you can skip the first section below.)
To build my sound effects library, I’ll be working with the 120 free sound effects that you can download from PremiumBeat.com right here.
Setting up a PostgreSQL Database in DaVinci Resolve 15
(Update: The DaVinci Resolve 15 Beta 2 update includes support for creating sound libraries using DaVinci Resolve disk databases, so the step outlined below is no longer necessary if you’re running the default disk database in Resolve 15 Beta 2 or higher.)
If you’re a single user on a standalone system, chances are you’ll be using a Disk database (the default) to save your projects, settings, and grades in DaVinci Resolve. In order to get the Sound Library to work, you’ll need to add a PostgreSQL database to store the sound effects. (You can run both databases on your system.)
If, like me, you’ve never used a PostgreSQL database in Resolve, you may not even have PostgreSQL installed on your system — or you might have an old version of it.
You can check your version of PostgreSQL on a Mac by going to Mac HD > Library > PostgreSQL. I have 8.4, which is incompatible with Resolve 15, and likely from an old version of Resolve Studio.
Unfortunately the readme that ships with DaVinci Resolve says that you’re supposed to update your version of PostgreSQL before you update your OS (which I also recently did):
Upgrading Your PostgreSQL Database Server on Mac
Until DaVinci Resolve 12.5.2, the Mac installer used to ship with PostgreSQL version 8.4.2. Starting from macOS Sierra 10.12, PostgreSQL version 8.4 is no longer supported.
If you intend to upgrade to the latest OS, you will need to upgrade your PostgreSQL database server to version 9.5.4 prior to upgrading macOS. Once your PostgreSQL installation has been upgraded and your data has been ported, you can then proceed with your macOS upgrade.
We have provided apps to simplify upgrading your PostgreSQL version on your Mac. The apps along with instructions can be found in the /Library/Application Support/Blackmagic Design/DaVinci Resolve/Upgrade PostgreSQL folder.
Starting from DaVinci Resolve 12.5.3, new installations will include PostgreSQL version 9.5.4.
So, after backing up your existing PostgreSQL database (and assuming no other apps on your system are relying on PostgreSQL), you need to completely uninstall and then reinstall it at version 9.5, which is compatible with DaVinci Resolve 15.
Installing PostgreSQL 9.5 for DaVinci Resolve
You can choose to install PostgreSQL Server on your Mac during the installation process for Resolve 15. Just click on the Customize button, and then check the box for PostgreSQL Server in the next window.
Now, when you open DaVinci Resolve 15, you can create a PostgreSQL database (you would have previously gotten an error message with “no/incompatible version installed.”)
When you first launch DaVinci Resolve 15 (or if Resolve is already open), click on the little House icon in the bottom right-hand corner, open the “Databases” sidebar by clicking on the icon in the yellow box (pictured above). Then click on “New Database.”
In the dialogue box, select the “Create” tab. Choose PostgreSQL, and then give the new database a name, like “soundfx.”
It’s best to leave all the others at their defaults — especially the location (which defaults to the local host, which is your computer) unless you want to store it on a shared server others can access (which is largely the point of PostgreSQL databases!).
Now, when you open Resolve and go to the Sound Library, you should see “No Library Connected” rather than “No PostgreSQL database connected.”
After all that, we’re finally ready to begin.
Using the Sound Library in DaVinci Resolve 15
The Sound Library works by scanning a folder (and its sub folders) for sound files and then building a searchable catalogue of those files, stored in the PostgresSQL database of your choice.
As each PostgreSQL database can store its own catalogue of scanned files, it seems to make sense to make one library in one PostgresSQL database that stores them all for easy searching. However, if you have thousands of files, it’s possible that the database might get unwieldy.
To actually add your sound files to a Library, just click on “Add Library,” and select the folder you want to scan. You’ll then see the dialogue box (pictured above) detailing how many sound effects have been added to the Library.
Once you’ve added some files to your library, the only way to find them is to search for the keywords in either the filename or its metadata description. Hopefully, more searchable metadata fields will be available in the future, such as artist, album, duration, etc.
As a test, I opened one of the sound effects in VLC media player to see if I could edit the metadata so DaVinci Resolve would recognize the text “Scary Action Riser” in the Description tab. But it didn’t work for me. Hopefully, these improvements might come in later editions of the beta.
To add more files to your catalogue or library, click on the three little dots to the right of the Sound Library and press “Add Library…” and then select the target folder.
To refresh the library, just reselect the same folder you’ve previously added, and any new items it finds will be added to the library as well.
Adding Sound Effects to the Timeline
In both the Edit and Fairlight pages you can add any of the sound effects by dragging and dropping them into the timeline. It’s that easy.
You can add In and Out points (shortcuts I and O) to set the range of the clip you want to edit in to your project. Within the Fairlight page, you also have a few more controls (pictured above), including setting a sync point marker, which allows you to set the frame within the clip that will match to the playhead in the timeline when you audition it.
To audition a clip, select the track in the timeline that you want to paste the clip into, set the sync point marker (at the top of the riser) and press “Audition.” Resolve will temporarily paste the clip into the timeline with the sync frame at the position of the playhead. If you press “Cancel,” it will remove the clip — or leave it in place if you select “Confirm.”
Feature Requests
Other than adding more metadata fields to search and scan, it would be great if you could sort the results by the metadata fields. This way you could sort the results by the number of stars in your rating column or the duration of the file — and so on.
I also experimented with taking files in the library offline. (I simply moved a file out of the folder it had been scanned into.) The result was that the entry in the database still existed, but no waveform appeared in the preview thumbnail. As soon as I added the file back into the folder, the waveform reappeared. Next, I’m hoping we see flags for offline files that need to be replaced.
Looking for more tips and tricks? Check out these articles.
Install PostgreSQL database server for DaVinci Resolve on Mac
In a previous article, we demonstrated how DaVinci Resolve users can create new databases in just several easy steps. Some users found them run into various problems when they were trying to setup a PostgreSQL database in Resolve. One of the most common errors they encountered is:
Failed to open database connection: could not connect to server: connection refused is the server running on host 127.0.0.1 and accepting tcp/ip connections on port 5432? qpsql: unable to connect.
The first thing you should check when you get this error is to check whether the database server is installed or not. Launch Finder. Click Go from the top menu bar, select Computer from the drop-down menu. Then browse to Macintosh HD > Library see if you can find a sub-folder name PostgreSQL. If you can’t find it, you will need to re-install DaVinci Resolve on your Mac. You can customize the installation and select to install PostgreSQL server during the setup process.
On the Installation Type screen, click Customize to reveal more advanced settings you can change.
Select PostgreSQL Server from the Package Name list and click Install button to install both DaVinci Resolve and PostgreSQL server on your Mac. Enter your computer password to allow these installations. You can find more details from this tutorial to install DaVinci Resolve on Mac for free.
Make sure to backup the databases in DaVinci Resolve before you uninstall it so as to keep all important projects.
Once you have installed PostgreSQL server along with DaVinci Resolve on your Mac, you should be able to create PostgreSQL databases in Resolve.
Creating A Shared Database – A Huge Workflow Enhancement For A Small Facility
In this updated Insight learn what gear you’ll need and how to properly setup a shared database in DaVInci Resolve.
Editors Note 6/5/17: Since version 12.5.2 DaVinci Resolve has shipped with a newer version of PostGresSQL (9.5.4) Any references to PostGres 8.4 in the steps below should be replaced with 9.5. Also PostGresSQL is not installed by default anymore. In the DaVinci Resolve installer you must eplicitly choose to install it. If you forgot to, you can simply rerun the installer. Finally, if a PostGres Data folder is not found first launch Resolve and create a local PostGresSQL database – this will create the nessasary data folder
Editors Update: In 2018 we posted an Insight on the DaVinci Resolve Project Server that makes the process of working with PostGresSQL databases much easier. After reading about the fundamentals of Shared Databases in this Insight be sure to click through to that Insight. (Hat Tip: Francois Dompierre in the Comments for reminding us to add this comment.)
Easily Share A Resolve Database & Gain Streamlined Workflows
As you probably know the database is at the heart of DaVinci Resolve.
Databases store everything about a project, your preferences, and perhaps most importantly your actual corrections and grades.
There is a lot of information out there on best practices for SQL and Disk Databases – how to connect, backup, etc. – indeed, Team Mixing Light has produced a lot of training on databases including nearly a whole chapter dedicated to them in our Deep Insights Training.
But if you work in a facility with multiple Resolve workstations or if you’re an independent colorist with multiple computers there is a compelling case to be made for having a shared database.
While nearly all the info I’ll share in this Insight is in the Resolve config guides or user manual, it’s hard to find it all in one place and in layman’s terms.
As a small facility owner/operator I can tell you that using a shared database has a been a huge, gigantic, even colossal benefit to our grading workflows.
A shared database not only makes moving from room to room simple, it unlocks some advanced Resolve features such as timeline collaboration and the upcoming remote rendering in Resolve 12.
Configuring a shared database server & SQL database is very straight forward, but also a little tricky if you haven’t done it before so that’s what I want to share with you in this Insight.
What Is A Shared Database?
For those of you who have been using DaVinci Resolve for years, you’re probably very familiar with the PostGreSQL database environment.
An SQL database is a standard way of storing data – your bank probably uses thousands of them to store user and financial data.
Resolve uses a database to store information about your user, the project, preferences and of course, the actual corrections you apply to any given shot.
Resolve used to only work with this type of database. While many users and facilities still use an SQL database for Resolve, it seems like increasingly BlackMagic is trying to steer users away from SQL databases or at least make them harder to create.
A few versions ago the Resolve team implemented Disk Databases, which function more like a project folder with all the database goodness contained within.
These databases are of course very popular, function pretty much the same (files are visible) and are now the default type of database that is created when you install Resolve.
BlackMagic seems to prefer Disk Databases so much, that Resolve 12 by default, won’t even install the PostgreSQL environment need to create a SQL database!
The big problem with Disk Databases?
Well, without some trickery with file sharing services or shared storage they’re not shareable.
You might have noticed if you’ve created an SQL database that unlike a Disk Database that has a file path to the location of the database, an SQL database has an IP.
By default, this is an internal IP, meaning it’s local to your machine and points to the PostgreSQL database server on your local machine.
However, because an SQL database uses an IP, it means that the database can be shared or accessed from other machines in your facility or even outside your office!
To be clear – by default an SQL database does run local to your particular machine running Resolve and is not shared.
But, as I’ll show you a little later, it’s easy with some pretty simple steps to setup any SQL database to be shared.
Why Use A Shared Database?
My facility has multiple machines running DaVinci Resolve.
We have a ‘hero’ suite with all the bells & whistles, a smaller suite but similarly equipped to the big room, and a couple assist stations.
My biggest issue with disk or local SQL databases is that if someone started a project on computer 1, but then I need the project on computer 2, I’d have to export the project from computer 1, import it into the local database on computer 2, and relink, etc.
This is an ok way to work, but sooner or later this shuttling back and forth and having to manage multiple versions of the same project becomes very tiresome and potentially dangerous – are you working on the right version of the project?
So why do I used a shared database?
With a shared SQL database, every Resolve computer can point to the SAME database, & can access the same version of the project, without the export/import problems or the hassles of managing multiple versions of the same project.
Also with a proper VPN setup, this database can even be accessed remotely.
For example, often I’ll come home to have dinner with my family but realize that I could get a jump on the next day by working on a project after the kids are tucked into bed.
Because I have a shared database, I can VPN into my office network and I can access the same database and same projects I use at work from my iMac in my home studio!
A shared database allows these good looking folks in a really nice looking studio to work in a collaborative fashion with DaVinci Resolve ©BlackMagic Design
Besides a simple convenience issue, using a shared SQL database is how you can leverage Resolve’s collaboration features, which allow multiple colorists, editors and assistants to not only work on the same project at the same time, but actually be working on the same timeline at the same time.
A shared database will also make the upcoming Resolve 12 feature ‘remote rendering’ possible.
What About The Media?
Oh right, the media!
Obviously a Resolve database in whatever form is everything BUT the media.
While shared databases can absolutely be used in any setup with multiple computers running Resolve, a shared database tends to work best in an environment with shared storage.
If you setup a shared database using the steps below but don’t have shared storage that’s ok, but you need to be aware of a few things:
As long as you have media that a project uses locally on each machine you can still get all the benefits of using a shared database, but you might have to relink media on each machine and of course you’ve duplicated, triplicated or even more ‘cated’ your media which is not all that efficient – but will work.
I’ve heard of people getting pretty creative with file sharing services like DropBox – locating media on DropBox, and syncing that media to a drive called the same thing on each of the Resolve computers. I haven’t tried this myself, but I would imagine it would work.
In my facility, we have a true SAN that allows all the computers that use the shared database to also point to the same location for the media that any project uses.
A SAN like this base TZ8 unit from Small Tree (the 10Ge SAN my facility uses) lets you share media easily in a shared database environment
With both the database setup and shared storage, I can get on any computer in the facility and access the database, project, user settings and so on just like I would running locally.
For example, I might start in the morning in the hero room, but then someone else is being supervised with clients and would like to use that room, no problem!
I’ll simply log off, go to another room, log back into the database, open my project and everything is right where I left it.
What Do You Need To Run A Shared SQL Database?
Chances are you probably already have everything you need to run a shared SQL database. Let’s break the components down:
Getting the gear together to use a shared SQL database is pretty easy. Again, I want to mention the computer you use doesn’t have to be an amazing machine because all you’re really doing is throwing metadata around, but in my experience a machine like a Mac Mini or even MacBook Pro with a decent amount of RAM and fast disk (SSD) will work really well.
Configuring The Server
After installing PostgreSQL via the Resolve installer, you’ll need to do some configuration using the Terminal app to properly configure the server.
If you’re intimated by the Terminal get some help!
Because you’ll be in ‘SUDO’ mode there is potential that you can screw things up, but as long as you follow the steps that I’ll list here or from the configuration guide you should be fine (please type in don’t copy these commands):
That’s the hard part! Almost done.
It’s a good idea to make sure that the SQL server is properly configured. To do that head back over to the Terminal and enter the following commands:
Create & Connect To A Shared Database
Now that you’ve setup the database server, the next thing to do is to actually create a shared database.
You can do this from any computer in your facility running Resolve, but since you’re probably already on computer that is the database server, simply plug in your dongle and launch DaVinci Resolve.
If everything worked as it should, the database should appear in the list of databases, double click on the database to make it active (connect to it).
At this point, you can pull the dongle from the database server and put it back on the machine it belongs to.
On any other computer (remember you can create a new shared database from any computer as long as you use the IP of the server) launch Resolve and go to the database list.
In the upper right corner click the the menu and choose Connect. Enter all the same information – name, label and IP and click connect.
You should now have access to the shared database on any computer you want!
The Mac, Windows, Linux File Path Conundrum
You have your shared database working, shared storage is humming and things can’t be better!
Well, there is one thing that I’ve encountered recently even with all this perfection that nearly killed my otherwise great setup.
For years we’ve been a Mac only facility. Because of this, every computer had the same file path to shared storage which looked something like:
/Volumes/SAN/
All media as well as cache files, gallery stills and so on pointed to this location.
No matter what computer I worked on, media automatically connected, cache files worked and connected no matter what computer they were created from and stills and saved corrections worked as they should.
Well, then I decided to get fancy and add a kick ass windows Machine, and dual purpose that computer as a Linux Resolve setup too.
That’s when I got really frustrated.
Different operating systems of course use different file paths so the same SAN on Windows mounted as:
On Linux this was different still:
/Volumes/Media/SAN
So when moving from machine to machine I had to manually relink media, and because the file paths were different, if I had cached something in one place and now opened that project on a different machine the file path was now different – I lost those cache files!
That last bit more than anything was HUGELY frustrating.
If I had spent 30 min to cache a timeline I had to repeat that 30min caching on another computer.
Luckily, I have some pretty smart friends.
Good pal and friend of Mixing Light Juan Salvo turned me on to a way to fix this problem that was right in front of me all along!
Mapped Mounts!
The best way to think of mapped mounts is as a file path substitution.
If on the Mac you have the path /Volumes/SAN you could add as Mapped Mount the Windows equivalent S:\ (or what ever it is on your machine).
In similar fashion, you can enter the Mac file path on a Windows Machine.
Configuring this ‘translation’ is simple.
With this Mount Mapping in place I can go back to the way it was prior to have different operating systems in the mix, and just like my previous Mac only setup, I don’t have to relink, or re-cache files.
This simple fix has been a huge overall workflow enhancement.
Pheww. Let Me Get Back To Part 2 Of The Z840 Review
Ok, now that I have all this database stuff out of my system, I’ll get back to part 2 of my z840 review.
As a teaser, for the most part, I’ve been LOVING the z840 & Windows 8.1 is actually pretty good too, but I have some issues that I’ll detail in part 2.
But overall, for running Resolve the z840 does indeed feel just like running a Mac, which I know a lot of you are concerned about.
Any questions on database setup or Mapped Mounts please used the comments below!