While I appreciate that the VST Live team moves fast on updates and bugfixes, there’s a lot of undocumented features/options in VST Live that are not included in the current manual v.2.0.0.
I’ve managed to find answers to someof the “mystery” options (from my point of view) in this forum. This is of course a testament to the activity in this community, but I can’t always find definitive answers - or sometime no answers at all.
Here’s a couple of examples (in no particular order):
How does “Compensate selected Track” work?
What does “Keep Channels Active” do?
What does “Controller Tracking” do?
What is the workings of “Chase Events” in relation to “Chase Events on Start”?
What is the purpose of “Action Value” under Song Actions? (this one I found in the forum)
Also, sometimes the naming of options could be a bit more self-explanatory.
“Reset Controllers” could be “Reset Controllers on Stop/Locate”
“Locate last Start” could be “Locate last Start Position on Stop”
VST Live 2 has no “Auto delay compensation” engine. That means if a Plug-In reports a needed delay the audio engine does not react to it. But with the action “Compensate selected Track” you can tell the engine to re-calculate the needed latency for a selected track.
Channels of a global part will not be paused while switching song.
If that Preference is enabled, VST Live will take care that identical controller events will not be sent multiple times to the MIDI output Ports.
Chase Events → Chase Events While locating
Chase Event on Start → Chase Events on Start
Chase Events + Chase Event on Start → Chase Events on Start
The Song Actions Configuration (Menu / Song / Song Actions…) has an entry called “Action Value”.
I see that you often make a post with explanoty statements on new releases.
Might I suggest that you create an online Pre-Release manual, so all comments and descriptions from the VL team is easily accessible?
I totally agree with you. We rely heavily on manuals, especially when there are no detailed tutorial videos, etc. , to guide us new users. The issues you have raised having been lingering in my head as well. So UPDATED manual will help, though VSTL weekly updates still have some areas for improvement - some of the errors noted in previous updates still remain unresolved. So, more TESTING TIME should be dedicated before an update is released!!!
Sometimes it takes some more time to get a bug resolved. But I am very sorry if we’ve missed an issue. If you have that feeling, please create a new thread entry and tell us about it. Or push a thread to the top of the forum to keep us informed.
That’s the idea. An Official Release will only be pushed from time to time to the “Steinberg Download Assistant”. Between those Releases we decided to keep you in the loop with Pre-Releases - every Friday.
This is 1st error:
Hi, my excitement about this export audio function has just died down - because it is not working properly - it exports only one track (piano in my case, out of 8 or so tracks per song) - the same track is being copied in the two songs it was tested on. I wish it could allow flexibility to identify one or more tracks to export - not necessarily the whole mix - this would allow me to edit the individual keyboard tracks I recorded on VSTL.
2nd error:
On the Add Bars function - it works half-way: it correctly adds the specified number of bars at the indicated bar position. However, it lacks in two respects: (a) It does not add the specified time signature change (e.g. 4/4 to 3/4, etc), though a workaround to this is to add the time signature track and change it from there; (b) The “Process” button does not illuminate to show if it is selectable/selected, though it works - also, after processing there is no button/msg that pops up to say process is finished and the Add Bar window can now be closed: these, though, are just cosmetic proposed enhancements.
Hi, I was just testing the following (quoted from Spork on your new release news): ** *Bypass Layer and Stack * And it’s now possible to bypass a Stack or a Layer. Those controls are also part of the Actions now.
So that blue button at the right upper corner of the layer window crashes my setlist/VSTL. However, it does not crash the system if I click on a new empty song with just one layer created. On my side it is not crucial, as I don’t even understand it yet. I don’t even know where the crash dump file is located. So lets wait for others to raise the issue.
Can you please check the following paths.
Win : C:\Users\YourUsername\Documents\Steinberg\CrashDumps
Mac : /Users/Username/Library/Logs/DiagnosticReports
Do you see any vstlive* files? Can you drop them here?
Thank you gentlemen for your continued support!!
Hi Spork:
After following the procedure you outlined, I have discovered the following:
(1) The Export Audio function works well - it is able to export the two tracks I have just created into a single mixdown.
(2) However, when re-applying the same function (using the very latest VSTL update) on my current song setlist (each song has about 12 tracks), and on the currently open song, it still does not work - still exports only the piano track. I even saved the song and loaded it on its own; the same problem recurs.
(3) There is something new that I have discovered, as well, when following your procedure - I could select the two tracks at the same time (Shift-key, then mouse clicking on each track). This has the potential of applying one function at the same time on the selected tracks - e.g. delete, copy (delete has worked), etc. However, this new functionality (selecting several tracks simultaneously) does not happen to my current song setlist, and not even on the single song I loaded. How so???
One little thing I have just discovered about selecting many tracks (from my 12-track song/s) is that only non-audio tracks are being selected together.
