The test here is to determine if Cubase and VST Connect Pro is failing at its audio paths or at least see a symptom of it failing
Try this: Load up Cubase 7.5 or 8.05 and VST Pro Template.
Create an Audio Input Channel via VST Connections and name it TB/Performer (if you want or use an existing audio input channel. In the Mix Console Insert VST Connection Pro.
Now create a group track and then delete it. Do this several times if you want, but the end goal is to see if the groups you’ve deleted are still in the list and select-able.
The list I’m referring to is in the project window/inspector where you can set the out of any audio track. If the deleted groups still show up, VST Connect Pro is hosing the internal signal path.
The above is the simplest way to see a symptom of internal connect fail.
And that is why it won’t work and you may even get varying results. i…e remove the VST Connection Inserts and then put them back in to see whats changers is ability… if its as my experience, what part I had working Stopped working.
The idea is to have a group track that you can send whatever tracks you want to the remote or LAN performer summed into this group track. But VST Connection Pro is hosing the connections internally, so this won’t work, its broke.
You can also try in VST Connections to set the audio input channel the VST Connection Pro is inserted into, to an audio signal you know is working, this bypasses or forks the audio signal and sends it to the “to performer” (or whatever track you have VST Connection Cue Mix inserted into and have routing set from TB/Performer.) The remote performer should hear this (assuming you have other things set- like volume to performer in the VST Connection online interface), but its limited to one or two audio signals.
My experience is VST Connect Pro simply does not work in Cubase 7.5 or 8.05 because the signal paths are getting internally hosed.
if interested see the thread of mine “draw me a path/map of connections” and start reading from teh last message backward. there are some images in some of my later posts.
I was getting varying results, unstable… but finally stabilized when I nailed the problem. I can repeat the problem in both CB7.5 & 8.05
Documentation is not Steinberg’s strong suit. This is a typical problem of Software Developers. As such I suspect if they focused on Documentation in the development process it would force them to discover more bugs in development but would also result in release dates between releases to be longer. Maybe such delay would be only until they get the documentation up to speed and integrated into the development process. I don’t know their internal development processes, but pushing for release dates often sacrifice … documentation. I do wonder about test suites they are running the software components through to expose bugs in the development process. Developing test suites is easier than the software its testing and though its can really make a difference… pushing for release dates… argh…sacrifice. Don’t have time to do the things that will save time? It has crossed my mind, does the Steinberg Development team lack a dedicated Documentation position that interacts with the development team, possibly having the side effect of bug exposure? Or maybe its all about finding someone to pay to teach your how to use the software and that would not be so uncommon with complex software. As many times as others have commented regarding difficulty with following my communications…I would probably do a better job with Documentation if I worked in such a position. I do believe I nailed the VST Connection Pro problem as best anyone can from a user POV. And It was very frustrating… duie sparce documentation.