I'm having big difficulities in taming the snare i'm using,
so I really need to broden it out, from the center to the
L & R using some effect. Don't know if this is possible
to add fx to single drum PCMs, if not i'd appreciate
anyones tip to solve this problem in another way.
Regards
/embry0
Is it possible to add fx to single drumPCMs in a drumtimbre?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Is it possible to add fx to single drumPCMs in a drumtimbre?
Last edited by embry0 on Sat Nov 24, 2007 1:40 pm, edited 1 time in total.

Proud owner of >RADIAS-R+RDKB|microX|KP3
- meatballfulton
- Senior Member
- Posts: 351
- Joined: Wed Jun 20, 2007 11:28 am
- klangsulfat
- Junior Member
- Posts: 75
- Joined: Fri Nov 02, 2007 7:00 am
- Location: Germany
klangsulfat: I second that..
Why on earth didn't Korg make send FXs instead of inserts.. would be much cooler that way and it really wouldn't require much more DSP time..
I believe that it is still possible to fix this in a future OS upgrade:
There are some unused bytes in the timbre data-- one of it could be used to squeeze in an FX "send configuration" id.
In order to maintain compatibility with V1/V2 programs, the firmware should switch to the V1/V2 "FX routing" (which is 4 * 2 FX units in serial + the master) if it detects that the "send configuration" id of one of the program timbres is 0.
If all timbres use "send configuration ids" 1..19 (3 for regular timbres
plus 16 for drum timbres if a drum timbre is active),
the new (imaginary
) custom FX "send configuration" should be used.
(edit: the "send configuration id" could be replaced by a simple flag
"use v3 send configurations"
which would require just one tiny bit instead of a whole byte ...
)
Each "FX send configuration" would basically describe how to
distribute the signal to the 9 FX units, e.g. 10% to FX1, 50% to FX2,
plus the "root" FX slot ( (id0) in the example diagram below)
(Ideally this information would be stored in the program data but I
do not think that this is possible without breaking compatibility, hence
the "send configuration id" solution.)
The part that requires a little thought is how to configure
the FX routing (there are 2*4 + 1 FX units in the Radias):
I would suggest to provide a number of preset configurations to make
this editable on the Radias itself. The routing should be freely configurable via Sysex, though:
For each FX unit in the "routing configuration", a "source unit id" must be stored.
For the "source unit id", Id 0 would mean "root" and ids 1..9 would
denote the respective FX unit.
Example:
--(id0)--fx1(id1)--fx2(id2)---
\ \__fx4(id4)--mfx(id9)---(out)
--fx3(id3)----------/
(hope the ASCII is still readable after posting
,
basically fx1+fx2 are chained, in parallel to fx3 and the
combined output goes to fx4, then to mfx, then to out)
For this example configuration, the "routing configuration" data could look
like this (a value of 127 means "unused", 1...8 are FX units
1..8, 9 is masterfx).
For each FX unit, a list of "input sources" is given:
fx1: 0, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx2: 1, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx3: 0, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx4: 2, 3, 127, 127, 127, 127, 127, 127, 127, 127
fx5: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx6: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx7: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx8: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx9: 4, 127, 127, 127, 127, 127, 127, 127, 127, 127
out: 9, 127, 127, 127, 127, 127, 127, 127, 127, 127
This may look complicated at first but in a PC/MAC editor the
configuration can ofcourse be edited graphically and on the Radias
there could be preset-configurations..!
Finally, some new SysEx functions would be required to send/receive the FX "send configurations" and "routing" for a program.
Korg: please give this a thought
Why on earth didn't Korg make send FXs instead of inserts.. would be much cooler that way and it really wouldn't require much more DSP time..
I believe that it is still possible to fix this in a future OS upgrade:
There are some unused bytes in the timbre data-- one of it could be used to squeeze in an FX "send configuration" id.
In order to maintain compatibility with V1/V2 programs, the firmware should switch to the V1/V2 "FX routing" (which is 4 * 2 FX units in serial + the master) if it detects that the "send configuration" id of one of the program timbres is 0.
If all timbres use "send configuration ids" 1..19 (3 for regular timbres
plus 16 for drum timbres if a drum timbre is active),
the new (imaginary

(edit: the "send configuration id" could be replaced by a simple flag
"use v3 send configurations"
which would require just one tiny bit instead of a whole byte ...

Each "FX send configuration" would basically describe how to
distribute the signal to the 9 FX units, e.g. 10% to FX1, 50% to FX2,
plus the "root" FX slot ( (id0) in the example diagram below)
(Ideally this information would be stored in the program data but I
do not think that this is possible without breaking compatibility, hence
the "send configuration id" solution.)
The part that requires a little thought is how to configure
the FX routing (there are 2*4 + 1 FX units in the Radias):
I would suggest to provide a number of preset configurations to make
this editable on the Radias itself. The routing should be freely configurable via Sysex, though:
For each FX unit in the "routing configuration", a "source unit id" must be stored.
For the "source unit id", Id 0 would mean "root" and ids 1..9 would
denote the respective FX unit.
Example:
--(id0)--fx1(id1)--fx2(id2)---
\ \__fx4(id4)--mfx(id9)---(out)
--fx3(id3)----------/
(hope the ASCII is still readable after posting

basically fx1+fx2 are chained, in parallel to fx3 and the
combined output goes to fx4, then to mfx, then to out)
For this example configuration, the "routing configuration" data could look
like this (a value of 127 means "unused", 1...8 are FX units
1..8, 9 is masterfx).
For each FX unit, a list of "input sources" is given:
fx1: 0, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx2: 1, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx3: 0, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx4: 2, 3, 127, 127, 127, 127, 127, 127, 127, 127
fx5: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx6: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx7: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx8: 127, 127, 127, 127, 127, 127, 127, 127, 127, 127
fx9: 4, 127, 127, 127, 127, 127, 127, 127, 127, 127
out: 9, 127, 127, 127, 127, 127, 127, 127, 127, 127
This may look complicated at first but in a PC/MAC editor the
configuration can ofcourse be edited graphically and on the Radias
there could be preset-configurations..!
Finally, some new SysEx functions would be required to send/receive the FX "send configurations" and "routing" for a program.
Korg: please give this a thought
