This is to say thank you to everyone who helped and engaged so awesomely in this forum, especially @Christoph-Hart, @d-healey, @dannytaurus, @HISEnberg and many more! To get this level of help and devotion in an internet forum is not common, especially not in 2024 where people usually are "go away noob!" or "use the damn search" ;-))) Therefor I thank you, the things I have learned over the past days are incredible, given I started from zero.

Today I finally managed to have a first usable prototype of the synth I have envisioned with beautiful waveforms and sounding exactly the way I wanted, and I ended up not using wavetables at all. Take a listen here if you want to:
https://www.dropbox.com/scl/fi/h211eql2t99ntdbltrbuo/IMG_8250.MOV?rlkey=a0n81idbt7oaldbkqpz16x9nr&dl=0

Here are the raw OSC waveforms, I shaped them using polyshaperfx

We solved the pops and clicks, the filters behave and sing like a diva, the analog vibe is all there and I'm thoroughly amazed. There is lots to tweak and add, but I got the basics and I'm confident I'm on the right track to continue with HISE as the best choice I could have made.

Thank you again, I can't state this often enough and sorry for the million more questions I will all bother you with in the future ;-) Love you guys!!! You made my week and enabled me to finally concoct a thing that has been brewing in my head for so many years. That's beyond awesome!

I*m just dropping this here as a guide because I just researched it, as I tend to make the mistake myself when designing my knobs and buttons. All units are preceded by a space, so it's 10 Hz not 10Hz etc. Keep it in mind when designing your plugins and button values/labels etc ;)

The International Bureau of Weights and Measures takes a no-nonsense approach: ‘The numerical value always precedes the unit, and a space is always used to separate the unit from the number,’ it says.

The only exceptions it makes are for the unit symbols for degree, minute, and second – °, ‘ and ” respectively – which don’t need a space.

Thought that question might creep you out a little. Happy Halloween!

Just finished my first FX plugin, and it's blowing me away.
It's mostly done in faust thanks to all of you guys who helped over the past days.
You can hear it here,
https://www.instagram.com/p/DBzkEWdonkV/?img_index=2

Also there is an easter egg, if you crank the knobs, your sound will turn into a Jet Engine!

Imagine there would be a way to put those networks into a pedal with real knobs and switches... Anyone ever heard about resources for homebrew pedals? A Bigsky is nothing different in principle so it should be possible... they are all just vst's in a box

Next Task: Compiling PC Versions, and learning how to make AAX (!), Adding Presets, tweaking a few parameters, adding automation etc.

@HISEnberg said in Ring modulator below 20hz:

Romain Michon is the GOAT when it comes to Faust resources so just finding his course lectures and online material is good place to start.

funny enough I'm already subscribed to him on youtube lol

@d-healey said in Style Value Popup?:

@Straticah I don't think there are any other properties you can change. The popup should be horizontally centred by default, it could be that the width of your knob is not evenly divisible by 2.

You could instead create the popup using laf. In Sordina I replaced the text label with the value, but you could place it above the knob like a popup - this means the clickable area of your knob will be larger though which isn't always desirable.

damn that's beautiful! brilliant usability and clarity

@Morphoice said in DSP fine tuning, that metallic diffuser sound:

de.fdelay1a

changing to the fdelaylti which uses the Lagrange interpolation turns the tail signal into more of a cymbal ring rather than that annoying thing I had... it sounds actually pretty sweet.

@Straticah where's a fix in the latest HISE version on the develop branch, it works fine with the latest xcode and HISE build now

@griffinboy unintentional, I'm just obsessed with pink and purple colors ;)))

@DanH through some sort of magic I got it to work, although I can't tell you what I did... I'm still trying to figure out what went wrong the first time

@HISEnberg somehow I've got it to work now, with the approach @klaytonrangel suggested, I'll have to try and test if it works without a hardcoded dsp, that would be awesome.

@Lindon I did but that didn't change anything and I never had to do this before with any project for it to load on PC after I was done compiling the mac version...

@DanH when I remove the ScriptFX1 which contains the network on mac then I can open the entire project on PC just fine. Compilation or the DLL works because ScriptFX1 is automatically added back temporarily, but without crashing... weird.

@Lindon it seems to compile fine using visual studio directly, it just wont open in HISE on PC

@DanH I'll give it a try and report back

@DanH just opening a project. I don't get any further.
Eventually I wanted to indeed compile the DLL and then a PC version of my plugins that work well on the MAC version of HISE

This is the last I see before everything simply crashes and closes. Beforehand there is compiling the faust nodes, it happens with any project on PC which works fine on mac with the very same faust and HISE versions...

has anyone encountered this before and any advice? what could be wrong with the scripts that works on mac but not pc?

it worked fine last week, I haven't changed any HISE or faust versions ever since. I though I finally had a stable version on both OS

@ulrik oops, thank you. didn't see that there

I'm having this weird problem where a temposync knob (values 0-18) in the compiled network ends up taking ms values from 0-1000 only as if the temposync node was completely ignored... what did I miss?

@d-healey true. you just never think about it with faust as the mere GUI labels are turned into the actual parameter names... also faust has pathnames as labels to represent certain groups which make them incompatible with HISE so far

e.g.

freq = vslider("h:Oscillator/freq",440,50,1000,0.1);

@d-healey same problem with / character which appears a lot in Dry/Wet or L/R sliders