Things were going so well, until a week ago…
Cubase has started crashing randomly, usually when editing but VST Connect is now crashing Cubase so frequently it’s unusable. Every time I try to download the HD files using the manager function Cubase crashes completely, with no warnings or Cubase crash dump being produced. This is 100% repeatable. Windows Event Viewer cites VSTConnect3 as the crashed module.
What I’ve done so far, to no effect:-
Windows 10 fully updated
Checked the Windows installation using SFC and DISM. No errors.
Completely removed Cubase 10.5 and VST Connect and re-installed, latest versions.
Run hardware tests on disks memory and graphics. All good.
Question 1: What to try next?
Worst of all is that I have downloaded the recorded audio files from the remote performer m/c using Teamviewer. However I can’t get them into the project via VST Connect because it immediately crashes Cubase (see above). I have tried reading them via Soundforge and they appear to be corrupt and unusable. I’m worried that this has been a whole session wasted. It’s now happened twice with the same guy…
Point worthy of note: I downloaded the directory from the remote machine that carried the project name we had been working on. However in that (huge) directory were many audio files (some readable, some not) that were from other projects.
I have run a test session from another laptop on my LAN running Performer into an otherwise empty project on the studio machine and the recorded wav files on the laptop are also seen as corrupt by Soundforge, but I am able to import them OK into the main machine project using VST Connect.
Question 2: Can I recover the wav files I downloaded from the remote machine on the real session? I was intending to extract them and import them to the project as normal wavs with VST Connect removed from the project. Is there some sort of decoding required?