It’s Friday again - and yes, two new builds (3.0.18 / 2.2.98) are ready. They focus once more on a set of bug fixes.
You can download them here.
Version history is here.
Have a nice weekend,
Michael
9 Likes
Can’t make Video Director Monitor to show PGM
//off
and @Spork I’m sorry for asking such… wanted to ask from the very beginning, is there a purpose of the YELLOW-border around the selected SRC? Anywhere I see in the industry a RED-border is used for selected SRC (that goes to “PGM” program) (OBS multi-view, Blackmagic equps, TV broadcast, …). Or it’s for the very purpose to distinguish VL’s “being-recorded-objects”?
//on
Hi guys,
I am testing 3.0.18 and while one of the previous issues was resolved, unfortunately even basic editing in the tracks window keeps being very buggy.
Issue 1:
Waveforms just disappear depending on Zoom level
These overlapping tracks (middle and bottom) are the same WAV on different tracks, because simple crossfades don’t work on the same track.
However in this example the middle one is randomly not showing the wave form, which makes precise editing impossible.
Issue 2:
I can’t move selected samples properly.
The bottom track with the kickdrum sample should be one bar to the right, but no matter how often I drag it, it doesn’t move anymore.
I write “anymore”, because it was possible to move it - until it suddenly wasn’t.
The way to resolve most of these issues, is often by selecting a different song in the setlist and then re-selecting the song where “nothing worked”. Then usually the action is possible.
Issue 3:
When I select all the kickdrum samples and change the length of the sample, only the sample that I am dragging gets changed. ALL others don’t change.
This is on Win 11 (newest update), VST Live 3.0.18.
Have a good weekend!
3 Likes
1 Like
Maybe tomorrow or Monday, I am on my way out now.
I don’t understand, why the one issue is fixed, and the next one is implemented. Do you not check your new versions before releasing? When will it happen to get a version with full functionality? We payed the full price for it, but get the half performance. The Video-Director-Monitor was THE ONE killer-feature why I bought the new VST Live 3. Two months later it doesn’t still work. I’m planning live shows for my band, and want to be able to use this feature. Wouldn’t it feel fair, if I’d say: “Please give me what I’ve payed for!”?
5 Likes
If all users started demanding the same, instead of trying to persuade them, maybe something would change in the developers’ approach.
But I completely agree with your statement!
1 Like
It’s strange, @sergeantt67 and @tunecreators, in this version the video feature works like a charm for me. The question I would ask is - what software did you use to make your videos? I’m almost sure that the problem could be a format of video and there are lot of parameters that, if misunderstood, can make whole playback different than expected.
Guys, I would like you to pay attention to the written words:
But in case you don’t like bugs and reporting them and don’t like to be a part of this very friendly community, you use Steinberg Download Manager to download the version you bought.
And, if you notice a bug in release version, you have two options - a) report it and wait for next release or b) report it and install the pre-release version to check how it was fixed and start talking to the developers to get the best result in the end.
Saying that developers should do this and that sounds like you have a million bucks and want to hire them so they work with you on your terms 
2 Likes
It’s a very good point that this is a perpetual pre-release. Can you give an example of at least one stable version without bugs? Version 2 is still far from perfect. I’m not talking about version 3, because I haven’t purchased it and don’t plan to.
Regarding the community, you, ArthurNeeman and fkalmus, are not the entire community, and you don’t need to impose your point of view on us. Especially since you’re both affiliated with Steinberg, one advertises their product, and the other is a beta tester, so any of your statements are not objective.
And we’re right to ask questions, and mind you, not you! But the developers.
Why doesn’t even version 2 of what’s stated in the official release work?
And the million-dollar claim and the idea that we need to hire someone are just some sick fantasy of yours. You made me laugh heartily.
3 Likes
Khm, I wouldn’t say it was nice from you…
It’s hard to see how this bickering has any positive effect on VSTL, more likely the contrary.
To slag off the beta testers is just daft - of course they’re objective.
Afaik any “affiliation” is on a voluntary basis based on a belief in VSTL and a desire to help improve it.
I don’t see anybody trying to impose a view, more to give advice born of experience. Of course you can decide to take advice or leave it, your prerogative. My advice to you would be to wind your neck in a bit and try to understand that people here are trying to help, and that if you upset them enough they just won’t be here anymore, for you or anybody else.
You can always tag the devs in if you want their direct attention but that would possibly detract from their labours trying to fix the very issues you have raised.
Sergey (@sergeantt67), please put one word in your signature - the region you are from and everyone will understand your rudeness and aggressivity.
Being beta tester allows me to be closer to the kitchen and if it feels like I’m affiliated, it’s an honor. Thank you!
Keep doing music, not war!
4 Likes
Always been ok, until last weeks update
mp4-files made with iPhone 13 works fine, but mp4 files made with Microsoft Clipchamp have the green bar. Trying to import MOV-files made with iPhone 7 VL crashes.
The version I bought promised a working video director monitor. There was nothing to read about it has to be developed and delivered in the future. And in the normal case there is no need to reinstall an older version, especially because this version also doesn‘t deliver the functionality it should to.
How did it feel to buy a car that promises an engine with 500 PS, and after buying they‘d say: „Oh, sorry, this function isn‘t still implemented, but we’ll deliver it in the future!“??! Than the upgrade comes: „Yeah! Now it has 500 PS!“ And therfore the breaks loose there functionality. Would this be an acceptable deal? Would you also say: „If you want to have working breaks, please reinstall the version you bought, without this 500 PS-engine!“? I can‘t imagine.
Its really simple: We paid for a service that we didn‘t receive. It‘s got nothing to do with being unfriendly. It‘s just about this guiding principle of market-economy. Pay for a product - Get the product you’ve paid for. Thats it.
4 Likes
Hi,
please : let’s keep this discussion constructive. We understand the concerns being raised, and we are doing our best to improve the software and resolve issues. Step by step.
If anybody is unhappy and would like to discuss this further, please write me directly at
m.spork (at) steinberg.de.
See you,
Michael
1 Like