@Lindon Perfect! Thanks!😀

@d-healey thank you so much😁

@d-healey Strange... I just need masks and proper blur too at the moment. And those layer limitations are bad 🙁

Graphics in general is a point that people are still asking for improvement and I understand Hise is not meant to be a photoshop clone. But when you hit limitations... I'd like to re-use OpenGL as well but not confident enough to deal with plateform specific issues... Well, it's one or the other I guess 🤷♂

@ILIAM Most of the docs are available as markdown files

https://github.com/christophhart/hise_documentation

You can also pass in specific urls, but the results are a bit hit and miss.

@Christoph-Hart said in Multichannel state of things:

It wasn't exactly an afternoon, more like 18 months...

Thank God they decided not to go with me....

@Christoph-Hart said in CSS :nth-child() supported???:

I can add an attribute to my parameter dictionary for scale/unipolar/bipolar,

I've added a method requested by @DanH where you can setup default properties for each new connection (so you can eg. set the base intensity to 75% or whatever floats your boat.

https://docs.hise.dev/scripting/scripting-api/scriptmodulationmatrix/index.html#setmatrixmodulationproperties

siiiiiiicccckkkkk!! Nice one Christoph!

@Christoph-Hart agreed. I have a M1 also with 64gb. I know you can store a whole app in memory with 16gbs, but i like to be over prepared 🤣

I run heavy multitracking sessions so I have to be ready. As far as HISE goes, never bogging. 👍

This might be helpful for people wanting to emulate the AurEx, this is a schematic version. The low band distortion is a classic hard clip config.

The high band distortion has a more cross over distortion type characteristic, not sure what the best way to program that is.

The clean signal is blended in with the two distortion paths.

57273f51-149e-4b6b-acb8-d257d303eb0b-image.png

@ulrik sorry its definitely user error, something in my project preventing ANY nodes from compiling not just this one. mysterious smh lol. this works fine in an empty project.

@d-healey I followed this method . Everything is working on my end except for one thing: the installer always shows 0 KB for the size of my data package. The samples are over 2GB but appears as 0 KB on the installer

@ulrik
Great, thank you! :-)

@dannytaurus yes, if the menu list is longer than the ui it will be drawn outside of it, like in your image.

@Lindon nope that aint it...something else is broken...

and its a line in my code..so that is the solution... just need to refer to Globals explicitly

@Chazrox 😹

@dannytaurus said in Scheduled knob task after initialization:

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

It can actually be used for other purposes.

But in my case, I'm actually using it for a bug workaround. When I buld a complex custom node with 23 parameters and use it in HardcodedFX, I noticed that in one parameter, the knob, wasn't getting its value during plugin initialization.

However, after init, when the knob is tweaked, the value is updated. That's why I chose this method. Creating a custom node with fewer parameters isn't a problem, by the way. As the number of parameters increases in custom nodes, the problems increase.

@lijas90 I usually chuck an Audio Loop Player in the module tree because it allows drag and drop of audio files to test with.

@Felix-W said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@CatABC said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@ulrik

@d-healey said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@CatABC Use constants instead of magic numbers

Sadly, I tried using constants, but the problem persists. Also, if I swap the positions of HIGH_KEY and LOW_KEY, and need to move the smaller value to the larger value, the contradiction still occurs.

const var ComboBox1 = Content.getComponent("ComboBox1"); const var ROOT = 2; const var LOW_KEY = 3; const var HIGH_KEY = 4; const var C1 = 36; const var D1 = 38; const var E1 = 40; const var B3 = 71; inline function onComboBox1Control(component, value) { Sampler.selectSounds("C3"); if (value == 1) { Sampler.setSoundPropertyForSelection(ROOT, C1); Sampler.setSoundPropertyForSelection(HIGH_KEY, C1); Sampler.setSoundPropertyForSelection(LOW_KEY, C1); } if (value == 2) { Sampler.setSoundPropertyForSelection(ROOT, D1); Sampler.setSoundPropertyForSelection(HIGH_KEY,D1); Sampler.setSoundPropertyForSelection(LOW_KEY, D1); } if (value == 3) { Sampler.setSoundPropertyForSelection(ROOT, E1); Sampler.setSoundPropertyForSelection(HIGH_KEY,E1); Sampler.setSoundPropertyForSelection(LOW_KEY, E1); } if (value == 4) { Sampler.setSoundPropertyForSelection(ROOT, B3); Sampler.setSoundPropertyForSelection(LOW_KEY, B3); Sampler.setSoundPropertyForSelection(HIGH_KEY, B3); } }; Content.getComponent("ComboBox1").setControlCallback(onComboBox1Control);

Ultimately, I set up two methods to call different methods depending on whether the value in the combobox increases or decreases.😹

Wow, this method is so cool! Thank you for the code comments; they really enlightened me.

@Elisee18 I have an old video showing a method of doing this (it requires scripting)

https://youtu.be/_s7LTRz8pEc