Most efficient list objects
Oct 09 2013 | 9:11 pm
Hi everyone,
Finally getting my 1st big Jitter patch finalized and I'm busy trying to optimize it.
Its a simple question really.
Whats the most efficient way of sending a list of parameters into objects.
I'll use jit.bfg as an example for this one.
I can use pak offset 0. 0. 0.
or
pak 0. 0. 0.
> to
a message object with offset $1 $2 $3, bang
( i use this method so I don't have to keep using the metro with high dimension counts on the jit.bfg object)
I uploaded a small example patch to try and make my question as clear as possible.
All tips appreciated, any other suggestions more than welcome :)
- Oct 09 2013 | 10:58 pmfirst version [pak offset 0. 0. 0.] is more efficient, I believe. If you are updating with the metro anyway, no need for the bang after each offset message as far as I can tell. If you don't need to update regularly with a metro, maybe use the trigger object instead of explicit ", bang" in a message box, ie [pak offset 0. 0. 0.]->[t b l]->I know that I can turn off the metro and just bang with a message but If i do this with up to 16 parameters do's that become inefficient ?maybe use pack instead of pak, so it only updates once all 16 params are in place
- Oct 09 2013 | 11:12 pmyeah, I do more or less the same thing; jit.bfg can get pretty expensive on the cpu; what I do is simply order it so that jit.bfg gets all the messages it needs, and then I conclude with a bang. One way of doing it is with coll, which has a "bang when done dumping" outlet (the rightmost one) - that's a nice way of handling it. You could also do it with [zl group] and [zl reg], I guess, it depends on what you have upstream from jit.bfg.Oh, and if you're doing a stream of data, consider having like a metro, and then going through a zl reg, so that you can speedlim in time with the rest of your patch.
- Oct 10 2013 | 9:22 amThanks Guys ! I'll try it out straight away :)
