I can't seem to get windows x64 and the latest version of kontakt (4.2.2.4504) to work - crashes reaper. Its the only plugin from Komplete that doesn't want to load
I am having a strange problem with Kontakt as well (same version 4.2.2 64 bit). I get this error when trying to launch any instrument from the factory content library "The patch could not be loaded (unknown error)". It does this both in Reaper 3 (version 3.75) and Reaper alpha 4 (version 60). Here's the goofy thing: All the other instruments work fine (ie session strings, evolve, pianos, organs, 60's drums). It's only the factory library and it's only in reaper 64 bit. The factory library works ok in stand alone and works ok in reaper 32 bit and Sony Acid Pro 7 (which I presume is also 32 bit). These are vst's by the way. This used to work in 64 bit reaper before. There are only two things that changed - 1. I upgraded to Kontakt 4.2.2, and 2. I changed my audio interface - I used to have a firewire Alesis Master Control interface connected but it broke, so in the interim I now have the audio going through my USB 2.0 Guitar Rig Kontrol 3 pedal. My computer is a Gateway FX series i7 proc. 8 cores, 8 gig ram, running Windows 7 64 bit. I think I will post this on the Native Instruments forum as well.
Ah- I have discovered this is not a Reaper problem. I tried opening Kontakt as a vst on my Native Instruments maschine. 32 bit works. 64 bit doesn't. Something's up with the plugin.
------------------------ Satisfaction isn't around the corner, it is the corner.
I tried to only go back to the 4.0.3 library and that didn't work then I tried to go back to kontakt 4.1.3 - didn't work either. HELP!!! I installed the program files on another drive other that the C: OS - would that make a difference?
------------------------ UNITED STATES COAST GUARD Support Search AND Rescue GET LOST!!!
Ok. I rolled back to 4.1.3 and the factory content still did not work with the 64 bit vst. I then rolled back the factory content from 1.0.4 (which is the current update) back to 1.0.3. Now everything is working again. So it appears that there is an issue with the factory content update.