Aria Salvatrice Signature Series Synthesizer Modules
Hiya hello hey hi what’s hip love, I’m Aria Salvatrice. I’m a French expat living on the Worldwide Web with my dog.
I make Gay Baroque Technopop and Pastoral Industrial music happen, and made a buncha virtual synth modules for my own use.
They are the Aria Salvatrice Signature Series. They’re growing into an integrated system for performing aleatoric techno. Lotsa artists found them inspiring for many genres of music. You can grab them for free!
They are part of Cardinal, which is currently the only supportedh ost.
They are not supported in VCV Rack 2, due to their behavior towards third-party contributors, and inclusion of women. Bug reports you cannot reproduce in a supported host will not be accepted.
Documentation
The documentation of the modules is only available from my website. It's beginner-friendly and detailed - please check it out.
Compatibility, Download & Installation
Those modules currently work with any 1.x version of VCV Rack, on Linux, Windows, and OS X. Please contact VCV to obtain them via their library. However, older versions are no longer supported.
If you build my plugin manually, you have to make dep before you make dist.
The Sonaremin project for Raspberry Pi bundles my modules in its distribution.
Other thingies
Acknowledgements & Namedrops
Thanks to everyone who created open-source modules I could learn from and make songs with.
Thanks to Jerry Sievert and cschol for their help with QuickJS integration.
Thanks to Silvio Kunaschk for their help with continuous integration.
Thanks to Squinky Labs, Stoermelder, David O'Rourke, and Anthony Lexander Matos for technical advice.
Thanks to Omri Cohen for featuring my modules in livestreams.
Thanks to Ken McAloon for Latin language translations.
Thanks to Sophie for music theory advice.
Thanks to Heavy Viper for years of inspiring conversation about synths and music.
Thanks to Mog for Mog.
Thanks to my dog Ornstein for being a good dog.
Thanks to my music-making LGBBQT internet shitposting gang for introducing me to virtual modular synthesis as something that's not just for old guys with more disposable income than impetus to write fresh songs.
But most of all, thanks to YOU for using my art.
Lawyer's corner
Yeah, the licensing rules are a bit complicated. But the big idea is pretty simple: my modules are GPL3-or-later, my logo is copyrighted, the rest is less restrictive. If there's licensing incompatibilities (besides the intended virality of the GPL) lemme know and we'll figure out something.
Here goes the detailed breakdown:
The output of my modules belongs to you
It should go without saying that no sane courtroom would ever humor the idea the output of my modules is original enough to be my copyright, even that of Arcane, which directly outputs random data obtained from a server under my control.
Since courtooms are rarely sane, I explicitly relinquish any claim of intellectual property over the output you obtain by operating my modules, not that I believe I ever had any. Any song you make with them is yours alone.
Source code of individual modules
The code of the Aria Salvatrice Signature Series Synthesizer Modules is distributed under the GNU General Public License v3.0 or later. The modules come without any warranty and might recklessly endanger life and limb, the usual.
Re-usable libraries
Not that the code is very good, but some libraries I created for my own use are available under the less restrictive terms of the Do What The Fuck You Want To Public License, to allow every creator to do what the fuck they want. The files in question are src/javascript.hpp, src/lcd.hpp, src/polyexternalscale.hpp, src/portablesequence.hpp, src/prng.hpp, src/quantizer.hpp, and src/widgets.hpp.
Faceplates
CC-BY-SA-4.0, with the exception of my signature logo, which is copyrighted, and generally not directly baked into my faceplate SVG files. You may freely distribute your faceplate edits. If you enjoy making custom skins, bear in mind that some of the colors used in my modules are defined in the code, not the SVG files.
Components (knobs, jacks, etc)
WTFPL graphics and code (in src/widgets.hpp). But if you re-use them, I request you do not entirely re-use my signature color scheme in your own modules. This request is not legally binding, as it'd make licensing complicated. Because I use a limited palette, it's easy to replace most colors in my SVG files using search and replace in a text editor.
My collection of modules and widgets does not use VCV's component library at all, and is thus unencumbered by its licensing restrictions.
Signature / Logo
Copyrighted. It's mine.
If you edit my code to use my modules as a base for your own altered modules, remove my signature from your faceplates, even if you think your changes are trivial: I don't want to endorse and take credit for something I didn't vet or personally participate in.
If you are faithfully porting my code to a new environment, are compiling binaries for another platform, or are otherwise distributing my modules as I designed them, keep the signature. If unsure, just ask.
The easiest way to remove my signature from every module is by blanking or replacing the graphic in the res/components/signature.svg file, and removing it from the blank plate: res/faceplates/Blank.svg.
Project name
Aria Salvatrice is the name I go by as a person. Distributed forks of my code should not make my name part of their title. The VCV project, and software libraries that distribute my code, should not distribute a fork maintained by a different person under my name without my explicit permission. To do so would impersonate me.
Distributed forks of my code should mention I'm the original author, but shouldn't use my name in a way that can be construed as implying my authorship of their fork, or my endorsement of their fork.
While the VCV project's policy allows taking over inactive plugins in its library, including those that are named after their author, I am requesting for its ethics guidelines protecting the brand names of companies to be extended to my own name as a human. I am also requesting the same out of any other project distributing my software: it is a long-standing tradition of free open-source software that forks should go by a different name, if only to avoid user confusion.
If you are faithfully porting my code to a fork of VCV Rack, are compiling binaries for another platform, or are otherwise distributing my modules as I designed them, but need to apply trivial compatibility patches to make my software work on your platform, you should keep the name, and the signature. The deciding factor is whether you are distributing my software as I designed it. If you alter it, you should rebrand it.
The name of the individual modules in my collection does not have to be changed. Whether to keep the name of the modules the same, change them, or name them a variation of the original name, is left to the forker's discrection.
Git forks of my code on sites such as github, created for example to experiment with my code, forks that are not directly distributed to end users but only seen by an audience of developers, are obviously not considered distributed forks, and are thus exempt from this request, as it is obvious to the intended audience that this is a fork, and no impersonation is intended.
Graphics for the Arcane module
The Arcane module uses Tarot cards altered from Yoav Ben-Dov's CBD Tarot. Its graphics are distributed under the CC-BY-NC-SA, to comply with the license of the graphics used. That includes the faceplate, as it uses a pattern taken from that tarot deck.
Fonts used
- The LCD Font is an edited SVG export of the Fixed_v01 font by Orgdot, released under a custom MIT-style license.
- The segment display font is DSEG by Keshikan, released under the OFL 1.1. A TTF file from that family is distributed with the modules.
- Titles are typeset in Francois One by Vernon Adams. This font is not redistributed with the modules.
- Labels are typeset in Nova by Wojciech Kalinowski. This font family is not redistributed with the modules.
Libraries used
- QuickJS by Fabrice Bellard is used in some modules under the terms of the MIT license
- TonalJS by danigb is used in some modules under the terms of the MIT license
Copyright assignment
By sending me pull requests, you assign their copyright to me, allowing me, in perpetuity, to license your contributions however I see fit.
Right now, that means a mix of GPL-3.0-or-later and WTFPL, but I reserve the right to relicense it or re-use code in proprietary projects in the future.
This is a personal project where I don't expect external contributions to be any more complex than small-scale bugfixes and feature additions, so I think that's reasonable. If you think that's unreasonable, don't contribute. You will be asked to acknowledge this policy the first time you send me a non-trivial pull request. See CONTRIBUTING.md for more information.
Contact
You can send me bug reports on my GitHub project page.
You can send me dog gifs to [email protected].
ttyl,
