Copy stamp a string value?
Posted 19 February 2012 - 08:20 AM
Is it possible to use the Copy SOP to stamp a string value?
My template points for the Copy SOP have a string attribute for each point, and I want a Font SOP in the copy to be stamped with each string attribute. My problem is the stamp value appears to be numeric only.
Posted 19 February 2012 - 08:29 AM
Posted 19 February 2012 - 08:47 AM
How do I assign a string value to a stamp input? When I enter "Hello" it always tries to convert it to a numeric value or gives me an error that it's not a value expression. When I look at val1 in the parameter editor, it's a float parameter.
Posted 19 February 2012 - 08:58 AM
Had to create a stamp value of $PT for the point number, and then I could use that to read the string attribute for the reference points going into the Copy SOP.
Not a very obvious way of doing, but I don't think you can stamp a string value. You can only use a numeric value as a string using stamps.
Posted 19 February 2012 - 10:10 AM
Has it been the part of H since the big bang ?
also could someone explain in simple programming terms how copy stamping is achieved ?
eg. for loop,recursion ?
Posted 19 February 2012 - 10:21 AM
senior FX TD - Rhythm & Hues
Posted 19 February 2012 - 12:09 PM
Tricks me all the time, but this one only works in DOPS.
DOP, and the Copy Data DOP.
Sadly this is the only hint in the documentation that it won't work in SOPs.
I think they're talking about stamping a 'real' string - like a filename.
In your example a stamp of $PT works just as fine.
Posted 19 February 2012 - 12:30 PM
I see what you're doing, but I need to stamp a string value (like a phrase or description).
The attached is how I ended up doing it. Using $PT on the Copy SOP so I could look up the attribute from the point templates.
Posted 19 February 2012 - 12:33 PM
We connect nodes in Houdini from the top down, but nodes are cooked from the bottom up. So in programming terms, when the Copy SOP is cooked. It then cooks it's inputs X number of times. Each time it does that it changes the value stored in the stamp variables. Allowing each input node to be changed with each copy.
Posted 19 February 2012 - 02:19 PM
Houdini ALWAYS cooks from the bottom up. Except for VOP networks they execute more like source code, but you could think of it as LEFT to RIGHT cooking order.
When you mark as SOP node blue, then that becomes the first node cooked at render time. How it works is kind of like this.
First node cooked is the blue marked node, but when it cooks it can't finish cooking. So it asks the node connected to it's input to cook. That node will cook (if it can) and return the result. Often nodes are cooked up the tree until they hit one marked RED or one with no inputs. If you know computer programming, then this type of cooking is called recursive function calls.
I should put together an AF explanation of how this works, because it would really help people to understand concepts like Copy SOP, attributes and the cook order of things. The big problem here, is that we are taught to create Houdini nodes in the reverse order that they will be cooked. So it's very confusing to understand for a beginner.
Posted 19 February 2012 - 02:35 PM
Then again, it is also the last node to cook, in a way, right?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users