Vital keeps saying "Preset created with newer version"

Bugs
#21

This preset was created with version 1.5.1 which is the newer version available in early access to Pro users and subscribers. (at https://account.vital.audio/?product=vital)

This preset wasn’t made with version 1.0.7 which is the version you’re on. Are you sure you made this preset? Is it possible you downloaded the preset from somewhere or were using version 1.5.1 when you made it?

2 Likes
#22

Hi,
This is really strange, I 100% made the preset myself on the 26th August. And I have never had the Pro version (I only have the free version, I wasn’t going to upgrade to Pro paid version until I get the hang of it).
I honestly have no idea how this happened, but I had just updated to the latest version before I started to make the preset because I had not opened Vital for a couple of months.
Is there any way I can fix the presets, I only made two that day and they both error while opening. I have tried to remake them from memory but I just can’t get them the same. I started a tune with them so it would be awesome to get them working again.
I’m sorry about all this.
Thanks,
Sophia :purple_heart:

#23

OMG!!! It worked.
You absolute Legend :raised_hands::grin::purple_heart::unicorn::boom:
I can’t thank you enough. If this happens again I’'l know how to fix it :+1:

P.S. I know the preset doesn’t sound great, its all about the post processing + automation :rofl:

2 Likes
#25

I have fixed it in the code and it now works. If this happens again I’ll definitely let you know :+1:
Thank for your help, I really appreciate it :purple_heart::smiley:

2 Likes
#26

Is there a way to fix this without downloading python & becoming a coder? lol I have the latest version 1.0.8 and I’m getting the same message except I didn’t create the patch. I deleted and unistalled everything vital related and reinstalled 3 times now and it’s still happening. Any solutions please?

#27

I didn’t use Python, I used Text edit on a Mac. I had to look through the code for the incorrect version numbers and changed them to the correct version numbers. I use the free version of Vital but the version numbers in my presets were the Paid Vital version numbers. It worked fine but this would be a hassle if you had to fix lots of presets.
Most of the code looks like random digits, every now a again you will see words amongst those seemingly random digits, that is where you will find the version numbers, there will be about 2 or three places where to make the change. It looks overwhelming at first but it is easier than it sounds.
I hope this helps, good luck :crossed_fingers::smiley:

#28

I created a separate post about this and someone told me to install the 1.5.5 version, I did & now the presets work! Thank you anyways

1 Like
#29

Hi, as someone who really has no experience coding would you be able to explain to me on how to do this ? happy to go through a tutorial online or something.

I am getting the same error for some presets I got from someone else and it is really annoying me !

FYI I am on Windows 10.

Thank you !

#30

If you got the presets from someone else, they were probably made with a newer version. What happened in the situations above was different because the presets were compatible, just the version number was off.

#31

I do have the latest version of vital though as I attempted to update it and there are no further updates available (1.0.7). This is also latest version available online.

#32

Have you looked closer? There’s also a 1.5.5 Early Access version, which I think many are already using (I do)

#33

I just came here to say a massive thank you to SlavaCat!! had the same problem and this fixed it! you sir are the true MVP!! :clap:

2 Likes
#34

I’m having the same issue but it’s just the presets that was given to me by the Kulture samples people…

#35

where are you finding this?

#36

Hi, I was stung by this too, thanks for explaining the problem. I’ve found the easiest non-code way to do this, in bulk, is to:

  1. Open Vital
  2. Open the Preset Browser
  3. Right click the preset that is erroring
  4. Press open file location
    image
  5. Copy the location of that preset
  6. Open Notepad++ Notepad++ Download
  7. Press Ctrl + H
  8. Select the Find in Files tab
    a) Find what = “1.5.5” (or whatever the incorrect version is after finding it earlier)
    b) Replace with = “1.0.7” (or whatever your version is)
    c) Filters you can ignore or put .vitalbank
    d) Directory = put the directory of the preset
  9. Take a backup of the preset folder if you dont have access to the originals
  10. Press “Replace in Files” button
  11. Once complete, try again and it should open

But agree, hopefully this can be fixed somehow, like an open anyway option?

Note - if you are really stuck for formatting the JSON you can try this online tool JSON Viewer

#37

Any newer insights into this?

I made some changes in a Vital instance in my FL Project yesterday and now I cannot open the saved FL Project anymore because it will just stop to load once Vital throws the “Preset created with newer version” error. Which is when the channels are loaded and before the patterns and arrangement are loaded.

Quite frustrating.

I basically lost all progress on my song I made yesterday night and if it wasn’t for my excessive autosaving settings and versioning my manual saves, I could have lost the entire project.

Now the change I made isn’t saved in any preset, it’s just saved in the FL Project. Anyone any ideas how can I unfuck my project.flv file?

#38

Hi,

You could try editing the preset directly in a Notepad type prog. Right click ‘open with > Notepad’
Find all ‘version’ instances and change the numbers to match the one you are using.

I hope this helps.

GM

#39

Not sure if you’re replying to me; if you are, thanks for your input and wanting to be helpful!
As others have succeeded with this method, your suggestion is undoubtedly worth a try when we’re talking about a broken Preset stored in a separate vital preset file.

I am not sure whether I phrased it clearly, but my problem is not in a separate vital preset file but in my FL Studio project file. Like when you open a project, it initializes all the channels and the respective plugins with the settings the project was saved with rather than with the names of the presets that were loaded in the plugins.
So, my vital preset is not saved in a separate vital preset file but in my DAW Project, which is in binary format. I guess I could try a Hex-Editor? But it’s unlikely I will get a Project file in a working state with manual manipulation.

I’d much rather have a workaround that prevents this obvious bug from throwing an error message, so that I could at least load the project and replace the preset instead of having a 10% loaded project that just aborts the entire loading process because Vital thinks a time traveller brought a preset from a future version and refuses to even try to load it.

#40

Hi,
Yeah, my bad. I didn’t direct the answer correctly nor understand the situation. My apologies for that.
I don’t use FL Studio so I can’t replicate it myself.
What version of Vital are you using? ( I use 1.5.5 )
Have you tried reinstalling Vital?

Sorry I’m not much help beyond that but it looks like an FL Studio issue.

Again apologies for my late response too. ( My laptop bit the big one :sob:, I’ve had to get a new PC and sett it all up again! :angry: )

Good Luck!
GM