{"id":7179,"date":"2024-11-11T09:19:21","date_gmt":"2024-11-11T09:19:21","guid":{"rendered":"https:\/\/tsugi-studio.com\/blog\/?p=7179"},"modified":"2024-11-13T04:51:20","modified_gmt":"2024-11-13T04:51:20","slug":"davinci-resolve-integration","status":"publish","type":"post","link":"https:\/\/tsugi-studio.com\/blog\/2024\/11\/11\/davinci-resolve-integration\/","title":{"rendered":"DaVinci Resolve Integration"},"content":{"rendered":"

Imagine generating high-quality audio ambiences that perfectly match the duration of your video clips or automatically inserting sound variations on markers in your timeline. What a time-saver this would be!<\/p>\n

Thanks to procedural audio, you can do just that, and more. In this post, we examine a new Python script<\/a> for DaVinci Resolve<\/a> that will allow you to control GameSynth from everybody\u2019s favorite video editor.<\/p>\n

\"\"
\n<\/a><\/p>\n

GETTING STARTED<\/h2>\n

In order to run a Python script in Resolve, the proper version of the language (3.6 or higher, 64-bit) must be installed on your computer. If this is not the case, you can download the latest version here: https:\/\/www.python.org\/downloads\/<\/a><\/p>\n

If it is not already done, three environment variables must also be added to Windows:<\/p>\n

<\/p>\n\n\n\n\n\n
RESOLVE_SCRIPT_LIB<\/td>\nC:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\fusionscript.dll<\/td>\n<\/tr>\n
RESOLVE_SCRIPT_API<\/td>\nC:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting<\/td>\n<\/tr>\n
PYTHONPATH<\/td>\nC:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting\\Modules<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

You can now download the \u201cGSAPI_RenderCurrentPatch.py\u201d script from our website<\/a>, and paste it into the following folder:
C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Fusion\\Scripts\\Edit<\/p>\n

The script will work with both the free and Studio versions of Resolve, and if you open the program, it should appear in the \u201cWorkspace\u201d menu, under the \u201cScripts\u201d section.<\/p>\n


\n\"\u30a2\u30c9\u30aa\u30f3\"<\/a><\/p>\n

RENDERING SOUND OVER A CLIP<\/h2>\n

The script offers several ways to render the current GameSynth patch and to add it to a timeline.<\/p>\n

When selecting the \u201cOver Clip\u201d mode, a wave file matching the exact duration of the current video clip (on which the playhead is located) will be generated. This is especially useful when you need to add environmental sound effects, such as rain, urban or forest ambiences, room tones, and so on.<\/p>\n

You can select the audio track on which the new audio clip will be inserted or create a new one. Please note that rendering will not be allowed if there is already an audio clip on the section of the timeline where the new clip is to be inserted.<\/p>\n

\"Rendering1\"<\/p>\n

RENDERING SOUND AT THE PLAYHEAD<\/h2>\n

The previous mode is intended for infinite GameSynth patches, for which the exact amount of audio will be generated. In the case of one-shot patches with a fixed duration, they will stay unchanged if they are shorter than the clip, or will be trimmed to match its duration if they are longer.<\/p>\n

However, to insert a one-shot patch at a specific position (or render an infinite patch with an arbitrary duration), you can use the \u201cAt Playhead\u201d insertion mode. The new audio clip will be inserted precisely at the playhead\u2019s position, and if the patch is infinite, it will have the duration you specified.<\/p>\n

\"Rendering1\"<\/p>\n

RENDERING SOUND ON MARKERS<\/h2>\n

The last insertion mode, \u201cAt markers\u201d, allows you to render variations of a GameSynth patch on each marker of the timeline. This can prove particularly useful when a video contains repeated actions (footsteps, gunshots, water drops, etc.).<\/p>\n

In this mode, you can select the color of the markers on which the audio clips will be added. Like in the previous mode, you can specify the rendering duration if the current GameSynth patch is infinite.<\/p>\n

New audio tracks will automatically be added to prevent clips from overlapping when markers are too close.<\/p>\n

\"Rendering1\"<\/p>\n

Using procedural audio is a great way to speed up your workflow while maintaining the highest audio quality. Indeed, no potentially damaging post-processing is needed as the required files can be re-generated (for example, if the duration of a video clip changes, etc.).<\/p>\n

This script is using the GameSynth Tool API. Check its website<\/a> to discover other integrations: with 3D animation software, game engines, DAWs, and more!<\/p>\n

\n

\nNote: as of 12\/11\/2024, support for the UI Manager – used by this script and many others – has been removed from the free version of DaVinci Resolve by Blackmagic Design. Therefore, this script will now only work on the Studio version.\n<\/p>\n<\/div>\n

\"GameSynth\"<\/a><\/p>\n

\"discord\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Imagine generating high-quality audio ambiences that perfectly match the duration of your video clips or automatically inserting sound variations on markers in your timeline.<\/p>\n","protected":false},"author":1,"featured_media":7180,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,6],"tags":[],"class_list":["post-7179","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-procedural-audio","category-gamesynth"],"_links":{"self":[{"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/posts\/7179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/comments?post=7179"}],"version-history":[{"count":27,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/posts\/7179\/revisions"}],"predecessor-version":[{"id":7208,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/posts\/7179\/revisions\/7208"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/media\/7180"}],"wp:attachment":[{"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/media?parent=7179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/categories?post=7179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tsugi-studio.com\/blog\/wp-json\/wp\/v2\/tags?post=7179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}