@Sampletekk What's strange?

@dannytaurus said in What are you using to build UI for your plugin? What's your preferred way and why?:

What's the RAM implication?

All images consume RAM. When you load an image into RAM it's uncompressed, so it doesn't matter if you're using a png or a jpeg, the size in RAM is the raw bitmap size based on the dimensions of the image. You can see the true usage in the pool table window in HISE.

Here's the calculation:
MB = width * height * 4 * numFrames / 1024 / 1024

@dannytaurus Sounds interesting, can you share some examples in context - are they in the images you posted above?

@dannytaurus said in What are you using to build UI for your plugin? What's your preferred way and why?:

I'm curious to know the performance difference in HISE between filmstrips and vectors/images drawn and manipulated in HISE

I haven't noticed any significant performance difference on my UIs - but if you start using lots of shadows or blur effects you might run into issues.

Using filmstrips has three issues:
RAM usage.
They don't scale well to different sizes.
They're not dynamic, you can't change the design on the fly via scripting.

@ericchesek look and feel should do it

@xsaad When you change the mode it adjusts the pitch of the notes to produce the rast scale. All the code is at the link I gave, specifically this file - https://codeberg.org/LibreWave/Osiris/src/branch/main/Scripts/Maqams.js

@pcs800 I recommend you start with this video

And then possibly this one

@xsaad said in Arabic Maqams:

I tried searching on patreon but I didn't find anything.

All my code is available on Codeberg.

For the knob layout someone on the forum helped me with the maths, probably @ustk

In an update I replaced the knob with a button grid

For a project I'm currently working on I made a more flexible microtuner which I posted a video about on YouTube and Patreon.

@bendurso Looks like a bug, seems to happen with any effect that has a modulation chain.

@pcs800 You can set the visible property in the button's callback

@ustk said in Project file extension:

preset (called Archive)

.hip

@bendurso got a snippet?

@bendurso You have to delete the child processor from the chain in the module tree. For example if you have a filter and you are modulating the frequency with an LFO, the LFO is the child processor, so you need to delete it.

This is not something you do through scripting.

@mrcurious I usually work with a designer and they will build the design in a vector program, usually figma these days. Or if I'm designing it I'll use inkscape.

Then I'll take that design and reconstruct it in HISE using look and feel.

@Braziliandutchy are you trying to compile HISE?

@AxiomCrux have you compiled HISE?

@VirtualVirgin Ah I see, then yeah a panel is probably the way to go unless you want to return them in an array or object

@VirtualVirgin You can store them in consts within on init or in a namespace like any other component reference.

@VirtualVirgin With a few exceptions .get only retrieves properties that are accessible in the property editor.

You can use this method to get the children. As is always the case when getting component references, this should only be used in on init (or an inline function called from on init).

for (c in Content.getAllComponents(""))
{
	if (c.get("parentComponent") == "Panel1")
		Console.print(c.getId() + " is a child of the panel");
	else
		Console.print(c.getId() + " is not a child of the panel");
}

@Simon Nice! I like the minimal setup, just a laptop and a keyboard, nothing distracting.