Read the 'Broken Forum' thread to access replies.

Thank you Toby. I was able to see the messages. Are these issues going to be fixed? I hope so. This forum is still important to some of us. I was looking at an old thread of mine, and there is an issue I had forgotten about. It had to do with midi remote, or maybe it's predecessor, clashing with the editor VST. Specifically, using  midi key commands seem to caused problems with the audio routing of the motif in Cubase.  my workaround was to not use midi for key commands. But now with the midi remote, I've set up the motif and my stream deck to do all kinds of neat things, like control channel settings, and quick controls and so on. so it looks like I have to choose between using the motif as an extended controller of cubase or using its sounds in cubase. Kind of a bummer, cause I still think the motif sounds better than many vstis out there, and it has the advantage that I already own it. But I'm thinking I might have to use the motif as my controller and start using other plug-ins like kontakt etc.  there's no question here, i'm just sharing my thoughts, though I would be interested in what any of you have to say.

Not sure if I'm shouting into the ether here, but for anyone who's listening, I think I figured something out. The problem is the old generic remote. When I disable it, everything works as it's supposed to. So this is kind of what I was saying in my previous post but more specific. I knew the problem was midi, but now having narrowed it down to the generic remote, I will be able to keep the other parts of my midi interface set up, which is nice. Knock on wood. Every time I think I figured this out some other problem pops up. After owning the motif for eight years and cubase for four, I hope I'll be forgiven for feeling a little pride that I was able to figure something out on my own. Lol. 

Not sure if I'm shouting into the ether here, but for anyone who's listening, I think I figured something out. The problem is the old generic remote. When I disable it, everything works as it's supposed to. So this is kind of what I was saying in my previous post but more specific. I knew the problem was midi, but now having narrowed it down to the generic remote, I will be able to keep the other parts of my midi interface set up, which is nice. Knock on wood. Every time I think I figured this out some other problem pops up. After owning the motif for eight years and cubase for four, I hope I'll be forgiven for feeling a little pride that I was able to figure something out on my own. Lol. 

Not sure if I'm shouting into the ether here, but for anyone who's listening, I think I figured something out. The problem is the old generic remote. When I disable it, everything works as it's supposed to. So this is kind of what I was saying in my previous post but more specific. I knew the problem was midi, but now having narrowed it down to the generic remote, I will be able to keep the other parts of my midi interface set up, which is nice. Knock on wood. Every time I think I figured this out some other problem pops up. After owning the motif for eight years and cubase for four, I hope I'll be forgiven for feeling a little pride that I was able to figure something out on my own. Lol. 

Disable "Reset on Stop" in Cubase
Go to Studio > Studio Setup > MIDI > Reset on Stop <a href=" removed link ">Slope and uncheck options related to Program Change or other MIDI resets.
This prevents Cubase from resetting the sound engine when switching tracks.

Thanks, but it's already disabled.
by the way, that setting is in preferences, not in studio set up. I wonder if that's a new thing.