Okay so I want to make a VST in order to learn the entire process and actually get a handle on how plugin infrastructure works behind the scenes of a DAW. Seems helpful but also like good knowledge to have, and y’know I wanna do it.

The idea: a single knob that turns over itself multiple times and basically just distorts everything into a square wave from 0% to 666%. my working title right now is “THE KNOB” but I dunno if that’s going to stick for long, i migt end up going with something edgy like “Sextructor” or “BinSmasher” or “RAWR|machine”.

https://www.youtube.com/watch?v=iVDlGFhbqw4&ab_channel=DrBruisin

https://docs.juce.com/master/classes.html

https://docs.juce.com/master/tutorial_simple_synth_noise.html

And we’re off!! To a bad start! I found a fun tutorial for a outdated but seemingly working way to setup an envirnment to dvelop a plugin, I went to the code space and immeidately got my reality check and was told to check myself before i wreck myself and to just use JUCE instead. Alright, I’ll use JUCE, which was pretty easy to set up, but now i’m a little lost. a couple of tutorials and a lot of syntax BS later I have a basic but functional UI. Sound just goes in one end and out the other right now, no processing is taking place, but DSP is going to be my next issue to tackle lmao.

OKAYOKAYOKAY I haven’t been able to do much but what process i have made has been of the research variety. Xcode is hurting my soul to look at, and everyday i wish i’d set up the environment in VScode instead but now im commited (sunk cost fallacy or something”

DSP is terrifying and all the lessons I do have and need/want to be at usually overlap with teh CSD lessons about DSP so i’m out of luck there, and sending emails is scary but i think i just gotta hype myself up and ask around if someone can help with JUCE dev.

i have a bunch of ideas, and i think i’m supposed to use like. a global timer to communicate/check for updates in certain vars and then update those on clock-ticks in the audioprocessor to change params like that, but the way to do that seem very convoluted, like why not just .getValue?!?

WEIRD WEEK, NO TIME, DO TUTORIAL, FIX PROBLEM HARD OK BYE.

audioProcessorValueTreeState, object based programing, crying in xcode, vst3 works, still no dsp implemented in large proj, where put params, scared.

Why no work if do everything right, me just too dumb?

https://docs.juce.com/master/classAudioProcessorValueTreeState.html

https://docs.juce.com/master/tutorial_audio_processor_value_tree_state.html#tutorial_audio_processor_value_tree_state_component_attach

everything hurts.

starting new big project, too many errors dunno why goofy like this, starting with clean slate will help (hopefully).

https://docs.juce.com/master/tutorial_audio_parameter.html

got this to work pretty good standalone and in vst, just gonna migrate to new project with less bs all over the place

wish me luck 🙂

everything is set up, apologies about sporadic updates, i got sick.

https://stackoverflow.com/questions/5731863/mapping-a-numeric-range-onto-another

https://stackoverflow.com/questions/9323903/most-efficient-elegant-way-to-clip-a-number

https://juce.com/tutorials/tutorial_audio_processor_value_tree_state/

The infinitely turning knob is dead, all hail the one knob subdivided into seven different little sections with different mappings, its called just “GAIN” now btw.

i finished the bare minimum by the deadline (eh), tutorial coming soon, very stressed abt spatialisatie teehee.

will upload VST/AU file when it actually looks pretty, as well as Projucer file if i make a tutorial anyway. since the tutorial is gonna be for dumbasses like me who are starting from absolute 0.

definteley not done with this plugin though, as i said i wanna add more fun dsp and different knob functionalities as wel as the fact that i wanna get the original knob concept working.