{"id":160,"date":"2016-03-29T15:46:15","date_gmt":"2016-03-29T06:46:15","guid":{"rendered":"http:\/\/blog.criware.com\/?p=160"},"modified":"2016-03-29T16:12:29","modified_gmt":"2016-03-29T07:12:29","slug":"auto-ducking-in-adx2-with-react","status":"publish","type":"post","link":"https:\/\/blog.criware.com\/index.php\/2016\/03\/29\/auto-ducking-in-adx2-with-react\/","title":{"rendered":"Auto-ducking in ADX2 with REACT"},"content":{"rendered":"

Lowering the volume of a sound when another one is playing at the same time is called \u201cducking\u201d. A ducking system is an important tool in the game audio mixing process. It allows the game audio engine to control and prioritize what type of sounds will clearly be heard by the player when the game action culminates. In other words, it prevents the game from becoming cacophonous when there’s a lot of action going on, while ensuring the most important audio assets can still be heard (for example dialogue).<\/p>\n

The ducking system in ADX2 is called REACT<\/strong>. It controls the audio volume dependency between different audio categories at run-time (in ADX2, a\u00a0category is simply a group of volume and playback rules that applies to a set of Cues). By configuring the REACT<\/strong> settings in AtomCraft, you can adjust the real-time volume balance between categories of sounds depending on the action. A typical ducking example is when a game is gently lowering the volume of the music when a voice is playing. It allows more headroom for the voice in the mix to make sure it will be clearly heard by the player.<\/p>\n

\"adx2_REACT_tutorial_01\"<\/p>\n

Here is how to configure the audio-ducking:<\/strong><\/p>\n

Step 1<\/strong><\/span>: Create 2 categories in AtomCraft.<\/p>\n

\"adx2_REACT_tutorial_02\"<\/p>\n

Step 2<\/strong><\/span>: Assign the Cues (Changing & Trigger) to your Categories<\/p>\n

*Simply drag & drop your Cues onto the right categories in the project tree.<\/p>\n

\"adx2_REACT_tutorial_03\"<\/p>\n

Step 3<\/strong><\/span>: Create a new REACT object in the project tree<\/p>\n

\"adx2_REACT_tutorial_04\"<\/p>\n

Step 4<\/strong><\/span>: Assign the Changing Category (the one that will be ducked)<\/p>\n

\"adx2_REACT_tutorial_05\"<\/p>\n

Step 5<\/strong><\/span>: Assign the Trigger Category<\/p>\n

\"adx2_REACT_tutorial_06\"<\/p>\n

Step 6<\/u><\/strong>:\u00a0Choose the REACT Hold Type<\/p>\n

\"adx2_REACT_tutorial_07\"<\/p>\n

Step 7<\/u>:<\/strong> Set the volume attenuation ( 1 = no attenuation 0 = mute)<\/p>\n

\"adx2_REACT_tutorial_08\"<\/p>\n

Step 8<\/u><\/strong>: Set the Change Time, Hold Time & Return Time of the Ducking<\/p>\n

\"adx2_REACT_tutorial_09\"<\/p>\n

That’s all! As you can see, using REACT, sound designers can easily implement auto-ducking entirely within the AtomCraft authoring tool and without the intervention of an audio programmer.<\/p>\n

Note that you can also test\u00a0your new REACT ducking – and adjust its settings if needed – without leaving AtomCraft, as depicted below.<\/p>\n

Step 1<\/u><\/strong>: Make a temporary Cue<\/p>\n

\"adx2_REACT_tutorial_10\"<\/p>\n

Step 2<\/u><\/strong>: Refer to\u00a0a Cue from each category in your temporary Cue<\/p>\n

\"adx2_REACT_tutorial_11\"<\/p>\n

Step 3<\/u><\/strong>: Hit play and listen to the result!<\/p>\n","protected":false},"excerpt":{"rendered":"

Lowering the volume of a sound when another one is playing at the same time is called \u201cducking\u201d. A ducking<\/p>\n","protected":false},"author":2,"featured_media":169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[5,7],"tags":[],"class_list":["post-160","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-adx","category-tutorials"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/posts\/160","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/comments?post=160"}],"version-history":[{"count":14,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/posts\/160\/revisions"}],"predecessor-version":[{"id":185,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/posts\/160\/revisions\/185"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/media\/169"}],"wp:attachment":[{"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/media?parent=160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/categories?post=160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.criware.com\/index.php\/wp-json\/wp\/v2\/tags?post=160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}