Synthwave Vol.2

What changes in Synthwave Vol.2

Synthwave Vol.2 is a separate Reveal Sound product containing 100 presets for Spire and ReSpire, seven construction kits, MIDI and 24-bit/44.1-kHz WAV files. Most programs expose Macro MOD and ModWheel transformations. It is not an automatic update to the 90-preset, eight-kit first volume, and ownership of one does not prove a licence for the other.

The right evaluation is therefore comparative. Vol.2 should add useful roles, controller responses or arrangement lessons that are not already covered in the studio. Create a clean inventory before merging its files with Vol.1 or any broader Reveal Sound folder.

Start with a duplicate-role audit

Choose five roles the current template already handles well and five gaps it still has. Audition Vol.2 against those needs at equal loudness. Tag a preset as additive only when its register, envelope, modulation, width or effect footprint solves a different problem—not merely because its name is new.

Keep three outcomes: replace an older favourite, add a genuinely distinct option or reject for now. This method prevents a 100-program expansion from becoming an undifferentiated browser list and makes the value of the separate purchase measurable.

Map Macro MOD behaviour for migration

For retained programs, record the saved Macro MOD position and listen at several controlled values. Describe the audible result rather than guessing which internal parameters move. Note whether the useful range changes density, tone, ambience or rhythmic motion, and limit the DAW automation when extremes become crowded.

If a Vol.2 patch replaces an older project favourite, copy only the musical role first. Do not copy automation values blindly: a similar macro position can produce a different response. Rebuild the curve by ear, print a level-matched comparison and keep the original track disabled until the migration is approved.

Treat ModWheel response as a second dimension

Test ModWheel separately from the macros with long notes, repeated notes and a phrase. Record minimum, middle and maximum states, then test slow and stepped automation. The goal is to find repeatable performance zones that can be recalled across intro, breakdown, build and main section.

Check whether combined Macro MOD and ModWheel movement becomes excessive. When both expand brightness, width or effects, one controller may need a narrower range. Document the chosen mapping with the project so another producer does not have to rediscover the safe area.

Run a seven-kit evidence log

Use the seven construction kits as seven focused audits rather than a sequence of demos. Assign questions such as transition length, drum density, bass-to-kick space, lead hierarchy, MIDI articulation, effect-tail control and breakdown contrast. Capture the observation before opening the next kit.

For every lesson, create an original eight- or sixteen-bar test with different notes and sound choices. If the idea still works outside the supplied arrangement, it is transferable. If it only works with the demo’s exact musical content, keep it as analysis rather than a production shortcut.

Separate MIDI knowledge from WAV character

Place matching MIDI and rendered WAV assets side by side. MIDI exposes note placement, rhythm and velocity; WAV reflects synthesis, processing and final audio. Replace the source sound, alter the progression and compare again. This identifies what can be learned structurally without copying the demonstration’s finished identity.

Keep original files read-only and create project copies for slicing, stretching or resampling. Name rewritten MIDI so it cannot be mistaken for the purchased source. Store licence and provenance notes with any rendered asset that remains in the release session.

Build an expansion matrix against Vol.1

Create rows for bass, chord, lead, pluck, pad, sequence, effect and transition roles. Add columns for Vol.1 favourite, Vol.2 candidate, controller advantage and mix consequence. The matrix turns a vague volume comparison into a concrete decision about replacement, expansion or redundancy.

Do not add preset counts together as if every program is unique in function. The products contain 90 and 100 presets respectively, but practical coverage depends on auditioning. A smaller set of complementary roles can be more useful than retaining every near-duplicate.

Check project versioning before committing

The imported source states Spire 1.1.16 or higher and ReSpire 1.0.7 or higher. Verify current requirements, then test saved sessions after any synthesizer update. Record the exact version used for approved sounds and keep an audio render beside critical MIDI.

When moving between computers, install the authorised synthesizer and bank before opening the project. Confirm preset paths and controller automation, then compare with the archived render. This migration check is especially important when Vol.1 and Vol.2 share similar folder names.

Stress-test low end and density

Audition bass candidates beneath the actual kick, not alone. Check note length, sub consistency, mono translation and low-mid accumulation. Compare with the existing project bass at equal loudness. Approve the new patch only when it improves the role or offers a deliberately different texture.

For dense chords, pads and moving sequences, listen beneath the intended lead or vocal. Controller movement may increase spectral occupancy even when the meter barely changes. Shorten releases, reduce voices or lower effects before relying on broad corrective EQ.

Create a controlled lead and transition test

Play lead candidates through legato and separated phrases, several registers and realistic effect levels. Test Macro MOD and ModWheel changes at section boundaries, then ensure tails do not hide the next downbeat. A compelling solo preset still needs a clear place in the arrangement.

Use one kit-derived transition lesson in a new musical context. Change rhythm, notes, sound selection and processing. The transition should communicate pacing without depending on the source demo’s composition or implying that a named artist used the product.

Organise the expansion for fast recall

Keep Vol.2 in its own immutable source folder. Create a curated project browser using role, register, controller type and intensity. Prefix edited patches with the project name and preserve the original preset identifier in notes. This prevents later confusion when both volumes are installed.

Review the curated list after several real sessions. Remove candidates that repeatedly need replacement and promote sounds that translate quickly. The objective is a dependable working expansion, not proof that all 100 programs were used.

Rights and collaboration boundaries

The imported listing describes the presets, samples and loops as royalty-free. Retain the live licence, purchase record and source filenames because that wording does not remove the need to follow the supplied terms. Record substantial edits and the destination project for any commercial audio asset.

Share rendered session material rather than the entire commercial bank or kit archive. Construction kits can teach arrangement relationships, but their supplied compositions should not be presented as original authorship. Rewrite musical content and keep collaboration provenance clear.

Strengths, limits and buyer fit

Vol.2’s strength is its combination of 100 controller-ready presets and seven kit-based studies. It is most useful for an existing Spire/ReSpire producer who wants to compare new role coverage systematically and preserve reliable project recall across an expanding library.

Its limitations are the separate licence, possible role overlap with Vol.1 and the organisation required by mixed preset, MIDI and WAV assets. The product name supplies style context but not verified hardware emulations or artist usage. Buy it for confirmed workflow value, not unsupported associations.

Sources and comparison links

This editorial uses the imported record for the 100 presets, seven kits, Macro MOD and ModWheel behaviour, MIDI, 24-bit/44.1-kHz WAV and royalty-free wording. Manufacturer documentation for Spire and the official store catalogue supply the supporting product context. Check the current offer and licence before purchase.

Use AudiobyRay’s links to Synthwave Vol.1, Spire and the Reveal Sound catalogue guide. Keep counts and rights tied to the correct SKU; Vol.2 is a companion for comparison, not evidence that the first volume is replaced or included.