Pedro Santos

I'm trying to optimize a patch which contains a series of slab processing objects.

To optimize it, I can use the "enable 0" message to turn off a particular slab when not in use or I can use gate objects to redirect the data, bypassing the slabs not in use. These techniques can improve the performance of the patch but I would like to know if it can be further optimized.

I thought that using the previous methods would be similar to not have the slab objects in the patch, but it's not:

When I use a chain of 20 slabs (ex:sinefold), I get 45 fps

If I use a gate in the patch to bypass slabs 5-20, I get 55 fps.

If I remove the unused slabs from the patch, I get 120 fps.

Is this behaviour to be expected? I find it odd, because the slabs aren't being fed with data to be processed at all, not even a bang...

If it is to be expected, is there a workaround to remove this unused slabs processing?

Hi list.
I'm trying to optimize a patch which contains a series of slab processing objects.
To optimize it, I can use the "enable 0" message to turn off a particular slab when not in use or I can use gate objects to redirect the data, bypassing the slabs not in use. These techniques  can improve the performance of the patch but I would like to know if it can be further optimized.

I thought that using the previous methods would be similar to not have the slab objects in the patch, but it's not:
When I use a chain of 20 slabs (ex:sinefold), I get 45 fps
If I use a gate in the patch to bypass slabs 5-20, I get 55 fps.
If I remove the unused slabs from the patch, I get 120 fps.

Is this behaviour to be expected? I find it odd, because the slabs aren't being fed with data to be processed at all, not even a bang...
If it is to be expected, is there a workaround to remove this unused slabs processing?

slab-processing-optimizations

On Sep 27, 2006, at 3:23 PM, Pedro Santos wrote:

> Is this behaviour to be expected? Thanks in advance.

It is if you're using 1.5.2 or earlier. Should be resolved in Jitter 

1.5.3 and 1.6.X. As always, platform and version number is essential 

It is if you're using 1.5.2 or earlier. Should be resolved in Jitter  
1.5.3 and 1.6.X. As always, platform and version number is essential  
to any report.

slab processing optimizations