Quick follow-up on the documentation gaps raised earlier: we’ve expanded SoundSync’s public pages so the features, fees, and commercial policies are easier to find.

Product migration is now supported. You can bring a catalog from another platform using public store/product pages or a supported spreadsheet/JSON export. Imports become drafts for review before publishing. Customer accounts and existing recurring payments are separate from catalog migration. Migration details

Security and integrations have expanded too. We support authenticator-based two-factor authentication, recovery codes, and team accounts with role and product-specific access. HISE developers have both HISEScript and native C++ integration paths, alongside the JUCE package. The API documentation now covers substantially more of the platform, including licensing, refunds, subscriptions, and partner integrations.
Account security · Developer documentation

We’ve also expanded the Website Builder and branding tools, including root-domain support and SoundSync-provided SSL, plus native affiliate and collaborator programs alongside reseller integrations.

The commercial details are now explicit: Stripe and PayPal checkout, USD-only pricing, and one 10% SoundSync fee covering ordinary payment processing on SoundSync-managed checkout. Developer, affiliate, and collaborator payouts follow the same schedule: the 1st and 15th, after the minimum 14-day hold.

The updated pages also explain Merchant of Record responsibilities, tax handling, refunds, disputes, and payout eligibility.
Pricing · Trust Center · Payout policy

Thanks again for pointing out what was missing. That feedback helped us make the information much clearer.

Thanks, that’s really clear. Out of interest, roughly how long does one demo video take you from start to finished, and which part takes the longest?

Thank you for the help @David-Healey ! This worked perfectly.

I would like to include a few additional notes. There is a good bit of information that needed to be passed to each sampler. The interface relayed this information to controls in the MIDI Processors via interface control callbacks in the following format:
scriptProcessor.setAttribute(controlIdx, value);

In the onNoteOn block, Message.ignoreEvent(true) and Message.makeArtificial() were called. The note IDs produced by the Synth.playNote() command were stored in an array that was referenced when turning off the notes with Synth.noteOffByEventId() in the onNoteOff block.

Not something I've explored for demo videos but might be something Claude Design can help with.

@dannytaurus hey thanks for the updated fix! You are right the knob movements weren't being recorded with mine. I haven't got around to integrating your fixed version yet but appreciate you sharing it.
@AxiomCrux this is my first HISE plugin so not sure when the issue appeared with Ableton, and I would look at that other PR if you want knob movements recorded - my proposed fix indeed broke that.

@David-Healey - well that seems to work so thanks again.

Tobias just informed me that their newer C++ module is indeed JUCE 6 compatible: https://github.com/Moonbase-sh/moonbase-cpp

Just swapped out my self-built solution with the C++ module with the help of Opus 5.5 - works like a charm! Nevertheless looking forward to see a official integration with HISE in the future :)

@scottmire said in Vibe Coding Custom Nodes:

Now, I'm trying to do as much as I can on my own without bothering too many people

Feel free to bother me, I could talk about DSP all day. It's already the thing I do day and night.

@duma That is the only way - compiling HISE and compiling plugins is the same process whether you use a precompiled build of HISE or not.

@cartemtune thanks folks! So Australia, New Zealand, and Japan seem to be the countries that I need to take a look at. I actually can easily unblock these countries on my store and set up custom tax rates on my store so I can at least collect the taxes, but I definitely need to do more research on how to remit them correctly. maybe after that then I'll start thinking about moving to an MOR if I need to. I'm just already so cozy here lol migrating platforms is so much work :')

@dannytaurus Thank you so much!

Started the process and Whish me LUCK :)

@resonant Yes sir im using A1, A2 isn't working for me at all it just crashes everytime when i try to load it, apparently its something to do with the top level architecture of A2 being SlimmableContainer which HISE isn't liking and A1 being top level WaveNet which works fine! Any ideas if im doing something wrong there?

@dannytaurus Haha, well I looked into it anyway. Seems like I have to use Wise assets to get the interest thingy, I checked with the bank I use for my savings account and if I open a new account I get 4% there, so that's what I did :)

@David-Healey Thank :)

@David-Healey Thank you for doing this. It really helps me in my Hise Sampler quest!

@Christoph-Hart Ok so thanks (or not) to Claude I could implement it fully after fixing many bugs. Obviously, this certainly has some AI non sense and I would be interested in your insight 😉

But it works a treat in context!

Here's the PR: https://github.com/christophhart/HISE/pull/1055

And a more readable bug fix report than the MarkDown: https://gold-reggie-20.tiiny.site/

The problem with Kontakt was never really the software. It was the ecosystem (native access), NI's licensing, ads in the home screen, and the proprietary source code meaning developers had no control over the software.

Koda might solve some of those issues, but it seems to me that the main one - control - is why most of the big developers left Kontakt to create their own samplers, and Koda won't solve that. Others have tried, Gorilla engine, Decent Sampler, Falcon, etc. Developers want control and you either use an open system like HISE or you build your own proprietary system.

FOUN IT . thanks.

Nice... Congrats !👍
But how can we export looped samples ? Piano/ pluck sampling is very easy.