On September 14 2024, I got on FL Studio and opened a previous project but then I was told there was a unknown problem opening the vital plugin. Since this happened with Analog Lab plugin aswell, I looked for online solution and I was told to update to newest version of FL Studio.
After updating FL Studio, I opened the previous project and vital opened just fine; however, the vital plugin reset its preset to default, the plain sin wave, and I lost a vital state that I customized a lot. This is even more stranger because Analog Labs did not reset to the default preset.
Maybe install an “older” version of FL side by side load the older project and see if it loads the right preset then save that preset and load that in the “newer” FL.
Is there any solution to this? It used to load all the customization before yesterday. And this issue has occurred for all my Projects.
Just yesterday, I had to format my PC after which I reinstalled FL Studio and Vital.
Seems like my whole project in which I invested a lot of time is just dead.
This is so disappointing, VITAL needs to fix this.
There is no solution, you must save your presets and projects, and also back them up.
Unfortunately this is the reality of data management on computer based systems
Dear users. I don’t know where you get informations about how presets and projects works, but you’re all wrong. Synths, unlike romplers, do not load any presets when project is load. Synths restore knobs positions and settings based on data stored in project. It’s basically like this - when you save your project, synth stores all data in DAW project (in midless way - as a chunk of data) and then, when project is reloaded - it restores it. I shared projects many times with someone else and it works perfect. Of course there may be problems like bad synth design (that is trying to load preset anyway or need additional files to recreate preset - like samples or wavetables if they’re not stored in synth data) or DAW problem (I see that few people have problem after updating FL Studio), but it’s not Vital problem. I just saved some project (not in FL) with custom preset where I change wavetable to custom one, then I installed Vital on virtual machine where I don’t have previously installed Vital, and project opens without any problem. So please - do not give advices that user must share/save/store presets (well, it may, but it shouldn’t be necessary to restore project on any computer that have Vital installed).
You’re half right in this case @pb1
If we were just talking about how general plug ins may save info in DAWs yes, thanks for your info, and yes that is how project and plug states are saved, but you are missing context
original poster is talking about Vital after a DAW update
Further on, the next user is describing a OS re install, and DAW install, and attempting to recover a project
In both cases, without the preset and/or project backed up, there is no way to recover it. Otherwise these users would not have a problem lmao
It’s not just about how the plug in state is saved, it’s how daw and OS updates or installs effects the project files
your troubleshooting and test is missing that the DAW and/or OS is also a variable(s) here, not the plug in, but again thanks anyway.
Thank you for your answer, but you’re wrong. First of all - I wouldn’t wrote anything if someone say that he lost his presets or projects after system reinstall - that would be normal, nothing unusual if someone made, for example, format drive before and forget to made personal files backup. But then - he wouldn’t complain on Vital forum about it, but rather use LTT forum. So…
Vital after DAW update - if updated DAW can read projects from previous version, but not restoring synth settings - it’s probably DAW bug. Making backups of projects or presets do not solve this problem. DAW update should not broke old projects. I see no difference in loading old project in new DAW version or when someone backup old project to another drive and then will try to load this project in new DAW version - it’s the same, still the same file loaded into the same DAW version.
OS reinstall - not a source of a problem as I said, I tested the same project moving from one computer to another (and/or VM). Works no matter how many times you want to reinstall your system.
OT, reinstalling system every problem (or, as I like to say, “clean mania”) is in most cases I know source of many problems like that, so I strongly recommend - use your computer and if you’re bored, made music, not constant pointless system reinstall.
I had gone through @pb1 post refuting all the incorrect assumptions based on the context of this thread and the user reported problem, but I’ve deleted it it’s not worth getting into a debate
Anyway,
maybe it’s just lost in translation, thanks for your additional information @pb1
but I don’t get why you are advocating for not saving your presets
@VisheshChamoli or @iamconfeddi1
I can only encourage you to please save your presets, I promise you please do not rely on saved projects states, especially over long durations or if any updates to your DAW or OS or plug in, these can and will effect your project save.
If you want to take music making seriously, I strongly encourage you to take data management seriously, especially if you engage with clients.
In a perfect world as @pb1 describes, yes it should have been saved, but the software interaction between all the variables is not within your control. The only thing you can control is having a save of the preset as a back up.
I never said that user shouldn’t save his presets. But saving presets is not a solution.
Imagine that you have 20 projects using Vital, every of them have 10 instances. That’s 200 presets. And sure - saving them is an easy job, but then you must also save every change you made in them if you want to restore your presets proper in project. Every knob you move - you must save another preset. Then you must wrote somewhere notes about every preset used in project - just in case because if DAW do not restore preset, it also may not restore preset name (it’s part of stored data too). It’s not the way musicians should work. So yes - I suggest to not worry about saving presets when user working on music and saving presets when user made his own presets and want to store them.
Please understand I’m discussing only these two user issues, you clearly are not absorbing the context at hand:
and
In both cases:
If the project has not saved, or somehow lost, the plug in state: there are only two methods of rebuilding what was lost, besides re-doing all manually.
Either you have the preset saved to reload and begin from there
Or you have the project file that may recover the plug in state.
Updates to your DAW, OS, and plug in, may or may not have an effect on the project save file.
This is what im saying, and what @Yeager mentions indirectly, by attempting the older version daw alongside (thereby eliminating the DAW version as a variable, like I’ve mentioned about you not testing successfully).
In @iamconfeddi1 's circumstance it is unfortunate the plug in state was lost after a DAW update.
In @VisheshChamoli 's circumstance, reformatting their computer (OS) and reinstalled FL and Vital is what lost the plugin state
There could be any number of reasons why: a DAW bug, a Vital bug, temporary files are not recovered, caches being emptied, etc.
You seem to be confusing my answers as a solution for missing plug in states. There is no fix outside of software. I am only suggesting how to rebuild or attempt recovery which is inheritenly based on having back ups, whether of the preset or the project file.
I just answered in general because I’ve also read two other topics where you answered about the same problem. And in one of them (All sounds reset to a default saw when moving to another device) you said that user “need to share the presets you used and have them saved in the same location” (when user had problem with opening projects on another device). Since Vital is not absolute path dependent or not even load presets when user load project and you repeated few times that user must always save presets (I assumed that in your opinion it’s mandatory if he want to open his projects on another computer), I just wanted to clarify that it’s not how it works and it may gives false impression that Vital somehow needs external files to restore presets in projects. That’s all. I assumed also that we do not talking about how important is to made backups (it is), because it’s not computer forum. I know that they’re my first posts on this forum and you have a lot of them, but I think who is right is not dependent on number of posts. I think proper method would be to investigate what happens with that project (maybe unpack it and see in editor, compare to another project made on new DAW version etc. - I was able to restore few projects that way when some developers changes something in their plugins and old projects don’t want to open proper). Small hint - many DAWs saves their projects as ZIP files, just with different extensions and you can easily unpack it with 7-zip (for example).
Personally, I would try:
Copying the same VST/VST3 file from one computer to another (if on second computer projects opens and Vital opens, but there is only INIT preset inside - that means chunk data may be from newer version of Vital). Low probability since there is no new Vital version from a long time, but who knows.
Save project on new DAW version, unpack both of them (old project and new) and check if there is any difference with plugin data (identifiers, chunk headers etc). This may help to restore important project by made changes in old project.
Try older DAW version (someone else suggested that before) - even on Virtual Machine (may be faster for tests - less uninstalls/reinstalls etc)
my brother in christ please lead with that
Holy moly, atleast I know what tf youre on about now (t’es fr ou j’suis fou?)
Next time just post " hey if you have a copy of the project from when it was working, try comparing the project save data against each other for differences"
ANYWAY
Apologies for the confusion, it was clear you werent discussing the thread at hand
For users that have the prerequisites, I will certainly link your steps to them.
Sharing informations how synths saves settings in projects (instead of looking for preset files) is helpful imo. It can help people to stop looking for missing files and wasting time trying to investigate problem that way.*
I don’t understand why you’re trying to be sarcastic at all costs. Do you know everything better?
*some synths, as I wrote, may be written bad and unnecessary looking for preset files. One I know is Syntronik - it’s not really a rompler like some people think, but synth that have sampled oscillators; everything user change in this synth will be saved in DAW project except… oscillators. If user change osc, which is possible, new preset must be saved because for some stupid reason Syntronik first load that preset and then change all other settings based on DAW data.
I never claimed to know better, that’s literally what you’re doing in this thread
I even agree with you across multiple posts.
my only point against your explanations was that you were overlooking a couple variables in your suggestions
Incredible…
I’m off, this is going no where, the thread is successfully derailed, and you seem so obtuse about what I’ve said it’s making my brain become an oblique triangle
Add few more “funny” emoticons,this will emphasize your sarcasm.
On every forum there has to be some guru who effectively discourages helping by usurping the right to be an oracle.
Bye. This was my last post here.
I know one person did away with a similar issue by completely uninstalling (excluding the data folder where the presets are ofc) and reinstalling Vital.
my brother in christ please lead with that
