Compiling with heavy produces empty folders for Wwise and other targets

dreyes999 · September 17, 2018, 8:51pm

Hello,

In response to my comment here:

I was informed that the online heavy compiler will now generate outputs for targets like wwise, unity, etc.

I just tried compiling a pd patch just now and all of the c targets compiled correctly, however the folders for Wwise, vst2, unity, etc are empty. They have the linux/resources/vs2015 folders in them, but these folders are empty. I’m posting this topic to see if it is user error on my end or if others are experiencing this issue.

Thank you

mars · September 18, 2018, 10:19am

I can confirm I see the same empty folders. Perhaps we need to configure hvcc with the correct SDKs. I will try it out.

mars · September 18, 2018, 10:43am

Okay so I found and fixed an error in the compilation script: the zip file now includes all the generated code for all targets, plus project files for building on Windows, Mac and Linux. Just recompile and download.

What it doesn’t produce is the binaries, you still need to build and link with your choice of SDK.

hope this works for you!

Martin

Hantise · November 15, 2018, 11:43pm

Hi ! Im making my first attempt to run a Pd patch in Wwise. Ive been able to compile my patch and got all the folders that you are talking about. I dont know much about programmation, i do not understand the part

Im trying to open the “build.json” file in the Wwise launcher so it can add the patch as a pluggin, but the launcher says:

“Cannot install from ‘C:\Users\pc\Desktop\wwise’
Cannot find file bundle.json”

Can someone help me out ?

dreyes999 · November 16, 2018, 12:30am

Read the Wwise documentation on the Heavy Github repo.

github.com

enzienaudio/hvcc/blob/master/docs/06.wwise.md

# Wwise

## Version Support

`hvcc` will generate a Wwise plugin project that links against a particular Wwise SDK version.

The default is currently `2017.2.2.6553`, however if it's necessary to link against a different Wwise SDK, change the value of `wwise_sdk_version` in the c2wwise generator (found [here](https://github.com/enzienaudio/hvcc/blob/master/generators/c2wwise/c2wwise.py#L58)) to the required SDK version string.


## Source Generator or FX Unit

The type of plugin that **heavy** generates is dynamically determined depending on the [I/O channel configuration](#02.getting_started#audio-input-output).

If an `[adc~]` object exists in the patch the generated plugin with be an FX unit. Otherwise it'll be a source generator plugin.

## RTPCs

The Wwise target supports both [input and output parameters](#02.getting_started#exposing-parameters).

![rtpcs](img/docs_wwise_params.png)

This file has been truncated. show original

To learn how to build the plugin, the information you are looking for is at the bottom of the page where it starts with “Compiling the plugin”.

dreyes999 · November 16, 2018, 12:31am

Sorry for the late reply mars. Thank you so much for correcting this.

Hantise · November 16, 2018, 1:26am

Hi ! Thanks for your quick answer. As I said, I know almost nothing about programmation. I copied the text you linked in your comment (its full version) in my text editor E-Pyo. I had to install Jinja2 in the cmd prompt for python 2.7. When i try to compile, E-pyo says :

=== Output log of process “Untitled-0.py”, launched: “15 Nov 2018 20:13:50” ===
Traceback (most recent call last):
File “C:\Users\pc.epyo\epyo_tempfile.py”, line 24, in
from …buildjson import buildjson
ValueError: Attempted relative import in non-package

Any idea how to fix that ?

dreyes999 · November 16, 2018, 3:06am

You shouldn’t be using python at this point. The overall big picture process is as follows:

(forgive me I’m doing this off the top of my head)

Requirements:
-VS2015
-Wwise version 2017.2.2.6553 with SDK

use rebel technology’s online compiler (you have already done this. You should have a wwise folder now that was produced by the compiler. Inside that wwise folder should be VS2015 folder. Inside that folder should be a .sln project. )
open a command prompt and change the directory to the location of the .sln project.
$ cd …/unity/vs2015
run the build script in the command prompt using VS2015
$ “C:/Program Files (x86)/MSBuild/14.0/Bin/MSBuild.exe” /property:Configuration=Release /property:Platform=x64 /t:Rebuild Hv_heavy_WwiseSourcePlugin.sln /m
(use the name of your .sln file, not the template one above)
if it builds correctly, you will get the plugin binaries in
wwise/build/win/x64/Release.
In that folder you should find:
HV_{PATCH_NAME}WwiseSourceAuthPlugin.dll
HV{PATCH_NAME}_WwiseSourceAuthPlugin.xml

Take those and put it in:

C:\Program Files (x86)\Audiokinetic\Wwise {version number}\Authoring\x64\Release\bin\plugins

Depending on what kind of plugin you are making (source, effect, etc.) You should be able to use it in wwise now.

So… That is the down and dirty overview. So how far you get with that and post here if you have some issues. I am planning on making a video for this at some point on my youtube channel Game Audio Guru

Hantise · November 16, 2018, 4:27pm

Ok. I think im getting real close. I did not understand what u meant by

Since im a total non-programmer and since I did not even know about the existence of Visual Studio hahaha. But still, I read in the “Compiling the plugin” section from the link you sent me yesterday that we could “build manualy” : ‘‘A Visual Studio 2015 project exists in the unity/vs2015 directory and the plugin may be built manually. It can also be compiled directly from the commandline’’.

So I chose the ''Release" option in Visual Studio, with the “Rebuild Solution”. It seems to have worked, since I now have the ‘’ wwise/build/win/x64/Release ‘’ , with the HV_{PATCH_NAME}WwiseSourceAuthPlugin.dll and HV{PATCH_NAME}_WwiseSourceAuthPlugin.xml.

I dragged those into the C:\Program Files (x86)\Audiokinetic\Wwise {version number}\Authoring\x64\Release\bin\plugins.
Then I opened the correct Wwise version ( 2017.2.2.6553), added a random container, and went to add my new pluggin in the Effects section.

Problem is that I cant see my new pluggin in there. Im trying to use an example of “Procedural Wind” that I found on your YouTube channel.

Must be something that im missing ?

dreyes999 · November 16, 2018, 4:51pm

Good! you’re real close.

The problem is you’re trying to use the plugin the wrong way. procedural wind is a source plugin, not an effect plugin. You’re trying to add it as an effect plugin.

Try creating a sound sfx object. Then for that object, in the contents editor window, click the “add source” button.

The plugin should be in that list.

Hantise · November 16, 2018, 5:11pm

Man. It works.

THANKS SO MUCH !!

I’ll come back here to share the results of my experimentations !

Hantise · November 16, 2018, 5:22pm

Can this procedure work with Wwise 2018 ?

dreyes999 · November 16, 2018, 5:38pm

Excellent! So glad that it worked. Yes it can. BUT you can’t use the rebeltech online compiler. I’m fairly sure its hard coded to that version of wwise.

In my youtube channel I have a video showing you how to use heavy without using rebeltech’s compiler. If you use that method, there is a way to change the wwise version. How to change the wwise version is not in the video, but its easy to find and when you get to that point I can show you.

Hantise · November 17, 2018, 3:14am

Hey ! Sorry for the late answer. Busy day.
Im trying to install the “enum” module in PyCharm but it says : AttributeError: module ‘enum’ has no attribute ‘IntFlag’

Any idea why ?

Hantise · November 17, 2018, 3:38am

Nm I managed to install it when switching to python 2.7 interpreter in PyCharm

Hantise · November 17, 2018, 3:53am

So yeah I succeeded compiling the patch as you showed in your video. So now how do I change the Wwise version, and what file do I need to use after compiling ? Thanks !

dreyes999 · November 17, 2018, 5:51pm

Sweet! Glad you got that sorted. Okay so you can do this in pycharm or any text editor.

In the hvcc folder look for the c2wwise.py file in the generators folder
On line 58 you can change the wwise/sdk version number to match whatever version you want

Hantise · November 17, 2018, 11:25pm

Cool ! So now I have the 3 folders : c, hv, ir

I guess I have to run Vs2015 ? What file should I be using next ?

dreyes999 · November 18, 2018, 12:19am

You need to generate the wwise folder.

In the video at 10:50 I show you the script to compile the patch. however you need to add the wwise generator to that script simply by adding “-g wwise”

so your script will look something like:

$ python2.7 hvcc.py ~/myProject/_main.pd -g wwise

This will generate the wwise folder which will have the vs2015 folder inside

Hantise · November 18, 2018, 12:29am

Ok cool, trying this right now. In the video the command stops at "_main.pd "