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.

Can you do this with CSS?

for styling the items in the list, use the HTML tag selector for table rows tr . It supports :hover , :active and :checked pseudo states with the same concept as the Buttons

Very cool!

@Morphoice Sounds great so far!

The Wiggler is really cool. Very limited, sure, but the expressiveness is great for a DIY project.

@griffinboy said in Midi Player :

@Robert-Puza

One of my frustrations with midi keyboards is that they generally only detect the velocity at which a note is initially pressed.
I wish more keyboards had continuous velocity control.

Do you mean aftertouch?

Many MIDI controllers/keyboards have this feature.

It's mostly channel (monophonic) aftertouch but some have polyphonic aftertouch.

@VirtualVirgin I think you need to load the image(s) into the pool first.

Engine.loadImageIntoPool( String id)

@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.

Check out the Cleveland Music Hothouse DPS pedal project.

It's based on Daisy Seed and the physical pedal has the Chase Bliss style layout of 6 pots, 3 multi-way switches and 2 footswitches.

Anything that can run on a Daisy Seed can run in this pedal. The best part is, all the stereo audio I/O boards are already there so it's a really easy build.

I've got a kit sitting here next to me waiting to be built.

@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.

@mmprod said in scrolling audio display/visualizer:

By any chance, can I style things other than color as well?

Like what? There's not much else to customize.

You can already set the width and height, the colours used to draw the waveform, including the stroke width of the outline, and the colour of the background. By setting the buffer size you are also setting the scroll speed.

In my plugin the audio is mono so I display only one channel of the waveform by putting the floating tile in a panel and making it twice the height. The bottom half is cut off by the panel bounds.

@mmprod said in scrolling audio display/visualizer:

@Lindon Also, can I zoom out even more? Like more than 32768 samples

Synth.getEffect("Analyser1").setAttribute(1, 65536);

This is double the 32768 available in the dropdown, and therefore half the speed of scrolling, and seems to be the maximum allowed. Settings higher than this are ignored.

The '1' refers to the BufferSize attribute.

@mmprod said in scrolling audio display/visualizer:

Is it style-able any further?

Use a LookAndFeel script

const laf = Content.createLocalLookAndFeel();

laf.registerFunction("drawAnalyserBackground", function(g, obj)
{
	//fill the background
        g.fillAll(Colours.blue);
});

laf.registerFunction("drawAnalyserPath", function(g, obj)
{
	// draw the outline path
        g.setColour(Colours.red);
	g.fillPath(obj.path, obj.area);
	// fill the path
        g.setColour(Colours.red);
	g.drawPath(obj.path, obj.area, 1);
});

Content.getComponent("Analyser1").setLocalLookAndFeel(laf);

@Christoph-Hart Excellent!

Is there any reasonable way I could've discovered that on my own through documentation?

Or is it a 'click around and see' kind of thing?

@aaronventure An autoscroll toggle would be cool for the console.

Is it possible to load a MIDI file into the HSIE transport when loading a preset?

I usually keep a MIDI file running while I'm tweaking things but I have to load it every time I open the preset in HISE.

Is there any way to load it automatically?

@d-healey said in Issue compiling HISE on Mac:

@bendurso said in Issue compiling HISE on Mac:

Debug is not slower than release?

Debug will build faster because it doesn't have to optimize as it does for the release.

Compiling a Release build is actually quicker for me than compiling Debug.

In Safe Mode (I can't realistically compile in normal mode):

• Debug takes ~13 mins
• Release takes ~10 mins

The Release app is much smaller too, 44MB compared to 195MB for Debug - is this normal?

EDIT - just tried building Release on GitHub and it was indeed slower - 23 mins compared to 11 mins for Debug.

@Lindon I find deleting the build (not Builds!) folder usually fixes this. Then I'll get the proper timestamps on both Debug/HISE Debug.app and Release/HISE.app

Projects > standalone > Builds > MacOSX > builds (delete this folder)

Also, sometimes Xcode builds HISE and the app size is around 100KB so I assume it failed but when I double click the HISE app it opens properly. Very strange.