Interested in Komplete 8 - but don't want to break Kore 2 compatibility

That's not what they're saying. They're saying the new versions will not work in Kore and will not be recognized.

I thought it would be easy, but can we force Kore to load the external plugin instead of the internal? By deleting the internal plugin? By replacing the internal plugin?

 

It is what they're saying, it just depends on the context in which the question is asked.

The internal engines won't support the maschine format - so they can't load presets from the new instruments - This ensures that existing ksd's continue to work.

If you take the new instrument vst's and do the "hack" and replace the kore engines with them, then kore will no longer recognise the ksd formats.

It seems pretty simple to me. We will have kore with engines that support the ksd format, we will have new instruments that we can load in as external plugins that support the maschine format Where is the issue there? None that I can see.

The kore readiness can be solved by NI offering Kore owners a maschine format to kore format translation tool. All problems solved and everyone is a happy bunny

 

Also sound designers should be encouraged to continue to make sounds for Massive, Absynth and FM8 in ksd format rather than the newer formats. As long as the conversion process is just one way (ksd to Maschine) if they just make them in the newer format they will lose a big chunk of the market whereas if they make them in ksd they will cover those who have upgraded and those who haven't.

 

for me, making sure the integrated NI engines are error free, when using Kore is the priority

sowari

 

The problem is: if you load Absynth 5, FM8 or Massive in Kore, the internal engine loads, not the external. Since the internal engine does not read the new format, you cannot load new patches made in the new format in Kore. For example: a Kontakt 4.2 patch can't be loaded in Kontakt running in Kore if the engine still is Kontakt 4.1. In other words: you can't add them to your Kore library.

I expected Kore would work with the replaced engines and therefore could import presets in the new format and still load koresounds because the koresound is a Kore preset, not only the plugin's preset. They are advising us not to replace them. And now they are saying Kore will not recognize the updated versions of the plugins.

The only way to add Komplete 8 to your Kore library is by replacing the internal engines and they're saying doing that will mess up Kore.

I'm dying to try replacing the engines... I can always put them back.

With a Absynth/FM/GR/Massive-koresound incompatible Kore there's always a way to preserve the original korepacks: run them in the Kore Player, lol.

 

Thats not my experience at the present time. If you go with the internal kore engines as is and then load the vst as an external plugin, it uses the vst version, not the internal engines - that has been proven for both Kontakt and Reaktor - When the vst and engine versions differ, can you positively confirm that it loads the engine version when you load it as an external instrument?

 

agreed.

if you load a VST of Reaktor Kore will look in your VST folder.

if you load a ksd of of Reaktor it will load the internal integrated engine version of Reaktor.

Reaktor is an easy one to try now because the internal engine in Kore is Reaktor 5.5 where as the current updated Reaktor is 5.6 and that is the version that will be loaded
loaded if you load the VST Plugin.

sowari

 

In my humble but correct opinion, this is the only sensible treatment. It means that existing .ksds will continue to work the same way they always have, and if you're building stuff on the new engines, you should use Maschine as your browser and not Kore.

 

And what happens, if you load Reaktor 5.6 in Kore, save it as Koretest.ksd and load it back into Kore? Which Reaktor version is instantiated? Reakto v5.5 (internal engine) or 5.6?

 

when things get uninteresting

good god, this is all turning into a math story problem. which i was never good at. Even though its uncommon these days, i am a musician, not an engineer or mechanic.
SCREW THIS BS!
i got, and liked Kore, because you DIDN'T NEED to be a rocket scientist to be creative with it.

Call me lazy or not hardcore but there is so much out there that one can just USE & get on with making music. I for one will not be learning code to keep Kore in my life. Or NI for that matter. but thats just me. Where they've stopped it i'll stay, yet will certainly be able to create unique sounds with Kore as it is till dooms day.

Seems i'll just have to begin/find a 'year 0 AK' librarian to slowly construct a 2000-teens set-up of some yet undetermined sort. Hopefully someone is out there right now pottering away with an innovative next-gen

LATER NI

 

i wouldn't know as i needed to replace the internal 5.5, because the Reaktor 5.6 install updated the Reaktor Library, so i was getting errors, when i clicked on the ksds of the Reaktor 5 Library patches.

to clarify, i had has to replace the 5.5 integrated engine,

sowari

 

Alright, false alarm, apologies.

I took all the vsts from the kore folder and the presets from kore packs wouldn't load, others did. So Kore can switch between the internal engines and the external ones.

Thanks guys

 

Damn, this stuff is as clear as mud. No wonder NI doesn't have a clue as to what's going on. Blunder after blunder. Oh well, I hope sales of Maschine are good...

 

So what's the upshot here? Are Kore users safe to install Komplete 8?
---

Yes, this is a mess. I no longer know which way is up. I'm no dummy, so I consider this to be 100% Native's fault.

 

NI are in the process of putting together a Knowledge Base page about this.

did you see Keir's post?

i would still make sure you back up your ksds to be 100% safe, especially if you have 'shared content' ones.

sowari

 

sowari - with your mod hat on I'd like to suggest you see if you can get the NI crew to post a sticky announcement that there will be an announcement soon about Kore and Komplete 8 issues.

It might help prevent things getting a bit bonkers (again).

I appreciate an announcement about an announcement seems a bit silly in itself - but I suspect it would be better in the long run for people (like me) logging in to quickly check progress.

 

just to remind everyone, i am not a Moderator for this forum, which means i can make stickies myself or do other Moderator type things

having said that, this is a good suggestion ... i will suggest it to Keir

sowari

 

no,i did not see keir's post. Was away for the weekend. Needed a holiday from NI-generated stress!

 

I'm very glad to see that NI is working on making an info base article available. This needs to be both comprehensive and accurate. Some of us have built our whole studios around the Kore + Komplete solution, we need to know how NI's vision of providing a complete DAW solution will evolve, in order to decide whether 'enough is enough'.

FWIW I am not fussed about the new effects already having Waves SLL, Sonnox and Altiverb etc. But I need to know how I will browse and use Komplete's sounds in the future if I am to continue using it. I dread dropping more money on K8 update plus Machine to get a solution which is less flexible, and more hassle.

I'm considering dropping NI altogether. But - correctly handled this moment is a big opportunity for NI. I currently use Cubase and am wondering what the future holds for Logic's sound library. Given the way Final Cut Pro X has been marketed, I wonder if Logic will also develop in a way that will leave some users looking for a better synth/sample solution.

I cannot be the only user who wants to buy an integrated, browsable large sample/synth workstation solution that is cross-platform and likely to be supported going forwards. There is no doubt that the Komplete concept must evolve - but I am not very attracted by what I see in the marketplace (including K8/machine) so far.....

Are you listening, NI?

 

I've read Keir's post now, and yes I see the section about instability.

I do believe that my new crashes in Cubase 6 (64 bit) may be due to the "hack" update of the engines.

I will think this over but for now I think I probably should fallback to the original versions to avoid the crashes. The crashes really screw with the 32 bit bridge and can end up causing me to have to reboot before my Cubase project works correctly.

Stability is more important than being able to say that I have the latest engines.