• Software
  • Kontakt users: ever seen anything like this? (Resolved) (p.2)
2018/06/21 03:11:18
RexRed
Sometimes I've had to set the midi channel to one instead of none and that would get some Cakewalk VSTs to sound again. Normally the channels route themselves.
 
Just noticed your post about the corrupted MIDI tracks. I have seen that before with old projects where the MIDI for some reason is not compatible.
2018/06/21 16:52:21
bitflipper
I can replicate this problem...just load an instance of Kontakt but don't check the options to create MIDI and audio tracks. 
 
Different libraries react differently to this situation. Shimmer Shake Strike comes up with the blank UI described in my original post. Orange Tree Samples and Spitfire libraries displayed a "library not initialized" error message. Most others load without complaint. Kontakt then becomes unresponsive when you try to close it, making it impossible to properly exit out of Cakewalk.
 
Only Kontakt behaves this way, and only specific nki's. Other samplers, such as Superior Drummer 2/3, don't have a problem with you instantiating the plugin before attaching it to any tracks.
 
The solution is to always create and route the MIDI and audio tracks before loading an instrument. Or just let Cakewalk create them for you automatically (which I often don't do, but will from now on).
 
 
2018/06/21 17:59:11
eph221
Its just bapu messin with u.
2018/06/21 18:42:09
msorrels
I get this too with Orange Tree Samples!  Seems to be related to not having at least one audio output routed to the instrument though.  I don't think it needs any MIDI.  Which kind of makes sense, Kontakt the plugin doesn't know what format the audio is supposed to be so the scripts get inited differently.  Though I didn't have any trouble adding an audio track and routing Kontakt to it, which caused OTS Stawberry to init correctly.  And I didn't see a hang when I tried to exit.
12
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account