I'm fortunate that I started with a (small) audience, and I'm selling to a focussed crowd. My plugins serve a very specific niche and the producers there are always hungry for more authentic products.

I've never done any paid ads. I might do an experiment on Instagram one day. I see a lot of adverts for plugins in my feed and I'm curious how effective they are.

I sell on Gumroad. They take about 15% fee, then you pay payment processor fees. I haven't done the maths for the total cut but I'd say it's less than 20%.

It's a good deal for me because it includes basic web presence, file hosting, secure delivery, payment processing (cards, Apple Pay, Google and PayPal), email marketing and analytics.

I started selling in September 2022. I'd done a couple of free plugins before that through various platforms like SimpleGoods and SendOwl but didn't take it seriously until later.

When I started selling I posted each new product on my Facebook and Instagram accounts. The engagement was pretty good to start with but I noticed that over time, I got more results from sending emails to my ever-growing email list. When I launch a new product now, I only send it to my email list at first. Then later I post short clips to Instagram but they're supplemental to the email list.

You NEED an email list. They say "the money's in the list" and in my experience, that's 100% correct.

Free products are a great way to build your email list. Most people stay subscribed and as long as you don't flood them with emails, they're happy to receive them.

This is my email strategy:

• Launch email for every new product with 20% discount code, valid for 2 weeks
• Reminder email 48 hours before the launch discount ends
• One email per month with 20% discount off a single product, valid for 2-3 days

That's it. I don't like to bombard my list with too many emails. I'm on some Gumroad seller lists where they send continual discounts, sometimes daily. This would be way too much for me as a customer.

Gumroad includes email marketing, which is a bonus because when your list gets large things like Mailchimp, ConvertKit, etc get into the $100's/month.

I can target emails to people who have or haven't bought specific products. Very handy for offering a discount only to those who haven't bought something. Or offering a discount for a product Y to those who have already bought product X. You can also target by how much someone has spent, so you can offer extra discounts or free stuff to your most loyal customers.

Gumroad also includes extra features like affiliates (having others push your products for a % split), collaborators (where you can split a products revenue with someone else), email automations (for sending drip emails to customers - I don't use those) and upsells (recommended products at checkout).

It does have some downsides. The download links in the receipt emails sometimes don't work and you have to send a link manually to the customer (Gumroad have so far refused to acknowledge this as an issue). I also find their fees to be expensive compared to other services, but for what I get built-in I still think it's worth it for now.

Something else that might be of interest is that Gumroad recently made the source code available, so if there's a feature you want to add and you're handy with Ruby on Rails and JavaScript you might be able to contribute.

Happy to report this has been merged in to develop branch!

@Christoph-Hart Just came back to look at this and finally solved it!

HISE uses the system Ruby version to look for xcpretty.

If you're using a Ruby version manager like rvm, Rbenv, ASDF or chruby you'll need to switch to the system Ruby to install xcpretty.

I use chruby so I did:

$ chruby system // or however your version manager switches to system Ruby

// Confirm I'm using the system Ruby
$ ruby -v
ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin23]
$ which ruby
/usr/bin/ruby

// Install xcpretty for the system Ruby
$ sudo gem install xcpretty
Password: ********
Fetching rouge-2.0.7.gem
Fetching xcpretty-0.3.0.gem
Successfully installed rouge-2.0.7
Successfully installed xcpretty-0.3.0
2 gems installed

// Run the same command that HISE runs to make sure it's there
$ gem list xcpretty
*** LOCAL GEMS ***
xcpretty (0.3.0)

Those categories are for Logic's native plugins. Apple doesn't allow you to list your plugin there.

You'll notice that there are zero third-party plugins under those categories.

All third-party effect plugins are under the bottom category of Audio Units.

Same goes for instruments. They're under bottom category, AU Instruments.

It would be cool to have a SemiTones control in the Waveform Generator, like the Sine Wave Generator already has. It would allow for easy interval creation and control.

I checked the source code and it seems doable - unless I'm missing something, which I almost certainly am.

@Christoph-Hart would you accept a pull request for this if I could get it working?

Something like this:

@Mickolos You're missing the * in your regex.

Instead of
const comps = Content.getAllComponents("^.(Knob|Button).$");
use
const comps = Content.getAllComponents("^.*(Knob|Button).*$");

The dot is looking for exactly one character. The * modifies that to look for any number of characters, including zero.

The way you had it will only match components that have exactly one character before the word and one character after the word, like 1Knob1 or ZButtonZ.

If in doubt, use a regex tester like regex101.com. Put the regex in the top text field then add some example component names including wrong ones, to see which ones the regex matches.

The next image shows that the only ones matched by your original regex are the last two.

The next image shows that with the extra * in the regex, ALL the names are matched.

@Morphoice For the effort you'd need to style the built in preset browser you may as well build it yourself.

I'm in a similar situation and just starting to build my own.

Would be good if there was a snippet for a simple preset browser. Shows a single list view of the available presets, No user save functionality. Just loading existing presets.

If I make anything that I'm remotely proud of I'll add it.

@bendurso For that price it's tempting to get the new M4 Mac mini just for compiling HISE and running Parallels for Windows exports.

@d-healey @Dan-Korneff @Oli-Ullmann Sorry, I was thinking about Maize Sampler

When you export at double size make sure the image name ends with @2x so HISE can recognize the format.

Like this: "background @2x.png"

EDIT: I don't think this is actually a thing in HISE. I was thinking about another app.

I'm using a vertical slider as a volume fader.

I want to use a custom image for the fader cap but making a filmstrip seems a bit wasteful of both time and plugin resources.

How do I implement a simple static fader cap image at the 'movement' point of the slider?

I feel like this is going to be either [1] using LAF to draw the fader cap image at the value point, or [2] using CSS to draw the fader cap as a background image in one of the slider's pseudo elements - but I genuinely have no idea how to look this up in the docs or the API reference.

+1 here too

@Chazrox said in Chord Player Inversions || Help with Indexing!:

I also got midi out to DAW working as CHORDS or ARP mode! yee!

Looks cool!

Since compiling as MIDI FX is currently not working (as I understand it), are you planning on releasing this as an instrument instead?

Trying to understand how that would work in various DAWs. I'm assuming you're taking a MIDI input from the DAW (either from a connected controller or a MIDI clip in the DAW), then outputting MIDI from your instrument plugin that is meant to play another instrument plugin?

Routing like that is easy in Reaper but other DAWs seem less flexible (I'm looking at you, Logic).

@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:

Engine.loadAudioFilesIntoPool();

Are you sure you aren't calling this function anywhere else in your code?

@Mickolos Other than the incorrect regex, your code seems have a couple of other problems:

1. You put all knobs into 'comps' but then later loop through 'knobs', which is not defined in your code.
2. You create a look and feel called 'ValueLAF', then later assign one called 'knb_LAF', which is not defined in your code.

I realise these might be copy/paste inconsistencies and your code is actually correct. But just wanted to point it out.

@Mickolos You're missing the * in your regex.

Instead of
const comps = Content.getAllComponents("^.(Knob|Button).$");
use
const comps = Content.getAllComponents("^.*(Knob|Button).*$");

The dot is looking for exactly one character. The * modifies that to look for any number of characters, including zero.

The way you had it will only match components that have exactly one character before the word and one character after the word, like 1Knob1 or ZButtonZ.

If in doubt, use a regex tester like regex101.com. Put the regex in the top text field then add some example component names including wrong ones, to see which ones the regex matches.

The next image shows that the only ones matched by your original regex are the last two.

The next image shows that with the extra * in the regex, ALL the names are matched.

@Christoph-Hart Nevermind, found this post https://forum.hise.audio/topic/1259/ahdsr-release-curve?_=1749402810437

Still, would be lovely to have release curve for AHDSR, if it's doable.

@Christoph-Hart That would be perfect if I could adjust the release curve - is that possible?

@d-healey RAM, I think. Swap and Memory Pressure go off the charts in Activity Monitor.

My Mac is basically unusable for the whole hour that it's compiling.

@d-healey Thanks for your help, as always!