Currently the device panel works well on a technical level. It just works poorly on a UI/UX level. In it’s current form it is hard to read and awkward to create. I think this feature can be revived with some UX polishing. Below is a mockup that uses current UI styles in Cubase 14.
To be honest, I would rather prefer to be able to use a VST3 plugin to control external synths, bit this is almost impossible, as VST3 doesn´t support neither Sysex nore Program Change. So it would require some additions to the VST3 SDK.
Why the preference for VST3 plugins?
There is a free software called CTRLR, where you can create decent looking VST2/3 plugins to control your synths. Unfortunately, unless you have a multi-client MIDI interface, at least in Windows you will have to use virtual MIDI cables.
Device Panels are very cumbersome to program, and limited to Cubase/Nuendo, so there is less motivation for programmers to create some.
VST3 plugins can save presets as VSTpresets, which will be understood also but another host.
I believe, Device Panels cannot receive data from an external synth, so editing an existing preset is more difficult. (Yes, CTRLR can, I just didn´t figure out, how…)
If someone makes a feature request for fully MIDI capable VST 3 presets, you can count on my vote.
Device Panels are very cumbersome to program, and limited to Cubase/Nuendo
UX refers to “User Experience”. So in my original post I’m arguing they should improve the experience. This means make it less cumbersome.
I believe, Device Panels cannot receive data from an external synth, so editing an existing preset is more difficult.
I’m only suggesting it should be improved for VST use because it works more easily there. I am able to create bi-direcitonal communication between it and the VST.