Right Don. Same here, I insert a controller 7 set to "0" at the beginning of the track that I send to the VoiceLive Touch. On other tracks, this is how I set my main volume using controller 11 for "expression".

But I've also noticed that since I upgraded to RealBand 2014, that a separate controller 87 is added to each track of the midi file following wherever a controller 7 is in the track. Its value is always the same as the value Controller 7 is set to for that track.

It seems that it has to do with the nodes automation mode for volume. This is especially evident at the end of a song where Controller 7 is used for a fade (rather than the controller 11). In each instance of the fade, Controller 7 is followed by Controller 87 at the same value. Seems to be just a duplication...but why?

If I manually delete each instance of Controller 87 in each part of the track, the node associated with it is also deleted. But more than that, there seems to be some other effect that this undefined controller is having on some tracks. I have some where the upper level patch is being changed. If I delete controller 87, all patch assignments are back to normal. Strange because I don't see any references to controller 87 in either of my romplers.

I would like to find a way to stop the program from adding this controller rather than having to go back through each track of each file to delete each instance. On the other hand, I do like the nodes volume level adjustment, so in that case maybe the way to deal with this is to go back to each track of each file and delete controller 7 and keep the graphic representation of controller 87.

Hope some other chime in so we can get to the bottom of this.

Jeff

Win11, Intel i7 7700K 4.2Ghz, 32Gb RAM, 2x1Tb HD, 500Gb NVMe, BIAB/RB 2025, MOTU 828MK3 audio, MOTU Midi Express, Yamaha Montage 7, DX7II, TX802, Motif XS Rack, Roland Fantom XR Rack, Oberheim Matrix 1000, VoiceLive3 Extreme, Kontakt 6, SampleTank 4.3