Create a Submission

Version metadata is specific to a submission of your content. This can change between updates, for example release notes or features.

Submissions in Muse Hub track content submissions to the platform, representing a snapshot of the metadata and binaries associated with a product. Once submitted to Release or Beta status, the metadata cannot be changed without creating a new submission.

Duplicate a version using the duplicate icon in the version row, make your changes, then re-submit. This avoids having to start again each time!

  • Submission type

    • Beta: This will make the product accessible within the Hub to beta testers that you've invited to the product beta, via the Beta Testing tab.

    • Release: This will submit the product to Content Review, before releasing to the full Muse Hub audience.

  • What's new?: Fill in your release notes here, highlighting any new features or important changes since the last release.

  • Description: This is a long-form description which should continue on from your Short Description, used to inform customers about your app's abilities and features. There is no limit on this text field, but short and punch descriptions work best. Don't duplicate the "Short Description", since these are shown together

  • EULA (optional): If you have a custom EULA, then enter or copy it in here. If you leave this blank, the Hub will show the Muse Hub Standard EULA, as outlined in the Muse Hub Distribution Agreement.

  • User Guide (optional): (.PDF) of your user guide which will be downloaded and shown to users if they click the respective button on your product page. The user guide is accessible to all Muse Hub users.

  • Knowledgebase Document (optional): a .txt or .rtf file, used by our internal systems and customer support agents to help support a customer through the use of automated systems (AI knowledge retrieval) or human reference.

  • Features: Highlight the top-selling points of your product here. Display them in blocks of 3, 6, or 9. Keep each feature brief, ideally between 70-100 characters.

  • Previews: You can add up to six assets to demonstrate your Plug-In. Please ensure these adhere to the Content Guidelines.

    • Audio (.mp3, .m4a): This could be a song or demo track, or an example of the sounds you can create with your Plug-In.. You can give this a title, and a waveform will be automatically geneated.

    • Image (.jpg or .png): A screenshot or product image showing your product in use.

    • Video (.mov or .mp4): A video file, such as a walkthrough or product trailer, that shows the Plug-In in use.

  • Assets: Drag your supported asset type (.pkg, .exe, .MSI, .MSIX, .vst3, .component, .aaxplugin) here. These should be the installers or binaries for the product that you are distributing. After uploading, you can select the platform architecture using the dropdown menu, such as separate Apple Silicon or Intel installers. Muse Hub will automatically install the correct architecture based on the customer's device.

    • Version Number: This should be a three digit (N.N.N) number that represents your true product version number. It should match the version number found in your Bundle's info.plist (on macOS) or your Windows Installer.

  • Enable DRM: If you are submitting a paid commercial Plug-In, it should have Muse DRM applied or the Muse SDK integrated. Turn this switch on to reveal the Muse DRM ID fields.

    • Muse DRM ID: Paste in the DRM ID generated by the Muse DRM tool.

  • MacOS Properties:

    • Bundle ID: If your Plug-In also contains a standalone a macOS .app, then Muse Hub can optionally also launch this straight from the Hub's UI. For this to work, you need to fill in the bundle name, from your Plug-In's standalone info.plist. Example: com.muse.synth

    • Minimum OS Version: Muse Hub supported macOS back to macOS 11 Big Sur. If your Plug-In has a different minimum required version, you can enter it here to prevent it from being installed on incompatible versions of macOS.

  • Windows Properties:

    • Application ID: Many Windows installers work with an App ID, or Installer Upgrade Code, which allows Windows to track the installation. Muse Hub can use this App ID/Code to launch the application automatically, and also ensure that updates are more reliable by choosing the most appropriate method. You should have set this installer code or App ID when creating your application's installer. Copy it in here for the most compatibility with Muse Hub's installer system. If you don't enter your Application ID, Muse Hub will not be able to uinstall or update application reliably.

    • Minimum OS Version: Muse Hub supports a minimum OS of Windows 10 21H1. If your product has a different minimum version of Windows required to run, you can enter it here to ensure it isn't installed on incompatible versions of Windows.

Once you've finished filling out your version details, press "Save".

Last updated