Proof of concept on property classes

[Theodeus]

No description provided.

[alexanderwallin]

Could you describe this a bit?

[Theodeus]

@tencircles had an idea for the properties that went way over my head, so we said he could build a PoC to test it out and then we'd take it from there. :)

[mikehelland]

I think I might have some kind of proof of concept for you.

openmusic.gallery/gauntlet/

If you click on the hamburger menu next to the sine oscillator or drum kit, you can hit "Add FX". You will see the FX of Tuna available as well as an EQ of my own. Maybe a couple additional.

This is done by defining properties very similar to yours. Here's an example:
[
{"property": "automode", "name": "Auto Mode", "type": "options", "options": [false, true]},
{"property": "baseFrequency", "name": "Base Frequency", "type": "slider", "min": 0, "max": 1},
{"property": "lowGain", "name": "EQ Low", "type": "slider", "min": 0, "max": 1.5, transform: "square"},
{"property": "filterType", "name": "Filter Type", "type": "options",
"options": ["lowpass", "highpass", "bandpass", "lowshelf", "highshelf", "peaking", "notch", "allpass"]}
]

Defining these controls for each FX, whether from Tuna or elsewhere, the app treats them the same.

Is that the kind of thing you had in mind?

[Theodeus]

Whaddoya say, @tencircles?

[mikehelland]

I started a conversation over here too just to see what else was out there:

https://www.reddit.com/r/webaudio/comments/ajb4yk/is_there_a_standard_for_web_audio_fx_libraries_if/

[Theodeus]

Hm.. reading the discussion, I'm not 100% sure this issue is about the same thing. This is more about the internal workings of tuna, and your discussion is more about a standard way to digest the API's of different effects.

An interesting discussion, indeed, and possibly something tuna could adhere to of the was such a standard. It would most likely happen through some other mechanic than our internal property descriptions though..

[Theodeus]

I totally understand why you'd think they're about the same thing, though. :) The issue description is seriously lacking in context. Sorry about that!

[mikehelland]

No problem. I couldn't tell exactly from the description which is why I had to ask.

[Theodeus]

#47 will be the issue to discuss this, going forward.