@d-healey You were right, it was the bundle identifier.
Posts
-
RE: AU Compiles but not visibleposted in General Questions
-
RE: Soundsync: HISE Ecosystem | UPDATE: WE ARE LIVE!posted in General Questions
Hey Gang,
Quick update on SoundSync & the HISE integration I've been working on.
SoundSync is now LIVE!
This means you have two integration paths available from the developer dashboard:
1. HISE Script Package
This is the simpler drop-in version for developers who want the fastest setup inside a regular HISE project.The include is intentionally simple:
include("SoundSync/Runtime/SoundSyncRuntime.js");This package handles the branded activation UI, login activation, serial activation, machine validation, deactivation, Store, My Products, and customer product access using HISE Script + WebView.
2. Native C++ HISE Package
This version is for developers who are comfortable building HISE from source. It moves the more sensitive licensing/runtime layer into native C++ and keeps the HISE Script side as small as possible.The HISE Script side is only a lightweight gate:
include("SoundSync/Scripts/SoundSyncNativeGate.js"); ssSoundSyncNativeGateStart();The Native package includes the C++ source, HISE source patch/tools, setup instructions, and the same product/developer branding flow as the HISE Script package.
The goal with the C++ version is to make the licensing layer harder to inspect or tamper with than a script-only package, while still keeping the HISE-side integration simple.
Current package features include:
- Activation by customer login or serial + email
- Product-specific machine activation, validation, and deactivation
- Server-side activation counts and serial status updates
- Offline grace period and cached local license state
- Branded activation UI with developer logo, product image, Brand Manager colors, and light/dark logo background handling
- In-plugin Store with catalog browsing and single product pages
- My Products panel with current product serial, activation info, copy serial, deactivate this machine, and owned-product access
- Branded storefront/account link handoff with SoundSync fallback links
- Test Connection flow for checking package/API setup
- Product-scoped generated config for each developer/product
- HISE Script package and Native C++ source-build package options
Both versions are generated from the SoundSync developer dashboard and are product-scoped, so developers can export a package with their own product info, branding, activation settings, storefront links, customer product access, and machine/license behavior already configured. They both include simple instructions for integration as well.
The HISE Script version is the fastest route for most developers.
The Native C++ version is the better option if you are already maintaining a custom HISE source build and want a stronger licensing boundary.SoundSync for HISE is live now, and both package options are available from the developer product dashboard.
If you are building commercial HISE instruments or effects, you can now generate a product-scoped HISE package with activation, validation, Store, My Products, branding, and customer access already wired in.
JUCE packages are also offered for direct JUCE connection.
Feedback from the HISE community is always welcome as we keep improving the developer & customer experience.
Best,
Aaron
-
Soundsync: HISE Ecosystem | UPDATE: WE ARE LIVE!posted in General Questions
Hey Gang,
I wanted to start a cleaner updated thread for SoundSync and keep this one focused specifically on the HISE ecosystem/workflow we’ve been building around it.
SoundSync started as a platform to help audio/plugin developers handle the pieces around releasing a product: licensing, customer accounts, serial activation, product delivery, storefronts, checkout, and customer libraries.
The HISE side has now grown into a much bigger part of the platform, so I want to use this thread to share walkthroughs, updates, screenshots, and short examples of how the HISE workflow is coming together.
The goal is not to replace anything inside HISE.
The goal is to help with everything around releasing, selling, activating, supporting, and managing a HISE-built product.
Some of the HISE-focused pieces currently being tested or polished:
Product setup and delivery files
Storefront and checkout testing
Customer library / download access
Serial generation and activation
Plugin-side validation
Offline grace handling
Suspend / deactivate / reactivate flows
Reseller, imported, and unassigned serial activation workflows
Branded activation UI
WebView-based in-plugin storefront
“My Products” customer view inside the plugin
Developer support links/pages
Customer/product ownership checks
Basic customer and purchase managementRight now the platform is still in test/beta mode. Stripe checkout is in test mode, so no real payments are processed.
For checkout testing, Stripe’s test card is:
4242 4242 4242 4242
Any future expiration date and any CVC should work.
What I’m mainly looking for from HISE developers:
Does the setup flow make sense?
Is the HISE package/drop-in workflow clear enough?
Does the activation/licensing flow feel reliable?
Does the WebView storefront/customer area feel useful inside a plugin?
Are the customer/product/storefront tools helpful or too much?
What would make this safer, clearer, or easier before real launch?
What support/docs/walkthroughs would make the HISE side easier to trust?This is still not meant to be a polished public launch thread. I’m mostly looking for a few HISE developers willing to test the workflow, create a demo product, run a fake checkout, generate/activate a serial, and give blunt feedback.
If you’re actively building or selling HISE plugins and want to test it, you can sign up here: https://soundsyncsolutions.biz/developer
You can also schedule a meeting with me here for any questions, walk-throughs, etc: https://www.soundsyncsolutions.biz/demo
I’ll keep posting HISE-specific walkthroughs and updates in this thread as the package gets cleaned up.
Best,
Aaron -
RE: Taking my Mailing list seriously, so a first question....posted in General Questions
@Lindon My subscriber list for my Plugins are roughly the same as yours (around 18k). Ill be as open and honest about what Ive done, results, etc since beginning my current plugin company 1 year ago.
My main focus for marketing is collecting emails. I do this in various channels (resellers, free giveaways, exclusive blog discounts, affiliates, etc).
Whenever I have a new release, my email subscribers get it first. Whenever I have a deal/bundle/sale, my email subscribers hear about it first and/or get a special/addional discount.
Any purchase recieves a thank you along with he downloads.
Some amount of time later, usually 5-7 days, i automate an email checking in on how they like the product and if they would leave a review. Leaving a review gets you a small discount/gift card to be used in the store.
As far as campaigns, it depends on what Im aiming for. A new release will get "hype" emails, 1-2/week, for a couple weeks. Then the actual launch and deal will recive 2 emails/week. The final 48 hours receive 2 emails as well for urgency purposes.
Bundles, deals and sale may get a similar treatment just less "hype".
My audience is pretty used to my email format and layout. Im usually pretty straight to the point with a bit of sarcasm. I think being yourself and not bullshitting is pretty important.
I typically can make $2000-$4000 from my email list each release/deal. These deals are usually 2 week periods.
Hopefully something in this ramble while im rocking my daughter to sleep s helpful.
-
RE: Apple altool vs notarytoolposted in General Questions
For anyone doing it it manually, here is the code.
Thanks @d-healey as always!
Codesigning Plugin
codesign --remove-signature "MacHD/User/Desktop/PluginName.vst3"
codesign --remove-signature "MacHD/User/Desktop/PluginName.component"
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.vst3" --timestamp
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.component" --timestampBuild Installer
Sign Installer
productsign --sign "Developer ID Installer: YOURTEAMID" "MacHD/User/Desktop/PluginName.pkg" "MacHD/User/Desktop/Signed/PluginName.pkg"Notarize Installer
xcrun notarytool submit --apple-id "YOURAPPLEID" --password "App-Specific-Password" --team-id "YOURTEAMID" "MacHD/User/Desktop/Signed/PluginName.pkg"Wait For Upload To Complete
Staple Installer
xcrun stapler staple "MacHD/User/Desktop/Signed/PluginName.pkg"Check Status (Accepted)
spctl --assess -vvv --type install "MacHD/User/Desktop/Signed/PluginName.pkg"FYI: Just a tip coming from the altool manual notarizing. I used to have to enter my TEAMID including my name like "My Name (GD78YHD87G)" but with the notarytool, it seems you just need the actual TEAMID Number, not the name as well.
Also, I dont think this way sends the Notarization Email Confirmation. I did a fairly small upload a while ago and have yet to receive it. I've had it take hours before, but for a much larger file. Typically it sent the email within 10 or so minutes with altool. (it does not send the email. Once the upload is complete, youre good to go).
-
RE: control.Timer crashing plugin in DAWposted in ScriptNode
@trillbilly If anyone hits the same problem, I got around it by using a tempo-synced ramp and a couple compare nodes to simulate the timers engagement.
Simple and works.

-
RE: Preset Crashes DAWposted in General Questions
@Lindon @d-healey @Dan-Korneff @Matt_SF @DanH I did another rebuild and managed to get things saving correctly (so it seems). I messed with a few settings and properties so Im not 100% sure what it was but it's working so thats that. I appreciate all the help and input fellers!
-
RE: Making a Simple Rompler?posted in General Questions
@daniel89ep Ya, @d-healey videos are great. I think this is with a Sound Generator but essentially you do the same with the Sampler.
-
RE: Sample Editor Functions + UI Controlposted in General Questions
I dug the forum again and found a little trick about naming the Sampler for instances of 2 const var calls.
Im horrible with scripting and new to this so excuse the shitty code, but hey, it did the job! Here is the code if anybody wants to try it out. It allows you to control the editing functions of the sampler (Loop Enable, Reverse, Loop Start/Stop, etc).
HISE SNIPPET:
HiseSnippet 2171.3oc4Z0sbaabEFPRPIj1owIStn2jYvvoWPkQVgT1wtM+TSQJoLbhjLCorSlwMSxRfkjvFbWLKVpeZGOSeD56Pauu8MvOB8t9Z365ktm8G.rfBjBRwIwSKuQd28bN624Cm8bNXg6wnd33XJyxtxwmGgsruoyfyI7IclfBHVc20xtpyQ3Sc6P8wVsOOBEGi8srsW8KEqaWYMK4uW9f1nPDwCmMkk0ioAd3CBlFvylsWquJHLbejO93foFRe2Vc8njNzP5L.Kq5zvJB48LzX7QHgXq3XYu9d9AbJa.GwwwV1q0l5e9fIzSIJ4ebPbvvPrXPSqAfgTSuOMzWfXwrVclDD52Kwmisrrc5kw.qpXfOv4v.+fz4yXhaIWvMSCS9vdk7va0bvqoI7ZX.uBfjsAjVSAo2yYfGKHhmsh.O2voKgiYiPd4eznj0Zk+dUmNTPBBeqonmg2mACR0ndysazXS262nwFeV0pe7GOXmC6cvd8ca5t+iNpywce3QCpVEdjDycOAwbGflFEhYMc+BWY7wViwb8b0qkrXMsoTCAScasdt.qv3teEgNrZ.ILffcGMi3wCnDWJQIiTDAdYzv5dzoQTBf7MgcObFdip+optvuQTV8X2.RJd1xigABe.NDKMW8Za8Q01XCovJUD+BodnP2P.7QHVLFHg5wBOnt1Lao96dD+M.WHQq3shufHRTpAk6G4FpE+4UeN35IrMX4NINPB6HUr1FBSpcxNnvvgPPd8hXfExj.FWNOBB7FOKBhjwgau8u6N2+dklHAcWNMlQ.WjDOfRiVdvnPhKMTrhfAQWWFjYxfnKmAQ4XvT.lwfrRPdopsHxadGeAj2Rh+Dq+lczmFgWsyuZkVFucogbeqnh2x3Mo.ugybRLd04NoZKi8L88EF0gfhm9tsmw4TR0EPhpUuzCt+xPgM0QeRG4pyhJeaYzXNuWvi.QJDws1oPk+w0RbYQXj9eeHJJtfh74pxKaPQN5BE5ikCml2HwoVVXEM8j1s.L+AAw75JC.OhFRGROykP43O00a5PPGBzwmKcjaxhW.fwJ4VVQBgHBPlMR9nnV.GOMt1lFfbqmRCfG5+AfZUX5HITR3pL3nmYg0cEaxRC8RiCBoH+T1ndFTdhT1a276.fbYUAUN3xJCZfGgiYfWgG9PRcInp97ptyuznQEtl1XhN9JZYQ+7rkoXcxroCwLSJQHHzja9NmcVbmylM16oXGCAojtj.9CivjE0tuklRgtrqnQEHJW1i8uR2i8fv.eLyJ.Zk9cbLZLyRBay2uwpDl3FNo0Uyaf+8e8EOnLFnhit.y7p+udP42eYF1R3.2RafNhidsomIMwMcxBnl2FubwfPkNRZg20oO9DLj2TOW4YxbF4gDL7zl+iwH2zIKS4UvWxQnoo5Kv.Op6tHNR7Rb5HMH5KBy3Ah.a6cwm.uQr5U5p3rKN9YbZD7F1omtgf+RFLdV111s04oC9yOtEGeFWZ.i27RvMkXKLCVWvF7hg5MPwjEX90KQnblwew3hLdUmjdMs7wiPyB4OtfmUk1iTg+KviZ8z7djR3BL+ke3vXGNxXGrtaKYcGK62xoMh7TZNqeCt9VGTVeen5.OfL93.HkmJt2bpllahkkA2wZoC4TwWuqSOFFJOzlQOMFXigiStbkJqCh+eD5HPU1r+yW8WdU9Y2VKr7mLvdkudEGQWQ0DocGfNQeht1m5xYyvalrxdmEgHwP1+3chASMapPhQnv3LQj2KCqX0EUghufFhpDJ4iMUHaZnvE3vvZMajpzN99EuG8whB6Eu1tPyf7Er19nSnLfhDWWk4ZZj0EbaebaJCbtbdvQylpXBA3aJmRM9aB74S5COfovBOQ1KXistyb+17JNOL82I2CQyV6.c3lxM5cXyh9SpVJj0mdZOjuOD4UV8FfQLuIsQr1zYDegm9D0BIrlhkLVs5ysNUP.voL6+lsk0Dbv3Ihyb1qYak6bxaU5xKYmP9gyLyM9D8A8JIxaEkzaPWeQRmjNzrfl7gfCNVOuVb+b3oRoqTsH770sztdx44enUh6mLymmlPDLoqvlkCyURfvxx7un5hK.uV+dMXVWJbIS5aVu7LyjtETzJIY5xS7ewqG8VNGR8mEh34usVwUTqW.REk6JREWCJbRketokm+JbWqbWg6xug4xB22yoW.2aRw3ckBvKzjwO03Ueg3uiydiFAucbFXWyY+uco298qcn7gJn79NC3P1roPNIcfu9aTjdL30v2nHpzeiBnDq7k4B9iFh8hVsmA7EK+r+iVxsZmoPtub6kF48wQXD+PwmYIcw2tU+9eIiNKZdsd4CjAKGyfW3CnByERN2a3icXz33Qf6HsUr4R8lwFK3prYRy0YLmn10DDgfCEudlsHw7ihEMhxC7NDwYA45IQtKMNFIeduhiZby4Fu8biuybiu6bi+j4Feu4Fe+rwouZsHxHoiq4eIyJk6kLAqzCA9sgjsCFmtCpYLihS4ZIdL97TeCzrzHJapgkFf4h15hMlpfOGz5+T8Ep9YM81O9rwud9fZURv3f.UUoSfSvvLBL99vqjIq4jLa9rIGRIznITRfW9yKP7+3wXlI1Kzg1gygiqYy7As5C8YhhMNv+aZcP.A5gJeZfqDWz7J+wEK740u1QAWWQJP2+2nJ5p+eeUzkQcyciAuY+b9lNxr9tx2U+WHn1mNSj9No.nCTkb.zYfG1rV4Jh5upwMDiE.Z.l3KG7J3mdwlIEVEK1LYQKuDSA9l9eKeOb6UwpOjfn4vPnjcnYHcLz+g.RPwveVP4TjGi98dpKOSf02VNCfRh7+8FUbNTL1sYxMl43zXqFVSgZUeumm3fvsAFtXc19ZnyctF5b2qgNex0Pm6cMz49WCc9sKUGQaB6LiSmpRRBSzaOUfk8doAVqZ8eY0VljDSCRIPT:
Content.makeFrontInterface(1200, 700); //SAMPLER 1 FUNCTIONS const var Sampler1 = Synth.getSampler("Sampler1"); //Sampler 1 - Sample Start Knob inline function onSampleStartControl(component, value) { for(s in Sampler1.createSelection(".*")) { local l = parseInt(s.get(Sampler.SampleEnd)); s.set(Sampler.SampleStart, value * l); } }; Content.getComponent("SampleStart").setControlCallback(onSampleStartControl); //Sampler 1 - Sample End Knob inline function onSampleEndControl(component, value) { for(s in Sampler1.createSelection(".*")) { local l = parseInt(s.get(Sampler.SampleEnd)); s.set(Sampler.SampleEnd, value * 229376); } }; Content.getComponent("SampleEnd").setControlCallback(onSampleEndControl); //Sampler 1 - Loop Start Knob inline function onLoopStartControl(component, value) { for(a in Sampler1.createSelection(".*")) { local r = parseInt(a.get(Sampler.SampleEnd)); a.set(Sampler.LoopStart, value * r); } }; Content.getComponent("LoopStart").setControlCallback(onLoopStartControl); //Sampler 1 - Loop End Knob inline function onLoopEndControl(component, value) { for(s in Sampler1.createSelection(".*")) { local l = parseInt(s.get(Sampler.SampleEnd)); s.set(Sampler.LoopEnd, value * l); } }; Content.getComponent("LoopEnd").setControlCallback(onLoopEndControl); //Sampler 1 - Loop XFade Knob inline function onLoopXFadeControl(component, value) { for(s in Sampler1.createSelection(".*")) { local l = parseInt(s.get(Sampler.SampleEnd)); s.set(Sampler.LoopXFade, value * l); } }; Content.getComponent("LoopXFade").setControlCallback(onLoopXFadeControl); //Sampler 1 - Loop Enabled Button inline function onLoopButtonControl(component, value) { for(s in Sampler1.createSelection(".*")) { local l = parseInt(s.get(Sampler.SampleEnd)); s.set(Sampler1.LoopEnabled, value * l); } }; Content.getComponent("LoopButton").setControlCallback(onLoopButtonControl); //Call "wrong" Sampler for SampleMaps const var Sampler11 = Synth.getChildSynth("Sampler1"); //samplemaps const var sampleMaps = Sampler.getSampleMapList(); //combobox note: cmb = name of combobox const var Samplescmb = Content.getComponent("Samplescmb"); Samplescmb.set("items", sampleMaps.join("\n")); //Note: Sampler = name of Sampler inline function onSamplescmbControl(component, value) { Sampler1.loadSampleMap(sampleMaps[value-1]); }; Content.getComponent("Samplescmb").setControlCallback(onSamplescmbControl); -
RE: Notarisation for dummiesposted in General Questions
@orange Ive gotten to waiting for the email. Ill post update after.
UPDATE: Success. Thanks again!
-
RE: Export Error - JUCE VST3 Wrapperposted in General Questions
@orange it looked a little different as I had downloaded the newest SDK. It had some extra folders but everything else looked the same.
@d-healey Thanks for the Password. Now that I am able to use the included sdk.zip contents, it has completed an export of VST3.
The help is much appreciated!
-
RE: Dropdown for Floating Tileposted in General Questions
@d-healey Perfect, appreciate it man!
@MikeB Im already on it!
-
RE: Payment providers comparedposted in General Questions
Hey Gang,
Quick update: SoundSync’s previous 10% pricing has been replaced.
3% SoundSync fee on discounted sales, excluding tax, plus actual payment-processing fees.
$20 monthly minimum on sales fees only—not $20 plus 3%.
Marketing emails: 1,000 free/month, then $0.50 per started 1,000.
Free/external redemptions: 10,000 free/month, then $0.005 each. License validations and activations don’t count.
Developer payouts through Stripe or PayPal, with applicable payout/FX fees deducted and displayed. Estimates reconcile to actual charges.
Using your own checkout? Licensing + Hosting remains $20/month, or Licensing only $10/month, plus applicable usage, with no percentage on external sales.
The old figures in my earlier posts/PDF are outdated.
-
Bringing an Existing Catalog Into SoundSyncposted in General Questions
Hey Gang,
One thing I wanted to go through is how you can bring an existing product catalog into SoundSync without entering every product again.
You can start with a public store URL, a product export such as a CSV, or use both together. The importer finds what it can, then gives you a review screen before anything is saved as a draft.
I’m using Moonwave for the examples below, with Conduit, Voidline, and Eidolon in the CSV walkthrough. The delivery ZIPs are small test files for showing the process; they aren’t the actual product installers. Everything shown stays unpublished.
1. Open the importer
Go to Products → Import / Upload. There is a Store URL field and an optional Product export field. You can leave the URL blank and use an export on its own.

The starting screen supports a URL, an export, or both.
2. Import from a CSV
Choose your CSV and click Find my products. CSV, TSV, Excel (.xlsx), and JSON exports are supported, up to 8 MB.
Open Review export column mapping and check where your columns are going. For example, Product Name should map to the product name, Price to the product price, and any download-link columns to private delivery links. Use product prices here, rather than an order total or sales report.
There is also a Download Demo Import CSVs button with editable examples, including WooCommerce- and Shopify-style exports. Unzip the examples and replace the demo values and URLs with your own.

Moonwave CSV selected, with the Store URL left blank.
Check the name, price, artwork, and video column mappings.3. Import from a website URL
For the URL route, enter your public store address and click Find my products. The export field can stay empty. An individual public product page can also be used to bring in one product.
SoundSync looks for readable product information and supported artwork, public audio, and video references. Check the final product list against your original catalog; the number found is not a guarantee that every product was discovered.
If the site needs a login, blocks access, or only exposes its product content after JavaScript runs, use an export or fill in the missing information manually. You can also provide a URL and an export together.
For the Moonwave product results in this walkthrough, I used the CSV route. If homepage scan does not recognize the products or you get an empty or incomplete result, add an export and check it against your catalog.

The URL entry step, using Moonwave’s public store address. Product-result screenshots below come from the CSV import.4. Check the product details
For either route, expand the products and check the actual information. In particular:
- Are all the expected products present, and are any duplicates or variants being mistaken for separate products?
- Are the names, descriptions, product types, and listed contents correct?
- Are the prices correct in USD? No currency conversion is performed. Review any missing-price or minimum-price warnings.
- Are the selected images the right artwork? Are audio files public demos rather than the files customers are meant to receive?
- Are video links correct, and is anything important missing?
- For repeat imports, is an item a new product, a matched draft, or a published product that will be skipped?
Selected artwork and public audio are copied into SoundSync storage before the drafts save. If a copy fails, retry it or deselect that file and upload a replacement later. Supported video embeds stay with their video provider.

Review Conduit’s name, type, price, and description.
Review the Moonwave artwork and video included from the CSV. Public media is separate from private delivery files.5. Save the selected products as drafts
Select the products you want, confirm the review checkbox, and click Save selected as drafts. Nothing is published automatically.
Matched drafts are unselected by default. If you opt into filling their empty fields, existing saved content and prices are preserved. Published products are skipped by this importer.

The three Moonwave walkthrough drafts are ready for delivery files and final setup.6. Add files from your computer
Under Add delivery files together, select your installers or product archives and check the product assigned to every file. Filename matches are suggestions, so correct them before clicking Upload matched files.
You can attach several files to one product. Here the Windows and macOS test ZIPs both go to Conduit, while the third test ZIP goes to Voidline.
These are private customer downloads, separate from the public artwork and audio demos. Package installers as ZIPs; supported manuals, audio, text, and MIDI files can also be attached.
The interface supports up to 10 GB per file. Keep the tab open for local transfers. Upload progress is retained for 24 hours from the start; after a reload, choose the same original files to resume saved chunks.

Two test files matched to Conduit, with a separate file matched to Voidline.
The Conduit draft retains both operating-system test archives when reopened.7. Add files from download links
If your files already have direct download URLs, use Import delivery files from links. Upload a CSV with a product-name column and one or more download-link columns, then click Review download links.
Confirm the name and link columns, check each product match, select the files you want, and confirm the private-delivery checkbox before starting the import. Unmatched or duplicate names need a manual product selection.
These need to be direct file links, including valid signed links where appropriate. A checkout page, sign-in page, or ordinary share page is not a direct download. Expired links need replacing.
SoundSync copies the files into private delivery storage and attaches them to the selected product. Link imports continue on the server if you leave the page. Check for an attached result and review or retry failures.
For the Eidolon example here, I used SoundSync’s public demo-CSV ZIP as a harmless test transfer. It isn’t an Eidolon installer. For an actual product, use your own delivery URLs.

Review the Eidolon draft, selected test download, and confirmation before importing. The test download is attached privately to the Eidolon walkthrough draft.8. Finish the product setup before publishing
Open each draft and check the remaining setup:
- Product copy, artwork, public demos, version, product type, and price.
- Actual downloadable files: filenames, Windows/macOS versions, manuals, and archive contents. Test the downloads.
- Compatibility/specifications, installation instructions, license documents, and support information.
- Access and licensing settings. For a plugin, generate the appropriate integration package and test activation and validation in your exported build.
- Any bundle membership or subscription configuration, which needs its own setup.
- The product-page preview, storefront placement, and intended publication settings.
The catalog import handles product information and supported files. Existing customer accounts, past orders, recurring billing, and marketing permissions need their separate migration workflows.
I wanted to show the whole process because finding the products is only part of moving a catalog. The review and delivery steps are where you make sure customers receive the right thing.
If you have an export from another platform, I’d be interested to hear which fields or file formats have been the most awkward to move.

The imported product remains a draft while the remaining product sections are reviewed.Import overview: https://www.soundsync.dev/features/product-import
-
Why you should plan for support before launch.posted in General Questions
Hey Gang,
Planning how your plugin business handles licensing, logging, customer accounts, purchases, activations, updates, and product management can prevent many support requests before they happen.
It also gives you the information and tools you need when a customer does need help.
A few things worth planning early:
- A reliable licensing system that handles activation, restoration, device limits, and offline use.
- A logging system that records useful technical information without collecting the customer’s creative data.
- A customer-management system that connects purchases, products, licenses, downloads, and support history.
- A solid checkout and order system for failed payments, duplicate purchases, refunds, receipts, chargebacks, and missing orders.
- A clear Merchant of Record or payment-processing setup so tax, billing, refunds, and customer responsibilities are properly defined.
- Self-service tools for resetting activations, managing devices, finding receipts, and downloading products again.
- A clear way to identify the installed plugin version and whether an update is available.
- Useful error messages that explain what happened instead of only saying something failed.
- A simple way for customers to send relevant diagnostic information with a support request.
- A plan for server outages, expired subscriptions, refunded purchases, and other unusual situations.
Purchase issues can create just as much support work as technical problems. A customer may have been charged but not received access, used a different email at checkout, purchased the wrong product, or lost their receipt. If orders, customer accounts, product access, and licensing are disconnected, resolving a simple issue can require searching through several systems.
When everything is connected, support becomes much easier.
If someone changes computers, they can reset an old activation themselves. If a customer reports a problem, you can quickly see what they purchased, which version they are using, and whether their license is active. If a payment or fulfillment problem occurs, you can trace the order and restore access without manually piecing everything together.
Good customer service is not only about responding quickly. It is also about building systems that prevent confusion and give both the customer and developer useful options when something goes wrong.
This is one of the areas we are working on with SoundSync: connecting commerce, customer accounts, licensing, activations, downloads, product versions, communication, and support information in one system.
The goal is to reduce preventable support requests while making the requests that do happen much easier to understand and quicker to resolve.
-
The gap between finishing a plugin and running a plugin businessposted in General Questions
Hey Gang,
This is something I’ve been thinking about a lot lately.
Finishing the instrument is only one part of releasing a plugin.
A lot of us can get the actual product built in HISE like the UI, samples, scripting, presets, installer, export.
That part is hard, but it is also the part most of us signed up for.
The harder surprise is everything that comes after.
Once you want to actually sell it, you suddenly need a whole second system around the plugin:
- a product page
- checkout
- license delivery
- customer accounts
- download access
- license resets
- device limits
- refunds and revoked access
- update delivery
- support emails
- “I bought this but lost the download link”
- “I got a new computer, can you reset my activation?”
- “My license is not showing up”
- “Where do I log in?”
None of that is really the instrument. But if you don’t have it, the release starts to feel unfinished.
That is the gap I’ve been trying to solve with Soundsync.
The idea is to give audio developers the business layer around the product like storefront, customer library, license/activation handling, download access, and the basic post-purchase flow that customers expect.
For HISE specifically, my goal is that the instrument itself should not become a mess of store logic, customer account logic, and manual support work. The plugin should mostly care about whether the customer has access. The rest should live in a system built for selling and managing audio products.
I don’t think every developer wants to build a mini Shopify, license server, download portal, and support dashboard just to release a plugin.
This is the bigger problem Soundsync is aimed at, not just licensing, but helping developers get from “I finished the plugin” to “I can actually sell and support this properly.”
Curious how other HISE developers are handling this right now. Are you using Gumroad, Shopify, custom scripts, manual serials, your own backend, or something else?
-
RE: Soundsync: HISE Ecosystem | UPDATE: WE ARE LIVE!posted in General Questions
UPDATE: Native-Authoritative C++ Licensing Bridge
SoundSync HISE package is rebuilt so the UI stays in WebView/HiseScript, but the licensing authority is now native C++. The WebView only collects user actions and renders safe public state. C++ handles activation, validation, restore, protected storage, device identity, offline grace, deactivation, and the final mayOpenProduct access result. HISE copy protection then reads that native result.
It’s not a pure C++ UI replacement. It’s a hybrid: WebView for branded UX, C++ for licensing authority. That seems to fit HISE better because WebView is still the easiest way to keep product branding, storefront, My Products, and login flows flexible, while C++ owns the trusted licensing path.
@Lindon thanks for the suggestion.
-
RE: Soundsync: HISE Ecosystem | UPDATE: WE ARE LIVE!posted in General Questions
UPDATE: Auto-Detect + Dynamic GUI Sizing
When you download the HISE package, you will not be required to enter the GUI size anymore as it is auto-detected directly in your project. Thanks @David-Healey
Also, the complete HISE package is dynamic and will change dimension based on changing GUI elements (like an expandable keyboard or effect section). Thanks @dannytaurus
For example: Customer didn't pay for their subscription, grace period ends, they are using plugin now with the keyboard extended. The plugin will pause, popup the activation webview, and the webview overlay will still block the entire plugin, not just the original size.