…ion method

- considers wwise version

- considers both plugin types (source,effect(in-place-only))

- introduces workpath for python-based integration, that leads to cross-platform compatibility between Windows and MacOs

- structured patch using 3 commands : TITLE | BELOW | REPLACE | CODE

support inject && replace operations

- standardizes DSP integration using faustdsp.cpp file

technical debt introduced with hardcoded paths remains

…cting lines into files

Supports both source and effect plugins

The method:

- extracts parameters from faust generated json file

- injects parameter code int wwise c++ template files using template tags

- updates source files and WwisePlugin/xml file

- conditional support for RTPCs using faust ui-label-metadata

This integration step was based on python implementations with minimal templating

IMPORTANT: this is the first cross platform implementation of the faust2wwise script

- create an orchestrator class to replace old bash implementation

- create cross platform scripts to allow users to use this feature with a simple `faust2wwise` command, similarly to other Faust scripts

- Implement methods for detecting Faust and Wwise paths. Note: Wwise paths must be exposed in the system using the AudioKinetic launcher → Wwise → {installed version} → Install options (tool icon) → Set environment variables.

- address technical debt introduced by previous platform-specific and hardcoded paths

- require semantical splitting of concepts into different files; maybe consider function-based implementation instead of class-based

example usage : faust2wwise dspfile.dsp <faust options>

Note: tested on Windows && MSYS environment and require further testing (i.e. MacOs)

…rors when the dsp file was outside the current dir; for instance when provided as a path/to/dspfile.dsp parameter

…st within the examples directory

…rupting the naming conversion used in the integration process

…ive structure using parse_ui / parse_group / parse_items / parse_item methods. These methods are based on a TypeScript implementation found in the faustwasm repo (link : github.com/grame-cncm/faustwasm/blob/3ac9238bb0579bd2c51e67f5868997395766dbab/src/FaustWebAudioDsp.ts#L730C1-L730C30)

…acted json file from the examples dir to the project's dir

…re unique

…files are additional files that get imported by other dsp files, so they have to be excluded, otherwise they are treated as separate projects

…id (for instance if starts with a number)

Faust compiles files that may start with a number, but wwise cannot handle such project names

thesolution applied is to prefix with _Dsp keyword

otherwise we simply capitalize the plugin_name variable

note: plugin name is by default initialized from the name of the dsp file. But the user is able to name a wwise project by declaring the name as a metadata from within the dsp file. This is why setting of project_name may be overriden after being initialized.

…valid (this time for when it contains spaces between words)

Note:

- all of the files that have been added in the exclusion list, cannot be compiled seamlessly with faust2wwise, but they we re tested using manual interventions that proved that they fail due to the fact that they require some additional configuration, such as including additional files, action which deviates from the faust2wwise scope

…ls and jsoninjector

… for next semantical splitting/merging of the integration related functions

…ed functions in the integrator.py file

…function since the operation applied within the lua script is not that similar with the integration steps applied int he template replacement method or the parameter integration method

… a configuration file and let the files been hardcoded.

also, the faustdsp.cpp file is removed from the list, since it does not contain any placeholders within it anymore and thus not used as a template file

…p integration within template files for all types of plugins

…ng both equal (==) and non equal (!=) conditions; prepare bargraph integration

…://www.audiokinetic.com/en/public-library/2024.1.7_8863/?source=SDK&id=authoringplugin_macos.html)

updated the readme file

added documentation

…he [RTPC:rtpcType] syntax

…the docs and the faust issues page

…tive values

…option

… the limitations section

…ration

…patible function

…renaming outdir in case there are other myF2Wtests directories present in the current working dir where the tests are being applied

…the readme. Now it redirects to the official repo

… testing script in macOs to hang; changed order of functions in testing class and moved platform_dependent_setup function higher closer to the constructor since it is called within it

…t not supported out-of-the-box due to the Wwise Authoring constraints that require compiling in both windows and mac and then transfering dll and xml files from the windows build into wwise plugin installation dir

…ns in readme file

…elevation issue in Troubleshooting section and imrpoved the format of the whole section

… type of wwise plugin

… new exit code equal to zero and adjusting try-except to in faust2wwise python script to catch explicit exit system calls.

defined a new error code related to the prerequisite environmental variables in case they are not set or found or in case the sys call fails to retrieve them.