@d-healey I'm clearly not explaining myself very well

I see folks on this forum releasing HISE plugins and I often think I'd like to check out what they're selling and how it works/looks/feels, as 'research' (easy way to justify spending money ) and partly a kind of HISE pride thing.

Of course people are going to promote their Black Friday sales on real, prominent places. I just thought it might be nice if the HISE devs here had a place to drop their links so other HISE devs here could be aware of them.

Example:

Prototype Audio are 70% off, including the new Fraction https://prototype.audio
Noise Ash plugs are up to 80% off https://noiseash.com/
Wave Alchemy Triaz is 50% off https://www.wavealchemy.co.uk/product/triaz/
Sampleson Meta Piano is 33% off https://sampleson.com/metapiano.html

@d-healey Ah gotcha. No, I mean for devs here to share their Black Friday sales on plugins made with HISE, so others here can check them out.

But you're saying you don't think a lot of folks in this forum buy plugins? That's fair enough!

@d-healey There are several folks active in this forum that sell HISE-made plugins aren't there?

Can we do a little Black Friday self-promotion post? @Christoph-Hart, please delete if not!

I don't do Black Friday sales myself but I know a lot of folks do and it'd be a great time for us to be able to check out each others plugins at a discount, while still supporting!

Drop your links below!

I expect we all want slightly different sets of interactions with tables. I wonder if we can expose them as project settings, so we can all have what we want in our own plugins?

I think (so far ) my preference would be:

Table points: left-click to add, left drag to move, double left-click to remove
Lines: left drag to bend (only within the current line boundaries), double- left-click to reset

The current method of left-click-and-drag to both add a point and position it in one motion is nice, but I'd happily give that up for a two-step click-to-add then drag-to-move system if it means not dealing with right clicks.

Although I do quite like the idea of double left-click to both add and remove points, as @DanH mentions above.

I would also want (as noted above) dragging curves to be restricted to the current line segment only. Currently if I drag a curve up/down then move my cursor left-right it starts bending neighbour curves. Feels very weird.

@Yannrog Gotcha. Aside from the other points here, make sure the convolution impulse file is in your project's Audio Files folder before you drag/load it into HISE.

@Yannrog Did you export as a FX plugin rather than an instrument plugin?

@Christoph-Hart said in [Loop points clicking issue in HISE but not in other samplers]

There are quite a few unit tests in deterministic parts of the codebase (eg. the SNEX compiler is almost fully covered by unit tests), but the nature of audio software makes it super hard to cover DSP things like this.

Yeah, I totally get it. I'm not criticising at all. Just coming from a different world.

I don't use strict TDD in Rails - more like a write code, then write tests to confirm the code. But just that alone gives some pretty decent regression-proofing.

If there's anywhere else in the codebase where I could contribute unit tests, I'd be more than happy to jump in.

My first HISE project looks like it will be a simple synth with no samples or other 'external' assets. The only thing it uses are a couple of short audio loops, which I believe are compiled into the plugin binary.

Does this mean I can export as VST and AU and distribute those 'bare' files?

Mac: MyPlugin.vst3 and MyPlugin.component
Win: MyPlugin.vst3

This is the kind of thing that could be covered by unit tests. They would confirm functionality and prevent regressions.

(Not saying it's a HISE code issue, of course, just saying that unit tests could tell you if is or isn't)

Coming to HISE as a Ruby on Rails developer, it's always felt weird to me that there aren't any unit tests here.

But I guess that's the norm for C++ and/or HISE/JUCE-type projects, especially predominantly single-author projects?

@Lindon Makes sense

Is this what Export > Compile DSP networks as DLL is for?

https://docs.hise.dev/working-with-hise/menu-reference/export/index.html#compile-dsp-networks-as-dll

Then put them in a Hardcoded Master FX module.

https://docs.hise.dev/hise-modules/effects/list/hardcoded-master-fx.html

The user can choose between 4 wavetables.

Is there any significant UX or performance difference between using 4 Wavetable Synthesiser modules and MIDI muting between them, versus a using single Wavetable Synthesiser which loads a different wavetable when the user switches?

I realise at this scale it's unlikely to have a big difference, but say I had 100 wavetables that the user can choose between.

@ustk Awesome!

@ustk I just started learning the Modulation Matrix.

Got a snippet of this issue? I can take a look at it.

@ustk Thanks for the pointer. I added another commit other than the PR to ensure the new props are shown in the Data section of the UI.

@ustk Yeah, cheers. That looks more like what I'm trying to do

@d-healey I checked the commit you posted. You were adding a new default property to the DraggableFilterPanel, right?

When I add one to the plugin UI, the only default params that show in the Data section are ProcessorId, Index and FollowWorkspace.

In the Draggable FilterPanel docs, I see all the properties I would expect - AllowFilterResizing, ResetOnDoubleClick, etc. - but they're not in the Data section of the UI builder in HISE.

Also, your new HandleSize default property isn't in either the Data section or the docs.

I'm so confused!

@Oli-Ullmann By "free-running" I mean not reset on NoteOn events. And yeah, I found the IgnoreNoteOn parameter right after my last post

Thanks anyway!

Or can I set the LFO free-running? And would that work polyphonically?

Yeah... I have no idea what I'm talking about!

EDIT: found the LFO IgnoreNoteOn parameter which seems to do what I want