Guide
Product Specifications and Compatibility
Enter the details appropriate to plugins, sample packs, presets, MIDI, bundles, or flexible digital content.
SoundSync
Type-specific information
| Type | Relevant fields |
|---|---|
| Plugin / instrument / effect | Formats, supported OS/minimum versions, architecture, Apple Silicon status, host/DAW notes, requirements, and size label |
| Sample pack | File formats, sample rate, bit depth, BPM range, musical keys, loop/one-shot/file counts, size, and genre/style |
| Preset pack | Target plugin/instrument and version, preset count/formats, and categories/styles |
| MIDI pack | File count, genres/styles, and version requirements where relevant |
| Bundle | Included catalog, product selections, description, and rules |
| Course / other digital content | Flexible custom specifications, included content, and delivery/access notes |
SoundSync
Product specifications
These are your product claims
Listing a format or OS in a specification field does not make SoundSync compile or certify that product for it. The current JUCE package targets Windows VST3 and Apple VST3/AU; your own advertised formats and system requirements still require release testing.
Write compatibility for the actual files/version offered, not a placeholder list of every format. Keep release/last-updated details and supported platform files aligned with the product description.
Bundles need commercial and delivery review
The included catalog explains the offer, while the supported bundle/checkout and entitlement paths determine what is sold and delivered. A descriptive bundle rule is not proof that an unsupported offer automatically works at checkout.
Match the fields to the product you sell
Choose the actual product type before completing compatibility and delivery. Presets and expansions can target a parent plugin/version; distinguish full-version requirements from player compatibility. Unknown compatibility should remain unknown rather than becoming an unsupported promise.
Product artwork, audio demos, delivery files, licensing and access are different inputs. A product-specific artwork upload can override the brand fallback. Imported product details remain a draft to review, not proof that a file, license or compatibility claim has been verified.
