hawkfuzz wrote:You talking about "velocity"? I thought OP made it clear which velocity they were speaking of and everyone else is responding to that definition, or am I missing something?
I'm not just picking on the OP. But, his attempt to clarify mid-way through didn't really slow anything down.
Here are various uses of the word “velocity” that I saw. This is in the context of a patch whose pitch and gate control signals are generated by a single sequencer module (Note: None of these are necessarily invalid if there is a common understanding in the conversation. If nothing else, this shows how ineffective of a word “velocity” is for general conversations like this):
1. The Technician: It refers to the primary SOURCE of the signal used to control the overall amplitude of the audio signal … i.e., the ability of the sequencer to record MIDI Velocity (1-127) messages and to convert them into CV signals (volts) that are sent by the sequencer on steps that send gate signals. A sequencer output labelled “Velocity” would refer to the source of the CV output signal, not (necessarily) the destination (so, not true that "an output labeled ”velocity” would be nonsensical since it would output CV that could be used for anything in a modular enviroment"). Usage of "velocity" should be limited to this because “velocity” is not a real world (or modular synthesizer) concept … drums and piano keys are hit with “force” … “velocity” is irrelevant if the drum head or string is not ultimate “struck”. And "volume" is not "velocity"
2. The Pragmatist: It refers to ANY control signal that is sent by the sequencer on steps with active gates, regardless of the signal’s original source … e.g., recorded MIDI Velocity, knobs, sliders, buttons, etc. A sequencer output labelled “Velocity” could be used to communicate that the output will be 0V when there is no live gate on a step (again, such a label would not be "nonsensical" ... if its intended meaning is understood)
3. The Fully Abstracted: It refers to the use of ANY control signal used to affect the ultimate amplitude of the audio signal, even if sent from a different module than the sequencer … e.g., you could use a Voltage Block or a Batumi LFO as a “velocity control” for a patch whose pitch and gate is sequenced by a Metropolis if you patch the CV output to the CV input of a VCA that is set up to control the amplitude of the sound source directly or the amplitude of an envelope patched to another VCA to control the amplitude of the sound source. This use may be combined with rude insults about "the imposement of MIDI/ITB limited thinking on modular gear". It is a flat out dismissal of any views of those using definition 1, 2 or 3
4. The Result-Oriented: It refers to an INPUT on a sound generating module that controls the volume of the module’s audio output via an internal VCA … the source of the CV signal is irrelevant. An input labelled “Velocity” may be used to indicate the types of available destinations by analogy to what commonly happens in MIDI land (e.g., Plonk). This can be an easier, and more cost/HP effective way to patch certain types of sounds (and the inputs are almost always normalled to full volume if you want to use something else)
Since Lisa asked what I'm getting on about, I used some quotes from her.
My point is that it is amazingly obvious that there are different meanings for the word "velocity" - in fact it has been pointed out by many posters in the thread. And (in my view) there are valid opinions to be made in all four descriptions. But, the thread has a sometimes-obnoxious, sometimes-comical, but always-endless stream of people posting responses that assume a different definition than the person they responded. So, to me, that indicates perhaps a goal not of bilateral communication and sharing, but of merely pontificating on a stage