Hello,
Just wondering, what happens if you use Mono2Stereo on a stereo input?
Does it leave the stereo signal as it is, or does it sum it to mono first?

I’m trying to make sure it won’t cause any unwanted channel collapsing or weird phase behavior if I use it in a ScriptFX that might sometimes receive stereo input.

Thanks!

@d-healey
.....wooooow, I feel dumb,
thanks!

@d-healey
I added below my message a screen of the code where I set the slider style (style: Vertical) using setPropertiesFromJSON.

@d-healey
I did it that way, but it doesn’t solve the problem

Hello,
I’m having trouble getting my filmstrip to show up when I export my project as a VST3.

It only appears if I manually change the numStrips value (for example, from 125 → 124 → 125 again , then it works, at least in the Interface Designer). Otherwise it stays invisible.

I unchecked showTextBox since I know it can be buggy, and I also tried loading the filmstrip through JSON in the code editor, but it still doesn’t show up, not even in the interface preview.

I’m sure the number of frames is correct and same for the location. Is there another setting I need to enable/disable to make the filmstrip export properly?

Also, as soon as I hit Compile in the code editor, the filmstrip disappears again.
(Attached a screenshot of my slider properties in case it helps.)

It’s interesting, but I don’t know what it changes for Hise users. Does it just mean that we don’t have to pay for a Steinberg developer license, or does it go further than that?

Hi,

I noticed that text in HISE looks smaller than in Figma, even when the interface size and font size are exactly the same.
For example, a 12 font in Figma looks bigger than 12 in a HISE Label, even though my .makeFrontInterface() matches the same pixel dimensions as my Figma export.

is there a ratio to calculate so the font sizes match visually between Figma and HISE?

@It_Used wow thanks that’s awesome ! I’ll be able to dig into all of this.

@It_Used said in Display slider value with custom font, size, and position:

@Yinxi create visual mockup your idea, and i maybe implement this!

Reply

I was thinking something like this : .

And when I change the slider value it will also change the value at the top left

Hi,

I’m trying to display the value of a slider (for example, the gain of the "Simple Gain1" module) in the interface. I would also like to be able to change the font, size, and position of the displayed value.

I’ve tried to find a solution, but I’m a bit overwhelmed by all the information. I imagine I need to use a panel script and paintRoutine for LAF to draw the value of the gain, and retrieve the gain value with a function, but this is beyond my current level in HISE.

If anyone has a working example or guidance on how to display a slider value like this with customizable appearance, it would be really helpful.

Thanks in advance.

@d-healey
That's very cool content
Thank you !

Hi,

I'm working on my first sample-based instrument in HISE. I’ve sampled an electronic piano and I’m now at the stage where I need to edit and trim the samples properly.

The thing is some of the samples have very long tails, in the spectrogram, I can still see content going down to around -115 dB. I'm unsure how far I should go when trimming those tails.

My initial take was to cut around -90 dB and apply a short fade-out to keep things smooth, but I’m not sure if that’s the best practice.

I'm really curious to hear how more experienced users approach this, especially when it comes to how low you usually go in dB when trimming tails. Do you have a typical threshold you stick to ?

I feel like this kind of information could also be useful for other beginners.

Thanks in advance

@d-healey Thank you !

Hi,

I'm using the spectrum analyser from the Parametric EQ effect, but I noticed that it freezes, it continues to display peaks or shapes even when there is no audio signal.

Reducing the decay time helps, but it only hides the problem, I’d like to keep a long decay for a smoother visual response, but still have the analyser clear completely when there's no input signal.

I've searched through some older forum topics, but I couldn't find a clear solution to this issue.

@Orvillain
Oh ok, my bad then. Maybe it’s your sample that’s below 0dB, so it goes up and then drops back down. Anyway, glad it’s working for you now!

@Orvillain

From the doc :
"this value will be used as start ramp value whenever the node is being resetted (eg. when the network is unbypassed)."

I suppose that setting a smoothing value along with a resetValue of -100 dB will create an attack-like effect, gradually ramping the signal up to the target gain after a bypass or a initialize start

Hi everyone,

I’ve been going through the Stereo Widener example in the HISE documentation, and I noticed something that seems strange for me: the routing.ms_decode node appears before the routing.ms_encode node in the signal chain.

However, according to the documentation for routing.ms_encode, it should be placed at the beginning of the chain to encode a stereo signal into Mid-Side, which can then be processed and later decoded with routing.ms_decode.

From Doc about ms_encode : "To use the routing.ms_encode node, you would typically place it in a processing chain with the stereo input you want to encode, and then use a container.multi node to split the signal into its mid and side components. You can then process the components separately and recombine them using a routing.ms_decode node placed later in the chain."

This seems like a contradiction

Image from Hise Documentation :

@modularsamples

Thank you! That was very helpful.

I just have one last question:
If I want to modulate the gain using the LFO from GlobalModulator Container (the one in your snippet), how can I make the last gain node from my screenshot effectively control the gain of the AudioLoopPlayer1, which is located higher in the module tree?

Hi,

I'm wondering if it's possible to make the Global Modulation LFO start or retrigger only when an audio signal is detected, like when sound enters.