I have owned VSTL version 1.5 and version 2 for a long time, both legally purchased and properly licensed/activated.
I recently downloaded version 3 and noticed that it appears to be a new product, and my existing licenses are not valid for VSTL3.
I’d like to understand: is it normal that previous licenses are not compatible with VSTL3, or am I facing an issue on my side?
Thanks in advance for your help.
VL3 is a new product, like Cubase13 vs C14, C15… needs their own license
New beta for us to test at our expense
3 Likes
The company announced here, there will be Trial version for it soon (they havent announced date)
Cubase at least works without needing a weekly update that fixes one thing and breaks 2 others. Never have I ever felt like a beta tester with Cubase. With vst live I feel like an alpha tester.
3 Likes
Wouldn’t say that. And dont forget, the weekly updates brought a huge amount of user requests (needless to mention the endless pression for multi-process for example) and other very complex and time-consuming features and they just arrived with simple updates.
2 Likes
It would be very nice if Cubase developers remember about users more often than a quarter of year 
BTW, you don’t have to update VST Live weekly. You can use first version you bought and you are just eligible to update your version until support ends (for the price you leave in one night at the bar). And that’s fine for many of us.
Last year I asked team when the next version will come out. Just to be able to support them more. Can you feel the difference between you and other users here?
If you bought this software, tested and felt that it’s not for you, then it’s not for you. That simple! Watch the videos on YouTube where VST Live users perform their gigs. They update every week or skip some. We went through all updates since very first version. And look - we are still alive. Because this software is for us. Are you in or out?
3 Likes
Thank you very much, Felician, for the appreciated reply.
What can I say… it’s a shame, I’m really attached to this software and I genuinely love it. As Arthur says, I’m one of those who is in, one of those who has been part of it for years.
I wanted to ask: for those of us who already own V2, is there any special pricing or discount available for upgrading to V3?
Thanks again for your support!
Of course there is! Only 40 euros if you already have Pro! It’s cheaper than cheapest V.S.O.P.
Open Steinberg page, select VST Live, click “Buy VST Live Pro 3”, then choose upgrade from V2.
2 Likes
If I purchase version 3 and install it on macOS, can I move the license for version 2 to Windows 11?
This way I would have two working VST environments, using the second one for VSTs that are not compatible with macOS.
You can use 3 computers / valid license 
Means can activate VL2 on 3 computers
Can activate VL3 on even different ones (but that would probably be a nonsense 
)
So no worries, BUT on “old” computer, I would deactivate (no-needed) licenses first
I LOVE the software. But it crashes, OR in my case right now, I’m using 2.2.52 that doesn’t crash, but also doesn’t work for video the way it’s supposed to, IE my track midi should start or stop my default video in between songs. It’s hard to try out another version over and over because we need it to be STABLE first and foremost. This seems to be in development Alpha/beta stage
And looking at the latest posts, it’s still an issue for some in version 3.
1 Like
Hi! Please describe your problem more.
- What OS you use (win/mac)?
- Do you have crash dump to upload maybe?
Etc
You need to specify a bit more. Developers fix crashes in top prio
Mac mini m1. I’ve uploaded videos of my issues and of the crashes, as well as crash logs. They did fix a couple things, but as I said, future updates broke them.
My midi issue is simple. I have a video that is supposed to play and stop with a midi command in the global media player. The reason is when my song starts, it stops the global video and starts the local video in the tracks. When my song ends it sends a midi command to Start the global video.
But the only way this works is for me to manually select the global media player and click play and stop with the mouse, THEN the midi will work. If I don’t do that, the midi falls on “deaf ears”.
Perfect
Hmmm. I think we started to talk about in another thread.
So just for cleaning:
-
No crashes any more that you reported and uploaded crashdump (or)?
-
you current problem is regarding GlobalMediaPlayer start/stop between song end/starts right?
Correct, but I’m on an old version. I’ll test the latest 2 release and report back (but I had same issue across many releases and most had crashes)
Ok, they let’s stay practical. A new “friday” version (VL2 & VL3) expected in the evening. You might download todays version and report if something is still not fixed (exept MediaPlayer questions, where we need to find the reproducable receipe first).
You can rename your current version (App) to e.g VST Live 2.2.0 (it will run renamed w.o. any problem) and while downloading the todays version you can rename it to actual. Then you can “switch” freely which to open
1 Like
great info. I didn’t know I could do that and didn’t want to mess up what has been working mostly stable.
I will test tomorrows version, But i tested 2.2.94 and it’s even worse than 2.2.52. In 2.2.94 the video in the global player no longer fades in and out when starting and stopping as my settings are set to have and when it’s paused, doesn’t FADE OUT, which it does on 2.2.52. The main issue with 2.2.52 is that the global media player will not respond to midi unless you specifically go into the global module, then onto the video window with the global overlay and press play and then pause. After that, midi will work.
All I want to do is to load up vstl2, and then press my button on foot controller that starts my global video. When I start a song (I only use tracks), The global video midi track fires off the same midi message which pauses the global video (it fades to black) and the video in the song tracks plays on the same monitor. At the end of the song, the midi track fires a signal to restart the global video, which starts at the top and fades in.
in 2.2.94 the track videos dont even play at all. Same project plays in 2.2.52??
Just Quick: for now forget v2.2.94. There is a new video-renderer-engine after
Public Release 2.2.90. So for now, if you experience video problems, save 2.2.90.
And also can try later if there will be a new release today, or thesed days.
And let’s get back to GlobalMediaPlayer in the weekend, because I have problems with too (something must be wrong there @musicullum , because e.g. on my system: RTZ QC fires 4 different actions(/states) (StopActivePlay/ON/OFF/OnOff that must be a bug) and as RTZ/GoTo1,GoTo2 buttons are stopping activePLAY first, instead of directly doing their job, it’s “hard(near-impossible)” to set the right MIDI messages controlling MediaPlayer QC’s , but we @trixdropd need to narrow and focus what to exactly report to developers. Step-by-Step.
1 Like
One problem is that the player refuses to apply stop/locate actions when it has fade in/out. We’ll change that so it reacts immediately. Also the fade sliders are not correctly shown initially, will also be fixed, so pls try again next version.
1 Like