Sam as before, but now with reverb.
Mess with the Q’s to change how the filters bhealve. The frequency and slope are merly a lowpass fitler at the end that i’m tyring to find the sweetspot for. They will get culled in the next iteration.
This is basically Tweety but then the output of tweety going into a vcf. One tweetybank goes is acting like a “carrier” signal and another is a “modulator” of sorts on the frequency of the vcf.
Work in progress generative piece.
Another doodle with EnzienAudio‘s Heavy. This time a bit of a kick-type sound. Play around with the feel/depth sliders to change to “motion” and the tones adjust the size of the sound. the bpm is not really accurate but it can be fun to play around with it in the very fast ranges when it becomes a continuous sound.
This is a doodle using Enzien Audio’s Heavy. Try moving about the sliders, i find it an interestingly hypnotic swarmy sound. Warm and lively at low pitches. Intense at higher pitches. Also let it develop for a bit once you find a place where it sounds good to you.
Let me know what you think 🙂
Heres a very quick and dirty write up on what you need to do to run the heavy uploader python script.
Thanks to martin roth for all the help
First of all you need to install Python 2 .
then install pip
might have to go the scripts sub folder of python to run:
pip install requests.
then download the latest version of the uploader script here:
then make a .bat file with this:
python uploader.py “C:/PUT THE FODLER OF YOUR PATCH HERE” -n PATCH NAME ON HEAVY -b -g “vst2-win”
Here’s the manual from the script itself:
usage: uploader.py [-h] [-n NAME] [-g GEN [GEN ...]] [-b] [-y]
[-o OUT [OUT ...]] [-d DOMAIN] [-x] [-z] [--noverify] [-v]
Compiles a Pure Data file.
input_dir A directory containing _main.pd. All .pd files in the
directory structure will be uploaded.
-h, --help show this help message and exit
-n NAME, --name NAME Patch name. If it doesn't exist on the Heavy site, the
uploader will fail.
-g GEN [GEN ...], --gen GEN [GEN ...]
List of generator outputs. Currently supported
generators are 'c', 'js', 'pdext', 'pdext-osx',
'unity', 'unity-osx', 'unity-win', 'wwise', 'wwise-
win', 'vst2' ,'vst2-osx', and 'vst2-win'.
-b All files will be placed in the output directory,
placed in their own subdirectory corresonding to the
-y Extract only the generated C files. Static files are
deleted. Only effective for the 'c' generator.
-o OUT [OUT ...], --out OUT [OUT ...]
List of destination directories for retrieved files.
Order should be the same as for --gen.
-d DOMAIN, --domain DOMAIN
Domain. Default is https://enzienaudio.com.
-x Don't save the returned token.
-z Force the use of a password, regardless of saved
--noverify Don't verify the SSL connection. Generally a bad idea.
-v, --verbose Show debugging information.
-t TOKEN, --token TOKEN
so if you read that and go back to my commandline you’ll notice this puts a vst dll in a subfolder of where your project is.
Important note: the patch that you want to use has to be called _main.pd. The rest, subpatches etc can be what you want.
Very small iteration. Just trying to make it sound a bit more interesting. Wont make a sound when you click play. You haev to move the sliders a bit.
Here’s a lil experiment with additive synthesis in Heavy/PureData.
Running pd in a browser. Woei! Remember last year’s #dspatchaday challenges? Well now they can become interactive.