@d-healey it's my understanding that logic and pro tools support mono to stereo where a mono track becomes a stereo track at the insert point where the user inserts an m>s plugin.

this plugin does not make sense to run as mono > mono.

Yes to both. There is a lot. I'm currently going through the process of commenting things out and making test versions to see if I can make one that works.

@d-healey Yes. I do have a high dpi mouse and now you’ve given me something else to worry about and have to test for. I did not think that dpi could be a factor.

Based on what I figured out rooting around the Hise source it seems like all sliders in Hise are set to absolute px mode as default with a value of 250 distance = full rotation. But when you turn on the modifier they switch to a velocity mode. The problem I had is that the velocity mode settings weren’t any good (at least for my mouse) specifically the offset aka minimum.

JUCE: Slider Class Reference

(docs.juce.com)

I found a setting that makes things much smoother and more predictable. But I guess I have to test with different mice?? Oh joy.

Where can I change the compile options that Hise uses when compiling faust nodes?

I can open the .cpp file generated by Hise for my faust dsp and it has the compile options Hise used commented out at the top, but I don't know where in Hise I can edit those.

As an example I would like to use double precision floats. Hise is currently set to use single.

@aaronventure thanks!

I had actually just figured out on my own how to do this with a gain module directly. But your version in scriptnode is better.

@Christoph-Hart thanks for tackling this issue so quickly!

Tested as working on my end.

@d-healey said in [Feature request] Missing Laf colour properties:

• drawPopupMenuBackground, use the combo box colour properties (would also be good if the base colour was transparent so we could do rounded corners, currently it's solid white).

This please!

Haha dirty indeed. But it works!

I don't know why but the mouseDownX and mouseDownY values I get when clicking on the panel are always huge. So I'm using an X that's higher than my object width to trigger that? Idk man... haha

if (event.mouseDownX > 26) {
	//click on panel
	//first click shows menu, second hides menu
}

if (!event.hover && !event.mouseDownX) {
	//click off of panel that also hides menu
}

@d-healey great. Thanks!

@d-healey said in Possible to draw beyond callback obj with LAF on slider and button?:

You have to make your control larger. Or draw the contents smaller.

yah... that's what I figured. Kind of a shame. A work around that's very silly but should work fine is to make 2 sliders linked, with one big and one small and disable the big one so it can't take user input but reacts to the value of the small one.

@d-healey I can't tell if the dropshadow on that extends beyond the bounds of the obj.area and it doesn't look like it really changes so it could just be a static background.

What about a glow that glows beyond those obj bounds? It gets clipped and looks bad.

@d-healey I'd like to draw things like shadows and glows and backgrounds that are reactive to the component value and extend beyond the callback area.

@Lindon appreciate this reply. I will give it another go.

With a LAF on a slider or button is it possible to either:

• draw outside of the bounds of the obj.area?
• limit the callback to only function in a specific reduced area?

I can think of a few very unclean workarounds but I'm hoping for something quick and simple instead.

I have 2 sliderpacks and I'm trying to make them match each other. Sliderpacks don't have the "linkedTo" option like knobs or buttons so my hope was to assign the values of one to the other.

I can get the value of any individual slider in the pack with getSliderValueAt(index) but I can't seem to find a way to assign a value to a single slider.

I'm guessing this might be possible using referToData but I haven't been able to figure out how yet.

I have 6 hardcoded fx and my original idea was that I would have a GUI that lets the user choose one, then it would load that dsp and programmatically draw knobs for each parameter in the fx. Each fx dsp has the same first 3 parameters and then after that some have 1 more, some have 2 or 3 more and those additional knobs are different for each dsp.

It doesn't seem like this is possible in Hise.

Issues i've run into:

• Knobs can't be added after init. This sucks but isn't a deal breaker. I can add the max number of knobs needed on init and then hide or show them as needed while reassigning their function for the currently active dsp.

• Biggest issue, slotfx seems buggy. If I have one fx loaded and I switch to another, it loads with default parameter values but if immediately send a knob.changed() for the knob that's controlling those parameter for some reason it's not always receiving that old knob value. Sometimes it stays at the default until it's moved by the user, sometimes it gets the changed() and updates to the knob value.

• Despite calling a setAttribute by name, it needs each parameter to be in the same order or it gets messed up. If my first parameter is Mix and my second parameter is Depth on my 1st FX, if I swap to a different FX and Depth is now the 3rd parameter, it messes up and despite calling myFX.setAttribute(myFX.depth, value) it will try to adjust the 2nd parameter, not the one called depth.

• .setAttribute() seems to only work with my fx defined by Synth.getEffect()
  While .setEffect() seems to only work when defined by Synth.getSlotFX()
  So I am defining the same FX slot both ways at the same time and calling each type as needed. This feels wrong but it seems to work?

• Odd behavior but an easy work around, if I try to programmatically check how many parameters are in an fx it will always return true even for ones that don't exist. If my fx has 3 controls and I ask if there is a 4th it returns true with a name of blank "".

There are other issues and odd behaviors but these alone have made me think I probably shouldn't try to do this and should just manually draw knobs and panels for each fx, load them all and then just turn them on and off since I don't actually need to reorder them.

Is there an update to this in 2025?

The solution is hacky and works. I'm just wondering if there is now a "proper" way to do this.

@d-healey Ok got it.

This is very odd. I compile your test project and it works fine both as Stereo and M>S.

I compiled my project with the same settings as your test. Support Mono FX flag and HI_SUPPORT_MONO_TO_STEREO=1 option.

When I do AUVAL I even specifically see this, which to my understanding means it supports 1 in 2 out and 2 in 2 out:

Reported Channel Capabilities (explicit):
      [1, 2]  [2, 2]  

But still the plugin will not show up in the inserts menu for mono tracks.

Is there some other aspect that could be stopping it from being allowed on a mono track? Possibly something with using hardcoded DSP modules?