Vital - Released

[chagzuki]

I haven't used Vital in nearly a year, forgot what it was capable of.
Does anyone know what bank the 'Cookie Growl' preset is from at 2:10?

[zzz00m]

I haven't used Vital in nearly a year, forgot what it was capable of.
Does anyone know what bank the 'Cookie Growl' preset is from at 2:10?

It's in Vital/Afro/Presets, but the patch in the video demo has some modified parameters from the stock patch. In the demo the "Flange", "Stereo", and "Squarify" knobs have been adjusted to give it a thicker, deeper growl. There might be other not so obvious modifications, but those 3 knobs are easy to spot.

[chagzuki]

It's in Vital/Afro/Presets, but the patch in the video demo has some modified parameters from the stock patch. In the demo the "Flange", "Stereo", and "Squarify" knobs have been adjusted to give it a thicker, deeper growl. There might be other not so obvious modifications, but those 3 knobs are easy to spot.

I guess that's in the Pro tier version? I seem to have the early access Plus tier.

[EnGee]

Hi, I'm not able to paint 32 half-steps into one LFO. Bug?

halfstep.png

Version: 1.5.5, Win 10, VST2

It seems not ready for production! I will wait not using it until it gets rid of all bugs.

[zzz00m]

It's in Vital/Afro/Presets, but the patch in the video demo has some modified parameters from the stock patch. In the demo the "Flange", "Stereo", and "Squarify" knobs have been adjusted to give it a thicker, deeper growl. There might be other not so obvious modifications, but those 3 knobs are easy to spot.

I guess that's in the Pro tier version? I seem to have the early access Plus tier.

Yep, it's part of the Pro tier that includes 400 presets.

[Trancit]

Can somebody who uses Ableton or Studio One please check if you can edit automation points with entering numerical values with the VST3 version of i.e. the Cutoff of Filter 1??

Here no matter what I enter the automation point jumps always to the maximum value in both DAWs...
And Reaper doesn´t show "real values" but some decimal representation while the realtime readout shows context values

[darkinners]

Can somebody who uses Ableton or Studio One please check if you can edit automation points with entering numerical values with the VST3 version of i.e. the Cutoff of Filter 1??

Here no matter what I enter the automation point jumps always to the maximum value in both DAWs...
And Reaper doesn´t show "real values" but some decimal representation while the realtime readout shows context values

Just tried for you, both Studio One 6 and Live 11.2.6, if I use type-in automation value, it either jumps to the max or min value depending on the type-in value plus or minus.
No problem with mouse dragging, this only happens when typing in a value.

[darkinners]

And this seems not Vital exclusive. TAL Software plugins in VST3 format also have this issue.
U-he plugins works fine though.

[Echoes in the Attic]

Has anyone had trouble with the mpe pitch sliding in CLAP format in Bitwig? Doesn't seem to work like the VST3 does.

[Trancit]

And this seems not Vital exclusive. TAL Software plugins in VST3 format also have this issue.
U-he plugins works fine though.

I have now the solution why this is happening:

Plugins where this happens do not have this feature (automation with real values) implemented properly!

Means they send the real values to the DAW for the realtime readout but for actual automation you still have to go the blindflight and have to enter decimal numbers between 0-1...
I don´t know the scaling in Vital but i.e. for ANA2 when the realtime readout is 481Hz it´s actually an automation value of 0.49 which you have to enter instead

This on the other side causes a lot of confusion in Ableton and Studio One because they cannot differentiate between plugins which have the real deal (readout AND automation with real values) but just the easier half of it...

Reaper seems to be the only one (from the ones I tested here) which identifies the fake and show the realtime values as real values but when you go into numerical editing it shows in the ANA2 example the "real" 0.49 instead of the realtime readout of 481Hz...

So most developers either plugin developers or DAW developers went the easy way...
The plugin developer was too lazy to implement the automation correctly in the VST3 version and the DAW developers were too lazy to implement that readout value must not be automatically the correct automation value...

No matter who´s guilty at the very end it´s just a pity...

For me numerical editing of real automation parameters is one of the few highlights of the VST3 standard and it´s sad to see how little developers take the time to implement it properly...

While Matt is for me the least guilty with his generousity about his plugins in general... but companies who just sell their plugins at more or less full prices should imho kindly squeeze their cheeks and do their job properly.

I just "caught" Steve as he tries to come away with the same behaviour for Serum VST3...
I hope as it´s still in beta that he might change it...

[darkinners]

And this seems not Vital exclusive. TAL Software plugins in VST3 format also have this issue.
U-he plugins works fine though.

I have now the solution why this is happening:

Plugins where this happens do not have this feature (automation with real values) implemented properly!

Means they send the real values to the DAW for the realtime readout but for actual automation you still have to go the blindflight and have to enter decimal numbers between 0-1...
I don´t know the scaling in Vital but i.e. for ANA2 when the realtime readout is 481Hz it´s actually an automation value of 0.49 which you have to enter instead

This on the other side causes a lot of confusion in Ableton and Studio One because they cannot differentiate between plugins which have the real deal (readout AND automation with real values) but just the easier half of it...

Reaper seems to be the only one (from the ones I tested here) which identifies the fake and show the realtime values as real values but when you go into numerical editing it shows in the ANA2 example the "real" 0.49 instead of the realtime readout of 481Hz...

So most developers either plugin developers or DAW developers went the easy way...
The plugin developer was too lazy to implement the automation correctly in the VST3 version and the DAW developers were too lazy to implement that readout value must not be automatically the correct automation value...

No matter who´s guilty at the very end it´s just a pity...

For me numerical editing of real automation parameters is one of the few highlights of the VST3 standard and it´s sad to see how little developers take the time to implement it properly...

While Matt is for me the least guilty with his generousity about his plugins in general... but companies who just sell their plugins at more or less full prices should imho kindly squeeze their cheeks and do their job properly.

I just "caught" Steve as he tries to come away with the same behaviour for Serum VST3...
I hope as it´s still in beta that he might change it...

Thanks for the explanation, however I read in Serum discord that Steve said the Serum VST3 was actually out of beta since 2 days ago. the install package still has "b" in it so I guess it's the same beta build but it's officially out of beta.

[EnGee]

While Matt is for me the least guilty with his generousity about his plugins in general... but companies who just sell their plugins at more or less full prices should imho kindly squeeze their cheeks and do their job properly.

I would feel the same if I still use the free version, but I bought the Pro and I expect a stable version. Kind of feeling regret for buying the Pro!
I do the same mistake trying to support beginning indie developers (not established yet) but in reality I feel I'm just wasting my money in the end!
Remember the Mangle? Although much cheaper but the not responsive developer should be a lesson to me.

Good luck with this synth.

[Trancit]

While Matt is for me the least guilty with his generousity about his plugins in general... but companies who just sell their plugins at more or less full prices should imho kindly squeeze their cheeks and do their job properly.

I would feel the same if I still use the free version, but I bought the Pro and I expect a stable version. Kind of feeling regret for buying the Pro!
I do the same mistake trying to support beginning indie developers (not established yet) but in reality I feel I'm just wasting my money in the end!
Remember the Mangle? Although much cheaper but the not responsive developer should be a lesson to me.

Good luck with this synth.

I bought the full version too but I cannot tell I would regret anything... I don´t have a real issue with it and for me it´s worth every penny even if I mostly go with Serum instead... don´t know why...

[zvenx]

I bought the pro version.. in a lot of ways I believe he still treats it like freeware, with a few bugs that go unfixed for months or more...
and quite a few of what I consider 'rough edges' that I have mentioned to him many a times on discord.

rsp

[zzz00m]

I bought the Pro version because I wanted the developer to keep doing what he was doing. I have dozens of other synths, but I just felt that there was something special about this one that made it worth supporting...