reducing number of send and receive objects to save CPU ?
Jan 15 2022 | 10:37 am
hello, I working on a project that usually use 64 or 128 instance of the same patch. they all contain parameters that should be controlled globally. what would be the best way to save cpu : having multiple send in each subpatchs , or having multiple inlets in each subpatchs, connected to the parameters ? Or would it be better to pack all the parameters, then unpack it in each sub patch in order to have only one inlet ? I also experimented with poly~ and it works fine, although since i would like my patch to be m4live compatible , it seems like it's to be better to avoid poly~ for this reason. And even though poly~ is quite handy , in my project all the 64 instances of the patch are always activated and making sound/calculations, so i guess it's useless to use poly~ for that reason . thoughts ?