Most free plugins get judged in about thirty seconds: twist a knob, decide it sounds cool, move on. That is how you end up with a plugin folder of forty things you never use. Here is a structured 15-minute test that works for Regrader or any other new effect. I do not list Regrader's controls or specs here, so take those from the developer's official page and use this procedure to decide if it earns a slot.
Before installing: the hygiene pass
- Get the installer only from the developer's own site or a store they link to.
- Note the file type. Plugins ship as installers or zip archives containing VST3, AU or similar. An unexpected .exe inside a Mac download, or a plugin that asks for a key generator, is a hard stop.
- Scan the download with your operating system's built-in security tools.
- Install to your standard plugin folder and rescan in your DAW. Do not scan on a project you care about; use a blank one.
The 15-minute test
Minutes 1 to 3: stability
Insert it on three tracks at once, save, close the project, reopen. If the settings survive and the session loads without a crash, it passes. Also test freeze or bounce.
Minutes 4 to 7: level-matched A/B
- Play a loop with drums and a vocal or lead through the plugin.
- Match output level so that bypass and engaged are within 0.5 dB on your meter.
- Alternate at least ten times. Judge with your eyes off the interface.
Minutes 8 to 10: null test
Duplicate the track, invert the polarity on the copy, and run one copy through the plugin at neutral settings. Silence means it is transparent when set flat. A faint residue means it colours the signal even at zero, which is fine for character tools, but bad for a utility.
Minutes 11 to 13: extremes
Push every knob to its limit on a short loop. Look for clicks, digital screaming, or runaway volume. Note whether reasonable middle settings sound good, since that is where you will actually use it.
Minutes 14 to 15: CPU
Duplicate the instance 10 times and watch the DAW's performance meter. A plugin that uses 3 percent per instance will hurt in a big session.
Scorecard
| Test | Pass | Fail |
|---|---|---|
| Reload session | Settings intact | Reset or crash |
| Level-matched A/B | Clearly better on at least one source | Only louder |
| Flat null | Silent, or purposeful colour | Unexplained noise or shift |
| Extremes | Musical or safe | Clicks, blasts |
| CPU x10 | Comfortable | Session stutters |
Keeping a testing log
Testing only helps if you remember the result. Make a note for each plugin with four fields: what job you tried it for, which settings worked, what annoyed you, and a final verdict of keep, situational or delete. A single line per plugin is enough. After you test five or six, patterns appear: perhaps you keep favouring tools with big, readable meters, or you dislike interfaces with tiny text. Use that to filter future downloads before you even install them.
Also record the plugin format and version you installed. When a DAW update breaks something a year from now, that note saves an evening of guessing.
Common failures and quick fixes
- Not visible in the DAW: check whether you installed 32-bit on a 64-bit host, or the wrong format for your DAW, then rescan.
- GUI blurry on a high-DPI monitor: see if the plugin offers a scaling option.
- Presets do not load: some installers place presets in a separate folder; look in the manual.
Sample test session for an effect plugin
Use a 90 BPM drum loop peaking at -6 dBFS and a dry vocal phrase peaking at -10 dBFS. Run the drum loop through the plugin at default settings, then at roughly a third of the range on each main control, noting the meter movement. Repeat with the vocal. If the drums improve but the vocal turns harsh, the plugin is a drum tool, and that is a fine outcome. Save the two settings as named presets like drum-third and vocal-light so your test becomes a starting point rather than a throwaway.
Genre lens
Electronic producers should test on a kick plus bass pair, because low-end behaviour decides usefulness. Singer-songwriters should test on an acoustic guitar and voice, where noise and colour become obvious. Hip hop producers should test on a sampled loop with vinyl crackle, since some processors exaggerate noise.
FAQ
How many free plugins is too many?
Keep one favourite per job: an EQ, a compressor, a reverb, a saturator. More than that leads to choice paralysis.
Should I trust a plugin with a high download count?
Popularity is not a security check. Follow the hygiene pass every time.
Is a limited-time free plugin worth grabbing?
If it passes the test, yes. If not, skip the pressure to hoard.
Related reading
Set up sane levels before testing with the gain staging guide. A known-good starting comparison is the LAEA optical compressor, and the wider free VST list is handy for benchmarks. Verify Regrader's current price and download page on the developer's official site.
Get Regrader from igorski
