Spectraforge Audio

Plugin workflows

How to investigate aliasing in a distortion plugin

Use a simple pitch sequence and controlled quality changes to investigate suspicious components, without mistaking every bright harmonic for aliasing.

Aliasing can occur when nonlinear processing generates content above the Nyquist limit that folds into the sampled spectrum. Brightness alone is not evidence of it: wanted harmonics, downstream overload and other digital effects can sound aggressive too. Check the dry source, drive and output stages first.

By Spectraforge Audio2 min read
Published

Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.

Look for a cause, not just a bright sound

Worked calculation, not a plugin measurement: at 44.1 kHz, Nyquist is 22.05 kHz. A generated component at 26 kHz folds to 18.1 kHz in the simple first-fold case (44.1 − 26). That explains why an artifact may move differently from the expected harmonic series; it does not predict how much a particular plugin emits.

Make a reproducible practice test

Use a clean sine-wave generator at a comfortable level. Save and inspect its dry render first; a bright oscillator or sustained instrument may already contain suspicious components. Disable unrelated pitch effects, modulation and feedback. Play separated notes followed by a slow pitch bend, keeping the same instance, drive and output setup. Save short renders rather than comparing a changing sound from memory.

If the plugin documents oversampling, repeat in two modes and level-match after processing. Saturn 2 documents oversampling of its distortion section; another control called High Quality may do something else. Follow the selected manual rather than assuming all quality switches have the same purpose.

Interpret the comparison conservatively

Follow a suspicious component in a spectrogram with the analysis settings held fixed. A component that changes with the documented quality mode is useful evidence to investigate. A descending trace alone is not proof: modulation, pitch processing and feedback can also create unusual motion.

A separate project sample-rate comparison adds variables, including conversion and possible plugin behavior changes. Raising the rate of an already recorded artifact cannot remove it. Change the processing that creates the sound and preserve the original production project.

Make a musical decision or request a technical diagnosis

Return the preferred setting to the actual part and compare in context. Check CPU, latency and the export. Keep higher quality when it removes a meaningful distraction at an acceptable cost; otherwise try less drive or another effect style.

For a firm diagnosis, give the developer the reproducible source, plugin version, drive, quality and session rate. This guide proposes an investigation, not a measured alias-rejection test. Deliberate bit crushing or rate reduction may be the texture you wanted in the first place.

Technical references

Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.

Help

Spectraforge Audio support

Send us a message and we’ll reply by email. Zoho Desk handles your message and any attachments. Privacy policy

Form not loading? Email info@spectraforgeaudio.com.

Your privacy choices

With your permission, Google Analytics measures site use and Meta measures advertising performance. Both are optional. Privacy policy

Privacy settings

Choose which optional tools can run. Your purchases and licence access work with both turned off.