Have you tried using a MIDI loopback app as an output from VSTL?
It may not meet your sonic needs but the free TAL vocoder has an onboard carrier so you wouldn’t need a sidechain input.
Have you tried using a MIDI loopback app as an output from VSTL?
It may not meet your sonic needs but the free TAL vocoder has an onboard carrier so you wouldn’t need a sidechain input.
Does VST Live 3 allow a layer to have (listen and respond to) multiple MIDI inputs (for example, a keyboard, an expression pedal and an external set of faders programmed to send various MIDI CC’s?
There’s a number of ways to achieve that:
Assign all your inputs to the same Virtual MIDI port and use that as your Layer input.
Use a number of Shared Layers to make a number of inputs target the same instrument.
Use wireless MIDI (CME WiDi, others solutions are available) to merge the signals before they reach VSTL.
Use a hardware merge solution.
Daisy chain your controllers with MIDI thru’ before connection to the PC.
I’m sure others will chime in with how they do it. If you already have a working solution in v2 it’ll work in v3.
Hi @Gregor_Torrence and @Carl0828,
Thanks for checking in.
Audio side-chaining is still on our feature list, but it has not been implemented yet. At this point, I’m not able to give a timeline.
We’re aware that this is an important request for some workflows, and the continued feedback is noted.
See you,
Michael.
Hello @bruno_ciaccafava
We will continue to address bugs in VST Live 2 through pre-release updates. Once a pre-release is considered stable enough, it will be made available as a public release via the Steinberg Download Assistant.
We understand the expectation that issues in an existing major version should be resolved, and user feedback plays an important role in that process. If you encounter specific bugs, please feel free to open separate forum threads so we can track and address them more effectively.
Thank you,
Michael.
Hello
I don’t know why I receive a personal mail about a post made in a public forum…
I still think that is it a bad message to release a new paid version while the previous one still have no public release with bugs corrections. About bugs, I think that there are still some that are not completely corrected, and still appears in v3, so I’m not talking about “new” ones, but about the existing ones.
I’m not convinced enough in the release/debug process to pay a for a V3. Sorry, as a already told, I’m done with beta testing.
Thank you.
Wohooo, super!!
Do Live Mods for iOS works with VST Live 3? Is the mismatch for metronome fixed or do we still need to wait for new iOS App ?
.. we still need to solve that one. Sorry,
Michael.
I do wish you’d do some decent, in depth videos. Never were any for V2, (laughingly the start of video tutorials from years ago is still pinned here, but it never followed through) and the introductory features video for V3 at the top of the product page is simply bookmarked further down for each new feature. Pretty poor really when you look at the resources available for Dorico for example.
I will do my best in 2026! Just give me a bit of rest
Hi! What specifications should my PC have for VstLive 3?
Te app doesnt need power at all, you could technically run it - with backing tracks - on a 15yrs CoreDuo PC. Tell you how much power you actually need only depends what you want to do with….
Thanks @fkalmus ! But if it’s all on you then it sounds like Steinberg aren’t putting enough resources behind VSTL…
no, it’s not about…
btw: what were you missing… I mean… what should a new tutorial talk about?
Well the software is not that complex, say compared to Dorico or Nuendo, but I think the lack of general setup videos, case studies, how I do this or that is quite glaring. All the other software I use, from those mentioned above, to Da Vinci Resolve, or Affinity Designer etc have a wealth of videos online, from the actual developers and from power users too. VSTL Live Tutorial was publish in November 2023, and since then virtually nothing. Some of us are visual learners not manual readers! I find it hard to read manuals but do so of course, but if I can find a video online when I want to learn a new facet of the software, that is preferable.
The announcement of the new features in VSTL3 re-kindled my interest in an app that I’m afraid I’ve given up on for many reasons - reliability being the main one - still can’t get ArtNet working. I just did a 4 hour show 2 nights at a Casino, using Studio One Show Page running live inputs and sending DMX prog changes to an interface. Several patches per song switched by an FBV MKII pedal. The 2015 stage Macbook running Monterey was on from 5pm soundcheck until 1.30 in the morning with the programme loaded. Not a glitch - I’d already sink tested it at home for several days so was confident. At this moment I cannot imagine trying that with VSTL, not least because every update seems to bring surprises (I do check in here from time to time and read the issues). Notwithstanding Studio One’s Show page being abandonware for the time being, it is absolutely rock solid. And no glitches between patch changes. I’d like to think that VSTL3 could replace it - I need live camera inputs, and multiple video tracks (none in Studio One Show) but I’ll wait until there’s a demo before I spend any more time on VSTL, and before I spend money on an upgrade.
Sorry, but this is a standard reply to any new version of any software of any company.
We are continuously improving and fixing issues in all versions. In fact, some bugs have been fixed for all (incl. prior) versions along the way when adding features, because developing those often require to look closer into the resp. area anyway.
We offer long version download history and easy rollback, as well as pre-release versions. This has been received positively by the vast majority here, if it were any different, we’d gladly omit this additional workload which is intented to give you the choice of checking which versions work best for you, and providing fixes quickly.
The notion that developing new versions prevents fixing bugs (all soft have some) is thus not only unfair, but plain wrong. Quite the opposite, we fix bugs faster than others and often provide those fixes almost immediately. Yes, some tasks are overdue, but stability always comes first.
As mentioned several times, it is a good recommendation to only use software on stage that you have tested thoroughly beforehand. We have 30 pages of praises and detailed reports from users describing successful and glitch-free performances with VST Live, large and small. We follow every crash dump/reports, stability is always prio 1. Just let us know what your problems are.
Sorry can’t look up all posts, ArtNet really works everywhere in many installations. What is your problem, which ArtNet interface and network configuration?
How do you have glitches with VST Live?
I hate to say it, but it sours my stomach to hear that I have to pay more to upgrade from a broken product to another broken product. It’s like I paid to be a beta tester.
Im still on an older build of 2 because it’s at least mostly stable. The video player doesn’t work correctly though. (MIDI is broken as I’ve shown on video in the past)
I’ve been watching the weekly updates and it’s a case of fixing one thing and breaking several others.
I just wanted to give my feedback and opinion. I guess I’m gonna go ahead and migrate to live 12 that is stable and works solid, which is the whole point of you guys making vst live in the first place.
Thanks for everything folks. Merry Christmas.
Jeremy
It’s not traditional to have to try 100 versions of a software to see which one doesn’t crash in your workflow. I appreciate the weekly updates, but it’s a lot of extra work trying to make vst live 2 do two things at the same time, those 2 things imo are running completely stable AND all the features working correctly.
I send midi to start and stop the media player. It’s broken. Specifically if I send a midi command from the track or through the midi jack, it only works correctly AFTER going into the media player and clicking play and stop with the mouse first. Again, I posted a video months ago showing this.