Kontakt VSTi and MIDI problems -ACID Product Family

Subject:Kontakt VSTi and MIDI problems Posted by: daveg90125 Date:12/1/2006 8:15:59 PM I've been working with the Acid 6.0c demo for about a week, trying to see if I like the workflow before deciding if I want to purchase the upgrade. I love a lot of the things about Acid 6 - obviously, it's leaps and bounds beyond the last version I purchased, 4.0. That said, there are a handful of problems I'm encountering in 6.0c that are serious enough to really put a damper on getting work done: - Kontakt 2.1 VSTi frequently loses its program info and loads up empty after a session is saved and re-opened; when it happens, it happens to every K2 instance in the session. (NOTE: I apologize if this is a Kontakt problem which has been corrected with Kontakt 2.2, but I'm scared to update to 2.2 with the authorization headaches people have been having with 2.2.) - MIDI tracks often lose their link to the VSTi that they should be playing when a session is closed and re-opened. Usually what happens is that all the MIDI tracks are trying to play the left-most instance of Kontakt in the master/aux window, regardless of their MIDI output assignments. Manually changing the MIDI output on each of the tracks from "no output" back to what they should be usually doesn't help. The only thing that does help is deleting every instance of K2 from the session except the first one and then re-instantiating them and re-loading their respective programs. - Often (but not always), a newly recorded MIDI region will not play back AT ALL until the program is closed and re-launched. I've found that if you go into a region that was recorded prior to the program being re-launched, you can delete all the note events from that MIDI region and record a new take into that now-empty region and the notes will play back without relaunching Acid. But as soon as you delete the entire region and try to record a whole new one, no dice...it won't play until you re-launch. I'm hoping these things are being addressed for the 6.0d release. On a search, I noticed others having similar or identical problems.
Subject:RE: Kontakt VSTi and MIDI problems Reply by: CineGobs Date:12/2/2006 1:01:30 AM I had some similar problems with Kontakt some time ago. There are 3 different versions of the Kontakt VST installed., which has different output configurations. It seems that sometimes Acid loads the wrong one, when opening a saved song. I deleted the Kontakt2_16out.dll and Kontakt2_8out.dll, and I haven't had the problem since. I guess somehow Acid get's confused over the 3 different versions.
Subject:RE: Kontakt VSTi and MIDI problems Reply by: daveg90125 Date:12/2/2006 9:11:16 AM Thank you VERY much for the tip. I think that did the trick with the Kontakt issues - at least, after closing and re-opening the session 4 or 5 times, Kontakt has behaved itself, so I'm assuming we're good now. That was the major concern keeping me from switching over to A6 as a full-time recording/mixing app, so I'm really glad to (fingers crossed) have that resolved.

I've been working with the Acid 6.0c demo for about a week, trying to see if I like the workflow before deciding if I want to purchase the upgrade. I love a lot of the things about Acid 6 - obviously, it's leaps and bounds beyond the last version I purchased, 4.0. That said, there are a handful of problems I'm encountering in 6.0c that are serious enough to really put a damper on getting work done:

- Kontakt 2.1 VSTi frequently loses its program info and loads up empty after a session is saved and re-opened; when it happens, it happens to every K2 instance in the session. (NOTE: I apologize if this is a Kontakt problem which has been corrected with Kontakt 2.2, but I'm scared to update to 2.2 with the authorization headaches people have been having with 2.2.)

- MIDI tracks often lose their link to the VSTi that they should be playing when a session is closed and re-opened. Usually what happens is that all the MIDI tracks are trying to play the left-most instance of Kontakt in the master/aux window, regardless of their MIDI output assignments. Manually changing the MIDI output on each of the tracks from "no output" back to what they should be usually doesn't help. The only thing that does help is deleting every instance of K2 from the session except the first one and then re-instantiating them and re-loading their respective programs.

- Often (but not always), a newly recorded MIDI region will not play back AT ALL until the program is closed and re-launched. I've found that if you go into a region that was recorded prior to the program being re-launched, you can delete all the note events from that MIDI region and record a new take into that now-empty region and the notes will play back without relaunching Acid. But as soon as you delete the entire region and try to record a whole new one, no dice...it won't play until you re-launch.

I'm hoping these things are being addressed for the 6.0d release. On a search, I noticed others having similar or identical problems.