Cycling 74 » Topic: One Big Patch vs many small ones http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/feed Tue, 18 Jun 2013 21:44:28 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-66443 <![CDATA[One Big Patch vs many small ones]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-66443 Mon, 11 Feb 2013 01:32:09 +0000 moris526 Hi.
Im planning to merge all my patches in a big one.
What do you think of that? in terms of accuracy, memory, timing.

]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239181 <![CDATA[Re: One Big Patch vs many small ones]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239181 Fri, 15 Feb 2013 16:28:42 +0000 Lee I’d always go for more modular approach to code, rather than a monolithic approach. Internally to max I don’t think this will make anything that is a measurable difference…

]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239182 <![CDATA[Re: One Big Patch vs many small ones]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239182 Fri, 15 Feb 2013 16:32:28 +0000 dtr Depends, top level patchers (= separate patches) have their own threads. Not sure if that only makes a difference in audio DSP or other things as well.

+1 for modularity .

]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239183 <![CDATA[Re: One Big Patch vs many small ones]]> http://cycling74.com/forums/topic/one-big-patch-vs-many-small-ones/#post-239183 Fri, 15 Feb 2013 16:45:13 +0000 Lee Good point…. I’m not really sure how that comes into play for non audio stuff assell

]]>