Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Fons Adriaensen <fons@...>
Cc: <linux-audio-dev@...>
Date: Tuesday, August 21, 2012 - 10:29 pm

--=-w3l0IrxKvUF6wvklsUmA
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2012-08-21 at 21:54 +0000, Fons Adriaensen wrote:

g

In this model, modules have only inputs and outputs, so yes, this is it
exactly.

> 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
frequency.

That is: some port will always represent an absolute frequency. No
matter what.

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.

-dr

--=-w3l0IrxKvUF6wvklsUmA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAABCAAGBQJQNAvCAAoJEDZyeCqb82jzFV8QAMxSGUesM/gX4+YNYkFxtL1z
nJIip3rB626LbCWCxdOfTjhRXSE0y5EKhQNwoav1ahULEN4TTKc6g08lKN7/rMX9
uoTcaaVYrBaQNQ2IgOAKEmJI8OU0x5qQ3oFuAbCjMdojbxFZm0ylggstaSabDqUa
+3PU+Vq1Mt0ftXN7HQ35cHdKTTbaWN9ym6j0oRFXWRm92WflbTrnPfIhVqZ1+uj4
3jQpt3F7Vf87r83ZRTETlz2LZsdUUpbIYqYHQ3v107ydDuLBR78hAWJElG2BkOn3
oOs5FfegZFbp/r8icDEO3ZJsDMELRY/DzWnP0BPAaIOJd5eEnu+p/HRVsqjkyox4
r/tsBlmz+YPkIo5ujeqB/pmuDEVDbkTLE7EMd82zNMuQzSMMq8g0Sb17tpSTnnhh
LCYLseE1ihNDqHHtUdwCvw0/bTjFmcumws1nptkj5P3E0Xk2RqVoYP53LxKxSKHt
rz0uI6mv/Uk/8zG3f1sH44p23rDU1AJ7Yu55LAJ/iC0hNx9yu5Z1UFa7i/jd9qBC
DfS2hUANY7g827DzVVLB1Gse/x9mVLTa37+DQlrbC7NsdcBQVWFsrvNy5L+13dc9
4Zj/q2mHWsMf7ulSbE3AjD7wUIZ0hCOijqzmGzyvGoeywyi6Vyoq+Hk5uBJhOjhN
Q7Cd41OSQ8CGxVcIrXdn
=E3s2
-----END PGP SIGNATURE-----

--=-w3l0IrxKvUF6wvklsUmA--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Jeff McClintock, (Mon Aug 20, 11:02 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Tue Aug 21, 12:50 am)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Nick Copeland, (Tue Aug 21, 8:14 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Fons Adriaensen, (Tue Aug 21, 9:54 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Tue Aug 21, 10:29 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Fons Adriaensen, (Tue Aug 21, 11:02 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Tue Aug 21, 11:50 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Thorsten Wilms, (Wed Aug 22, 8:30 am)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Wed Aug 22, 4:43 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Fons Adriaensen, (Wed Aug 22, 9:12 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Wed Aug 22, 9:32 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Fons Adriaensen, (Thu Aug 23, 10:56 am)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Thu Aug 23, 4:06 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Fons Adriaensen, (Thu Aug 23, 4:35 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Thu Aug 23, 5:07 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Wed Aug 22, 5:37 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Nick Copeland, (Wed Aug 22, 1:24 am)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Wed Aug 22, 1:57 am)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Tue Aug 21, 8:59 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Nick Copeland, (Tue Aug 21, 10:11 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), Jens M Andreasen, (Wed Aug 22, 3:50 pm)
Re: [LAD] Plugin 1/oct frequency controls (AMS/MCP/VCO), David Robillard, (Tue Aug 21, 10:52 pm)