interesting observation and discussion arebee:
in the case of the "hard EQ" replacement for filter 2, you're dead on in your assessment of my method. however, that never came through, but it does have a quality of some of my approaches, mainly with keeping multiple copies of pgms, samples, tracks...etc
a similar example of "hard fixing" is my method of programming chopped samples, the alt loop, NOTE ON, specifically determined DURATION (simulates HOLD, each note lasts til next note)....all of that is very hard fix, very little of the original pad performance is not "perfected" in mge. though this can be very fatiguing, the result is a simulated "realtime timestretch" or "rt pitch shift," as you can either change the tune or tempo and the timing and/or tune stays the same, respectively.
BUT i'm drawling. in this case, i'd argue that this isn't a "hard fix," it's a little different. "subtract" in SEQ edit is a nice function because it brings everything down collectively, maintaining its variance. say you have a bunch of tracks whose velocity is all over the place: subtract 20 vels, and it's still all over the place, just 20 vels softer.
such a usage is certainly not hard, as it may be changed back at any time. HOWEVER: in most cases when using the track velocity function, (MOST), it was just for a quick volume control. today, that operation is easiest performed in either track mixer view: MIXER (pad 4) or the textual track readout (window over TRACK). from there you can adjust your actual LEVEL---rather than VELoCITY, which, depending on the program/device you are controlling, may have a different effect at high/low velocities.
phew - lot of words, but do you see where i'm going? in THIS case, it's not really a "hard fix" as much as a "different fix." i do this a lot, as i use reason's nnxt a lot and sometimes their sample layers are arranged in a clunky way, so i duck my velocities in SEQ EDIT (formerly using track velocity) in order to bypass the tinny top layer in favor of a warmer, more intimate softer layer.
as far as "losses" go, track velocity was a "loss" but at the same time it was a slightly redundant function, in the light of the TRACK MIXER, because of WHOLE+LVL in GPE, and ESPECIALLY because of the "velocity" depth that defaults to 50-100 in AMP. this causes much lighter hits to sound much louder by default.
one last interesting point: lately i've been running midi through various MIDI vst and jesusonic effects before it hits Reason: stuff like velocity limiters, midi scale snappers, midi arpeggiators. THiS is a whole NEW approach that really excites me: especially when i then bring that midi back into the MPC for further editing. it's like adding dozens of options to "SEQ EDIT" in realtime, blows my mind every time i give it a whirl. a little new to me, still, but highly recommended: try these free plugs:
http://www.tobybear.de/p_midibag.html
complex and interwoven, caffeinated answer but hopefully it was an interesting read
