Synthwave

What Reveal Sound Synthwave contains

Synthwave combines 90 presets for Spire and ReSpire with eight construction kits, MIDI and 24-bit/44.1-kHz WAV material. Most presets provide movement through Macro MOD controls and the ModWheel. It is therefore more than a static bank, but it does not include a Spire licence and its title alone does not prove that any patch emulates a named vintage instrument.

The useful starting point is a baseline inventory. Treat the 90 programs as sound-design starting states and the eight kits as arrangement-study material. Keep those two branches separate in the browser so a producer can evaluate patch usefulness without letting finished demo assets dominate the judgement.

Build a role map before choosing favourites

Create project folders for bass, chord, lead, pluck, pad, sequence, effect and any additional role that appears during auditioning. Do not assume the source guarantees a fixed category count. Assign a role only after playing the preset across several octaves and listening inside a simple kick, bass and percussion context.

Give each retained patch one practical note: strongest register, useful controller range, tail length and the arrangement position it could fill. A small set of clearly documented programs is more valuable than a long favourites list that merely remembers an impressive first impression.

Audit Macro MOD controls as performance states

Test every promising preset in its saved state and at several Macro MOD positions. Match level while comparing because a louder or brighter state can appear more useful than it is. Record whether the macro changes filter tone, modulation depth, effect balance, layer density or another audible dimension, without guessing at an assignment that the interface does not confirm.

Convert useful positions into named arrangement states such as restrained, moving and open. If the extreme value becomes harsh or crowded, limit the automation range in the DAW and save a project-specific copy. This produces repeatable performance behaviour without rewriting the supplied bank.

Design a separate ModWheel test

The ModWheel may interact with a macro or move a different group of parameters. Test minimum, centre and maximum positions with held notes, repeated notes and a musical phrase. A slow sweep reveals discontinuities; stepped values show whether the program can support precise verse, build and main-section changes.

Check the transition in mono and at reduced monitoring level. Wide effects or high-frequency lift can exaggerate motion in headphones. Keep a controller note with the preset so the useful range survives project handoff and later recall.

Use the eight construction kits as eight questions

Open one kit at a time in a disposable analysis session. Assign each a different question: section length, low-end balance, melodic hierarchy, fill placement, automation, transition density, effect-tail management or contrast between breakdown and main section. This avoids treating the kits as eight interchangeable templates.

After each review, write one observation and build one original experiment that changes the musical material. Mute supplied melodic parts before rebuilding. The aim is to extract transferable arrangement logic, not to reproduce the demonstration or imply authorship of its composition.

Compare MIDI with the rendered WAV result

The included MIDI shows note timing and structure, while the 24-bit/44.1-kHz WAV material captures a rendered outcome. Place corresponding assets together and compare phrase length, velocity, articulation and processing. Replace the supplied sound with a personal Spire patch to identify which qualities come from the notes and which come from synthesis or effects.

Preserve the original files in a read-only archive. Save rewritten MIDI and edited audio in a project folder with clear names. That separation prevents accidental redistribution and makes it obvious which elements have been transformed for the session.

Create a baseline palette rather than a nostalgia label

The product name supplies a broad stylistic frame, not a verified list of machines, records or artists. Judge programs by audible function: envelope shape, harmonic density, movement, width, transient behaviour and effect footprint. Describe those qualities in project notes instead of attaching unsupported hardware or artist comparisons.

A baseline palette can include one dependable low-end sound, one compact chord voice, one controllable lead, one pad that leaves vocal space and one transition texture. Filling those roles first exposes genuine gaps before additional patches are added for colour.

Test bass and chord interaction

Place bass candidates beneath the project kick and compare them at equal loudness. Check note length, sub stability and low-mid buildup. Reduce unnecessary width in the lowest range and verify phase in mono. A preset that sounds large alone may still need fewer voices or less effect return inside a complete rhythm section.

For chords, try short stabs and sustained voicings. Listen for release overlap and for modulation that obscures harmonic rhythm. Adjust the patch or voicing before using broad corrective EQ; a simpler register or shorter envelope often creates more space with less processing.

Evaluate leads, pads and moving parts

Lead presets should survive both connected and separated notes. Test glide, envelope retriggering and effect tails across a real phrase. Automate Macro MOD or ModWheel only after the static line reads clearly. Movement should support phrasing rather than compensate for weak note choice.

Hold pad and sequence candidates long enough to hear their complete modulation cycle. Check tempo response and print a reduced-effects version when possible. A moving program can occupy more arrangement space than its average level suggests, so audition it beneath the intended lead or vocal layer.

Arrange a producer and DJ-oriented stress test

Build a short session with intro, first section, transition, breakdown and return. Limit the test to a handful of bank presets and one reconstructed kit lesson. This reveals whether controller changes create useful energy stages and whether tails leave a clean downbeat for club-oriented arrangement changes.

Check the result at low level, in mono and against a reference only for balance and pacing. Do not claim that the bank recreates the reference or was used by its artist. The test measures translation inside the producer’s own session.

Keep rights and collaboration records

The imported listing describes the content as royalty-free, but the current licence supplied with the purchase remains the controlling document. Store that licence and the receipt beside the untouched download. Record any supplied MIDI or WAV asset used in a release with its source filename and the project edit.

Share rendered project parts or authorised session files rather than the complete commercial source folder. Construction-kit availability is not permission to present the supplied composition as original work. Rewrite musical material where authorship matters and retain provenance through collaboration.

Requirements and reliable recall

The presets require a separately licensed compatible Spire or ReSpire installation. The imported source states Spire 1.1.16 or higher and ReSpire 1.0.7 or higher; verify the live listing before installation because current compatibility can change. MIDI and WAV assets need a suitable DAW or sampler.

Archive the preset bank, note the synthesizer version and save important edited programs with the project. Render critical dry and processed stems. Those steps protect long-term recall if a collaborator lacks the soundbank or a later software version changes the result.

Strengths, limits and Vol.2 comparison

Vol.1’s clearest strength is a defined starting system: 90 programs, expressive controller paths and eight kits for structured study. It suits a producer who wants a compact baseline library and is willing to document controller behaviour instead of browsing by name alone.

Its limits are equally clear. It is not the synthesizer, its style title proves no specific emulation, and kits can narrow originality when copied. Synthwave Vol.2 is a separate 100-preset, seven-kit product; compare role coverage and existing ownership rather than assuming the higher volume number automatically replaces this bank.

Sources and related Reveal Sound guides

This guide uses the imported product record for the 90 presets, eight kits, MIDI, 24-bit/44.1-kHz WAV content, controller behaviour and royalty-free wording. Reveal Sound’s official Spire page, manual and store catalogue provide manufacturer context. Verify the live offer and licence before purchase or release.

Use AudiobyRay’s internal links to Spire, Synthwave Vol.2 and the Reveal Sound catalogue guide. Keep each SKU’s counts, media and licence distinct, and avoid transferring unsupported hardware or artist claims between related pages.