I just had my first session with a client which in principle run fine.
Then I wanted to get the HD files from him and the program started to download a couple of the recordings and then stopped downloading all the other takes from several performer tracks I created within that session.
So it somehow was not able to get all the files downloaded to my Cubase project.
Then I asked the client to send me his local recording manually via google drive and when I just had a look inside I recognized that the recordings are all corrupted. I can’t open them with any wav-file player nor with Cubase itself.
Does anybody know a solution for this?
I bought the Pro-Version and I also have the issue when I’m doing vocal takes locally from a second PC. One month ago it was recording it properly and I think since 2 weeks it behaves like this.
How did you get the files from the Performer? There is a dedicated action in Performer “Export for Get Local HD”, you should use that. If that doesn’t work, the files are really corrupted because of external reasons (we never had that).
We recommend to use “lossless” for audio upstream on the Performer side, nowadays network connections should do that w/o problems. You don’t need “Get HD Files” then anymore, it will not improve audio quality.
thanks for your response. He zipped the files manually from the HD folder location. But I also tested it locally today by using the “Export for Get Local HD”-Button on my second PC and the files inside are also corrupted.
What external reasons could cause such a strange behavior? As I wrote, it was working when I got the Pro-Version one month ago for my first local trials and then ~ 2 weeks ago it suddenly stopped working.
I’ll also try to setup the lossless for the next session and see if that helps. I wanted to avoid this, because I’m in Germany and he is from the US.
Well, file corruption can happen for various reasons. Just wanted to point out that we never had reports that VST Connect would not record properly or otherwise cause file corruption. You may send a short file per PM for us to examine, maybe we can find something.
It doesn’t matter where either party resides, only the connection bandwidth matters for that. In 2026, it should pretty much always be sufficient for that. It has no impact on timing etc; to assure proper recording, with long distances, you may increase the remote latency value which gives the system time to stream.
Hello there. Just want everybody know that when I import the corrupted files into Cubase 15, it’s working fine. The question is, why it doesn’t work in other audio editors like Wavelab 12. When I import the files into Audacity as RAW and choose stereo instead of the default mono, it’s also showing a meaningful waveform.
Based on the error messages I receive e.g. in Wavelab 12, I think it might somehow be related to security settings or admin mode. If someone happen to know an answer to this question, I would appreciate if you could answer to this post.
Hello Paddy,
Your approach with the WAV files is interesting.
I suspect that the audio files you received from your performer are not WAV files, but internal recording formats from VST Connect or Cubase. They are essentially RAW files for temporary storage, which is why they can be read by Cubase.
Perhaps someone can confirm this?
They are entirely regular Wave files. They contain a broadcast chunk for timing information which enables you to put them into Cubase at the project time they were recorded, this is entirely conforming to the WAVE file specification.
No idea why WaveLab should complain (maybe an old version?), every other player accepts it w/o problems.
