I thought at one point the "full mod range representation" has been made available so it covers the full range of lastModValue (like in the above post)

Was I dreaming?

modvalue.gif

@David-Healey I added a dragThumbOnly property to Scriptslider

if enabled:

A left-click on the slider track no longer starts a drag or jumps the value.
HiSlider::mouseDown hit-tests the click against the drawn handle centre
and only forwards to Slider::mouseDown when the click lands on the
thumb (within dragThumbSize/2 + dragThumbPad). Right-clicks still pass
through for MIDI-learn / context menu. Snap-to-mouse is disabled, so dragging the thumb is relative and the
value does not snap to the cursor on click.

if anyone is interested it's on my fork
https://github.com/morphoice/HISE/commit/7b206d1951558381a2a38b2691a504d7542eec56

however the dimensions are currently hardcoded to my needs, so there will be further changes needed to make this a general feature. I therefor didn't make a PR

@David-Healey The Problem was that I was including the same Expansions.js in the actual Expansion! Ive commented that and deleted the file and is working in the exported Plugin!

@David-Healey Thank you, kind sir.

@paper_lung Gotcha. Not too far behind then. Still worth getting up to date though 👍

@VybeCodeDSP StripKit looks really nice!

It seems you only support the Windows platform?
If so, are you planning to support MacOS?
If so, let me know if you need a beta tester!

@paper_lung Check this thread: https://forum.hise.audio/topic/5499/audiowaveform-laf

@Sawatakashi said in Which version of faust works fine for HISE？:

it crashed after i loaded a faust scriptnode.

A blank node or are you copying in a script?

@dannytaurus Yeah, keeping the colours tidy in your code is easier in the end. Then you can set the component colours from script when needed and everything updates automatically if you adjust something instead of copy/paste in all components...

I tend to to everything I can in paint routines, the less components in the tree, the happier I am!
That being said... In order to reduce CPU load, I still tend to keep fixed drawing (bg, mask, etc...) in separate panels so the LAF function job is only constrained to what is really necessary. I also keep all the math constants externally, unlike the example...

Other issue with the "multiple panel masking technique" is that when you want to move it, it can be very annoying, unless adding them all in an holder panel, which is one more component... 😬

@Chazrox Have got a Glitch FX and a Granular Pitch Delay. Would be interested in the pitch and varispeed!

@Felix-W Break it down. Make a minimal project with one sampler where notes only trigger during legato transitions. Once you get that working you can start to incorporate it into your project.

@David-Healey Ok,

Is it possible to discuss in private?

@dannytaurus said in Stop pruning default values from XML?:

because I'm setting some values in script that happen to be default values.

Hmm this might be the source of an issue I was having too, I might try it.

@David-Healey Yes the Global Modulator Container worked beautifully for this.
Thanks to your video I've now also understood the global modulator container better.

Regarding the body + release in one sampler:
That's what I've tried first, but it's bugged when using together with loop regions.
It's what I described in this earlier post you commented on:
https://forum.hise.audio/topic/14799/loud-click-artifact-when-using-releasestart-with-looping-enabled/14?_=1781354181861

I haven't gotten around to testing it with 48kHz samples yet.
But by now I've found enough use cases to split apart the sections into dedicated samplers.

@chimaera_09 Make the button show/hide a panel. Use the panel to house all your extra controls.

const pnlSettings = Content.getComponent("pnlSettings"); const btnSettings = Content.getComponent("btnSettings"); btnSettings.setControlCallback(btnSettingsControl); inline function btnSettingsControl(component, value) { pnlSettings.showControl(value); // button shows/hides the panel }

You can add a button in the panel to close it too:

const btnSettingsClose = Content.getComponent("btnSettingsClose"); btnSettingsClose.setControlCallback(btnSettingsCloseControl); inline function btnSettingsCloseControl(component, value) { if (value) { pnlSettings.showControl(false); btnSettings.setValue(0); // sets the 'off' state of the button } }

Speaking of which...

https://github.com/christophhart/HISE/pull/984

I can't believe the math were wrong the whole time
-> upDecayTime was inverted...

@dannytaurus Good job detective!
I agree to the WTF, seems that developing new protocols of all sorts but there's still no agreement whatsoever in the way DAWs handle such a simple task... Shame...

@dannytaurus said in Anyone doing factory presets only, with no Save button?:

power-user feature

It for sure is a power-move and not as intuitive as a user preset.

@zachhealy1005 said in Linux:

so compiling hise on my laptop is in fact impossible.

If you reduce the number of compile threads to 1 or 2 it might still compile.
make CONFIG=Release -j 2