Hello list,
I don't work with GEM so regularly, so I had a question regarding
independent processing chains.
I'm showing different [shpere]s, and wanted to do individual
transformations on each, such as [color] and [translateXYZ]. Until now I
used an individual [gemhead] for each [sphere], but I just learned that it
can also be done using one common [gemhead] and [separator]s instead.
I would like to learn, what are the pros and cons of each solution? Which
solution is more efficient and for which reasons?
Plus: [color] and [colorRBG] seem to have the same function. Besides the
extra inputs, is there any difference/advantage in one object instead of
the other?
Best,
jmmmp
The [gemhead] also controls the order of execution of chains while [separator] inherits that from the [gemhead]. One giant chain off a single [gemhead] with a bunch of [separator] will not give the same results as a bunch of different [gemhead] with explicit order of execution. There is some overhead with [separator] that can become non-trivial if enough of them are used (like in a loop).
One thing that helps is to always give each [gemhead] a value for render order. This will avoid, or at least help understand, many problems with how rendering occurs.
On Sat, Dec 5, 2015 at 9:15 AM, João Pais jmmmpais@gmail.com wrote:
Hello list,
I don't work with GEM so regularly, so I had a question regarding independent processing chains. I'm showing different [shpere]s, and wanted to do individual transformations on each, such as [color] and [translateXYZ]. Until now I used an individual [gemhead] for each [sphere], but I just learned that it can also be done using one common [gemhead] and [separator]s instead.
I would like to learn, what are the pros and cons of each solution? Which solution is more efficient and for which reasons?
Plus: [color] and [colorRBG] seem to have the same function. Besides the extra inputs, is there any difference/advantage in one object instead of the other?
Best,
jmmmp
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
My examples are very simple, so there won't be any problems with loops and
no rendering orders have to be calculated.
Do I take from your comment that using [separator] does add more overhead
than [gemhead]?
For my simple case, it seems that using both of them has the same result.
But I would want to know what is exactly the difference.
Best,
Joao
The [gemhead] also controls the order of execution of chains while
[separator] inherits that from the [gemhead]. One giant chain off a
single >[gemhead] with a bunch of [separator] will not give the same
results as a bunch of different [gemhead] with explicit order of
execution. There is >some overhead with [separator] that can become
non-trivial if enough of them are used (like in a loop).
One thing that helps is to always give each [gemhead] a value for render
order. This will avoid, or at least help understand, many problems withhow rendering occurs.
On Sat, Dec 5, 2015 at 9:15 AM, João Pais jmmmpais@gmail.com wrote:
Hello list,
I don't work with GEM so regularly, so I had a question regarding
independent processing chains. I'm showing different [shpere]s, and wanted to do individual
transformations on each, such as [color] and [translateXYZ]. Until now
I used an >>individual [gemhead] for each [sphere], but I just learned
that it can also be done using one common [gemhead] and [separator]s
instead.I would like to learn, what are the pros and cons of each solution?
Which solution is more efficient and for which reasons?Plus: [color] and [colorRBG] seem to have the same function. Besides
the extra inputs, is there any difference/advantage in one object
instead >>of the other?Best,
jmmmp
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
One use for [separator] is to texture the same image or video to multiple surfaces. Another is to control the center position of multiple geos that are offset from that center.
On Sunday, December 6, 2015, João Pais jmmmpais@gmail.com wrote:
My examples are very simple, so there won't be any problems with loops and no rendering orders have to be calculated.
Do I take from your comment that using [separator] does add more overhead than [gemhead]?
For my simple case, it seems that using both of them has the same result. But I would want to know what is exactly the difference.
Best,
Joao
The [gemhead] also controls the order of execution of chains while [separator] inherits that from the [gemhead]. One giant chain off a single [gemhead] with a bunch of [separator] will not give the same results as a bunch of different [gemhead] with explicit order of execution. There is some overhead with [separator] that can become non-trivial if enough of them are used (like in a loop).
One thing that helps is to always give each [gemhead] a value for render order. This will avoid, or at least help understand, many problems with how rendering occurs.
On Sat, Dec 5, 2015 at 9:15 AM, João Pais <jmmmpais@gmail.com javascript:_e(%7B%7D,'cvml','jmmmpais@gmail.com');> wrote:
Hello list,
I don't work with GEM so regularly, so I had a question regarding independent processing chains. I'm showing different [shpere]s, and wanted to do individual transformations on each, such as [color] and [translateXYZ]. Until now I used an individual [gemhead] for each [sphere], but I just learned that it can also be done using one common [gemhead] and [separator]s instead.
I would like to learn, what are the pros and cons of each solution? Which solution is more efficient and for which reasons?
Plus: [color] and [colorRBG] seem to have the same function. Besides the extra inputs, is there any difference/advantage in one object instead of the other?
Best,
jmmmp
Pd-list@lists.iem.at javascript:_e(%7B%7D,'cvml','Pd-list@lists.iem.at'); mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2015-12-06 17:16, Chris Clepper wrote:
One use for [separator] is to texture the same image or video to multiple surfaces.
you *can* do this with multiple gemheads as well (though it requires explicitness, whereas [separator] just does it for you)
Another is to control the center position of multiple geos that are offset from that center.
i see [separator] as a way to *group* geos. if you ever want to apply a single transformation to all geos in the group (though probably not all geos in the world), [separator] is the way to go. (this is just a more generic way of saying what chris said.)
my usual example is a "hand": you can move the fingers (somewhat) independently, but if you move the entire hand the fingers will move along; hence they form a "unit" and i use [separator]. conversely, two "people" can move totally independently, so i'd use multiple gemheads...unless i'm modelling a star system, were humans and midgets are sub-elements of entire planets.
as for overhead: start worrying about that once you do hit a performance boundary, not before.
fgmasdr IOhannes
-
Chris Clepper -
IOhannes m zmoelnig -
João Pais