<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 1/9/2011 2:09 PM, <span class="moz-txt-link-rfc2396E"><a class="moz-txt-link-rfc2396E" href="mailto:ronni.montoya@gmail.com"><ronni.montoya@gmail.com></a></span>
wrote:<br>
<pre wrap="">Hello, one question, if i have a big patch with a lot of subpatches,
is it possible to know which parts of the whole patch are consuming
more cpu resources?
Is something like this possible?
</pre>
<blockquote>One way I can think of that you could do this would be
to open each subpatch individually and then use the load meter
(Media > Load Meter) to see what the cpu load for each subpatch
is, though this may take a while for a lot of subpatches. You
could also estimate it by looking at where most of your audio/DSP
processing is happening. These are most likely to be the most cpu
intensive parts of your patch.<br>
</blockquote>
<pre wrap="">
thanks
R.</pre>
<pre wrap="">
</pre>
</body>
</html>