@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 said in Wavetable creation:

how does the wavetable player know we are using (say) 2048 samples as our cycle size and not (say) 1024 ???

Short answer: it's clever.

Longer answer: it guesses the cycle length based on the correlation of slices. It starts at 128 then goes up in powers of 2 to 2048. If it finds a very high correlation in the slices at any one of those slice lengths, it returns that as the cycle length.

I suppose this only works on files that morph fairly slowly between waveforms. If your file has a cycle length of 2048 but each cycle is very different to the next, it won't find a suitable cycle length and will fall back to resynthesis.

Also, if your file happens to have Loop Range metadata, it will use that first, before any guessing or resynthesis.

@DanSound @Lindon I just found the recent saveAsHwt(). Makes creating HWT files trivial now.

Just drop an audio file into a Wavetable Synthesiser, then run this code to save a precomputed HWT file.

const wc = Synth.getWavetableController("Wavetable Synthesiser1");
const dir = FileSystem.getFolder(FileSystem.AudioFiles);
const out = dir.getChildFile("MyWavetable.hwt");
wc.saveAsHwt(out);

For simple wavetables, this seems like the way to go, rather than the whole wavetable creator popup thing.

This totally removes any lag or pause from loading since the HWT is precomputed.

Video here: https://share.cleanshot.com/tD1qGCsv

@DanSound The next attempt actually worked!

I load the concatenated file into the wavetable synth then change the LFO range according to which section of the wavetable you want to play. I set the LFO to 25%, so with the offset it goes from 0%-25%, 25%-50% 50%-75% and 75%-100%.

Weirdly I had to use the Table Index Bipolar mod source with an LFO set to unipolar. But it works.

Video here: https://share.cleanshot.com/SZHZH3Lp

Updated project ZIP: https://wmd.d.pr/f/iVTorn

So this is how we can use audio files as wavetables and allow instant switching between them - with no need to build wavetables beforehand

Caveats: the plugin init will take longer because it’s doing calculations on the long concatenated file, and as you might notice in the video the waterfall flickers on a couple of the join points. Might just need to tweak the concatenated file.

const ws = Synth.getChildSynth("Wavetable Synthesiser1");

inline function loadWavetable(component, value) {
    local start = component.get("id").split("n")[1]; // 1-4
    start = (parseInt(start) - 1) * 0.25; // 0%, 25%, 50%, 75%
    ws.setAttribute(6, start);
}

for (b in Content.getAllComponents("Button")) b.setControlCallback(loadWavetable);

@DanSound I thought about concatenating the 4 audio files into one then using the setSampleRange() function.

That might might allow for instant switching between them, but the pause still exists. I think because even though the whole file is loaded, it still does the recalculations when you change the range.

Engine.loadAudioFilesIntoPool();
const wt = Synth.getAudioSampleProcessor("Wavetable Synthesiser1");
const wc = Synth.getWavetableController("Wavetable Synthesiser1");
wt.setFile("{PROJECT_FOLDER}" + "wavetable1234.wav"); // concatenated audio files
const length = 524288; // length of each audio file section of the long file

inline function loadWavetable(component, value) {
    local start = component.get("id").split("n")[1]; // 1-4
    start = (parseInt(start) - 1) * length;
    local end = start + length;
    Console.print(start); // multiples of 524288
    wt.setSampleRange(start, end);
}

for (b in Content.getAllComponents("Button")) b.setControlCallback(loadWavetable);

@capygeneral Did you try hooking up the combo box to LoadedBankIndex?

From the docs:

LoadedBankIndex - This will store the index of the wavetable in the current list.

@the-red_1 Unfortunately, 4.1.0 doesn't tell me which version you have. That version number is not updated very often.

If the git comma hash doesn't populate, then you likely have a very old copy of HISE.

Did you download the app HISE app, or did you build it yourself from the source code?

@the-red_1 Do you have a Script FX module called "Script FX1" in your module tree?

What version of HISE are you running? Go to HISE > Help > About HISE and tell us the git commit hash shown, like this image:

@13murderer The svf_eq node is a 12dB/oct slope, which is quite gradual.

If you need a steeper slope, you can either stack multiple svf_eq or choose a filter that has a steeper slope. The linkwitzriley and ladder filters both have 24dB/oct slopes.

If you're looking for a full-cut, DJ-style "Kill EQ", you'll need to stack more EQ nodes.

@David-Healey Roger that

@DanSound Not sure. Haven't tried compiling it yet. I think it's due to the calculations done after loading the file, so will probably be the same.

I'd like to test the caching more, to see if it can speed up the process.