The phenomenon is occurring in Nuendo 12, but I believe it’s likely the same in Cubase 12 as well. Does anyone have any information?
I’m using older versions of Cubase and Nuendo 12. I think the functionality of Nuendo 12 as a DAW and how to access it is almost 100% the same. The MIDI Remote function of Nuendo 12 and Cubase 12 is excellent, but this feature seems unstable from the beginning. Specifically, with a controller connected to the Midi Remote Manager, I’m troubled by the following phenomenon:
- It works correctly once immediately after connecting, but at some point during the session, for some reason, the DAW stops sending MIDI to the controller. In this case, sometimes it can be restored by turning off the script and turning it back on, along with occasionally executing “Reload Script,” but in most cases, restarting Nuendo 12 is necessary. Also, even though it was displayed immediately after the connection when this problem occurs if you check the MIDI port settings of Nuendo 12, the controller disappears from the MIDI IN list for some reason. I don’t think it’s related to the fact that the controller I’m using is cheap.
If there were no issues like the one mentioned above with MIDI Remote, it would be much more convenient to use than the legacy method of registering and holding templates assigned to CC# according to the purpose. However, if there are fundamental communication issues, work comes to a halt.
Is the reason for deliberately keeping the legacy method because the stability of MIDI Remote functionality has not yet been established?
OS: Windows 11
DAW: Nuendo 12
MIDI Controller: Korg nanoKontrol 2