Following up from last time, we'll introduce a new script using Perforce, Excel, and Wwise. This script focuses on placing audio files not yet implemented in Wwise into Reaper and automating the pre-implementation processing.

Following up from last time, we introduce a new script using Perforce, Excel, and Wwise. This script checks whether sound objects and events with the same names as audio files recorded in Excel are implemented in Wwise. Using this script allows you to detect missing voice implementations.

Over the next three articles, we will introduce new scripts using Perforce, Excel, and Wwise. The ultimate goal of this script is to write files stored in Perforce to Excel, check whether they have been implemented in Wwise, and automatically notify you if they have not.

Following on from the previous blog, this time we will introduce a script that tests the integration of Perforce with Excel, Wwise, and Slack. we will show you how to generate a Wwise soundbank and notify the results via the Slack app.

This time, continuing from last time, I'll introduce a script that attempts to integrate Perforce, Excel, and Wwise. I'll cover the part that renders audio files placed in Reaper and imports them into Wwise.

Over the next three blogs, we'll introduce scripts that test the integration between Perforce, Excel, and Wwise. The final destination is to retrieve files from Perforce, configure and adjust settings based on an Excel spreadsheet, and then automatically implement them into Wwise.

This time, we'll introduce a script using the track-related API added in SILVER 1.3.0. It creates tracks according to the file naming convention.

This time, we'll introduce a script that uses the API added in GOLD 1.4.0 for copying Wwise objects.

This time, we'll introduce a script that utilizes the API added in GOLD 1.4.0 for configuring Wwise's randomization feature.

In previous blog (038), I created and configured a bank. This time, I will introduce a script that adds the process of generating the configured bank.

This time, we will create a script that links Reaper and Excel. Import audio files into Reaper and set their volume according to the data in the Excel file you prepared in advance.

This time it will be an integration script between Reaper and Excel. It writes the information of an audio file imported into Reaper into an Excel file. In this script, if there is already a corresponding row in the Excel file, the information is only updated, and if there is no row, a new row is created.

This is a script to automate the integration between Perforce and Wwise. It can retrieve audio files managed by Perforce and import them into Reaper.

This time it will be a script to automate the integration between SVN and Wwise. It retrieves audio files managed by SVN and imports them into Wwise.

This time, it will be an application that makes Slack notifications useful. It will automatically reply to the completion notification thread and list the waveform names that executed the HANDAUTOMER.

This is a Perforce automation that is new to GOLD 1.3.0. It automates the process of retrieving files from the latest revision and inserting them into the Reaper project.

New to RIGDOCKS GOLD 1.3.0 is the automation of SVN. Specify a revision of a file update, and Reaper will retrieve files updated with that revision and automatically line them up in your Reaper project.

This Reascript employs new automation features from GOLD 1.3.0, which is about to be released to the public. In addition, SoundBank generation and Event stringing have been automated. We hope you will experience the ever-advancing automation.

Again, this is a Reascript that employs new automation features that are now executable in the latest version of GOLD (1.2.0).

This Reascript employs a new automation feature that can be executed by using the latest version of GOLD (1.2.0).