I’m able to open this preset - I’m running 1.5.1 on macOS Catalina 10.15.7
1 Like
Wow, thanks for letting me know. I’m totally stumped by this 
Interestingly, if I double-click the preset it opens Vital but doesn’t open the patch. But if I place it in a folder in my Vital library, I can open it within Vital. I have no idea what this means.
1 Like
Interesting. It’s in my user presets folder, how would I put it in the library?
Thank you much for testing it out for me, I really do appreciate it 
The synth version of this preset is 1.5.1 as well as the wavetables. You can do a quick command+H replace of 1.5.1 with 1.0.7 for a temp solution.
2 Likes
Thanks SlavaCat. I’m not sure where you are doing this or how. I’m quite new to Vital.
Just open the presets with a text editor
1 Like
When I open the preset with text editor it looks like this:
It doesn’t look like the pic you sent, I’m not sure where to go from here. It’s a very large file.
Thanks a lot for your help though.
I just reformatted mine with JSON indents–If you have python on your machine I can give you the code. All you really need to do is search and replace 1.5.1 with 1.0.7 and you should be good.
The problem then becomes figuring out why your 1.0.7 vital is creating 1.5.1 presets. If you can find it, the vital config file has the version number it’s on, so that would be a good place to start.
1 Like
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
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
OMG!!! It worked.
You absolute Legend 
I can’t thank you enough. If this happens again I’'l know how to fix it 
P.S. I know the preset doesn’t sound great, its all about the post processing + automation 
2 Likes
I have fixed it in the code and it now works. If this happens again I’ll definitely let you know
Thank for your help, I really appreciate it
2 Likes
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?
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 
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
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 !
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.
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.
Have you looked closer? There’s also a 1.5.5 Early Access version, which I think many are already using (I do)