Vember Audio Surge is now open-source

[crickey13]

All right, I've figured it out. All the presets were made with the previous Surge, not the XT. While the XT reads the old presets just fine, they might not show up in the preset browser if you drop them in the "presets" subfolder. I will probably re-save them all so that they become fully compatible with Surge XT and show up in the browser.

So the lesson of the day is that the presets made with the old Surge are kinda compatible with the XT, but not really and it's better to re-save them. Secondly, it's best to leave your newly chosen User Data location completely empty so that Surge XT can create its own folder structure, otherwise problems may arise.

Thanks for help and sorry for bothering you, EvilDragon, this was more of an oddity rather than a bug, maybe somebody will find this of use though.

[EvilDragon]

The folder name has to be Patches, not Presets.

I have no problems with having Surge 1.9 patches in Surge XT user folder - they show up in the patch menu just fine and load just fine... They are perfectly backwards compatible.

There's no need to resave them.

[crickey13]

The folder name has to be Patches, not Presets.

Yeah, I just mixed up the names, meant Patches.

I have no problems with having Surge 1.9 patches in Surge XT user folder - they show up in the patch menu just fine and load just fine... They are perfectly backwards compatible.

There's no need to resave them.

They still don't load up for me in the preset browser even when I put them in the Patches subfolder, but maybe I'm an isolated case, I have no way of telling. I'll try again later and will re-save them if necessary, there is not too many of them thankfully.

[crickey13]

OK, I've figured it out too, I take that back about the old presets not being fully compatible with the XT.

They are, but in order to make them show up in the patch browser, you need to put each one of them in one of the categories in the patches folder e.g. plucks, basses, pads etc., otherwise they won't show up, simply putting them in the Patches subfolder won't do.

It's better to make a few new default patches with the XT and then import the old patches into the newly created categories, everything should work fine then.

[EvilDragon]

Huh, weird. Can you zip up your 1.9 patches folder exactly as it is and shoot it over?

[exmatproton]

XT is amazing guys! What a giant leap from 1.9. amazing stuff!

[baconpaul]

OK, I've figured it out too, I take that back about the old presets not being fully compatible with the XT.

Heya!

So here's what's happening

1. FXP files from 1.9 all load fine in XT once you find them
2. The location for FXP categories in 1.9 is "~/Documents/Surge" or your OS equivalent; in XT it is "~/Documents/Surge XT/Patches"
3. In both 1.9 and XT, fxp files placed in the patch root are ignored. So "~/Documents/Surge/foo.fxp" won't show up and neither will "~/Documents/Surge XT/Patches/foo.fxp". That's why you had to put them in categories. XT 1.0 will ship with this behavior
4. We have a change ready for XT 1.1 (our suspected bug and small feature release we will do after XT1.0) which will put these into an "_Unsorted" category.

[crickey13]

Huh, weird. Can you zip up your 1.9 patches folder exactly as it is and shoot it over?

I've already imported all the old patches into the XT and deleted the old Surge folder, sorry.

I can still copy the remaining old patches, zip them and send them your way if you want, but honestly, there was nothing special about them as far as I could tell.

Heya!

So here's what's happening

1. FXP files from 1.9 all load fine in XT once you find them
2. The location for FXP categories in 1.9 is "~/Documents/Surge" or your OS equivalent; in XT it is "~/Documents/Surge XT/Patches"
3. In both 1.9 and XT, fxp files placed in the patch root are ignored. So "~/Documents/Surge/foo.fxp" won't show up and neither will "~/Documents/Surge XT/Patches/foo.fxp". That's why you had to put them in categories. XT 1.0 will ship with this behavior
4. We have a change ready for XT 1.1 (our suspected bug and small feature release we will do after XT1.0) which will put these into an "_Unsorted" category.

Bingo, that's pretty much it. I'm glad I've figured it out and made it work on my system, but there are people out there who might run into the same issue.

Maybe a remark about this ought to be included in the readme file if anyone should stumble across a similar situation.

[baconpaul]

Maybe a remark about this ought to be included in the readme file if anyone should stumble across a similar situation.

Yeah we will add this to the changelog if we haven't already.

[JamminFool]

gettings errors trying to use Extract All on Windows 11.

[EvilDragon]

What are you extracting? Just use the installer...

[JamminFool]

i'm extracting from the zips that are on the nightly builds.
of course i can use the installer, but thought you might like to know that the zips aren't useable.

[EvilDragon]

They unpack perfectly fine over here using WinRAR. Unsure why they wouldn't work using Windows' own extraction, it's a regular ZIP file...

(But I can confirm it on W10 too, hmmm...)

EDIT: After a bit of Googling, looks like built-in ZIP unpack support in Windows is extremely limited. I guess install WinRAR or WinZIP then...

[JamminFool]

They unpack perfectly fine over here using WinRAR. Unsure why they wouldn't work using Windows' own extraction, it's a regular ZIP file...

(But I can confirm it on W10 too, hmmm...)

EDIT: After a bit of Googling, looks like built-in ZIP unpack support in Windows is extremely limited. I guess install WinRAR or WinZIP then...

lol, install something to access the zip file which i downloaded to avoid using an installer.

it may be limited, but i have used it to unzip everything forever, and this is the first time i have seen this happen. no problem though.

[EvilDragon]

If only Windows would give a more helpful error message about what exactly is wrong with the ZIP file, then we might've done something about it...