OT: CC1, Absynth Presets & Whoops!

OK, P5 users who also happen to own Absynth

anybody ever notice how P5 resets CC1/Mod Wheel to 0 on any twiddle of the Wheel or stopping track play or switching from editor to track play?

yes it's true,
you might want to change a few factory presest from XY to sliders to see this in action

when CC1 is controlling significant (like a filter) this reset can make a huge differenced in sound -- or like no sound at all

This is obviously some sort of host/Absynth interaction -- and since some hosts like FLStudio don't allow the setting to be modified at all (which isn't exactly an ideal solution is it?)
So I'm assuming this is some sort of designed host decision OR I have some setting I can change that I don't know about. But this action just seems wrong --or at least not quite right
it would be ideal if the Mod Wheel could be twiddled and return to the preset setting and never, ever have a reset based on switching track and editor play, or track play halt.

Any experts on the philosophy of midi CC1 resettting? And why Cakewalk seems to have gone down this path?

yep, i've noticed this too. you can always change the midi controller numbers back on the envelopes page; i've effectively eliminated all cc0 messages (strangely, my controller tends to reset the wheel as well, and in any event, i prefer knobs to the tonewheel). but it's still a hassle.

As I pointed out in the email I sent, I think that the way a number of the Absynth patches have the MW control set to a start value other than zero is strange...I haven't noticed this practice in any other synths presets. If the initial value of the preset has the MW at full, then any subsequent movement on a midi keyboard (or P5 sending a midi reset, if that is what it does) will result in a large jump in whatever parameter Absynth has assigned to the MW. It seems like a preset making 'no-no' to have the MW initialised to anything other than zero...