thepianist65
Max Output Level: -78 dBFS
- Total Posts : 644
- Joined: 2004/07/30 15:09:51
- Location: Boston, MA
- Status: offline
Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt SOLVED
I updated to Kontakt 5.8 from the previous version today, and now when I open a project, Kontakt is crashing and freezing Sonar, either the new bandlab version or my Platinum version. Starting a new project, I try to add a synth, but instead of showing my 64 bit Kontakt listed, it only shows two instances of Kontakt 32-bit version--this has never happened before. I tried rescanning the vST folders, didn't help. I checked the location of my .dll files for Kontakt and they are all there, in their usual and proper location , and indicate that my version of Kontakt is indeed the 64 bit version. I'm lost at how to fix this. I have contacted Kontakt support, but I fear that this is some new incompability with Sonar/Cakewalk, since the standalone of Kontakt seems to be fine. I'm going to tinker with the VST scanning again, but if seems that should have fixed the problem already. I hope someone has an idea, this is putting my work at a standstill. Thanks.
post edited by thepianist65 - 2018/04/13 00:08:15
|
quietman
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2009/08/24 15:56:56
- Location: North Devon
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 20:40:23
(permalink)
that is a worry... think I'll hold fire on the 5.8 update until there is some clarification from Bandlab... hope you can find a solution... Can you move back to Kontakt 5.7 by a system restore point?
www.4th-eden.comComposing until I'm decomposing
|
thepianist65
Max Output Level: -78 dBFS
- Total Posts : 644
- Joined: 2004/07/30 15:09:51
- Location: Boston, MA
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 21:03:25
(permalink)
I may indeed try and do a system restore, but not sure if I have one or it will work, but it's a decent idea. I'm trying to re-scan, but having some scanning-crashing issues, too. It's all very annoying and puzzling. But we'll see.
Thanks.
|
quietman
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2009/08/24 15:56:56
- Location: North Devon
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 21:10:12
(permalink)
thepianist65
I may indeed try and do a system restore, but not sure if I have one or it will work,
By updating Kontakt to 5.8 a system restore point may have been generated automatically..if it was the last software update you did you maybe able to go back.. not guaranteeing of course! Ive sent a msg to Bandlab to clarify... if your Kontakt 5.8 works OK in standalone ..sounds like Sonar/CbB has an issue...
www.4th-eden.comComposing until I'm decomposing
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 21:17:21
(permalink)
Sounds like you got the 32 bit update. I'd try the D/L again.
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
Phoen1xPJ
Max Output Level: -85 dBFS
- Total Posts : 255
- Joined: 2016/11/03 18:14:22
- Location: Atlanta
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 22:53:38
(permalink)
Updated and running fine here in CbB.
Yours With a Song, Phoen1x Wayfarer Station Micro Studio including:*new* Cakewalk by BandLabIntel Core i5 quad core 3.10 GHzASUStek P8B75-M mobo32 GB Mushkin Blackline RAMNVidia GeForce 210 1 GB vid card(2) 1 TB HD & (1) 500 GB HD*new* Win 10 Pro 64 bitEcho Layla 24 PCI audio interface (faster than USB!)Tascam US-224 control surface (with jog/shuttle wheel, impossible to find elsewhere)MIDIMan 2X2 MIDI interface...not bleeding edge but vintage rockin' http://verticalalignment.rocks/
|
Jazzy2040
Max Output Level: -90 dBFS
- Total Posts : 36
- Joined: 2015/04/17 12:09:17
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/12 23:04:35
(permalink)
Just to rule out any incompatibility, I updated yesterday and it's working properly.
Maybe it's like ampfixer said.
Good luck.
Reaper, Samplitude pro x3 suite, Cakewalk by BandLab, NI Komplete 10, Windows 10 v1803, Asus ux501vw, I7-6700HQ @ 2.60GHz , 16GB. RME Babyface Pro, Komplete Kontrol S25, Impact LX25+. Retired musician, can't retire from music.
|
thepianist65
Max Output Level: -78 dBFS
- Total Posts : 644
- Joined: 2004/07/30 15:09:51
- Location: Boston, MA
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/13 00:01:00
(permalink)
Well, I did finally solve it in a rather unconventional way. Since Cakewalk (nor Sonar) was "seeing" the new version's .dll's, even though they were present in the scanned directory, I decided to copy the .dll files to a couple other of the folders where some of my 64-bit vst's reside (some vst's put their .dll's in directories other than my default c:/program files/cakewalk/vst). Anyway, after doing that, I launched Cakewalk, and the scanned picked up my three kontakt plug-ins, and everything is back working as normal. I have no idea why or how this worked, but I had a hunch that copying the files into additional directories wouldn't hurt anything and might trigger a "discovery" of a "new" VST, and voila, it did!
BTW, I wasn't able to do a system restore, as it didn't indicate that the Kontakt changes would be affected either way, and I'm relieved I didn't have to go to those lengths.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/13 00:10:55
(permalink)
5.8.0 running fine here, near as I can tell. Tested it standalone and as a plugin.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
thepianist65
Max Output Level: -78 dBFS
- Total Posts : 644
- Joined: 2004/07/30 15:09:51
- Location: Boston, MA
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/13 12:42:38
(permalink)
Yeah, it's funny that this problem surfaced out of nowhere, and the solution was even wackier. I definitely had the 64 bit version, but the update was not being scanned by Cakewalk properly until I copied it into another folder that is normally scanned for changes, and then it was fine again.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: Neither Sonar nor Cakewalk by Bandlab seeing 64 bit Kontakt after update of Kontakt
2018/04/13 13:16:29
(permalink)
I had the same problem at one time. It resulted in multiple versions of Kontakt co-residing on disk, which took me awhile to notice. It wasn't until I updated Kontakt to fix a specific bug, and the bug persisted after the update, that I figured out what was going on.
The problem was self-inflicted, caused by me attempting to keep my plugins organized. The solution: don't fight the installer. Let NI install files in whatever default location it wants. I deleted all existing copies of Kontakt*.dll, re-installed, located the newly-installed DLLs and added that location (c:\program files\native instruments\vstplugins 64 bit) to SONAR's VST search paths. It annoys me every time I see that path in there, but it solved many problems.
All else is in doubt, so this is the truth I cling to. My Stuff
|