KSD Batch Convert - do I have to?

I've downloaded the latest update from the service centre 5.1.0 and the first time I opened it standalone it's asking me if I want to convert all my ksd files to a new format.

I clicked no but when Absynth finished loading up I can't see any of my own sounds or any of the patches downloaded from Absynthsounds, does this mean that if I wish to continue using these patches I have to either convert them to the new file format or roll back to the previous version of Absynth?

 

Yes, the new version does not read ksds but uses the new .nab format

 

It's looking like it's the same for all the NI stuff now, but the file types look specific to the synth.

One small problem I've discovered is that as I go through patches I colour them & rate them - after they've been converted everything has reverted back to white with a 1 star rating.

 

They should not have changed this till a full version upgrade was in place - then at least people could opt to keep the old version alongside the new one (I did that for a long time when they ditched glo because the conversion was so naff for some patches). Either that or made it optional and allowed people to still use ksd - most people don't have Maschine anyway so don't need the new formats.

 

I've updated the ksd's to nab's.

Absynth 5.1 didn't see the ksd's anymore but Massive 1.3 still did.

Removed the ksd's from the individual Standalone app libraries that see both and added them to Kore as separate user libraries.

Bit of a process but now no double ups in Standalone browsers or Kore... Be easier to move my library in future that way also...

 

Please help. I can't open .nabs when I use Absynth as a plug-in now? The filenames are grey in the 'open sound' window. If I try to open the sound from the 'recent files' it just won't load. Really annoyed at the moment :angry:

Also I noticed that in standalone mode the browser and the attributes sections are bank name/type/subtype/mode, whereas as a plug-in it's instrument/source/timbre/articulation/genre just like it was in the previous version.

---

Edit: So the problem was that during the installation of the upgrade I hadn't ticked the VST Plug-In option, which was unticked by the installer itself as a default.. Silly. Anyway though after I reinstall it I had no problems..

Just posting this in case someone encounters the same problem.

 

That doesn't sound like the sort of thing I'd be interested in…