Reconstruct by AudioFusion is one of those free plugins whose name suggests one thing while the software may do another, so the smart approach is to test it with a structured session rather than guess. This scenario-led guide follows a producer, call her Mia, who has a stale four-bar loop at 95 BPM and wants to know whether a new free effect can rescue it. The method works with any unfamiliar effect. For actual features, formats and price, rely on the developer's official page.
The scenario
Mia's loop: a dusty drum break, a Rhodes-style chord and a bass. It sounds correct but bland. She has 30 minutes to decide whether the plugin earns a place in her template.
Minutes 1 to 5: place it and set safe levels
- Create a new audio track with the drum loop only, so you hear the effect clearly.
- Insert the plugin last in the chain.
- Lower the plugin's output about 3 dB before adjusting anything, in case it is loud.
- Note the meter: if the loop peaks at or above -6 dBFS, reduce the track fader.
Minutes 5 to 12: explore every control once
Turn each knob from minimum to maximum while the loop plays, listing what changes: level, tone, stereo width, time or texture. Write a one-line description per control. This tells you what category the effect belongs to and exposes anything that behaves oddly.
Minutes 12 to 20: three test signals
| Signal | What it reveals |
|---|---|
| Drum loop | Effect on transients and rhythm |
| Sustained chord | Effect on tone, movement and stereo image |
| Full mix | Whether it helps or harms overall balance |
Mia found that a light setting worked best on the chords, while the drums needed the mix control turned down. Yours may differ; the point is to pair each source with a suitable amount.
Minutes 20 to 25: the level-matched A/B
- Loop 8 bars.
- Toggle the plugin every 4 bars.
- Adjust the plugin output until both states sound equally loud.
- Close your eyes and pick the one you like without looking at the screen.
If you consistently prefer the processed one, keep going. If it is a toss-up, the plugin is not adding value for this material.
Minutes 25 to 30: stress test
- Duplicate the instance four times and check CPU.
- Save the project, close it, reopen, and confirm settings reload.
- Render an offline bounce and compare with real-time playback. They should match.
Decision matrix
- Keep in template: works on at least two source types and is stable.
- Keep as specialist: good in one situation only.
- Remove: unstable, or nothing you cannot do with a stock plugin.
Common problems with unknown free plugins
- Sudden loudness jump on load. Always lower the output first.
- Presets that save wildly hot levels.
- Windows that do not resize on hi-res screens.
- DAW scanning issues: check that you installed the right format (VST3 versus VST2) for the host.
Where it fits in a chain
Creative effects usually go before EQ and compression so that you shape the result afterward. Correction tools go first. Keep a healthy signal from the start, as described in the gain staging guide. For time-based additions, a companion such as a multiband delay pairs well.
FAQ
Should I put a new plugin on my master right away?
No. Test on a single track first; a master insert affects everything.
How do I choose between two similar free plugins?
Level-match and run the blind toggle above. The one you choose without looking is your answer.
Is Reconstruct still free?
Check the official developer page for the current price and availability.
More candidates for testing sit in the free VST collection.
Bonus: build a reference loop
Keep one four-bar loop that you know well and use it to test every new effect. Because you know how it should sound, differences become obvious faster. Store it in a dedicated template with a spectrum analyser and level meter already loaded, so each test starts from the same baseline and results stay comparable across weeks.
Worked example: three quick settings passes
Run the plugin at a subtle, medium and extreme setting on the same chord loop. Subtle should feel like a small improvement, medium should be clearly audible, and extreme shows the limits. Note the medium setting numerically and the point where it breaks. Producers often stop at a spot between subtle and medium. Save that as your default preset and label it with the source it worked on.
Genre tips
- Lo-fi hip-hop: use gentle settings and level match; let the sample carry character.
- Electronic: try it on sends, so you can blend it under the main signal.
- Pop: keep it subtle on lead vocals and stronger on background layers.
More troubleshooting
If the sound changes when you close and reopen the project, check the automation and preset saving; if it introduces latency, enable delay compensation in your host and re-record any live takes.
Take notes as you test
Write down the settings for anything you like, even roughly, such as "medium amount, mix 40 percent, works on chords". Notes make it easy to reproduce a sound in a later session and turn a one-off happy accident into a repeatable tool. Add the tempo and source, since these often change what setting works best.
