Migration guide
Regenerate a HISE Package
Replace package-owned files when credentials, variant, or generated product settings change.
SoundSync
Regenerate without losing your own work
-
Record the build
Note the product ID, environment, variant, package version, HISE checkout, and shipped plugin version.
-
Save your customization
Keep your own interface and DSP files separate. Review any edits you made inside generated files before replacing them.
-
Generate again
Use the saved product and current credential/branding configuration. Never reuse another product package.
-
Compare the package
Read the new setup guide, config, paths, and changes. Apply native installation/export steps again where required.
-
Rebuild and test
Test existing saved activations, new claims, revoked credentials, branding, device limits, and the exact exported binary.
-
Publish the matching binary
A regenerated download on the dashboard does not update already installed customer plugins.
Rotation can affect existing builds
Revoking credentials used by an installed binary can prevent its future validation. Coordinate rotation with a package update and customer release plan. Regeneration is not an assisted commerce migration or a transfer of another provider's licenses.
