Bug report: Incorrect nested Wwise object creation

[Dishcleanser]

When creating any nested object types other than nested virtual folders the creation will fail in a few different ways:

Affected versions:
Wwise 2025.1.4.9062
ReaWwise 1.0.7
ReaWwise 1.0.6
Reaper 7.61

More versions could be affected, I did not test other versions

Affected versions:
Wwise 2025.1.4.9062

Case 1 - Control:

The following settings will create the project structure in Wwise as the UI indicates

Case 2 - Incorrect Object creation:

The following settings will properly nest the created Sound SFX and Sound Voice objects, only the parent object will have the appropriate object type, all nested objects except Sound SFX and Sound Voice objects will have the Virtual Folder object type

Affected object types:
Actor-Mixer / Property Container
Work Unit

ReaWwise Settings:

Resulting Wwise transfer:

Case 3 - Nesting failure:

The following settings will fail to nest, the parent object will have the correct object type but no sub-objects are created, all Sound SFX and Sound Voice objects are direct children of the main parent object.

Affected object types:
Blend Container
Random Container
Sequence Container
Switch Container

ReaWwise Settings:

Resulting Wwise transfer:

Case 3.5 - Nesting Failure incorrect file name incrementing

After the failed nesting of Case 3 the next attempt will result in different behaviour. Any failed nested Sound SFX or Sound Voice objects that already exist and are attempted to be replaced using ReaWwise using the same settings are Case 3 will not result in those objects being replaced, instead the object name will be incremented and created new.

ReaWwise settings:

Resulting Wwise transer:

[ak-spressey]

@Dishcleanser , I am trying to repro the issue and I can't seem to get ReaWwise to recreate the heirarchy, in your control example, where the Folder named Glass Random is a child. When I create a Reaper structure with the Glass Random, (Folder) track , nested. I always see it named in ReaWwise as Main SFX/GlassRandom and not nested. I do not expect it to transfer to Wwise sucessfully as it would try to create an object with a / in the object name, which is not allowed by Wwise. Could you screen capture your Reaper project, so I can understand the structure and how you are calling render.

[ak-spressey]

A side note, only ReaWwise version 1.07 will work with Wwise 2025> . This is because 1.07 adds support for the new in Wwise 2025 , new hierarchy names and revised object names.

[Dishcleanser]

@ak-spressey , hey, I am using the render matrix to render my tracks, and from the looks of it the folder structure you have in reaper should recreate the behaviour I listed. Here are the screenshots showing my project and the rendering:

[ak-spressey]

I have reproduced the bug. It manifests slightly differently on Win to MacOS. The cause is the wildcard $folders, it returns the full path, Main SFX/Random Glass. ReaWwise on PC attempts to create the desired structure, but on transfer fails to so because it is trying to create an object with / in the name. I tried using $folders[_] to separate the name with an allowed character, which it does, but ReaWwise then creates the object with the name Main SFX_Glass Random and loses the nesting within the Main Project object. We have an internal bug now and an investigation into a fix will be prioritised in our next standup. I will post here when we have a fix candidate build ready for an alpha release via Reapack.

[ak-spressey]

I will investigate work arounds, and will suggest them if I find one.

[Dishcleanser]

I have already found a workaround:
I found a bunch of Wwise scripts to make life in Wwise easier, one of those scripts is a script to convert an existing object into a different object type. So I just installed that, bound it to a free keybind and do that on the created virtual folder. Thank you for keeping a potential workaround in mind though

This is the github page for the Wwise scripts I found: https://github.com/anfelab/waapi/tree/main/waapi-scripts