New Preset Format

Hi everyone - as I said in my previous post, work is ongoing on a knowledge base that will cover all the key issues (and more). I know a lot of your are fed-up (to put it mildly) but you will have all the relevant info before the updates are available.

I think it's important that we have all the relevant information in one place, and more importantly that it's presented in a clear and concise but detailed manner, this is what is being worked on at the moment.

That said - following my last post there are some things I feel we should clarify:

Firstly, you will be able to import .ksds created in older versions of Absynth, Massive, FM8 into the updated versions of the synths. (Please note, I’m not talking about .ksds saved in Kore, I’m referring to .ksds that have been created to use with those plugins).

When running the update for the first time, a user can select to batch convert all existing presets to the new format, or he can do so individually. Either way, this process will not overwrite the existing .ksds. However, once converted, these new preset formats (.nabs/.nfm8/.nmsv) will not be recognised by Kore.

Finally, I know some Kore users are aware of the hack to replace the current Absynth, FM8 and Massive engines in the directory with the vst versions of the updates – this worked with old .ksds but with the updated versions of the synths you will not be able to save it as a Kore .ksd and load it successfully. The advice which has been officially in place since Kore 2.0.0 is that fiddling around with the IE files is explicitly unsupported and makes the Kore system unstable for a variety of reasons. For this reason we strongly advise against replacing the Absynth, FM8 and Massive engines in the Kore directory.

I'll check in on the process of the knowledge base next week and do my best to keep you posted on its progress - but even if I can't give you a date next week, it won't be too long to go.

Thanks again for your patience, gents.

 

thanks Keir

and yes the Knowledge Base idea is a good one!

sowari

 

I sort of have the feeling that in the future (maybe nearer than we think) NI will say something like

We listened to our fans of KORE and have now integrated KORE features to MASCHINE 2.0. with a new controller. Upgrade price is...

Will just need to wait and see.

 

Hi Keir, thanks for the update. Yes we know the hack is unsupported but it has really been the product of necessity given the lack of updates to Kore to stay inline with the engine updates rather than our preferred way of doing things. The fact is if you don't do that you end up with patches made with the newer versions not loading properly or at all and if updates are less and less frequent that may mean waiting a long time to use your patches again in Kore, something most users are unwilling understandably to accept.

That leads me to wonder, even if we don't update the internal engines, if we would run into problems if we even update the plugin and standalone versions at all? The reason is, as you probably know, when I run say Massive (or Absynth/FM8) from an already saved Kore sound it loads the internal engine version, but when I load a new instance of Massive from the main plugin menu it is loading the version that is in the VST plugin folder, which would then be incompatible. Now if I was then to save a Koresound with that version and try and reload it what would happen? My guess is that reloading it within Kore would make Kore attempt to load the older engine version and that would probably lead to a "this sound was created with a newer version of said plugin" type message. I suppose we should have to take care, until NI sort this situation out, to only load the internal versions when making new sounds in Kore?
---
btw - note the current update status folks !

http://www.native-instruments.com/forum/showthread.php?t=56654

cheers Thomas

 

i would agree, and suggest that you should load Massive by choosing a ksd which will load the integrated version. you can then edit/choose another patch/edit that, and then save as a ksd.

well, that is a workaround that makes sense to me.

sowari

 

Thanks for the reply Keir.

The ability to import by batch or single patch and the knowledge that existing ksd's will not be over written is an important clarification. This appears to address at least the first part of the problem.

The second part of the problem is the kore readiness of Massive, FM8 and Absynth Komplete 7 instruments after the update. It appears that these instruments will only output in the Maschine format. Will there therefore be a mechanism to translate these Maschine format presets to ksd or a save as option from the relevant instruments to maintain the "kore readiness" of the Komplete 7 instruments?

 

It's been that way since June.

 

Oops for some reason I thought there had been a change