This is an attempt to modernize
hvcc to work with
python3 and add some additional targets.
Not all functionality is being tested. Bugreports and feedback are appreciated.
hvcc is a python-based dataflow audio programming language compiler that generates C/C++ code and a variety of specific framework wrappers.
The original need for
hvcc arose from running against performance limitations while creating interactive music and sound products for the iPhone. Pure Data (libpd) was the only real choice for a design tool as it was embeddable and provided a high enough abstraction level that musicians or sound designers could be creative.
The goal was to leverage Pure Data as a design interface and statically interpret the resultant patches to generate a low-level, portable and optimised C/C++ program that would be structured to take advantage of modern hardware whilst still generating the same behaviour and audio output as Pure Data.
It has since then been expanded to provide further support for many different platforms and frameworks, targeting game audio design, daw plugins and embedded production tools.
jinja2(for generator templating)
nose2(for tests, optional)
hvcc is available from pypi.org and can be installed using python3 pip:
$ pip3 install hvcc
If you want to develop hvcc you can install it from the source directory:
$ git clone https://github.com/Wasted-Audio/hvcc.git
$ cd hvcc/
$ pip3 install -e .
hvcc requires at least one argument that determines the top-level patch file to be loaded.
Generate a C/C++ program from
input.pd and place the files in
$ hvcc ~/myProject/_main.pd
This command will generate the following directories:
~/myProject/hvheavylang representation of the input pd patch(es)
~/myProject/irheavyir representation of the heavylang patch
~/myProject/cfinal generated C/C++ source files (this is what you would use in your project)
-oSelect output directory
As seen in the above command, typical output of
hvcc is split into several directories that contain the intermediate files used by the compiler itself, the final generated source files, and any additional framework specific files and projects.
--out_dir parameter will specify where the output files are placed after a successful compile.
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/
Will place all the generated files in
-nSpecify Patch Name
--name parameter can be used to easily namespace the generated code so that there are no conflicts when integrating multiple patches into the same project.
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/ -n mySynth
hvcc has generated internal information about the patch the
--gen parameter can be used to specify the output files it should generate. By default it will always include
c for the C/C++ source files and additional generators can specified for certain framework targets.
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/ -n mySynth -g unity
Will also generate a
unity section in the output directory contain all the build projects and source files to compile a Unity plugin.
It is also possible to pass a list of generators:
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/ -n mySynth -g unity wwise js
Available generator options:
hvcc will iterate through various directories when resolving patch objects and abstractions. The
--search_paths argument can be used to add additional folders for
hvcc to look in.
This can be handy when using a third-party patch library for example https://github.com/Wasted-Audio/heavylib.
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/ -n mySynth -p "[~/Workspace/Projects/Enzien/heavylib/, ~/Desktop/myLib/]"
hvcc can take extra meta-data via a supplied json file. It depends on the generator which fields are supported.
By default all the generated source files via
hvcc will have the following copyright text applied to the top of the file:
Copyright (c) 2018 Enzien Audio, Ltd.
This can be changed with
$ hvcc ~/myProject/_main.pd -o ~/Desktop/somewhere/else/ -n mySynth --copyright "Copyright (c) Los Pollos Hermanos 2019"
Displays all the available parameters and options for hvcc.
There are several places where heavy/hvcc conversation is happening:
Or you can use the discussions tab of this repository