|
Hi all, I have a problem with SC3.3 over SC3.2 and it's hard to say what exactly is causing this, but it is stopping me from making the move. The issue is with SCLang which is glitchy and causing lots of lates when scheduling with the AppClock. I'm working on a large project which is 1. Regularly updating cocoa gui items. 2. Sending messages to synths running on a local server. When I start my project everything appear fine but after approx. 3 mins everything on my mac starts glitching which then leads to scheduling lates. After this, anytime I either open a new window, hover the mouse over the dock, access a file from the hard drive or do anything new it causes more glitching. I've tried using several different versions of 3.3 and also a fresh install on a different mac but nothing seems to stop this from happening. My system is as follows: 2GHz Intel Core 2 Duo MacBook 2GB Ram OS 10.4.11 SC Version 3.3 (Revision 9134) SCLang is running at about 45% CPU in the activity monitor. (This is the same in SC3.3 as in SC3.2) I'm not having any of these issues with 3.2, which is running exactly the same code with no lates what so ever. I can't include my code with this email because the project library is large at 1.9MB but I'm willing to email this on to anyone who can help. Possibly something is wrong with cocoa in sc3.3 and is demanding more CPU or memory resources than it should. Or are there any pitfalls I should avoid in SC3.3? Can anyone help please? Neil (LNX) Windows Live Messenger just got better. Find out more! |