jjloving
Max Output Level: -90 dBFS
- Total Posts : 42
- Joined: 2008/03/08 17:13:52
- Status: offline
Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
Hey Folks, System Info: - Intel Q6600 @ 2.4Ghz - Windows 7 x64 - Kontakt 3.5 - Kontakt 4.x - Sonar 8.3.1 Producer - MOTU Ultralite mk3 Hybrid I'm at a loss with this one - Instruments loaded in any version of Kontakt from v3.5+ in Sonar 8.3.1 (x86 and x64) don't update the GUI appropriately. Whether that be changing a value for a CC or other function (either by mouse or external controller), selecting an option that should display a new set of controls, etc.. there is no change whatsoever. In the case of some K4 libraries (Cinesamples VOXOS, for example) which use many graphic elements - these reflect the selections made (i.e., selecting the "Phrase Builder" button in VOXOS highlights it correctly, but the interface doesn't switch). The behavior is present with all libraries and doesn't appear to be related to which version of Kontakt the library was created in. A bit of background - I've had this issue with all versions of Kontakt 4 in Sonar for a while now, but K3.5 had always been fine until I unplugged the system for 6 months and went on tour. Since returning home K3.5 hasn't been working either (no updates or changes initially and the machine was never used during that time) - quite bizarre. I then updated drivers , etc.. with no change. I have done the uninstall/re-install dance with both Sonar and Kontakt and there's no change with any version/combination. I've also verified that the VST plugin files are located correctly and are the correct version at each stage. All libraries are fully up to date as well. The behavior is only present in Sonar, everything responds correctly stand-alone and in ProTools 9, Sibelius 5 and Sibelius 6. It's crossed my mind that it might be some graphics Service-related issue, but my services configuration hasn't changed and I've been through a number of services enabling/disabling with no change in behavior. Further, the issue persists regardless of what plugins are available, and when Kontakt 3.5 or 4 is the only plugin in the VSTPlugins folder. Enabling/disabling/changing Plugin X-Ray settings in Sonar do not change the behavior, either. I'm really not sure whether it's Kontakt/Sonar/System. I'm going to pick up an upgrade to X1 (for unrelated reasons) and maybe I'll luck out and the issue will be resolved, but short of that has anyone seen similar behavior or have any ideas? Let me know if there's any other information that would be helpful. Thanks Jonathan
|
Beagle
Max Output Level: 0 dBFS
- Total Posts : 50621
- Joined: 2006/03/29 11:03:12
- Location: Fort Worth, TX
- Status: offline
Re:Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
2011/05/22 16:53:31
(permalink)
this isn't an answer for all of your problem, but Kontakt 3.5 is not compatible with 64bit, only 32bit. in fact, I don't remember the exact update version, but not all of K4 is 64bit either, IIRC. also, I don't think 3.5 is multicore compatible either. in 3.5 you might need to turn USE MULTICORE off in sonar.
|
jjloving
Max Output Level: -90 dBFS
- Total Posts : 42
- Joined: 2008/03/08 17:13:52
- Status: offline
Re:Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
2011/05/22 18:03:00
(permalink)
Thanks Beagle. When you say K3.5/4.x are not x64 compatible are you referring to Windows 7 x64? Both 3.5 and 4 have been supported on Vista x64 since release, though I believe the initial release of K4 was only supported up to Vista x64. Or is it a Sonar compatibility issue that I've missed? If it's a Sonar x64 issue it's extending to Sonar x86 with the 32-bit K3.5/4.x plugins as well. Was I just running lucky for 8 months or so - I'd like to think not! In any event, even with 4.2.2 and 4.2.3 which are officially supported on Win7 x64 the issue persists. K3.5 had previously run without a hitch in x64 until I powered up again. I'll look at the multiprocessor settings to see if something has changed, I'm not sure why it would have, but stranger things have happened I just can't wrap my head around this...generally the line reads Everything Worked>I did something stupid>Everything stopped working, not Everything worked>I unplugged/plugged in>everything stopped working Jonathan edit: There's no change in behavior after adjusting multiprocessor settings. Standalone is still working fine for both. My X1 upgrade download has finished now, I'm going to transfer that over and see if I can't pull a rabbit out of my....er, hat...
post edited by jjloving - 2011/05/22 18:16:23
|
Beagle
Max Output Level: 0 dBFS
- Total Posts : 50621
- Joined: 2006/03/29 11:03:12
- Location: Fort Worth, TX
- Status: offline
Re:Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
2011/05/22 19:39:51
(permalink)
no, I did mean with 64bit OS, but if you know I'm incorrect and that 3.5 has been compatible with x64 OS then I withdraw my statement, I wasn't 100% sure about that. do you have S8.5 or S8 or some previous version of sonar on your machine that you could try it out and see if the behavior is only in X1?
|
jjloving
Max Output Level: -90 dBFS
- Total Posts : 42
- Joined: 2008/03/08 17:13:52
- Status: offline
Re:Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
2011/05/22 19:55:50
(permalink)
The issue is with 8.3.1, I just bought the X1 upgrade today and need to transfer those files from my laptop to the other machine and then see if it persists with X1 or is limited to 8.3.1. I don't have anything older than 8 installed, and I skipped 8.5 - we'll see what X1 gives me... Thanks
|
Beagle
Max Output Level: 0 dBFS
- Total Posts : 50621
- Joined: 2006/03/29 11:03:12
- Location: Fort Worth, TX
- Status: offline
Re:Sonar 8.3.1, K3.5, K4 - Unresponsive Instrument GUI
2011/05/22 20:09:31
(permalink)
man, so sorry, I forgot which forum I was in. but yeah, that would be a good test to see if it happens in X1 as well.
|