@bendurso Today I learned that right-clicking a module in edit mode shows a different context menu to right-clicking not in edit mode.

PR that adds StartPhase1 and StartPhase2 to Waveform Generator.

Coded for my own needs but someone else might find it useful.

Works great for setting a random phase offset on MIDI note-on.

Works independently for Osc1 and Osc2.

https://github.com/christophhart/HISE/pull/792

EDIT: from this conversation https://forum.hise.audio/topic/13720/free-running-or-randomised-phase-for-waveform-generator-oscillators/9

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!

Some of you might remember my troubles compiling HISE on my 2020 M1 MacBook Air with 8GB RAM.

It was taking an hour to compile a debug version, if it finished at all - it usually crashed.

Seemed like the 8GB RAM limit was the issue, causing havoc with memory swap.

My solution then was to write a build script that builds my version of HISE using GitHub Actions, whenever I push a change live. It took about 15 minutes round trip to push a change, wait for the build, then download the build artefact to test the change.

I used this long-winded system to add features and fix bugs for the last few months. Painful!

Finally I upgraded to a 2024 M4 MacBook Air with 32GB RAM and I can now build debug HISE locally in 20 seconds! It's like a dream!

Just wanted to put this out there in case anyone else is having issues compiling on an 8GB MacBook.

@aaronventure said in Quick F5 tip for Mac users:

@d-healey Hold Shift while typing to amplify my anger.

Exactly this! Left pinky on the SHIFT and hammer those keys!

Same on iOS. Instead of double-tapping the shift key to lock it, I shift uppercase every character, just so it makes me more angry!

@d-healey LOOK AT THAT BEAUTIFUL RELEASE CURVE! 🥰️

@Chazrox Wouldn't you have to call SomeFunctions.HelperFunction() outside the namespace?

I use Myriad to batch process samples. It's saved me untold amount of hours in the last few years.

https://www.zynaptiq.com/myriad/

You can run individual tasks or create workflows to batch process in groups.

My usual workflow for trimming samples is something like:

1. Trim End below -70dB (tweak this based on the group of samples)
2. Fade End below -60dB (this produces a nice fade to zero at the end)
3. I also usually trim sample start below -80dB, at zero-crossing, because Logic Auto Sampler always has a bit of start gap.

You can do a lot more in Myriad (normalising to peak or LUFS, trim around loop points, set MIDI notes and velocity ranges, etc). Very handy app!

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

@d-healey By 'might' do you mean we don't have control over it?

Some of you might remember my troubles compiling HISE on my 2020 M1 MacBook Air with 8GB RAM.

It was taking an hour to compile a debug version, if it finished at all - it usually crashed.

Seemed like the 8GB RAM limit was the issue, causing havoc with memory swap.

My solution then was to write a build script that builds my version of HISE using GitHub Actions, whenever I push a change live. It took about 15 minutes round trip to push a change, wait for the build, then download the build artefact to test the change.

I used this long-winded system to add features and fix bugs for the last few months. Painful!

Finally I upgraded to a 2024 M4 MacBook Air with 32GB RAM and I can now build debug HISE locally in 20 seconds! It's like a dream!

Just wanted to put this out there in case anyone else is having issues compiling on an 8GB MacBook.

My previous plugins were all made with Maize Sampler. In those plugins, the preset list appears as a large panel, out of the bounds of the plugin UI.

Can we do this in HISE? Or are we limited to drawing panels within the plugin bounds?

@lijas90 I usually chuck an Audio Loop Player in the module tree because it allows drag and drop of audio files to test with.

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

@d-healey Mainly because the default method of showing the octave numbers doesn't really work for small and large key sizes, but also partly to avoid using LAF.

Since I know I'll want control over octave numbers in every plugin I create - and I probably won't want to override anything else about the already-very-nice-looking keyboard - it made sense to me to bake it into HISE rather than using LAF every time.

@d-healey In this case I ended up adding some new data properties to the keyboard floating tile that allow me to customise the octave number text.

Fun exercise, but not worth a PR, right? Since I assume most folks would use LAF for this?

{
  "KeyWidth": 26.0,
  "DisplayOctaveNumber": true,
  "OctaveTextHeight": 14, 👈
  "OctaveTextMargin": 6, 👈
  "OctaveTextColour": "0x55000000", 👈
  "LowKey": 24,
  ...
}

@d-healey Right, that's what I tried but wasn't seeing any autocomplete for laf.registerF but I just figured it out.

I have to hit F5 after creating a new variable before the autocomplete will work.

So, in terms of available versus documented functions - are all the available functions listed in the autocomplete but some of them just aren't in the docs? Or are there available functions that don't even show in the autocomplete?

@d-healey Autocomplete popup from what? What would I type to trigger the autocomplete that shows the available LAF functions?

@d-healey Great, thanks! But my real question is - how do you know what functions there are?