Keezix wrote:So long as you don't specifically create a "MIDI Device automation" track for the Motif (or any other device), you won't encounter this bug. This is a different type of track that can only be created by selecting the Motif in the MIDI Device Manager, clicking on "Open Device", and then activating the "write" button within the newly opened Device window. So those are the actions to avoid. The actual MIDI track you use for playing the Motif turns out to be unrelated to this particular issue. This issue is brand new to 7.5.2. If you upgrade to 7.5.0 or 7.5.1 instead you will not run into this at all (although maybe others
Keezix wrote:This had the effect of essentially disconnecting my entire MIDI system every-time I wanted to open or start a project. I have no choice but to retreat back to 7.5.1 where this is not an issue.
Keezix wrote:Alexis: This now confirmed bug only affects those external devices defined in the "MIDI Device Manager" for which an automation track has been created for it. It absolutely doesn't make any difference what device(s) you are connecting. If you are only using the Motif as an input controller, you're not likely to encounter this, unless you want to automate it's setup (For example having it's "local control" automatically switch to "off" for computer, rather than live use). Closing and reopening a project won't help with this. The device will remain "Not Connected" until you go into the "MIDI Device Manager" and manually re-connect the output.
For me this was a complete showstopper, because I use templates with folders of automation tracks in place for most of my couple dozen external devices. This had the effect of essentially disconnecting my entire MIDI system every-time I wanted to open or start a project. Reconnecting all of these Devices every time is ridiculous!
I have no choice but to retreat back to 7.5.1 where this is not an issue. I still have the installer and I hope it works this way. I've been a Cubase user since it's inception in 1989 and this is the very first time I've had to "downgrade". I'll have to stay "downgraded" until this is fixed.
Keezix wrote:I'm happy to report that I just received a response from my tech support representative at Yamaha, who has finally confirmed this bug and reported it. As such, the developers are now aware of this issue, so hopefully it will be fixed in a future version. Meanwhile, I successfully "downgraded" back to 7.5.1 which works perfectly fine for the way I use Cubase, and I can now get back to getting actual work completed.
Thanks to all of you who have assisted with this issue!
Users browsing this forum: No registered users and 1 guest