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

Where is the documentation for local Look And Feel?

I'm trying to create a LAF for a floating tile MIDI keyboard but I don't know where to find the functions that draw the parts of the keyboard.

I want to customise the octave number text because it doesn't work well with different key widths, but I really don't know where to start.

I feel like there must be a reference somewhere for what I need, but I don't know what to search for.

@lplr I just started using Figma to design the UI for my next plugins. It's mainly vector but you can drop images in there too.

It'll work fine with any of the assets from the aforementioned UI design services.

The main advantage for me is speed of iterations. You can easily nest and group things, and use constraints to keep things evenly spaced and shrink/grow as you modify your layout. You can't do this very easily in the HISE Interface Designer.

Once you're happy with the design, you can take the UI elements' position and sizes straight into HISE scripts that create the UI.

I know it's an extra piece of software to learn, but the flexibility of this way of designing is a winner for me. It keeps a nice separation between functional and visual design.

Additional bonus is I can share the progress of the visual design with someone else (stakeholder, collaborator, etc) without having to either share the HISE project or having to continually take new screenshots of the UI in HISE to email/message to them.

If you have a team it's even better. The UI designer can work on the visual design in parallel with the plugin/DSP developer, and as long as they have a central interface document - showing what parameters and displays the plugin exposes in the UI along with ranges, units, etc. - then combining them near the end of development should be cake.

@Chazrox Does this help? https://forum.hise.audio/post/2480

Bit easier than reading, adjusting and rewriting:

const var FloatingTile1 = Content.getComponent("FloatingTile1");

var data = {
    "Type": "FilterDisplay",
    "ProcessorId": "Filter1"
};

// either
FloatingTile1.setContentData(data);
// or
FloatingTile1.set("Data", JSON.stringify(data));
// both ways work but I find the first one easier to read

@d-healey 100% bot

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