Mapping and conditioning
by alexarje • Tuesday 11 December 2007 • Research • 2 Comments
The concept of “mapping” is frequently used in the computer music community these days, and has also been used over the last couple of days during the Jamoma workshop. This reminded me about the distinction between mapping and conditioning, as frequently pointed out by Marcelo Wanderley:
- Conditioning: filtering, scaling and normalizing signals in a 1-to-1 mapping
- Mapping: creating couplings between multidimensional data sets, e.g. MxN.
For clarity’s sake it is probably useful to separate between the two.
Conditioning sounds very similar to the “preprocessing” step in ML, but I guess Mapping does as well (esp. when more dimensional feature transformations are used).
Of course, the domain (synthesis, ML, analysis) will specify different criteria for the output. Or is your idea of conditioning more standardized?
Yes, I agree. The terminology is somewhat blurred here. The main idea is probably to separate between technical “transformations” between different sets of data, and more conceptual “mappings” between for example a physical controller and a sound engine.