Have you given any thought to this being caused by your keyboard controller/driver? What model do you have? You are looking at all your audio settings, but maybe you should take a look in your Studio One preferences, Midi options menus. Look for any settings which may not be the same as the other DAW software you are checking it with. Screenshot them in Studio One, you could even upload it and link here. But that way you can open that SS and then open another DAW to directly compare, while you are looking at both of them.

It's never a bad thing to have and know multiple DAW software suites either. Studio One wouldn't be so bad to be stuck with as the only one that does something the way you want. That is part of the reason I really stick to Logic, and just use other programs for various infrequent tasks.

 

It's not a MIDI controller problem. I thought that could be it, but when the sound cuts off it is not because pressing the keys does not trigger sounds, but because the audio engine stops. The decay of sounds is cut short. So it's not a MIDI controller problem.

 

I don't think so either, but what else is left? Usually when you have some problem like this, and you have done all of these different suggestions to test and fix it; the cause is usually something totally stupid and seemingly unrelated. A bad USB cable, or something like that. I had a problem recently where the 1/4" to 1/8" adapter on my DT-990s had failed. I never even disconnect them. It had me bamboozled, thinking something was wrong with my console mixer.

 

I have tried reinstalling Windows, I have even tried on two different computers. It is logical to think that the problem is in the audio interface, however, if I activate the integrated audio card on the motherboard, the problem persists. On the other hand, why don't I have any problems in Studio One? Maybe it all depends on the way a DAW is programmed. Perhaps most people do not notice this interruption of sound because of the way they work. If you are in the habit of loading the plugins you need at the beginning and in one go, you may never notice that audio dropout. In the Cubase forum I have seen some posts talking about this problem. It seems to be a minority issue that affects few people, perhaps because it depends on the way each person works.

 

that could be. I just switched a Virtual Instrument from Omnisphere to Axxcess during playback of the track I am working on. Not only did it not click, hesitate, but it even began playing the part right away. Maybe there was a click, or something; but it is a big project and there was no audible issue like you are having.

It could be how you work, I agree with you. When I play a part in on my controller, I never switch the patch or the plugin while i am still playing. If I am recording the midi of what I am playing, I always hit stop as soon as I have recorded what I wanted to. It's just faster to cut the empty end space that way. It's also a habit now, because the transport buttons on the S49 do not work in Logic. At a certain point, all you can do with some of this stuff is develop a workaround, like that one.

 

What scenario do you even need to have audio still playing when first load a VST a new or existing track? Because how often do people even use VSTs in their default state? Almost never? And isn't that double for instrument VSTs. I'm curious what your personal workflow is, such that the playhead stopping is a hindrance to you? Because, i've never noticed what you're describing as a problem since I don't work that way.

For example, if I load a delay the default parameters would never be used so there's no reason for me to hear it. I would make a majority of my tweaks, then hit play, and while it's playing fine tune my adjustments.