1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

How to activate legacy products in Kontakt 4 now that service center is no longer available?

Discussion in 'KONTAKT' started by hendyb, Dec 28, 2021.

  1. hendyb

    hendyb New Member

    Messages:
    3
    Hi,
    I have some old Cubase projects that are still using Kontakt 4 instances with old products like Heavyocity Evolve and Virtual grand piano, and they now appear to be inactivated since I have re-installed my PC (due to hardware failures).
    I have registered them with Native Access and they are accessible from Kontakt 5 or 6, however I'm wondering if:
    1. Is there a way to get them activated in Kontakt 4 instances so that I don't have to change much in the Cubase project?
    2. If #1 is not possible, what would be the easiest way to switch the Kontakt 4 instances into Kontakt 5 instances, while preserving all the VSTi automations?
    Thanks
     
    hendyb, Dec 28, 2021
    #1
  2. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Kontakt 4 should still be activatable with Native Access.
     
    EvilDragon, Dec 28, 2021
    #2
  3. hendyb

    hendyb New Member

    Messages:
    3
    Yes for the Kontakt 4, however the problem is Heavyocity Evolve and virtual grand piano appear to be not activated, although on the same system both products have been activated in native access and can be used in Kontakt 5 and 6.
     
    hendyb, Dec 28, 2021
    #3
  4. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Hmmm unsure about that, then. It might be related to Kontakt library activation change that happened between K5.6.6 and K5.6.8, so those particular libraries wouldn't work in versions prior to 5.6.8.

    In that case you would need to manually replace those K4 instances with K5 or K6 instances. Unfortunately I don't know of a way to do that in Cubase while retaining any automation.

    BTW when you say automation, are you talking about MIDI CC data (then you will be fine) or host automation envelopes (in that case you'd need to rebuild the track most likely, unless there's some copy envelope feature in Cubase (there probably is)).
     
    EvilDragon, Dec 28, 2021
    #4
  5. hendyb

    hendyb New Member

    Messages:
    3
    it's more on the host automation envelopes (ie. volume automation) on the VSTi channel itself (some of the libraries doesn't respond to changing the volume/expression CC in the midi tracks)
     
    hendyb, Dec 28, 2021
    #5
  6. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Right, so I suppose you will have to open that project, create a new track that will host an instance of K5 or K6 (preferably K6), load the same NKI, then copy automation from track to track.
     
    EvilDragon, Dec 28, 2021
    #6