God I hate my stupid brain sometimes.

So yes... that is exactly what it was....

In my c++ I run these smoothers for some parameters. To avoid discontinuities when turning a parameter. You generally don't want to flush 1000's of parameter updates on things like delay times, so you smooth it out over time. Maybe only 10ms, but it helps to make it sound better and brings down CPU too. Cool.

And that was all well and good. Worked fine.

But in my setParameter callbacks, I was only setting the target. I wasn't setting the initial value. Which now I read it, is literally the dumbest stupidest mistake that I could've made.

Time for more Guinness.

@Oriah-Beats I Can give an idea to emulate something like the JUN Chorus with a diagram that you can recreate in Scriptnode, The Pre-emphasis EQ (Can be a High Shelf) that helps to emulate the "Hiss" that produce the BBD circuit and get a more clean saturation, then you compensate with the LPF to get a more "Warm" sound. Just Play with the Modulation Shapes, times and amount to get the sound you like.

[Input Mono] ↓ [Pre-Emphasis EQ] ↓ [Split] ↙ ↘ [Delay A] [Delay B] ↓ ↓ [LFO A] [LFO B] ↓ ↓ [Saturation][Saturation] ↓ ↓ [LPF A] [LPF B] ↓ ↓ [Pan L] [Pan R] ↓ [Output Stereo]

@Christoph-Hart Still experiencing this.

@Lindon 😂

If you have autocorrect turned off, you're already at Pro level! 😜

@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

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

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