Version 3.0.22 is having the same problems as version 3.0.21, it is not playing all tracks in some songs. I’ve had to revert back to 3.0.19 again and it works fine. This was reported when 3.0.21 came out.
As you can see in the screen recording below the song is playing but no sound coming from the song, observe the mixer at the bottom of the screen recording.
I assume, that you have the same problem as some other. If the sample rate of your audio files are not the same as the project, there is a chance, that they wont play. One possible solution is to convert this files.
I checked the sample rate of all my audio files used in the project and did find some that were at 41k instead of 48k. I converted the strays to 48k and everything works just fine. I assume something changed from version 3.0.19 to 3.0.20??
Yes, they changed something in the “on the fly” conversion of sample rate with 3.0.20, as the previous solutions did some audio artifacts when the audiofile contains quiet parts. This leads to other problems. But I’m sure this will be solved soon. 3.0.21 has solved some, but not all issues.
We can play 44.1 kHz files in a project/hardware rate of 48k just fine (and vice versa) with v 3.0.22. Could you send us an audio file not playing at any one sample rate? Thanks!
The files I was having problems with were from songs that have been in my project for a time. I seem to remember switch my audio hardware over to 44.1k for a short period of time because of Project I was working on the Cubase. That is probably when I created these few songs in VST. Nevertheless, I’ve manually converted the songs to 48k, so I don’t have them to send.
I’ve been experiencing serious issues with VST Live 3.0.23. There are major inconsistencies with the tracks — some that worked perfectly in previous updates are now not functioning at all. At times, everything works as expected, but after a while certain tracks suddenly stop working again.
This instability makes the software unreliable for live performance, and I cannot risk using it in a show with these ongoing bugs.
Has anyone else experienced this? Is there a known fix or workaround? I would greatly appreciate any help resolving this issue.