@pcs800 I found two related threads that might help

https://forum.hise.audio/topic/7976/wrap-midi-node-in-compileable-dsp-network
https://forum.hise.audio/topic/4364/snex_node-needs-to-be-wrapped-into-a-compileable-dsp-network

@Felix-W Yes, check out the preload callback

@dannytaurus That looks great, thank you! Will play with it on weekend.

@David-Healey
All right, I'll take a look. Thanks for the tip! :-)

@13murderer I think your reply was aimed at @DanH 😀

@dannytaurus
Thanks for the suggestions and explanations.

To be honest, I’m not fully sure about the specific branch or commit details — I haven’t worked with building HISE from source before, and I don’t want to take up too much of your time diving into that.

At this point I’m just trying to get the current functionality working, so I appreciate all the help and pointers, and thank you for your patience!

@iamsteinco You will need to use scriptnode for this.

From here, there are several ways of achieving a distortion depending on what you are accustomed with:

straight scriptnode graph with the math operator nodes, math.expression SNEX shaper (although I wouldn't recommend it due to the limitations and above all the fact that if you can understand SNEX you most probably are 90% understanding C++ already) So third party C++ node Faust RNBO NAMM model

Anyway they are all happening on the scriptnode graph, where you can either create signal path, write code, or import models

In my humble opinion, without having watch the video yet, I’m a little bit septic about AI arrival on the VST/plug-in market. Especially in creative industry, people will still like to make things themselves even if an AI tools can do the job 10 times faster. AI on DSP will have a deep impact on other markets, like telecommunications or car industry’s. I even think that AI could reconnect people with original/“basic” things. We just have to see how crazy the vintage synths/gear market is. As mentioned in a ADC video, it’s relevant to say that key for audio developper will be to do very specific products, for a specific niche, where they will be the best and becoming a reference. Market places will obviously evolve as DAW becomes full ecosystem (eg : FL Studio with FL Cloud…). People will win time to find good products and how to make the sound they want, but they will still spend countless time to manually EQ that f******* snare, or choosing the right pad sound. Would love to keep talking about this topic, as I said it’s only the small opinion from a +10 years producer/plug-in consumer that I am. Would love to know more about other HISE user opinion.

Bests :)

@JamesC said in Custom Display panel questions...:

inline function onrvbfilenameControl(component, value)
{
local currentReverb = ConvolutionReverb1.getCurrentlyLoadedFile();
if (currentReverb == "")
{
rvbfilename.set("text", currentReverb);
}
else
{
rvbfilename.set("text", currentReverb);
}
rvbfilename.repaint();
};

Ok well lets look at this:

local currentReverb = ConvolutionReverb1.getCurrentlyLoadedFile();

is trying to get a file name..... from ConvolutionReverb1....

ConvolutionReverb1 is an AudioSampleProcessor, because of this:

const var ConvolutionReverb1 = Synth.getAudioSampleProcessor("Convolution Reverb1");

but when we look in the documentation at AudioSampeProcessor it has no method called
.getCurrentlyLoadedFile();

https://docs.hise.dev/scripting/scripting-api/audiosampleprocessor/index.html

..it does however have:

https://docs.hise.dev/scripting/scripting-api/audiosampleprocessor/index.html#getfilename

@David-Healey You're right as usual. I forgot the test the basics.
the issue seems to lie in the Faust network specifically. I assumed that because it exported fine on mac and windows it would export fine on Linux. have to dig more.
Thanks as always
Chris.

Still broken

2d7e4ace-d079-43ae-af6a-ce90e8ea76f4-image.png

@David-Healey thanx, this helps a lot!! :D

@dannytaurus said in Customize the text content in the pop-up window？:

Or do we have too many undocumented preprocessor defs already?

Yes.

I think a separate function would be better, or perhaps it could be part of getAlertWindowMarkdownStyleData. I'm not sure of the inner workings.

@Oli-Ullmann Snippet worked flawlessly thank you

@tycarrier said in Changes Not Saving in HISE Project After Reopening:

I am assuming I can save multiple xml files for different versions

Try to only use one xml per project. If you need to track different versions use git. For little test patches you should use project presets (.hip).

Check the free Bootcamp course for more info about project management: https://audiodevschool.com/courses/hise-bootcamp/

@David-Healey Yes, I tried that method, but it didn't work. However, I just used the Image component, and it worked.😅

@David-Healey sorry I only watched what I wanted (what was necessary). but thanks

@Christoph-Hart thanks!