adding new instances of vital 1.5.5 causes memory to shoot up enormously, removing them barely clears up any of its allocated memory, this weirdly only started happening recently and i’m not entirely sure what’s causing it, but it happens on two separate computers running Win10 and Win11
opening old projects intact that used the 1.5.5 version of vital is impossible now, memory usage shoots to the skies and ends up causing FL Studio to crash before i can do anything
possibly relevant info:
- win10 and win11
- intel cpu from 2011
- daw: FL Studio 20
video: Watch 2024-05-02 20-13-33 | Streamable
(i installed v1.5.5 as VitalNew since i’m currently using v1.0.7 as an alternative on the same machine)
if any more info is needed i can give it
3 Likes
Is it maybe vst2 versions in older projects?
Dang haven’t seen this bug before
How much ram do you have? As you have a 2011 cpu (intel haswell or older I think?) it could be just hitting the limit of ddr3 ram with the new fl studio update maybe?
hi! both my PC and laptop have 8 gb of ddr3 ram, though i’ve never had much of an issue with ram when making music
my cpu is intel i3-2120 so it’s pre-haswell, as for vst2 in older projects im not sure what u mean but i have the VST3 version of 1.5.5 and VST+VST3 for 1.0.7
Wow, glad your 10+ year old system isn’t hitting it’s limits yet!
Really not sure, is there maybe a graphics or DirectX update?
You mention even removing the Vital instances in the project doesn’t fix the ram issue? It stays still quite high?
Does launching the standalone version also cause the same issue?
I wonder if there’s a process hanging in the background even after closing ( sorry didn’t actually get to see your video clip)
I can definitely say we’ve seen more users with issues between vital and fl studio recently(last 6 months ish?) on both windows 10/11 
Did you ever figure out a solution to this? I came here looking to see if someone was having the same issue. It’s happening to me in FL 2024 (v24.2.1, just upgraded to the newest build 4526 to see if it helped…nothing).
I just bought a new PC (gaming PC, so it’s plenty powerful), and I noticed adding in Vital was using about 200MB of RAM per instance. And like you said, even if you remove the instance, the RAM usage only decreases by maybe <10MB if that. Even starting a new project doesn’t clear it up.
I even downgraded to Vital 1.5.1 to see if that helped. Nothing. Also I get the same issue with VST2 or VST3.
It’s definitely disheartening to come here and see this post was all the way back in May with no fix or Vital updates since. I guess development is dead. It would be nice if Matt would at least make it opensource so SOMEONE could improve it. I’ve already sunk $80 to Matt and maybe another $40 in presets elsewhere but it seems like moving on is imminent.
1 Like
sadly i haven’t, i’ve already moved on to Serum and Phase Plant instead
the low-spec pc i was using at the time died this summer, and i tested on my new pc to see if maybe the issue only happened on the old pc, but it persisted on the new one aswell
for reference, my specs are now GTX 1650, intel i5-13400K, 16GB ram, and FL 24
1 Like
Heya guys @zero_contrast @realmariluu
I’ve used most of the synths you mention so if you have questions hit me up anytime
Personally, Serum is very similar to Vital in workflow and features, etc.
One could argue that Vital offers more than Serum, which I agree, and personally I do find Vitals interface a bit better/easier/etc.
Currently, I use mostly PhasePlant and Vital.
PhasePlant is a super great synth, but does take some getting used to the workflow. I think it offers more value than Serum especially when it’s on sale for $99 (plus you get all the kilohearts free stuff)
Can also confirm Arturia’s Pigments is also a great synth.
I’d also recommend a few others, depending on what you’re looking for in a synth?
All in one type thing? Or maybe you want more analog flavour? Or something awesome for pads, like Spire or Hive? Etc etc
200mb is nothing for Vital, how did you get is so low? Loading up Vital in Bitwig shoots up my RAM usage by at least 700mb. Removing the instance brigs it down by 200mb.
Btw. check this out: HACK: 119 instances of Vital occupying <2Gb RAM! (W11 & Live) if you’re on Windows. That brings my mem usage in Task Manager down by over a gigabyte and it doesn’t go back up.
edit: Yeah Serum grabs like 160mb while a gigabyte for Vital isn’t even surprising.
reckon vital would replace 90% of my VSTIs if this wasn’t an issue. running renoise on Win10 and yep eats a gig on loading and doesn’t let up until ive closed and reopened renoise.
has this always happened or is it a recent development? wonder if relenting to MS’s demands to update to Win11 would help…
It’s been like this as far as I can remember. If you clear the working sets with that Sysinternals tool it will slash the mem use tho. It’s a bummer you need to do that to get it under control but at least you can try. I don’t think Win11 will do a thing if it’s a memory leak in Vital, but what do I know.
Not sure if you’ve upgraded to Win11, but if not, it does not help. Personally I’ve abandoned Vital (except for the projects that already have it in them) just as the developer did.
Sorry, I’m ridiculously late on replying. I looked at the hack you linked some time ago, but couldn’t get it working.
Also, I’m not sure how it was so low. That was on my old computer, I think I started noticing the issue after some Windows update if I recall correctly. That computer originally had Win8, and it wasn’t all that long ago I upgraded it to Win10, but i think it was still low for some time after the upgrade.
As I mentioned to another user, I’ve abandoned Vital. It’s still installed for the sake of projects that have it in them already, but it’s not in my plugin database to be able to add it into new projects. I’m just disappointed I forked over $80 to Vital and maybe a total of $50 more to Demis Hellen and other creators for more presets.
Seems like it might also be an FL issue?
Re-reading the thread it seems like FL users are more likely to have the RAM issue?
Does vital use the same amount of ram when you run it in standalone?
It’s a bummer for sure, but don’t get me started on plugins where I spent $100 to never use them again ( im looking at you Waves and Universal Audio) hehe
1 Like
It’s definitely not an FL issue. I’ve never used FL and it’s the same for me.
It seems it has something to do with the GUI. When I load Vital into Cantabile, which doesn’t show the GUI right away, the mem usage goes up by 120mb. When I open Vital’s GUI, RAM use goes up by additional 800mb. Closing the GUI doesn’t free the resources.
Ah, great to know - nice testing Herman!
1 Like