Content-Type: text/plain; charset="UTF-8"
On Tue, 2012-08-21 at 21:54 +0000, Fons Adriaensen wrote:
In this model, modules have only inputs and outputs, so yes, this is it
> The weak part in that argumentation is that such a port
This issue is less vague and hand-wavey when we instead consider the
output that generates this value. Usually, the frequency output of the
'note' module which reads MIDI or whatever and emits frequency, gate,
and so on.
What is this signal? It either means some absolute frequency, or it is
useless. This is what I mean by: in reality/practice, signals that
represent absolute frequencies *do* exist here, whether anyone likes it
or not. They must exist, since the ability to make an oscillator play
the appropriate frequency is obviously something you must be able to do
in order to build a synth.
In AMS, this is true.
In actual analogue modular synthesizers, this is true.
In every modular synthesizer ever, this is true.
It has to be true, because otherwise you can't build synths.
This perspective about all signals being relative requires making the
frequency a property of the receiver instead. This seems to make sense,
except since parameters are parameters, this simply means you have moved
the problem to another port. Then, *that* port represents an absolute
That is: some port will always represent an absolute frequency. No
Having to patch two wires instead of one every time would just be a
nuisance with no benefit.
What this implies is that in a purely volt/oct world, there will
inevitably be a signal somewhere that is in volts/oct that represents an
absolute frequency. Here we can avoid that by indeed having that 'unit'
always be relative and adding a second port in Hz that defines where
zero is. Then the absolute frequency port is in Hz. This is a good
idea because it would make patching tunability simple. However, nothing
from AMS does this, so a convention is needed anyway. Hypothetical
plugins with this port would set the default value to the conventional
base frequency, and these plugins will just have it hard-coded.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----