I’ve also experienced issues caused by this behaviour when clocking Live w/ Pyramid. When Pyramid’s sequencer is stopped, these continuous CC messages prevent me from auditioning instruments loaded in Live. Looking forwards to a solution!
as above CC 120, 123 are one of the few CCs that have a well supported meaning, and are widely use by many sequencers/daws etc to cease notes.
CC 123 (all notes off) is sent on first stop, and is also used by many controllers/daws etc for ‘midi panic’
CC 120 (all sounds off) is often done a second stop, the difference is to cut all sounds immediately , in particular things like reverb tails.
you will find many sequencers and most DAWs send these when stopping transport.
if novation are setting AMP release = 0, then that is just plain wrong…(and lazy )
as its expected after CC120/123 you can then continue to play.
its not really the job of daws/sequencers to deal with obscurities of particular synths, as that would be unmaintainable.
unfortunately, like @verstaerker , my approach to these kind of oddities in midi (which do crop up all over the place) is to use a hardware midi processor or router.
(in my case the mioXM or blokes midi hub, could block these from the ‘offending’ synth )