What are you talking about? It absolutely is an issue.
I tried the same setup with Logic and Abelton and the issue doesn’t exist. That means there’s something about Cubase that creates the issue. For better or worse, I’m faster with cubase and would rather not switch. But if workflow is interrupted by that much, it makes the working environment untenable and the switch will have to be made.
I’m glad your Moog and Atari took forever to do menial stuff, but we live now, and my projects are time and workflow sensitive, so please forgive me for wanting things for going well. The Turing machine took forever too and its still ok to complain when your computer runs slow. Its like telling someone that they can’t complain that their car goes slowly up a hill because at one point people had to do it on the backs of mules.
I come here and ask questions not to get flamed because a sequencer is working better than Notator did back in the 80’s, but instead to find solutions. If you don’t have one, fine, but don’t come in here and decide that because back in the day you had to walk up hill in the snow both ways that we should all want to work slowly.
I don’t think it’s too much to ask that a sequencer not take inordinately long to save a sequence. I load very large palettes and with auto save is on, workflow is very horribly interrupted when it autosaves. So now I have the option of turning autosaves off, or dealing with painfully long saves every 10 minutes. Neither of these options is acceptable.
The other solution is to keep the Kontakts loaded in Vienna, but that is unworkable due to the issues Cubase 8 has with Vienna.