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

@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 :)

@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

@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.😅

@Christoph-Hart thanks!

@Morphoice yeee! Let go! 🙏

@Chazrox Sweet! it is really helpful Thank you!!

@Chazrox How do I change the size of the grid in interface veiw

@lloyduss @David-Healey Thank you so much it worksssss!

1a19fd04-c3c3-4c8e-8b03-e590d7c5f3bb-image.png

@David-Healey Roger that 👍

@xxx id rather have it called midi, or plugin name, or whatever the file is originally named

@Orvillain You can set up the hierarchy in your script I guess. Then at least you have it all in one place.