Just to add some hopefully useful info for VSL it happens in Nuendo 10, Cubase 10.5 and Studio One 4.6 so it has nothing to do with "DAW Specific".

The fact is that I can reproduce it 100% of the time.  All I have to do is use Synchron and VI Pro for a while and it starts happening.  I will be sitting here working and suddenly go, that's odd, what's happening to my Solo Flute?  Sure enough, I open up the player and I am getting the red alert that it's having an issue and dropping my notes.

I have 10 separate NVMe SSD drives with every section on their own.  I have my preload buffer settings at 32768 maximum and still this happens with 1 single instance of a single note VSL flute, or VSL Guitar playing.  I don't even have to hit playback.  I can just hit the note on the midi keyboard or hit the note with my mouse inside the VSL player and it goes red and drops every note I play.  Once it starts happening for 1 instrument it starts happening for every and all instruments that are VSL regardless of what drive they are on.  I can still however play all of my other instruments that are not VSL perfectly without any issues.

I reboot, open VE Pro, Studio One and 20 minutes later I am up and able to start again.  Repeat every day since the last major update when the big bang brass came out.  I have to reboot at least 2-4 times a day with this issue and that's sometimes when only working a few hours.

I just noticed when I opened my project there's new versions of the Software.  The only one I don't see an update for is VE Pro 7.

I am going to update them all and see if it helps.  I will post here and in my ticket if there's any improvements.

Thanks

Hi cgernaey,

I updated and it did not fix the problem.

Dave

Hi,

Am I right that we all use RME audio interfaces?
If so, could you please send me your RME interface settings, and do you use the WDM Device feature?
And please reportif the option "Enable MMCSS for ASIO" is enabled or not in the "About" tab of the interface settings. (feel free to just screenshot the settings and attach them here or send them to us via support@vsl.co.at with the note "To Ben").
Also please add the exact Windows version (for example: Windows 10 1903, 18362), as well as the current RAM usage when these dropouts occure (example 12.5GB / 16GB).

I encountered this issue once as well, but after system reboot I was no longer eble to reproduce it to this day, which makes it hard to find and fix the issue.

Many thanks, Ben

@DaveJ said:

 

Hi cgernaey,

I updated and it did not fix the problem.

Dave

Hi Dave,

I updated and it still happens as well.  I will gather the requested info Ben is asking for.  By the way yes I do have an RME-Audio interface.

Thanks

Many thanks! Could you try to enable MMCSS in the options and then reboot the computer?

Does this improve the situation?

I sure can.  I will update if and when it starts happening again.

FYI Ben, this issue happens without VE Pro in the mix as well.  Just using it as a standalone track inside any DAW it performs the same way so the remaining issues of VE Pro I believe are completely separate from this VI Pro and Synchron Player issue.

Thanks!

Thanks you all for the information you provide, as well as for your patience.
It is a really strange issue, and hard to track down on just one system.

Ben,

I am getting pops and clicks since turning it on.  These are true pops and clicks as if you were overloading the system or had a really low buffer type pops and clicks.  I was not seeing the red streaming warning indicator like I do with our current issue.  It was just pops and clicks, even if I just did a simple 2 note trill with the flute.  I turned it off and they all went away.  I wonder if that's because I have 32 cores in my machine.  For now I have the setting off again as I can't even play the song or use any instrument without pops and clicks with it on.

During the pops and clicks I went into my Solo Flute Synchron Player and the power button for the velocity xfade slider was blinking red.  When I hit it, it turned off and then I turned it on again and it went blue.  First time I ever seen that.

**I have added more of my system configuration in my signature incase we have hardware similarities as well.**

Thanks

Hi cgernaey,

I tried Ben's suggestion about enabling MMCSS but still had the same problem. I almost gave up for the night but then decided to uninstall (control panel, uninstall a program ) the RME drivers and software. I rebooted then reinstalled the RME driver then rebooted again.

It seems to be working much better now. It is to early to tell if the issue is gone but I playback looped a large template in VEP 7 for an hour and a half and came back and there was no hard drive flashing symbol.

Would be interested to see if you tried the same thing if your problem would improve. Just make sure to sort the uninstall list by Publisher to get everything by RME.

I am going to try Cubase 10.5 tomorrow and will let you know the results. Still to early to tell but maybe windows update messed with the driver somehow.

Dave

Hi cgernaey,

Too many cores could lead to issues in previous Windows and Cubase version, which should mostly be fixed by now.
You could try to disable SMT (Simultaneous Multithreading, can be disabled in the BIOS; on Intel CPUs it's called Hyperthreading) which lowers performance a little bit, but often solves many audio issues.

It's really strange too hear that enabling MMCSS leads to pops and clicks, because this feature should improve exactly these issues. So I would also test the combination of disabled SMT and enabled MMCS.

I would also give Dave's advice with uninstalling, rebooting and re-installing all RME drivers a try.

Best, Ben

Good morning Dave and Ben,

Here's the things I have done since my last post:

1.  Updated my BIOS - had no affect.  Same results.

2.  Enabled Windows 10 updates and let it install every update it had except update version 2004.  I did this because I read a post where a user was having horrible audio issues on a brand new machine because he had done all the "kill all possible ways for Windows 10 to do updates".  He claimed as soon as he allowed Windows to do the updates and just said to hell with it and let it do them all and he left all the settings back to default "allow" mode his issues all went away.  I had done exactly as he and disabled all the Windows updates and services.  At the moment I have them all available again and fully patched.

3.  Uninstalled the RME Audio driver, saved my Totalmix settings backup and then reinstalled the most up to date driver (same one I already was using) version 4.30.  What I noticed was that in Control Panel since you mentioned it, I found the drivers for not only my latest one, but the previous version were showing there.  I went ahead and removed all 3.  The software, the driver version 4.30 and the driver version 4.29.  Rebooted and then reinstalled only version 4.30.  I can confirm that now I only see version 4.30 in control panel.

4.  Restored my Totalmix settings - success.

5.  Tested my Windows audio - success.

6.  Tested Studio One (this is where I live) - Interestingly at this point, Studio One has finally stopped crashing upon opening.  It would crash guaranteed 100% of the time upon opening for the last month (exactly when I installed VSL Updates).  After that initial crash, it would open and carry on its day.  Interestingly, Nuendo and Cubase would do the same many/most times.  This morning, didn't happen.  Very possible the system was confused by seeing multiple versions of the audio driver.  Dave, did you by chance see more than 1 version in yours as well?

Ben,

I forgot to mention I never change my buffer settings or sample rates during a project.  In fact, I never do ever.  I know my system can handle running at 64 or 128 because I tested it but I am ok working at 256.  Also, I found the setting for SMT but haven't done anything to it yet.  I know in the past hyperthreading was a real issue especially for DAWs.  For the moment I feel like I have made enough changes and am going to test my system today knowing all of the things I have done this morning.

Thanks again and I will report back throughout the day what I find.

Christopher

Thanks for your update, let me know how it works. I have looked it up and I have 5 versions of the RME drivers in my apps menu. Looks strange to me, I will clean up this as well (thanks for the hint, Dave!)

Yes, I had multiple versions of the same driver. I had never seen this before. They were a different color and slightly greyed out. I could only uninstall the latest one. When I tried to uninstall the others (there were at least 5) windows would not let me do it so I had to use that free tool CCLEANER to get rid of the others. 

I will be testing cubase soon!

Dave

Unfortunately, after about 45 minutes into Cubase I started to get the dropouts and the red hard drive again(with and without MMCSS). I am using the VST3 version fo the Synchron player. I am going to try the VST2 version for the loaded intruments to see if that makes a difference. My processor is the intel 9900k I may try to disable hyperthreading to see if that makes a difference.

Thanks again,

Dave

Same thing for me Dave.  I still have the issue and it's not resolved.

This time I loaded up the project and ran absolutely nothing but Studio One.  No VE Pro, no internet browser, nothing.  Just opened the project and left it looping and it started doing it shortly after.

While the project was now misbehaving, I added a brand new VST3 instance and added a simple woodwinds flute 1 and it does the same thing.  I then added a VST2 instance and added the same flute and setup and it doesn't do it.

I then loaded up VE Pro and all of my VE Pro instances are VST3 and they do it as well.  I added a VST2 64bit instance with a Synchron player inside of it and it didn't do it.

Perhaps it's a VST3 thing?  I am going to copy all the parts to these new VST2 instruments and let them loop for a few hours and see what happens.

Christopher

I was not able to make the VST2 Synchron Player do this tonight in my testing.  I ran it for several hours and all the VST3 instances were doing it, but the VST2 instances were running just fine.

Christopher