# Generic remote template on CMC-AI not working after restart **URL:** \ **Category:** Cubase\ **Tags:** cubase-older-version\ **Created:** [May 21, 2012, 7:22pm UTC](https://forums.steinberg.net/t/generic-remote-template-on-cmc-ai-not-working-after-restart/615784 "2012-05-21T19:22:46Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![JamesTNL](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@JamesTNL](https://forums.steinberg.net/u/JamesTNL)\ **Post date:** [June 17, 2012, 7:43pm UTC](https://forums.steinberg.net/t/generic-remote-template-on-cmc-ai-not-working-after-restart/615784/12 "2012-06-17T19:43:51Z")
> [@csd](#): > > Considering that generic remotes don’t recall correctly (i.e. by default rather than xml auto-import), I would say it’s a bug with something in the CMC controller config that isn’t activated after a restart. > > What you are seeing may actually be there with any controller, but since most are simply midi CC controls, it may not affect those - i.e., you move a cc control, and Cubase sees the assignment. > > The CMC may have additional sysex or midi messaging that has to be reset before Cubase can see it’s assignments. That doesn’t make much sense to me. If the CMC conforms to the MIDI spec as any other MIDI device, at the very fundamental level, it is a generic midi controller. Case in point: After restarting Cubase, the midi signals are registered perfectly fine (as I can see in the midi activity window), but Cubase just isn’t aware of the generic remote assignments. I believe this is more likely caused by a Cubase design error where the CMC extension somehow tricks Cubase into thinking all necessary configs have been loaded and never get’s a chance to load the user defined generic remote config. Whichever way, the underlying cause is irrelevant. Either Steinberg fixes this issue, or I need to use the workaround I mentioned earlier. Thanks for thinking with me here though… --- _[View the full topic](https://forums.steinberg.net/t/generic-remote-template-on-cmc-ai-not-working-after-restart/615784)._