@David-Healey I just had a go at fixing this. Is that what you mean?

HiseSnippet 1112.3ocsVs2aaaCDmJIJKwacqEne.H7e4roYH+pIcACMO8pwxCi4rhMDDTPKcxhKRjFRTMwXneH12z8MH6ndXKO6klZfI.av6Eue2wi2w9QRGHNVFQLpb0jw.w3qLGLQn7O1mwEjdmPL9ZyyYwJHhlw5nIiYwwfKwvX8eRyvX6MHoe+8aNhEvDNvLVDx6jbG3LdHWMia+C9YdPPWlKbEOrj1sOnmiTbrLPlf3YcSaxXlysrQvELsZqYRdKK1mX7sl1scX60zqSqVu9061wcH330.FtqCytCyqCC41l0tSi1DiMO0kqjQCTLEDia5QR2IC7k2Ixbv63w7gAflnAY.54L1ji84At8KRNwDhwF8mkpVOKU8Ryy4t7o7mkxddp.5LKJmzLV6wfTiOCHYTBRajAoWXNvIhOVMShFOeoYOAdB5wvylxPISWxZ+05lGKQMDp5gragtQHwTKp0z11hh+sy9UpfmOwJZ.yi9izBSbh.LRNS5vBNSJu8PgaW.BpoUGUrdDLhqqe5lHbTbonVU2H1c8kiSFeNHRNBOhGEISDtUsndE5LxhJG9G6T4OqPwuQ0iAUVcQsp12am+UEcQlXOrd5W.GUsqssrsz.F+cCJ9iOQTzSAg+29+CrHJCiXjUcFFs3dVvdLy8PjCJ7Z1012P+NZSKJ65FSW07F52SaqW0Jc0M6uPHo2Vd7a4i7CveJvk9FZln35ih.PP+gozCCRf4CacpCb0QOSLJ.pkiHK5d6TBmJ3dUAPy0HCt6YUDCHnmsNE1Md0LFstYIHu.U24yUyfEJuKVaTq5IfGKIPgI1FsqaOUtNyeHFpBv8JDVowuFeVSQoEsZ.3opVbBlU1crLbn7H48MJU7MRikvwRAnc3TMzVNkPCnEJOwhhc1u37lJEWHUvkhZ5i7sq7wJz+sHOukJSiiHYP.DsTw5FbQOlg0DIgCgHK7PRexVnHdgd9tDa9z5R3jkVJonTzSvUWNFxo6JCb0290qWrmBIOup6tjiPTUUZukmm2aoHuR3t5VKSSyjzPnbyexu16DlhUrY39h9ZLDo35Px3D3C3vgrFWaadBDeqRNF6yO8.kXrUlqeVQaMl.BR86VloqaPturCmTl.KICKFlr8lDxCOLO2lkYeG2U4OyZ9A9f9tXYNjR35KdhoDDclFMyPlowKwEgrTdqunO+8CzXCSLei4kBnxU2IqbkOd8GGXtPedbBizMIfoleridfbt.rJatd8594hXtZR4A1eFyhrezYQOUH9By9bki+xw3ZKAiXsy+GXLeB9yLO0yC6bNCfaX182V0w0eB2icpUbwnyYpHttF3hjvAXYnCfdWf0xw55h0z2Ayns0z5Lv.P3lR7.9kKrgl1HWXiBgX0kSj78NY2b0uQXqTNHlDougZa7wbHMcIWVCwmr7dGm42pELr4pZXqU0v1qpgcVUCe0pZ3tqpg68oMT+hxCSTxvrqMDx48OMs4pgwoBFVAlVsR9GztgJYG

Content.makeFrontInterface(200, 200);

const laf = Content.createLocalLookAndFeel();

laf.registerFunction("drawPopupMenuBackground", function(g, obj)
{
    g.setColour("0x00000000"); // any transparent colour
    g.fillRect([0,0,200,200]);
});

laf.registerFunction("drawPopupMenuItem", function(g, obj)
{
    var a = obj.area;

    var padArea = [a[0] + 2, a[1] + 2, a[2] - 4, a[3] - 4];
    g.setColour(obj.isHighlighted ? Colours.green : Colours.blue);
    g.fillRoundedRectangle(padArea, 8);

    var textArea = [padArea[0] + 8, padArea[1], padArea[2] - 16, padArea[3]];
    g.setColour(Colours.white);
    g.setFont("Default", 14.0);
    g.drawAlignedText(obj.text, textArea, "left");
});

const ComboBox1 = Content.getComponent("ComboBox1");
ComboBox1.setLocalLookAndFeel(laf);

The drawPopupMenuBackground object should probably include an area, and the popup menu items still have a subtle drop shadow. But they're both fixes for another day.

PR here, if it's useful: https://github.com/christophhart/HISE/pull/805

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

@ustk Could do, but I prefer to keep the button's 'on' state synced to the panel's visible state.

If I start flipping values as a workaround, my future self will not thank me when he looks at the code in 2 years!

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! 🥰️

@DJJD12345 Faust is an optional external dependency. It's not required unless you're actually using Faust code in your project.

@Lindon Node looks cool. You could probably build that in HISE as a standalone app.

@13murderer I think your reply was aimed at @DanH

@Lindon said in Wavetable creation:

Well I assume you mean "audio file 2 as frame 2", but in any case..."interpolates" means what for a set of 2048 values(an array)?

Sorry, no. I mean:
Audio file 1 is frame 1
Audio file 2 is frame 128
Audio file 3 is frame 256

That will make a full 256-frame wavetable. That's 256 frames of 2048 samples each.

Interpolating as in morph each value of the 2048 cycle length to the next. Like, sine wave slowly becomes a saw wave, or whatever.

There are different methods of morphing between waves for a wavetable. Spectral is a different way. You'll have to read up and find the way that best suits your needs.

Personally, I'm only working with 'primitive' waves and morphing between them, so linear interpolation is fine for me.

@Lindon said in Wavetable creation:

So how are they building their wavetables?

Personally, I'd either use Vital (free VTS/AU) or I'd write a script that takes in 3 audio files of 2048 samples, then interpolates between them with audio file 1 as frame 1, audio file 2 as frame 128 and audio file 3 as frame 3.

@Lindon said in Wavetable creation:

• so if they build their own wavetable wav file they would know it needs to be one of these values...

If they're building their own wavetables, just have them put Loop Range metadata in the file which sets the cycle length.

Then they won't need to choose it from a dropdown.

It makes their wavetables more portable too.

@JamesC You can adapt the example in the docs:

https://docs.hise.dev/hise-modules/effects/list/convolution.html#parameters

Instead of a combo box, use control callbacks on the 2 buttons to call setFile(). You'd put the list of impulse names in an array, then the buttons would load the previous or next impulse.

@David-Healey What about setting it with preprocessor definitions?

#ifndef HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TITLE
// Override this in your build settings (preprocessor definitions)
// Example:
// HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TITLE=Samples ready
#define HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TITLE "Sample Folder changed"
#endif

#ifndef HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TEXT
// Override this in your build settings (preprocessor definitions)
// Example:
// HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TEXT=Samples found. Please reload the plugin once.
#define HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TEXT "The sample folder was relocated, but you might need to open a new instance of this plugin before it can be used."
#endif

Function that draws the text would be changed to use the new defs instead of hardcoded text:

if (handler.areSampleReferencesCorrect())
{

  // PresetHandler::showMessageWindow("Sample Folder changed", "The sample folder was relocated, but you might need to open a new instance of this plugin before it can be used.");
  PresetHandler::showMessageWindow(TRANS(HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TITLE), TRANS(HISE_SAMPLE_FOLDER_RELOCATED_ALERT_TEXT));
}

Or do we have too many undocumented preprocessor defs already?

@Lindon How would you make sure the user's file has a cycle length of 2048?

@Orvillain Looks like the full Wavetable Creator tries to find a cycle length from the root-note, but since the dropping an audio file into a wavetable synth doesn't have a root note it does it differently.

Audio files uses [1] metadata Loop Range, then [2] guess cycle range from correlation, then finally [3] resynthesis.

For simple 'traditional' wavetables, the audio file route is probably fine but for more complex ones the full Wavetable C reactor might be better, yeah.

The only reason I went down this whole route of using audio files is because I opened the Wavetable Creator and thought 'Nope!' . So when I saw using audio files would work for my use case I wanted to learn how to do that.

@the-red_1 Use the latest commit 3c36e36c0c27adf97be22206fdebf87ec9c7eeb0, as as @David-Healey says, use the develop branch.