I have had a look at the Node cutting problem and would advise as follows:

Controllers CC7 & CC85 Node indicators.

Nodes were introduced in 2014 to provide a graphical means of showing changes to volume in the Main Tracks Window. These controls work for both Midi and Audio Tracks.

While I use Nodes extensively when Mixing Audio Tracks, I do not use them when developing Midi data. When developing an existing Midi file I usually remove all Midi data and store this in a separate frozen track

Unfortunately, the operation of the Edit Function “CUT” combined with the Data Filter has been altered and now gives problems.

If you use “CUT” and select “Events” (Default) then the Events are cut, but some CC7 and all the CC87 data entries are not and remain in the track. Combined CC7 & CC87, with identical timings, are not treated as Events.

There is now an option for “Nodes” separately. If you select this option and CUT then CC87 plus any associated CC7 with the same timing remain – all other CC7 entries are removed.

Now, CUT selecting “Nodes” only. The result is the same as for the previous test.

Now select the option to use the Data Filter(which should override any selections in the Main Panel) to delete all Controllers 0 to 127. The result is to remove all Controller Events except the Node data CC 87 & associated CC7 Events.

You can delete CC87 and rogue CC7 Events laboriously in the Event List one at a time.

You can also open up each track in the Main Tracks Window to show the Node items and use the right click menu to select “Erase all Nodes”. Also very laborious.

The best workaround is to COPY all the Tracks but not select the “Node” option. Then Paste the tracks back again overwriting the existing data. Work can now proceed as previously.

Interestingly, the CC87 nodes once removed do not reappear on future re-openings of sanitized .seq files..