Cakewalk to Allen & Heath QU-32 MIDI mapping memory issue

 
<edited for better clarity>
I’ve been using the Allen and Heath QU-32 as my MIDI control surface in my studio for several years (32 fader strips, one super strip for EQ etc), I recently decided to try the latest version of Cakewalk by Bandlab. The platform seems very intuitive to me (being familiar with older versions) and overall it seems quite useable. I haven't put it to the true test yet, in my studio, as I have not gotten past the issue explained below.

On the latest Bandlab edition of Cakewalk, I was able to easily use the “learn” function (right click on parameter you wish to control- remote control- move suface control-Learn-ok) to assign all of the faders and mute/select/PAFL buttons on the Custom Layer of my console to work with the channel strips in Cakewalk. No ACT Controller/Surface neccesay. Using the assignable controls in the ProChannl strip in Cakewalk, I also used this “learn” function to set all of the EQ knobs in the QU-32 Super Strip section for each channel. (i.e.- the LF Gain knob selected on the console controlled the LF Gain for the related track in Cakewalk)… THIS WAS GREAT!! and a function that I have not had before (the EQ for each was adjusted equally by using the console knobs!!!)….
Unfortunately, when I saved this Template in Cakewalk and came back to use it again, the EQ assignments did not seem to have saved…. the faders and buttons on the individual console channels work fine and are still linked properly, but the EQ knobs and HPF don't work from the console at all…. I have tried many options (all of the different controller/surface options, a couple third party ideas, etc) and I have scoured forums. I believe this is a software issue, as I have tried assigning the QU-32 faders, which do save properly as fader controls, to be EQ controls instead... They work just as well, but still dont save...
To be clear, Cakewalk will properly learn the functions in the ProChannel EQ section (channel by channel), but will NOT recall them when the project or template is pulled back up.... if this function is fixed I think it would add a lot of value to busy engineers, like myself, who would like to use a MIDI controller to run those functions *this is a lot more common these days with modern digital consoles having super strips capable of sending unique MIDI for each channel selected.
I’m assuming its an issue with Cakewalk as opposed to the console, because it learns it fine, but then forgets it when I close the session or save it as a template.
 
The QU-32 super strip has 17 rotars and 4 buttons that can be assigned independantly to 32 faders and the QU-32 will mimic the DAW precisely... x 32 thats over 400 controls that can be assigned, but get forgotten as soon as you save...

Thanks in advance for any help.... Let me know if I can be of any more assistance in getting this figured out.... Barring this issue, I am liking it so far.

Hey, thanks a lot for the response..... I have read that thread and, to be honest, most of it is over my head.... like WAY over my head.... I'm an old school recording engineer and not much of a computer guy, much less MIDI stuff
 
I will help you in any way I can to figure this out... I have a QU-32 and QU-16 to work with and would love a solution that will work with both.
 
Will this, hypothetically, work to control the aspects of the EQ in the ProChannel, just as it was before it forgot my settings? (it was nearly flawless interaction... I would choose a channel for the super strip and it would adjust that channels EQ settings on the QU and in Cakewalk)
 
Would it also allow "force feedback" to the faders on the QU?(i.e.- right now the QU controls cakewalk, but movements on cakewalk do not control the QU.... I would like the same to happen either way)
 
Thanks a ton for your interest in helping to get this worked out.... what can I do to help?

Have you tried saving your  settings in the A&H QU-32 itself as a MIDI map, instead of trying to save them in the DAW?

A mix scene just records 'mix' settings and automation. A MIDI map "saves" controller functions for the DAW.
 On my old ancient Allen & Heath button "A1" was a map for faders, pan pots, and automation. Button "A2" mapped pan pots to EQ, button "A3" was  compressor parameters,  "A4" mapped to my Lexicon reverb. All hardware 19" rack mount gear running off an 8x8 MIDIMAN MIDI Sport patchbay.
 Very old A&H desk circa 80's running on a Commodore 64 for automation, but MIDI maps had to be stored in the desk/console itself.
 I would assume a modern digital A&H desk would be almost the same for storing MIDI  maps for DAWs and plugins?
 
If the A&H doesn't have specific drivers that (you can control and set up) listed in SONAR/CbB'S "Control Surface" dialog box than the DAW won't recognize it and save settings.
 It might as well be a jar of mayonnaise as far as a DAW is concerned. 
 
Sorry, but where would we be without a sense of humor????????