knvlt

Can be, don’t have a FM-1 - but I had to tweak it until i enjoyed the result. It did measure the filters via spectrograms and could explain my points, but I’m not sure if it would have been able without my help (I used Opus 5.5). You can listen to a patch with the curtis filter, noise and unstable oscs i made here:

https://drive.google.com/file/d/1kG1jWOXU6-N7aGWstWGiOY-fP5k...

The stock synth can’t do that. But making a svf and oscillators isn’t something musical or groundbreaking, integrating it in an assembly blob is, somehow.

I paid 20€ for improving my synth and confirming my existential crisis as a developer. …but, truth is: I spent quality time with my daughter while claude worked and thats a good thing.

Two days ago I (that is, AI) started to mod my modal electronics Cobalt8 after trying the model:cycles mods.

Half a day of setup and i had my first curtis-style filter on the synth. 2 days of low intensity prompting and I have

- 3 Filters: Curtis, 303, Steiner Parker

- An additional noise source

- The oscillators from braids

- Prophet08-ish oscillators in a stable and instable fashion

- a granular delay, tape saturation and a klon centaur like distortion

- karplus filter and a body resonance fx

- polystep arp (different pattern per note) with scales or gated euclidean patterns

I have interest but no skill in dsp programming (never found the time to pursue it). I love the filters and oscillators, it went from a tame, boring synth to gritty synth I like to play. At the same time I have to stress that this is a result, not an achievement. Anyone with a 20$ claude subscription can do that and people do. So I think it’s smart to open source(and not novel, see modular synths diy modules). Though when gigging I need devices that are stable and working in any conditions and I’m willing to pay for that.

Native German here: In my experience the issue is in most cases not compounds, but the domain language.

There are terms that are specific to certain domains and used by everyone to precisely name a certain process. Belegprüfung, Indexpartizipation, Zessionär, etc.

Sometimes germans outside of your field of work don’t know these terms either, but those who do all use the same term. If you use english expressions you have to replace a domain term with one of multiple possible translations, making it confusing in many cases.

We have the same with translated documentation. Ever read the german version of Azure Docs? I have no clue what they are talking about until i switch to the english version.

Yes! Dexed is great and I would recommend trying the samples from the book with it. You need a bit of exploration, to get a grasp whats going on.

Whats hard (and impressive in regards to those who came up with meaningful patches in the 80s) about starting with FM synthesis isn’t only the programmability (modern FM synths have that covered, see the other comments). It’s not an intuitive thing to work with algorithms and you need to learn what is happening.

I can recommend FM Theory and Applications by Musicians for Musicians for everyone who wants to create own patches:

https://www.burnkit2600.com/manuals/fm_theory_and_applicatio...

What‘s rubbing me the wrong way is the author pitting against NodeJS/Typescript on the front page without real arguments. You can pit your framework against another, but show me how it makes my life easier in comparison. Argue with features and developer experience, not with personal opinions.

„and unlike a lot of JavaScript web frameworks, Spark won’t be deprecated tomorrow.“

Especially if you can’t hold your promise. Deprecations are a normal thing in every software driven by individuals. We lose interest, get kids, etc.