Re: [sc-users] Glitchy 3.3

[James Harkins <jamshark70@xxxxxxxxx>]

There was a bug fix for AppClock - in 3.2, if a routine running on
AppClock asked for thisThread.clock, the answer would not be AppClock.
I don't remember exactly what the answer was, but it was not correct.

http://supercollider.svn.sourceforge.net/viewvc/supercollider/trunk/build/SCClassLibrary/Common/Core/Clock.sc?r1=7589&r2=7706

It's possible this could cause a difference in behavior somehow.

Could you say more precisely what you mean by "glitchy"? Audio
dropouts? Clearly the timing of server messages is impacted somewhat
(from all the "late" messages").

You said SuperCollider.app doesn't show a significant increase in CPU
usage. What about memory? Is the server using more CPU or memory?
Other processes?

It would be helpful to have as controlled a test as possible. Reboot
the machine and run your code with no other applications launched, and
estimate rough averages for memory and CPU for both the language and
server.

Did you compile SC yourself? If so, check to be doubly sure that all
three Xcode projects use deployment style, not development. I've seen
that setting switch back to development on me sometimes after an
update. (Even if you're sure it's right, check it anyway.)

James


On Thu, Apr 30, 2009 at 2:56 PM, Neil Cosgrove
<neil_cosgrove@xxxxxxxxxxx> wrote:
>
> 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)


-- 
James Harkins /// dewdrop world
jamshark70@xxxxxxxxxxxxxxxxx
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/