Spire Trance Essentials Bundle 2 In 1

Read the 2-In-1 bundle as its own SKU

Spire Trance Essentials Bundle 2 In 1 is listed with 212 presets for Spire and ReSpire, thirteen construction kits, MIDI and 24-bit/44.1-kHz WAV files. Most presets offer Macro MOD or ModWheel movement. The bundle must be treated as its own purchase and delivery rather than a mathematical label pasted onto two child pages.

The imported child counts of 112 and 100 presets reconcile to 212. Their kit counts are five each, while the bundle page states thirteen. Do not silently change thirteen to ten or transfer three unexplained kits to a child. Verify the delivered bundle folders and current listing.

Create a source-total reconciliation sheet

Record bundle claim, child claim, delivered folder and observed total in separate columns. Start with presets, kits, MIDI and WAV. Keep the receipt and listing capture beside the sheet. This makes a source discrepancy visible without inventing an answer.

If delivery differs, contact the retailer or manufacturer with the exact SKU and evidence. Do not “fix” metadata by assumption. Editorial transparency is more valuable than a falsely tidy total.

Audit ownership before download

Check whether the licence library already contains Vol.2 or Vol.3. Record standalone and bundle entitlements separately, including purchase dates. A duplicate download may still contain the same files even when the store labels differ.

Decide whether the bundle adds missing content or only a second licence record. A “2 In 1” label is not a substitute for a delivered-file comparison. Useful value comes from distinct assets and an ownership gap.

Build a 212-preset catalogue without duplication

Keep volume identity in every preset tag, then add role, register, envelope, width, effects and controller notes. Compare likely duplicate roles at equal loudness. Retain both only when they solve different arrangement problems or offer materially different performance behaviour.

Do not assume all 212 programs are functionally unique. The exact count is a source fact; practical coverage is an audition result. A smaller curated catalogue is faster and safer for project recall.

Map controller behaviour bundle-wide

Test Macro MOD and ModWheel independently for retained presets. Save minimum, middle and maximum states and describe the audible outcome. Tag whether movement is suitable for intro, build, breakdown or return.

Use one consistent controller template across both volume folders, but do not assume identical assignments. Limit ranges when combined movement adds excessive density. Store notes with the preset identity and volume.

Verify thirteen kit folders instead of assuming

Count actual delivered kit folders and record their names without reassigning them to children unless the source makes that relationship explicit. The bundle’s thirteen-kit statement conflicts with a simple five-plus-five sum, so delivery evidence is required.

Use each verified kit for one analysis question and rewrite all musical material before release use. If only ten are delivered, preserve the discrepancy and seek clarification rather than filling the gap with unrelated content.

Keep Vol.2 and Vol.3 workflows distinct

Use Vol.2 for a five-stage controller and arrangement curriculum around its 112 presets. Use Vol.3 for a hybrid preset, kit and one-shot workflow around its 100 programs. The bundle catalogue can link both without erasing their product-specific strengths.

Separate browser roots and source notes prevent one volume’s count or audio branch from leaking into the other. This also simplifies uninstallation and licence support.

MIDI and WAV comparison across volumes

Compare MIDI structure with corresponding rendered WAV files, changing notes and sounds to isolate transferable arrangement ideas. Keep source material read-only and save rewritten files under project-specific names.

The imported WAV format is 24-bit/44.1 kHz. Verify sample-rate conversion and tails before grid placement. Render approved edits for reliable recall.

Design a cross-volume arrangement test

Create an original session with one retained role from each volume, one independently verified kit lesson and one controller transition. Limit the test so differences remain audible. Use equal levels and a neutral rhythm section.

Check mono, low-volume translation and downbeat clarity. The aim is complementary coverage, not maximum layer count. Remove any source whose function is already handled more clearly.

Requirements and archive structure

Imported requirements state Spire 1.1.16 or higher or ReSpire 1.0.7 or higher; verify current compatibility. Presets need the separately licensed synth, while MIDI and WAV require a suitable DAW or sampler.

Archive the bundle, listing, receipt and licence together. Preserve volume subfolders and record the synth version used in projects. Render critical stems for long-term recall.

Rights and collaboration

The bundle listing describes presets, samples and loops as royalty-free, but the supplied licence controls use. Track source files retained in a release and do not redistribute commercial folders to collaborators.

Share rendered parts or authorised projects. Construction kits are study sources, not automatic authorship. Genre context does not prove artist endorsement or use.

Decision checklist

Before buying, confirm ownership, required synth version, delivered preset total, delivered kit total, MIDI/WAV need and storage plan. After download, compare source totals with folders and retain evidence of any mismatch.

Buy the bundle when its verified combined delivery fills a real gap. Prefer standalone volumes when only one workflow is needed or an existing licence already covers the other.

Prepare a precise support request when totals differ

If the delivered folders do not match the bundle page, capture the product title, order number, download version, folder names and observed counts. State separately that the imported bundle listing reports thirteen kits while the two current child listings report five each. A factual support request is more useful than claiming which number must be wrong.

Keep the response with the licence archive and update the studio inventory only after receiving authoritative clarification or a corrected download. Do not alter child pages merely to make the bundle arithmetic look consistent. Future buyers and collaborators benefit from knowing which fact came from the bundle listing, which came from a child page and which was observed in the delivered files.

Strengths, limits and sources

The bundle’s strength is a single entitlement covering 212 reported presets plus mixed study assets. Its limitation is the unresolved thirteen-kit claim versus the two child pages’ ten-kit sum. Transparency and delivery verification are therefore part of the product workflow.

This guide uses the imported bundle and child records for counts, formats, controller behaviour, versions and rights wording, supported by Reveal Sound’s official Spire documentation and store catalogue. Use AudiobyRay’s Vol.2 and Vol.3 pages for child-specific evaluation.