I already posted about this once but the issue is still unresolved. On my old pc vital basically never saved preset names but kept the sound. Even if I used a preset that was already saved separately with a name, after closing the project it still showed it as init preset but it worked otherwise. However if I try to bring any of these projects over to a new pc it opens them as the actual init preset which makes all my projects unusable that had vital in them. It also starts with this message when opening them up on the new pc. And again this happens with every project without exception, and only happens to vital.Is there ANY solution to this?
upload some of the Vital presets that are causing this problem.
Also, OS? Vital version?
Windows 10, vital is 1.0.7 on both PCs.
Uploading the presets is pointless I can open presets in vital. The problem is that vital doesnt save its parameters/used presets properly in projects and for some reason FL studio is also not saving that information. I could save every single vital patch in every project, load the newly saved presets into the vital instances on the new pc and then save them there but with like 100 projects with up to 10 or more instances of vital each this quickly becomes unsustainable, especially that automation would have to be set up again for every single parameter for every single patch in every single project.
Its not the presets themselves its vital not saving properly I just dont understand why this is. I saw old forum posts about vital constantly resetting preset names to init preset which was supposedly fixed (presets still reset to init preset for me) but on top of that once I move any project to the new PC all those patches actually become the init preset.
Try to update Vital to 1.5.3 and see if it resolves your issue
I’m getting this error when I try to open a project from someone else in FL Studio. I can add a new instance of Vital and choose whatever preset I want and it works, but when opening someone else’s project, the “preset corrupted” error pops up. I can load the same presets they used into Vital and they all work, just not on initial opening of the project. I’m using VST3 version 1.5.5. Anyone been able to find a solution for this?
I’m having a same issue. I just builded new pc, tranferred all my projects and presets. All vital presets witch are used in old computer are “corrupted”.
Since we’re only getting these reports from FL users it’s probably safe to assume that it’s an FL problem.
After talking with the FL Studio tech team, they would like you to contact them so they can work with you to figure out how to solve the error. They’ve requested that I ask you to log a support ticket with them here: Ticket Post || Ticketing explaining the issue so they can help. Could you please log a ticket so we can all use your plugin without errors? Much appreciated!
Thank you!!!
1 Like
Hi, I’m one of the developers of FL Studio. I’ve been talking to darkmattersound about this but haven’t been able to reproduce the error message.
However, the message “There was an error open the preset. Preset file is corrupted” is shown by the plugin, not by FL Studio. So I was wondering if you would be able to share under what circumstances that message is show, this may help to identify what might be wrong in the FL Studio code.
You can contact me through our ticketing system: Ticket Post || Ticketing
Regards,
Frederic
1 Like
Have you confirmed that you’re using the same plugin format and Vital version at both ends?
I was having the exact same problem with the presets and i found a fix that worked for me
the folder “/Documents/image-line” in there a folder called vst3 and that had the vital.dll and vital.vst3 and i found out that it was missing on my new pc so i transferred it and the presets worked…
So try looking for some kind of missing vital folder so that the new pc with vital is as close as possible to the old pc. Idk if that helps you guys but it solved my problem
Yes, we’re both using v 1.5.5
Hi, @HermanVonElsewhere .
Have you had a chance to investigate this or logged a ticket with Image-Line as @frederic suggested? We’re still getting these errors.
Thanks!
I’m not associated with Vital dev even though I read and reply to this forum quite frequently. If @frederic wants to get in touch with Matt they should email Vital’s support mail (support@[Vital’s website]) and hope for the best.
1 Like
Had the same issue for some time now. I found a fix for my problem and you should try it aswell. Make sure to install BOTH vst2 and vst3 version of Vital, even if you intend to only use vst3 now. That way FL can load the older vst2 automatically for older versions where you may have been using vst2 instead of vst3. In my case the newer vst3 version of vital wasnt capable of loading older vst2 vital presets (for whatever reason, prob a bug). That fixed it for me =)