@Christoph-Hart don't know if this is helpful or how hard it would be to implement in HISE/C++ side, but, since you never got this running in linux: as an alternative to using websockets (and this would be my preferred way of communication if it were possible), you could potentially ust mqtt for communication. That's what I've done with a pretty large electron sound design app I made, and it works great for ipc and communication. (plus it's more reliable, faster, and cleaner because you have topic based message routing).

Basically main process just spins up an mqtt broker on launch, and then all my different webviews, and swift audio rendering processes, just connect to the main broker and use that for pub sub. Disadvantage would be people would have to include a lib like https://github.com/mqttjs in their webview, but it looks like you need to add a little code already anyways to get the comms working.

@T-B-Guang Having this same problem with no obvious reason. Trying this in a new tester project. only a few samples. sampler channels are the same as master channels. Have you found a solution?

@Allen Use a silent synth with a poly FX, there you have the ability of setting the channel amount.

https://docs.hise.audio/hise-modules/sound-generators/list/silentsynth.html

@elemen8t Yessuh!

@ustk said in How to modify these title texts in CustomSettings:

so you can just make your own comboboxes

For those three settings actually I think this is a good idea. For the audio settings though it becomes complicated very quickly.

@orange yes some nodes seem to only work on windows and some only on macOS. The source code of my project can be compiled on windows and MacOS the same. Make sure to clear the binaries folder of the dsp networks. Do not delete any other folders.

When compiling make sure you first set all networks to not compile - then compile the dsp networks - open Hise and set your networks with Airwindows nodes to compile.

@bendurso thank you for this.

@Christoph-Hart It was a dodgy faust node. I didn't bother to look at the faust code to see what was wrong. I was just going through the nodes one by one and deleting them and recompiling. I didn't need it any more and must have edited the code badly before going on holiday and forgot what I did. 😆

HISE was built with Faust and all paths set correctly to answer your question. Thanks for the help!

@Morphoice

Well maybe. But it'll be so cpu hungry. And fiddly because the routing of a real reverb is a complex matrix with taps coming in and out of all kinds of places

@d-healey Ok. Im playing with it now. Just made all my samplemaps disappear in my main project but I was able to bring it back so I kinda see whats happening. Im gonna have to keep playing with it to fully understand whats going on. I'll get it soon enough.

@hisefilo Just wanted to chime in about this work here:

Building AI Enhanced Audio Plugins by Matthew John Yee-King

https://github.com/yeeking/ai-enhanced-audio-book

I am just finishing the work and its a great starter for training in Torch then building in the JUCE framework. I haven't tried HISE integration yet (I didn't know the API was updated either). I am happy to share the pdf if you are interested!

@d-healey Ok I'll check it out on patreon thanks for your time

@HISEnberg Did you get the patch to work in hise? I get no mix or sound when I insert the patch into hise.

@d-healey Thanks, simultaneously I just found this thread:
https://forum.hise.audio/topic/9830/attaching-text-json-files-to-the-compiled-binary/6

I really assumed that I could load data like this but that's ok - I will do the suggestion in there of checking for a file and falling back to a default object if not found, at least for the resets/presets code. The main data I can definitely move to a .js no problem. The main data of my entire script including samplers came from a JSON file and I was tricked into thinking it was working fine because the samplers are created at compile with the correct data, and so I figure the UI was as well. No wonder absolutely nothing has been working correctly.

@d-healey thanks alot that worked!

@hisefilo cool. I'll do some reading. Might be back. Thank You!

@whoopsydoodle

Here's an example of 'simple and easy'.

anything outside of this, you're definitely making it less simple and easy.

Laf Shadows and a subtle glow are attached to the slider knob body so it seems 'responsive' moving up and down the slider.

Slider made separate then drawn into Laf function.

Screenshot 2025-04-18 at 3.36.25 PM.png

You could LAF some shadows and glows to help the vibe for sure.

Slider Example Shadows.gif

@Straticah
ikr : )
I think it was one of the first questions I asked on the forum, so this is very nostalgic.

@d-healey So, I think the issue had to with the most recent Xcode Update.

I was on 16.3 and reverted back to 16.2, seems to be all good now.

Thanks for the help folks.