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

Hi Christopher,

I was able to run a couple of Cubase projects for a few hours with no issues after changing the VST3 plugin for the VST2 plugin. Luckily the Synchron presets are compatible between VST2 and VST3 so it is not that big of a deal. interestingly enough both of these projects use the Synchron Piano player that only comes in VST2 and I have never had an issue with it. So It may be a VST3 issue with the Synchron player.

Dave

Hi,

We are investigating this issue, and would like to know if you are using NVMe SSDs to store the samples, and could you please post the drive speeds shown in the Synchron Player's settings?

Best, Ben

Hi Ben,

I have 10 NVMe drives with every section on it's own.  Synchron Player shows over 600MBs on the speed for all drives.

It automatically set it to 3072 for preload buffer for all drives.  That used to work perfectly up until this issue started on that update.  I have since tried every setting up to the maximum of 32768 which is where I am right now and it happens no matter what setting I use.

Thanks,

Christopher

Hi Ben,

Yes. NVMe SSD, read speed 625 MB/s. I set the preload to 8192.

Dave

Today I tested using VST2 instruments in several situations and every time they worked fine the entire day while the VST3 had issues all day.

At this point I guess I hope the VSL team will get this resolved.  I don't have the energy in me to replace all my instruments as my template is 1500 tracks of VST3 and my current song is 491 of those.

Christopher

Please create a process mini-dump of the host after the issue appears (host the Synchron Player in Cubase and create the dump from the Cubase.exe process), please see the following image on how to create a minidump with process explorer:
http://cloud.addictivetips.com/wp-content/uploads/2012/02/create-dump-1.png

https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Send us the dump to support@vsl.co.at
Hopefully this will help in the investigation.

Many Thanks!

We use our own plugin-format inside VEP for our players.

@bbelius said:

We use our own plugin-format inside VEP for our players.

I noticed Ben posted hints about editing BIOS, dumping Cubase and other Windows-only related stuff.

For the rest of us that that are on Apple platform what should we do?
Thanks

@bbelius said:

We use our own plugin-format inside VEP for our players.

I can tell you with absolutely certainty that it happens in VE Pro 7 because it does it for me on Windows 10.  It's the first place the issue arose and I put in a help ticket for it.

For myself and Dave who have done all this testing above as well as many others who are simply not voicing it yet, it's not DAW or host specific and so far proven to do it in VE Pro 7, Studio One, Cubase, and Nuendo.

With Ben just bringing to light that VE Pro 7 uses it's own proprietary version of Synchron Player, it just further shows it's specific to the Sychron Player and most likely nothing else.  We were able to quickly get to the fact that it's VST3 inside a DAW and VE Pro 7's version specifically.

I would be cautious about making any adjustments to your systems, especially since I have risked and almost lost everything doing the tests I did above.  All to which amounted to absolutely no improvement.

Christopher

@bbelius said:

Please create a process mini-dump of the host after the issue appears (host the Synchron Player in Cubase and create the dump from the Cubase.exe process), please see the following image on how to create a minidump with process explorer:
http://cloud.addictivetips.com/wp-content/uploads/2012/02/create-dump-1.png

https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Send us the dump to support@vsl.co.at
Hopefully this will help in the investigation.

Many Thanks!

I am trying to capture this tonight.  Does it only work in Cubase or will the one from Studio One also work?

Christopher

Works with every host.

Ben,

I was able to reproduce it in Cubase pretty quickly.  I took a minidump while it was playing the song and crackling, popping and dropping the notes.  I also then stopped the song, let the computer catch up for about 30 seconds to calm down and took another minidump while it was sitting idle.  I was able to reproduce that as always, even when idle like that, the second I hit a note it drops it with the red disk.

Here's my case number as I emailed a link to my OneDrive with the minidumps:

Case 351129

Thanks,

Christopher

@bbelius said:

Please create a process mini-dump of the host after the issue appears (host the Synchron Player in Cubase and create the dump from the Cubase.exe process), please see the following image on how to create a minidump with process explorer:
https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

http://cloud.addictivetips.com/wp-content/uploads/2012/02/create-dump-1.png

Send us the dump to support@vsl.co.at
Hopefully this will help in the investigation.

Many Thanks!

Hi Ben,

I have 2 mini-dump files. They are about 175 MB. Too large for regular email. What is the best way to get them to you?

Dave

@bbelius said:

Please create a process mini-dump of the host after the issue appears (host the Synchron Player in Cubase and create the dump from the Cubase.exe process), please see the following image on how to create a minidump with process explorer:
https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Send us the dump to support@vsl.co.at
Hopefully this will help in the investigation.

Many Thanks!

Thanks Christopher, I will look into it.
@Dave you can use something like wetransfer.

Ok Ben,

I sent you 2 mini dumps using we transfer. That was for the using Synchron VST3 plugins hosted in Cubase.

Today I also had drop outs (red hard drive flashing) using VST2 plugins hosted in Cubase. So I am sending you 2 more mini dumps called, Cubase10a_VST2.dmp and Cubase10b_VST2.dmp

Dave

I have an update: it seems that this issue occurs most often when soloing one track only.
If I open the key editor for one single track and solo it, then dropouts occur, but if I un-solo it, no longer dropouts occur, at least in this simple test I am doing today