How to deal with differing defaults across Tidal/TidalMIDI?
When reusing existing parameters from Tidal in a MIDI mapping, defaults can be kind of useless or counterintuitive.
cutoff is by default
0 and the logic withing Dirt and SuperDirt will only read its value as soon as
resonance is also specified (at least this was the case at some point).
However, TidalMIDI currently has no such logic and therefore a
0 might lead to absolute silence, when omitting the param in a pattern (depending on the device used I guess).
I am not really sure how to best deal with this, since param reuse reduces mental overhead (at least for me).