The thing is when 1.5.1 is released to the Plus and Free levels there is likely going to be a wave of new reports so it’s probably not going to be the final version.
So to hold back the release until it’s “perfect” is probably a futile move.
2 Likes
Sort of agree. But the wide masses would start reporting about the same issues again and again.
I assume there will be new issues not yet reported by the Pro and Subscription level user base simply because the testing group size has doubled or at least gotten larger by some percentage.
It’s not uncommon for a plugin to go through rigorous private beta testing and yet once released to the general public some issue that slipped through is reported.
Public beta testing by a large user base is not unheard of. IK Multimedia does it whether they intend to or not every time they release a new plugin.
At any rate I’m just saying to think that 1.5.1 is a final release is probably a bit optimistic since as I say a much larger group of people will be getting their hands on it at some point.
It’s not a knock on any developer, it happens to the best of them. It’s just the nature of software. There are just so many different system configurations and use cases that it’s nearly impossible to cover them all. Especially for a plugin that has Windows, Linux, CLAP, and M1/Non M1 Mac versions.
3 Likes
Just stumbled upon a strange bug, in Ableton, setting a custom tuning in Vital works fine, yet if I save the project and reload it, the tuning is reverted back to default, and keeps reliably doing it every time.
Also, back to the previous bug I mentioned, now the Macros get displayed correctly in the automation lanes, and this is great, yet, in projects done with previous versions of Vital, they seem to be assigned to a bunch of LFO parameters or otherwise messed up… now, I really have no idea how that happened, but it is kind of an inconvenience, I have the rendered audio of almost everything, yet well, the idea that I can’t go and edit it without having to do through the tedious work of getting everything where it belonged is kinda discouraging.
Why does Mr. Tytel not offer a Vital v.1.5.1 Demo like other companies ?
This way users could test if this version works with their OS and DAW.
And if it works they can buy the Pro pack.
I understand that Mr. Tytel wants money for his work, that’s o.k.
Hmm? Vital is free!! Not like other companies at all. The reason you don’t get 1.5.1 as of yet is simply because there are still bugs to fix etc. That is exactly why it is called a beta pre-release. Putting it out in this state for everyone will generate a massive amount of support/bugfix requests, that will slow down developement and probably frustrate many users and Matt as well.
Also, what in particular do you need from 1.5.1 that 1.0.8 does not offer?
1 Like
In my case I did the mistake of making presets for the 1.5.1 version thinking I would be able to sell them in July.
Still waiting.
I definetly won’t do that for the next beta.
I understand it must be quite a job to fix all the bugs and make everything alright, I just won,t proceed that way next time. But maybe others are looking forward for similar reasons.
1 Like
Vital is not free. There is a free level. The people who paid the most, the Pro and Subscription level customers are the ones who have access to 1.5.1 now. They are being rewarded for their support by gaining access before the Plus customers and Free version users.
The point is if there are bugs that slip past the Pro and Sub users then the rest of the user base will likely find them whether it is released today or two months from now. If there are no bugs that slip past then there will be no “massive amount of support/bugfix requests”.
You said it yourself. Fixes for bugs and issues present in 1.0.8 and new features and functions.
That’s the whole purpose of a new version…to improve on the old version.
If Vital v.1.5.1 wil be released for free or to plus users when there are no more bugs then it will never be released for free because there will always be more or less bugs in such a complex software !!!
As mentioned before a v.1.5.1 Demo would be very helpfull.
A commenter asks what might I need in v. 1.5.1. that v. 1.0.7 doesn’t already provide. If you are a Mac user then 1.5.1. provides native support for Apple silicon. That is HUGE! It has been (more than) two years since developers were given the tools for incorporating Apple silicon programming. At this point (OS 11, Big Sur and OS 12, Monterey are largely in the past while OS 13, Ventura is imminent). I’ll be frank; I do not use Vital currently because a more than reasonable amount of time has passed (in my opinion) for native support to have been implemented. To be sure, Vital is far from the worst offender in this regard. Native Instruments has been a disaster; only Kontakt has been upgraded (with Native Access 2 now in beta). And their hardware as well has been neglected. I refuse to buy another product from Native Instruments at this point. My feelings toward Vital are more benign, but I do wish Mac users had been given a version 1.0.8. which incorporated native Apple silicon processing. I’ll happily wait for 1.5.1.'s other features until they’re ready. As a Plus user I also wish that I’d been given the opportunity to participate in this latest version. I do understand that my financial commitment is not as great as some other users, but I still feel that having also paid for my software that I should be regarded as also invested in the software’s development.
2 Likes
Apple seems like a real pain to developers and users alike. I suppose to them, backwards compatability is for losers.
3 Likes
I’m sorry to say it, but this so reeks of entitlement.
You do realise, that Matt is just a single person, doing all the heavy lifting in developing Vital, don’t you? Apple, repeatedly throwing everyone under the bus, is just additional weight to lift. Feel free to support Matt financially and reap the benefits of M1 support. If you have cash to throw at Apple for a bleeding edge machine, I’m certain you can afford pittance for a Vital subscription.
4 Likes
That is why Windows is the best for audio production. Cheaper and no hassle.
2 Likes
That’s a good idea. Apple Corp should donate some money to Vital really.
I’m just happy and thankful that Vital is M1 compatible, and that it only cost me $25. I bought Massive X for way more, and I don’t like it at all. Matt is doing a so much better job than the entire Massive team over at Native Instruments. (I don’t understand what the f**k those people are doing at all)
1 Like
Yeah I think next time I’ll have a better idea how long things will take. Part of this change was using a new graphics engine and it’s been a bit of a pain tracking down the issues that only happen on certain computers.
2 Likes
I do private beta testing for other developers and just recently a bug was found in version 3 of a plugin and that bug has existed since version 2 going back many years and no one caught it until now.
It requires certain actions to be performed in the DAW and then certain parameter combinations in the plugin. In others words a very specific and obviously very rare use case.
So no matter how rigorously a plugin is tested it’s almost impossible to cover every use case and every system configuration.
You are right !!!
So it depends on Mr. Tytel to decide when a bug level is reached which suits to a puplic release.
One particularly nasty bug in version 1.0.8 was that the vst3 plugin could not resize itself in my DAW. Most of the synth area was outside the visible area. This bug is now gone in vital 1.5.1 and the plugin resizes properly. Kudos to Matt for this (and many other fixes …)
However, I still get a very high DSP usage (up to 50% for a single track) with some patches,that is comparable to the previous version, when other vst instruments barely reach 5-6% for sounds of about the same complexity.
I know, I have a low spec laptop (intel i7 with 4 cores, 8 threads), and also different synths operate differently, but again, I consider the new Vital 1.5.1 heavy on resources…
1 Like