Cycling 74 » Topic: finding bottleneck & benchmarking of a big patch http://cycling74.com/forums/topic/finding-bottleneck-benchmarking-of-a-big-patch/feed Wed, 19 Jun 2013 12:20:56 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/finding-bottleneck-benchmarking-of-a-big-patch/#post-46922 <![CDATA[finding bottleneck & benchmarking of a big patch]]> http://cycling74.com/forums/topic/finding-bottleneck-benchmarking-of-a-big-patch/#post-46922 Tue, 01 Dec 2009 09:14:59 +0000 Julien Bayle hello,
I just finished (at last…) the protodeck controller interface.
it works.
I’m sure it could be faster (by the way, it could be enough now)

so, I’d like to dig a bit into how to benchmark his own patch.
How could I do that?

I’m sure there are redundant bangs or things like that, you know (I’m sure)

any ideas, help would be appreciated :)

Julien

]]> http://cycling74.com/forums/topic/finding-bottleneck-benchmarking-of-a-big-patch/#post-168729 <![CDATA[Re: finding bottleneck & benchmarking of a big patch]]> http://cycling74.com/forums/topic/finding-bottleneck-benchmarking-of-a-big-patch/#post-168729 Tue, 01 Dec 2009 13:25:25 +0000 Julien Bayle I didn’t put some examples.

why about routing the WHOLE midi flow directly to a lot of midiselect vs midiselect progressively the flow?

why about segmenting in a lot of subpatch ?

why about using a lot of send/receive objects ?

for these examples, I found some differencies using this or that method.

]]>