@Oriah-Beats This Is sweet. I think it does help achieve my goal thanks brother.

@Orvillain @dannytaurus given my post above, I think I'd be better off learning to type....

@DJJD12345 You might find this useful too https://audiodevschool.com/hise-community-scripts-and-snippets/

@DJJD12345 There isn't a way to do this directly. If you want to build a new project that has the same basic look another project, then the simplest method is to duplicate the first project folder and use that as the basis for the second project.

If you just want to copy interface elements you can open the JSON view in the first project (select a component in the component list and press J), select the text, copy it, and paste it into the new project.

Or you can copy/paste it in the project xml files.

@Adam_G we‘re not using the JUCE 8 webview in HISE

@dannytaurus Thanks, so definitely a path to explore in the case the rest fails...

@Orvillain gotcha thank you as well. You guys are awesome I really appreciate the help

@David-Healey No errors found. I will try recompile them

@daniloprates It might be related to this: https://forum.hise.audio/topic/13397/hise-won-t-open-on-windows-10/28?_=1766235476592

@Felix-W https://docs.hise.audio/scripting/scripting-api/scriptpanel/index.html#setloadingcallback

@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

@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!

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