Am 27.04.2013 02:29, schrieb Geoff Beasley:
> why can't i change the A note in the new drum list editor? - I want to
> do that all the time ..
this is by concept. The new drum editor does not map the notes in the
parts to notes actually played. They are *the same*.
You also cannot change the A-Note of a F#-3 in the Piano Roll, that's
exactly the same thing.
Why would one want to change the A-Note? My drum-"workflow" is as
follows: My synth dictates me which drum sounds are available and which
notes trigger which sounds. Then I play around a bit, until i found the
drum sounds i want, and program/record them.
If I afterwards want to change the sound, e.g. i want the AcousticSnare
drum to be replaced by the ElectroSnare, then I just select all notes,
using CTRL+Click onto any AcousticSnare event (this will select *all*
AcousticSnare events), and move them to the ElectroSnare.
Am 27.04.2013 16:17, schrieb Robert Jonsson:
> Though when I think about it I'm not sure why the E-note is adjustable
> but not the A-note.
> Maybe it should be the other way? Florian do you remember if there was
> an intention?
The E-Note is indeed adjustable. When you have a (physical) MIDI-drumkit
you play on, that dictates you the MIDI events it will output, then you
can adjust this here, as in "when note 41 arrives, then treat that as
the new drumtracks are really exactly like the pianoroll, just with some
eye- and usability-candy.
with old-style, muse-internal-flow was: event 123 arrives -> treat (and
store) it as drum note 123 -> (if echoing is turned on: look the A-Note
up and output the note 42.)
with newstyle: event 123 arrives -> look the E-Note up and find out that
this is meant to be note 42 on track 1 -> treat and store it as such ->
(if echoing is on: output note 42.)
with the pinaoroll: event 66 arrives -> no lookups -> treat and store it
as such, i.e. event 66) -> possibly output event 66.
hope this helps.