Great, used on a session today and all worked great. Looking forward to the HD files timecode/position sync issue (VST Connect Pro) being resolved soon.
I just updated my Pro version to 4.0.42. And the same on my Laptop (Performer). It shows āPublic Betaā ?!?
Next thing: it tried to connect within my local network, wich worked well with 4.0.40 but now i get an error: āSorry you can not connect within your local network. Make sure both sides use the same and up-to-date version!ā
Thats nonsense! I have on both sides se same version. But it does not work.
Looks like a bug.
And now i can not go back to 4.0.40, cause there is no 4.0.40 on the download page. Only an old 3 version.
Strictly speaking ā4.0.42ā is a public beta although itās also the latest (and most stable!) release. Much better than 4.0.40 IMO so stick with it
Iāve also had issues with testing via the local network with more recent version. Installed on 3 different PCs and 4 different pc/mac LAN clients. Fresh install works fine but some installs work over then LAN on cubase 10.5 but not 10 but is ok on nuendo 10 ā¦another install works on 10 but not 10.5 !! ā¦feels totally random ? ? So itās not network specific issues (or windows firewall before anybody points that out !)
This leads me to believe itās something in the cubase preferences - as VST connect pro (NOT PERFORMER) saves itās preferences in the cubase project/setup.
IF you REALLY want to get it working over the LAN then you could try deleting all your cubase preferences (painful I know ) and all your VST connect Performer preferencesā¦try it then
On the other hand I donāt find LAN connections at all useful - apart from testing.
The compromises you have when working with VST connect pro over a LAN seem to outweigh any possible advantage for not having to run a longer mic/headphone cableā¦and Iām a massive VST connect pro fan and use it all the time !!! YMMV
Iām struggling to think of any useful āreal worldā LAN use application ?
well the in app description says āpublic betaā and the version is IDENTICAL to the āpublic betaā that was released a couple of weeks agoā¦it hasnāt gone through all the full regression testing of the other releases. It hasnāt got the full catalina notarisation like final releasesā¦
Yes thatās what I want. Itās a good idea to test on LAN for to learn all funktions. If you have a recording session and a performer with no experiences with VSTConnect, it is important to know exactly how it works. You can not do testings with a client.
Yes, that was my work around totday. But then the next problem appeared: the Performer can not open my audiodivice (UA25). It works perfectly with WaveLab and all the others but not with performer. . And when I had a recording session a few days ago, Connect Pro crashed 2 times and cilled my Cubase. So I thing this version is realy buggy!
I just purchased Connect PRO 4.0.42, downloaded and installed. Does not show up anywhere! VST cloud still says Connect Se only. Have uninstalled and re-installed a few times. Nothing. Suggestions? Running win 10, Cubase 10.5 latest version
My version of CB said SE also but when I downloaded the 4.0.42 update, it was labeled VST Connect SE/Pro so I thought SE and Pro were one in the same? The other version is Performer and 4.0.42 isnāt compatible with that.
Someone else may want to chime in on that?
@saxguru, thank you for your purchase! I have checked the database and VST Connect Pro does not show up because the activation code you received with the order hasnāt been used yet. Please activate the license using the eLicenser Control Center and your USB-eLicenser.
Well,l whadaya know.!!! Thanks Ed.!(I must have cancelled the action instead of ācontinueā . Trying to work too fast instead of actually reading), the buttons)
And thanks for the quick reply!!! Awesome!
When I tried to record an audio track (Vst-Instrument) and the corresponding midi track Cubase crashed. That happend two times. Where can I find the .dump file?