From 2902ca4af3a87597e90e207222299505a3d07da5 Mon Sep 17 00:00:00 2001 From: Andrew Belt Date: Sun, 15 Aug 2021 06:17:54 -0400 Subject: [PATCH] Update email address to support@vcvrack.com. --- Issues.md | 2 +- MenuBar.md | 2 +- PluginDevelopmentTutorial.md | 2 +- PluginLicensing.md | 4 ++-- Polyphony.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Issues.md b/Issues.md index 1855a21..e680078 100644 --- a/Issues.md +++ b/Issues.md @@ -1,6 +1,6 @@ # Bugs and Features -VCV offers technical support of commercial VCV plugins by emailing . +VCV offers technical support of commercial VCV plugins by emailing . For technical support of VCV Rack, open-source VCV plugins, and third-party plugins, refer to the correct category below. diff --git a/MenuBar.md b/MenuBar.md index 5ccc881..4f85f4e 100644 --- a/MenuBar.md +++ b/MenuBar.md @@ -82,7 +82,7 @@ Due to [simultaneous multithreading](https://en.wikipedia.org/wiki/Simultaneous_ ### Login Logs into your VCV account registered at [vcvrack.com](https://vcvrack.com/). -Email for account assistance. +Email for account assistance. ### Update all Updates and downloads all new plugins and plugin versions added to your VCV account. diff --git a/PluginDevelopmentTutorial.md b/PluginDevelopmentTutorial.md index 13b941d..74040d1 100644 --- a/PluginDevelopmentTutorial.md +++ b/PluginDevelopmentTutorial.md @@ -37,7 +37,7 @@ Version [1.0.0]: License (if open-source, use license identifier from https://spdx.org/licenses/) [proprietary]: CC0-1.0 Brand (prefix for all module names) [My Plugin]: Author []: VCV -Author email (optional) []: contact@vcvrack.com +Author email (optional) []: support@vcvrack.com Author website URL (optional) []: https://vcvrack.com/ Plugin website URL (optional) []: Manual website URL (optional) []: diff --git a/PluginLicensing.md b/PluginLicensing.md index 69b4833..7ea06a4 100644 --- a/PluginLicensing.md +++ b/PluginLicensing.md @@ -1,6 +1,6 @@ # Plugin Licensing -VCV Rack is free/open-source software, but you should still familiarize yourself with the [VCV Rack licenses](https://github.com/VCVRack/Rack/blob/v1/LICENSE.md) before releasing your plugin, to avoid misuse of intellectual property. If in doubt, send your licensing questions to [contact@vcvrack.com](mailto:contact@vcvrack.com). +VCV Rack is free/open-source software, but you should still familiarize yourself with the [VCV Rack licenses](https://github.com/VCVRack/Rack/blob/v1/LICENSE.md) before releasing your plugin, to avoid misuse of intellectual property. If in doubt, send your licensing questions to [support@vcvrack.com](mailto:support@vcvrack.com). ## I want to release my plugin under the [GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.en.html) (GPLv3) free/open-source license. @@ -26,7 +26,7 @@ If someone makes a fork of your non-GPLv3 open-source plugin that is not a Rack ## I want to sell my plugin commercially under non-GPLv3 terms. -VCV offers commercial royalty licensing for Rack plugins by emailing [contact@vcvrack.com](mailto:contact@vcvrack.com). +VCV offers commercial royalty licensing for Rack plugins by emailing [support@vcvrack.com](mailto:support@vcvrack.com). This license also includes permission to use the [Component Library](https://github.com/VCVRack/Rack/blob/v1/include/componentlibrary.hpp) graphics by [Grayscale](https://grayscale.info/), which are normally licensed for non-commercial use only. It is recommended to contact VCV as early as possible in your development process to make sure the license agreement is ready well before you release your plugin. diff --git a/Polyphony.md b/Polyphony.md index bd934ea..194e7d1 100644 --- a/Polyphony.md +++ b/Polyphony.md @@ -36,7 +36,7 @@ This means there is only one type of cable in *Rack*: polyphonic. Zero-channel cables are also possible, which make modules think the cable is unpatched. This can be useful if a module has a particular unpatched behavior you want to use but don't want to actually unpatch the cable. It is even possible for a hypothetical module to automate the number of channels of its outputs, in order to virtually patch/unpatch a cable according to a gate signal. -(Email contact@vcvrack.com if you know or made a module that does this.) +(Email support@vcvrack.com if you know or made a module that does this.) Modules that support polyphony almost always have better performance than using multiple copies of monophonic modules, often as high as 4x (25% the CPU). This is because polyphonic modules are usually written with [SIMD instructions](https://en.wikipedia.org/wiki/SIMD), and/or take advantage of compiler auto-vectorization, which allows your CPU to process 4 channels (with [SSE](https://en.wikipedia.org/wiki/Streaming_SIMD_Extensions)) simultaneously on the same core.