The C-C- -01 is my entry into the KVR Developer Challenge 2021. The voting and downloads period of the challenge is underway right now, until the end of the month, July, 2021! You need a KVR account in order to vote, and you have to have been active on their Forum, I think, also, in order to vote. There may be other requirements. See the rules at the 1st link below, they should be at the bottom of the page, you'll have to click a blue link to show/hide the rules, then look for the "Voting" (not in quotations, though) section. You can also check out and download all of the plug-ins that are featured in the challenge there as well:
Quickly, I'll tell you (so you don't necessarily have to read the more detailed version with good technical stuff and known issues, below, but it should help you, there are warnings about some stuff), the C-C- -01 v1 is a Signal Enhancer. It is a 64-bit Windows VST ® 3 plug-in. It can:
- EQ/Filter (7-bands).
- Peak Follow (with RMS, Oscillators, and Noise also, and also change the Oscillators' sound response curve going into the Oscillators Peak Followers, and change both response curves for both Peak Followed signals), and change the signal's Attack and Decay moderately.
- Blend RMS and the Peak Follower.
- Blend Saturation and the previous EQd, Filtered, and Peak Followed Signal.
- Subtract the EQ and Filtering from each previous signal at each EQ band, and/or subtract the entire EQ process from before Equalization, and use "Non-EQd Makeup" controls to boost back (and beyond), in parallel, the remaining signals after the EQd signal was subtracted.
- Oversample (Using the Effect Off feature in the plug-in will not bypass the Oversampling, though).
- Use dual-bands, can split Stereo signal into Mid/Side, all things can be manipulated per channel.
- Use Linked Controls.
- Use Control (hold)-Click and drag to control the knobs and slider movements with greater precision.
Key Features/Notes/Known Issues/Problems, and some things you can do with the C-C- -01:
- I cannot fix DAW/Host compatibility issues, that might be a SynthEdit problem. Also, Automation Parameter names may not completely show inside of some DAW/Hosts.
- All Parameter Automations have not been tested, some have, I did this only because all controls of themselves have been tested during the testing and development phase. I cannot fix Parameter Automation problems if they arise, unless there is a setting I've missed in the internal working of SynthEdit, maybe I can fix that. I've plugged in all of the SynthEdit signal wires properly, as far as I know.
- Has Peak Following (with a 2nd Peak Follower using Oscillators and Noise), RMS (for both Peak Followers), EQ/Filters (with a added subtractive process that subtracts the EQ'd signal from it's predecessor, and allows you to blend back in the remaining signal, plus add a boost of that signal, or just use the subtractors on the whole EQ process, and then use the LMeqs and RSeqs sliders to blend back that remaining signal from before the entire EQ process, or a combination of the two sets of blend-back sliders for creative effects. I call this process "Non-EQd Makeup" on the plug-in GUI, above those blend-back slider controls), and Saturation.
- Peak Follower 1 (called Peak Follower in the plug-in) operates on the Main Input Signal, after EQ/Filters. Peak Follower2 also operates on the Main Input Signal, after EQ/Filters, using the Oscillators/Noise. Both Peak Followers modulate (I think that's the term) the volume control of separate sets of VCAs, one after the other (the 1st Peak Follower's VCAs to the 2nd one's VCAs), for each Peak Following process.
- Has Left/Right and Mid/Side Input Signal Selection.
- Has linked controls (internally, not on screen, also the Oscillators section has no linked controls), as well as fully independent control of both signal halves throughout most of the plug-in. Use the Left/Mid set of controls when using linked controls.
- Has volume response curve options for both halves of the signal (see additional notes below for more about this).
- 7-band EQ: 6 bands of Biquad modules, band 7 is a Band Shelf Mid Range Boost/Cut. The EQ processing order is: EQ1 to EQ7, consecutively.
- Wet/Dry mix for the entire FX process, as well as a Saturation blend and an RMS to Peak Follower blend per Peak Follower.
- Has Oversampling up to 32x, and FIR type (Using the Effect Off feature in the plug-in will not bypass the Oversampling, though).
- Has Channel On/Offs to isolate your signal.
- Use the Input Trim and Drive Controls to find the sweet spot on each of the 3 Saturators, and make up gain lost or boosted using the Effects Makeup Gain, so you can compare the before and after of the whole FX process. Drive your Sides signal into Saturator 1 at 30% Wet while pushing the Mids into Saturator 3 at 70% Wet for smoother, more subtle distortion/saturation sounds (Hypothetically speaking. each Saturator is different, and may still have a harsher edge to it, also depending on your setting, but this process helps to smooth that out a bit).
- (Also hypothetical, depending on your sound's frequency range) Use a Notch Filter to cut an area, then boost back its' remaining predecessor signal to get rid of some of those "nasal-y" artifacts, careful though, too much can almost ruin your sound. I think some phase shifting can occur, but I have not examined that. Basically, a HiPass or LoPass, Notch, Band Pass, or any "static type" filter that got rid of any frequencies can now add just some, or more, of those frequencies back using the "Non-EQd Makeup" Gain Sliders. Creative effects can be found by randomly moving and setting the Non-EQd Makeup sliders before/while EQing. In one instance, I tried cutting a large amount (-60 db) using a Peak EQ Type with an average to moderate Q setting (I think the Q was somewhere in the range of .2 to 10), then boosting the Non-EQd Makeup in moderate to large amounts, and the effect was good.
- Be careful when using the Oscillator Monitor Function, the volume may be intensely loud. Be sure to set your volumes low before you turn on the Oscillator Monitor. It is there to let you set a balance, if you want, but you can really push the volume into the Peak Followers if you want, but you probably don't want to monitor that louder sound, it's very distorted, and Oscillator waves at low, mid-range, and high frequencies might damage your ears (maybe all of them can actually, I actually don't know, and I'm no expert). The real effect was designed for the Peak Follower, so no Oscillator sounds are actually heard when using it for it's intended purpose, but you can hear the effect on the audio, it subtly equalizes and can boost clarity in your signal. Try a Sine at 1500 Hz on one channel and some Pink Noise on the other and you will hear for yourself. Try the Decay at max (about 5 o'clock) for more body. At the shortest Attack and Decay settings, transients can be more audible with a greater clarity of energy, but not drastically, depending on the setting. At the longest settings, smoother, bigger sounds are achieved. Add RMS and change the Rate Control to hear the difference, and blend between the Peak Follower before the RMS using the RMS Blend control for a natural balance. It is subtle. Use White Noise and Pink Noise together in a Mid/Side configuration to have the Peak Follower put Pink Noise on just the Sides signal, and White Noise on the Mids, and you can balance the volume going into the Peak Follower (it is just subtle to hear it), but when using Oscillator waves (Sine, Saw, etc.) near or at the same frequency and volume (in Mid/Side mode) you may notice more of a Left or Right balance to your signal, I believe since the Oscillators are Mono, not Stereo. I included one Oscillator for each signal half. So, Oscillator wave types and/or frequencies far enough away from each other should give a Mid/Side signal a chance of being encoded/decoded by the process, which means for more fun in your Peak Following. The White and Pink Noise seems to always work in Stereo or Mid/Side, though. Muddy bass can be refined a bit by using an oscillator at 100 to 250 Hz, or somewhere where you hear it work. Just use the volume sliders at the upper right of the Osc Panel page of the plug-in, after you choose your Response Curve type there.
- The Peak Meters may be slightly inaccurate, they show the level below clipping, while it may be that the signal is just clipping a bit. Sorry. As far as I've seen it's only on very quick, loud peaks that it won't show, otherwise it seems fairly accurate (compared to my DAWs meters, it is just a little below), but I'm no expert. I'm not quite sure how to fix this.
- The Main Panel's bottom left features a set of VCA Response Curve choices (I forgot to label them, sorry, you'll see the words, Decibel when you load the plug-in), they apply only to the Main Signal's 1st Peak Follower (called Peak Follower on the plug-in GUI, it's the one that doesn't use Oscillators). All of the Standard Volume knobs throughout the plug-in have the VCA Response set to the Decibel Curve. I couldn't decide if I should change that, and I also didn't have room to give another set of options for you to choose that. I think it's best if you all can choose it, so I plan to add it later, in a newer version someday, with more Oscillators also.
- Currently, there's no internal preset browser. I have experienced issues, in a plug-in created using an older version of SynthEdit, where a saved DAW/Host version of a .VSTPRESET would not be recalled in a project, for some reason, I do not know the reason why though. I don't know if that issue is present here, or if it's even a SynthEdit problem at all, it could be that my DAW/Host version is older. Also, with this version of the plug-in I've experienced an issue where a saved .VSTPRESET in my DAW (which is a 2 or 3 years older) would not recall all of the values that I saved in the preset, so the preset is now different after saving it, according to what the plug-in shows when it loads it (some buttons and choices were totally different), maybe the information in the .VSTPRESET is actually correct, but I have no way of knowing for sure what the issue is. Maybe it is actually because I did not add a Preset Browser within the plug-in, who knows.
- I have not tested MIDI Learn with a hardware controller, so I don't know if it works.
- You can still change the Response Curve types even if the Peak Followers are off, but the Response Curve types on the top-middle section of the Osc Panel should not work. The Response Curve types at the middle-right section of the Osc Panel should still work.
- The EQ bands might give a "sound" to the plug-in at the default settings (when you load the plug-in), maybe it's good for you, or not, depending on the situation maybe. You can just turn the EQ bands off, and also save a .VSTPRESET in your DAW/Host with them off.
- Currently, sidechaining does work, as far as I know, sorry.
"EULA" for the VST ® 3 plug-in titled "C-C- -01 v1", as well as any presets I release for/with it now or later.
I thought originally that I would have one "All purpose" "EULA" that would apply to my creations, but I realize now that each project might have specific differences and restrictions, because SDKs and tools available to create plug-ins, etc. can impose restrictions on their use and re-use for and in products created with them, and so, I see now that each creation should now have it's own separate "EULA", though some "EULAs" may end up being exactly the same, sort-of, basically, besides maybe some technical details about the product.
If this "EULA" should change, the most recent edition/version of it should be online at https://christophercarmichael-plugins-presets.blogspot.com at the page for this plug-in, and/or elsewhere if it was necessary. It could also be online at https://christophercarmichael-artistmusician.blogspot.com somewhere. The new edition/version will most likely be released as well for download.
I will attempt to never change the core purpose of this "EULA", unless there was a legal issue, I'm sorry for any confusion this may cause.
I don't know what I'm legally allowed to require you to do regarding the use of this plug-in and/or any presets (I'm not a registered Business or "doing business as").
This VST 3 plug-in is released by myself, Christopher Carmichael, under the terms of the Proprietary Steinberg Format VST 3 SDK license for binary plug-ins (which I have signed the Agreement for and am currently licensed), which is my set of rules that have to be followed in order to release a VST 3 plug-in in this binary executable format.
I'm sorry, but I don't know all of the laws that apply to what you (and myself) are allowed to legally do regarding the use of this plug-in and any presets. You should check for yourself (sounds horrible, doesn't it), if you think that there are laws/clauses that apply to your use case.
I know I can release a VST 3 Product to the public in this manner since I'm licensed to do so.
Possibly, I am releasing .VSTPRESET files for this VST 3 plug-in, "C-C- -01 v1" because I am allowed to do so, while following the VST 3 Usage Guidelines.
I have created this plug-in, and any presets, using software and plug-ins that have valid licenses and are designed for the purpose of creating plug-ins and presets. I was unable to find search engine results online about how to release a VST plug-in product, so I am writing this document to let you understand what I hope for regarding the use of this plug-in and presets.
Each Country, State, and Local Government might have a different set of rules regarding the use of this plug-in and any presets.
I am mostly certain that you are supposed to follow the United States Export Laws regarding the re-export of this plug-in and any presets.
This plug-in and any presets are/were released in the United States, in California by myself, Christopher Carmichael. You can e-mail me at email@example.com or firstname.lastname@example.org if you have issues and/or questions.
The "C-C- -01 v1" can only have limited support, due to the fact that I'm not a real computer and/or software programmer, and the program used to create this plug-in was used in a manner by me that doesn't allow for very technical modifications of the internal parts. I have only tested this plug-is on one (1) VST 3 plug-in host, and it performed quite well.
THERE IS NO GUARANTEE THAT THIS PLUG-IN AND ANY PRESETS WILL WORK FOR YOU! I'M VERY SORRY IF THEY DON'T.
I'D SAY ALL OF THAT "I CAN'T BE HELD LIABLE, INDEMNIFY ME" STUFF, ETC., IF I KNEW THAT I COULD, BUT I'M JUST A MUSICIAN AND CONTENT CREATOR TRYING TO MAKE SOME VST 3 PLUG-INS AND PRESETS, USING SOFTWARE, MODULES, AND PLUG-INS THAT ARE SORT OF PRE-PROGRAMMED AND HAVE FUNCTIONALITIES INCLUDED FOR THE USERS OF THEM. I JUST CONNECT SOME VIRTUAL CABLES AND WIRES, DIAL IN SOME SETTINGS, ADD GRAPHICS, AND THEN SAVE THE END RESULT AS A FINISHED PRODUCT, SO HOPEFULLY IT SHOULDN'T DO ANYTHING BAD TO YOUR COMPUTER SYSTEMS! IT WORKED ON MINE!
REGARDING THE DISASSEMBLING AND RE-USE OF THE VST 3 PLUG-IN'S INTERNAL PARTS, ETC., I SAY:
1) THIS IS NOT AN OPEN SOURCE PLUG-IN, MAYBE ONE DAY I'LL DO OPEN SOURCE PLUG-INS, I JUST DON'T HAVE THE TIME TO FIGURE IT ALL OUT.
AS FAR AS I KNOW, YOU NEED C++ Runtime 2015 and .NET 4.6 to run this SynthEdit plug-in. This plug-in that I'm releasing here was created using SynthEdit version 1.4.603.
I say here and now that you are allowed to use this FREE VST 3 plug-in and any presets, absolutely FREE, for commercial, non-commercial, and private use in your VST Workstations/Hosts/D.A.W.s, etc. (any software/host that utilizes the plug-in and any presets in the format that they were provided to you in here in this "C-C- -01 v1" content package, or a separate package I might provide at a later date). I don't know of any other use case scenarios that are allowed legally.
If you are using non-commercial or educational versions of Microsoft Windows that don't allow for commercial gain, then possibly this plug-in and any presets shouldn't be used for commercial purposes on those versions of Windows, but I actually don't know if I'm correct about this license type and use case, I just feel like it should be true because of this. You should check it out for yourself. The fine print will let you understand (or your lawyer will, Ha Ha!).
When you display a Font, you may be required in certain use cases to give and/or display credit to the Font owner or creator, or other people with rights and/or trademarks, or Vice Versa, to the Font.
* SynthEdit is a trademark of SynthEdit Limited, New Zealand.
:SynthEdit open-source Modules
* Copyright (c) 2007-2021 SynthEdit Limited
* All rights reserved.
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions are met:
* * Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* * Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* * Neither the name SynthEdit, nor SEM, nor the
* names of its contributors may be used to endorse or promote products
* derived from this software without specific prior written permission.
* THIS SOFTWARE IS PROVIDED BY SynthEdit Limited ``AS IS'' AND ANY
* EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL SynthEdit Limited BE LIABLE FOR ANY
* DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
* VST is a trademark of Steinberg Media Technologies GmbH, registered in Europe and other countries.
VST is a registered trademark of Steinberg Media Technologies GmbH.
The Microsoft supplied font, Arial, is used with permission from Microsoft.
Microsoft Windows is a trademark and/or a copyright of Microsoft, or Vice Versa.
All trademarks and copyrights are the property of their respective owners, and no affiliation with or endorsement by them is implied.
SynthEdit is a trademark of SynthEdit Limited, New Zealand