The problem is... the arrays HAVE to be visible AND accessible to the mouse,
it's part of the abs. concept: you have to be able to draw your own graphics
using the mouse. Otherwise, youre solution sure works!
D.S
--------------------------------------------------
From: "Cody Loyd" <codyl...@gmail.com>
Sent: Sunday, August 01, 2010 3:21 PM
To: <pd-list@iem.at>
Subject: Re: [PD] CPU saving strategies
You can save some power by putting your arrays into tables so you
can't see them. On my system, drawing graphical elements like that
takes alot of power.
On Sun, Aug 1, 2010 at 5:35 AM, David Schaffer
<schafferda...@hotmail.com> wrote:
Hi there,
I recently built a midi CC sequencer abs. It helps me add some
timeline-based control to my patches. But I came across a problem I never
had to deal with before: CPU consumption. I realized I could'nt use more
than four instances of my sequencer before the patch would become
unmanageable (interface freezes, audio drops, and, finally... a crash) I
think this is related to the use of large size arrays. I would be
grateful
if someone out there could point me to a better data storing/ CPU
saving strategy for my sequencer, maybe data structures? Thanks in
advance.
D.S
http://www.flickr.com/photos/schafferdavid/
http://audioblog.arteradio.com/David_Schaffer/
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
