Remember when open ai was a nonprofit first and foremost, and we were supposed to trust they would make AI for good and not evil? Feels like it was only Thanksgiving…
Cool project! Will it explain some of the related concepts like envelopes and ADSR? It might be nice to talk a bit about calibration/microtuning so it can match external gear. Also maybe some recipes for making sure a readers synth they build has a few basics to work from.
Is the synth going to support the other scales? C is great but you’re gonna want the black keys.
In terms of things that make you stand out: paying attention to the UI/UX of the interface. How do people use it? What do you like about the other interfaces they have?
Another feature is support for drivers. Something Linux and windows have less adoption/support compared with Macs. Obviously it’d be nice if your synth could take in sound from controllers and output to other gear. Or have your sequencer drive a midi clock for other devices.
Another direction is to look at what parts of audio you find interesting. Maybe it’s low latency fax processing, maybe it’s elaborate acoustic modeling or reverb, or control of harmonics. All those are good ways to stand out and specialize. Or tools to help analyze and visualize audio.
Look at some of the existing VST ecosystem and you might get inspired!
You can make a windows registry change to have Chrome let you keep using uBlock Origin, with the V2 manifest. It will buy you six more months, basically the enterprise support period.
There was a handy shortcut created by the Security Now podcast you can use as a one-click file to update the policy. The show notes also give a more detailed breakdown of what’s going on.
The relevant section in the notes is page 10. The link to the file is page 12. https://www.grc.com/sn/sn-995-notes.pdf