lloydcole wrote:...Also, as I mentioned in an earlier reply, I have in my test project a Drum Machine track, playing midi notes from the arranger, AND a simple midi track playing hi hat from a launcher clip, routed to the Drum Machine. I cannot mute the midi coming from the drum machine with the MUTE button, but I CAN mute the midi from the midi track using the MUTE button.
Which is precisely how it should work, you just don't understand signal flow. The mute button is always at the end of the signal chain and ONLY works there. See below.
Drum Machine track:
MIDI from clip -> Drum Machine -> Mute Button
In this case the mute button can only mute what comes out of the Drum Machine.
Expand to include pads and you have this:
MIDI from clip -> Drum Machine Pad -> Pad Mute Button -> Mute Button
Again, the mute button only works at the end of the device chain.
The reason you Hihat track works is because of this:
MIDI from Hihat track clip -> Hihat track Mute Button ->(routed to Drum Machine track)-> Drum Machine -> Mute Button
Here you're pressing the Mute button that sits between the MIDI and the Drum Machine. That's why it works, you're cutting signal before it gets to its destination.
Here's one way to be able to mute MIDI and retain Drum Machine pad names for editing:
Make individual tracks for all the pads, group them and route their MIDI to the group track. Now click on a Drum Machine pad's plus sign and once the popup browser shows click OK. You should be able to rename that cell and it will show up in the MIDI editor.
Then you create individual clips and compose MIDI in there. If you want to edit all of them at the same time take advantage of the layered editor. You can also colour code your parts this way