KVR Audio

zvenx · Post by **zvenx** » Wed Jul 08, 2020 4:37 pm

Does going back to 6.2 fix the issue for you?
Hope so.
rsp

simmo75 · Post by **simmo75** » Wed Jul 08, 2020 5:25 pm

zvenx wrote: ↑Wed Jul 08, 2020 4:37 pm Does going back to 6.2 fix the issue for you?
Hope so.
rsp

Yes, thanks for the link my friend

zvenx · Post by **zvenx** » Wed Jul 08, 2020 5:38 pm

Welcome. Glad i worked out.
rsp

faxinadu · Post by **faxinadu** » Wed Jul 08, 2020 5:48 pm

Kontakt team is aware of the issue and of the impact on users, working on a hotfix.

faxinadu · Post by **faxinadu** » Thu Jul 09, 2020 4:41 pm

Kontakt 6.3.1 is released which fixes this issue, cheers!

zvenx · Post by **zvenx** » Thu Jul 09, 2020 4:44 pm

Now That is a hot fix

rsp

faxinadu · Post by **faxinadu** » Thu Jul 09, 2020 4:48 pm

Well, this is the worst kind of bug, we couldn't let this sit in the wild, apologies to the people that had broken workflows.

Some info to people with Cycles, or experiencing a similar issue with other libraries:

For DAW projects that worked with Kontakt 6.2.2 and were never saved with Kontakt 6.3.0 , the users should simply update to Kontakt 6.3.1 and launch the DAW project normally.

The solution will allow the users to salvage a DAW project that was saved with Kontakt 6.3.0 and continue to work with Cycles, but unfortunately will lead to some data loss in a scenario where they have edited the broken Cycles instance in their project. The user will have to remove the NKI and reload a fresh cycles NKI and then save the project.

Users should take the following steps if they saved the DAW project with a broken Cycles instance within Kontakt 6.3.0:
- Update via Native Access to Kontakt 6.3.1
- Load the DAW project containing the Cycles instance that manifests the issue.
- Remove the Cycles NKI from the Kontakt rack WITHOUT saving the NKI.
- Load an NKI from Cycles back unto the Kontakt rack
- Save the DAW project in this state

Kontakt 6.3.0 Update