@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.
@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.
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
}
2025 Bump
Is this still missing functionality? I know there is a clear undo list function, but there doesn't seem to be any way of knowing if you're at the beginning or end of the undo list or how many items are in it.
So until we have native Cmajor support in HISE, how much of a pain would it be to compile a Cmajor patch as C++ and then use it in HISE as a 3rd party C++ node? Is there a web of dependent libraries you'll have to worry about including?
Just wanted to voice my support for having this in HISE.
So until we have native Cmajor support in HISE, how much of a pain would it be to compile a Cmajor patch as C++ and then use it in HISE as a 3rd party C++ node? Is there a web of dependent libraries you'll have to worry about including?
@obolig maybe accidentally compiling for debugging instead of release?
I wrote a reply but I guess it got sucked into the void with the forum server instability yesterday.
I did get it working. The things I changed were that I switched to using a global_cable node instead of a global_send. I don't understand why I needed one over the other but with that change my scriptnode now compiles fine.
Also I needed to be routing a 0-1 value to the cable input in scriptnode. I was sending a negative value which shows up fine on the value knob readout in the scriptnode but I guess was being clamped to the 0-1 range and showing up as all 0.0 once it was read by the interface script. Using the .setrange() function apparently maps 0-1 data being input to the range you set, it doesn't change the requirement for the input data to be within 0-1.
All of this is somewhat stabs in the dark as there seems to be very little documentation on anything scriptnode. But it is working.
@oskarsh that sounded like a good idea and something I obviously missed, however after that fix I'm still getting 0.0 values returned.
I am trying to get metering data out of a faust node onto my UI. Is there a guide anywhere on how to get this working?
I have a faust node with a hbargraph, it shows up as a modulation source in my scriptnode. I am then routing that to a global_send node with "cabledata" set as the output cable.
In my interface script I then have:
const var GlobalCables = Engine.getGlobalRoutingManager();
reg cableValue = GlobalCables.getCable("cableData").getValue();
inline function ontestBtnControl(component, value)
{
Console.print(cableValue);
};
testBtn.setControlCallback(ontestBtnControl);
I'm always getting back "0.0". I feel like I probably need to compile my scriptnode but if I enable AllowCompilation then I get a "Project XML Invalid" error when compiling DSP networks. All help is appreciated.
I'm trying to design a scriptnode that will switch between a series of different FX nodes. I'm using softbypass to turn them on and off to save CPU. However I would like to switch between them as seamlessly as possible so I'm trying to design a script that when switching will enable the target path, then fade to it, then once the new path is the only thing passing signal it should softbypass the old path.
I'm wondering if anyone has done this before and can point me in a good direction? There doesn't seem to be any premade nodes designed for this I will have to build something probably using multiple switcher nodes with one lagged behind with a smoothed parameter node? At least, that's my first idea for making this work.
@d-healey So you think I can use the filter floating panel but can't capture mousewheel from a panel?
Old thread, I know... but wondering is there a way to do this in 2025?
I'm using a panel to draw EQ controls. I have control over freq with click and using a right click modifier I can do Q. Is there a way to capture the mouse scroll wheel so I can map that to control Q value with a panel instead of needing right click? Pretty much every other modern EQ plugin uses scroll wheel for Q adjustment so I very much would like to do that.
I'm using custom DSP so afaik I can't map that to a default filter floating tile, instead I'm drawing everything I need on a panel.
2025 Bump
Is this still missing functionality? I know there is a clear undo list function, but there doesn't seem to be any way of knowing if you're at the beginning or end of the undo list or how many items are in it.