jsmackHi jsmack, thanks for the reply. But can´t I do that in the same LOP network, right? (so Solaris would and up creating all the necessary dependencies when generating the resulting usd file)
Sequences have to be combined with usd stitch clips or with a valueclip prim.
guilhermecasagrandijsmackHi jsmack, thanks for the reply. But can´t I do that in the same LOP network, right? (so Solaris would and up creating all the necessary dependencies when generating the resulting usd file)
Sequences have to be combined with usd stitch clips or with a valueclip prim.
In my understanding, I need to do that manually, and then get the stitched usd back to LOPs, right?
jsmackguilhermecasagrandijsmackHi jsmack, thanks for the reply. But can´t I do that in the same LOP network, right? (so Solaris would and up creating all the necessary dependencies when generating the resulting usd file)
Sequences have to be combined with usd stitch clips or with a valueclip prim.
In my understanding, I need to do that manually, and then get the stitched usd back to LOPs, right?
Correct, it has to be a two-step process. Mark, maybe you can clarify? Value clips are a dark art that eludes my understanding.
guilhermecasagrandijsmackguilhermecasagrandijsmackHi jsmack, thanks for the reply. But can´t I do that in the same LOP network, right? (so Solaris would and up creating all the necessary dependencies when generating the resulting usd file)
Sequences have to be combined with usd stitch clips or with a valueclip prim.
In my understanding, I need to do that manually, and then get the stitched usd back to LOPs, right?
Correct, it has to be a two-step process. Mark, maybe you can clarify? Value clips are a dark art that eludes my understanding.
The (two step) process is ok for me, but It would be really usefull if we could set up this kind of info in the network (with nodes) and solaris would end up building the “correct” usd file. This “two-step” process makes the workflow not so procedural when we are getting geo from SOPs, because we must bake the sequence of usds before rendering (or adding switchers in the network) to test the render befor creating the “final” usd file.
jsmackguilhermecasagrandijsmackguilhermecasagrandijsmackHi jsmack, thanks for the reply. But can´t I do that in the same LOP network, right? (so Solaris would and up creating all the necessary dependencies when generating the resulting usd file)
Sequences have to be combined with usd stitch clips or with a valueclip prim.
In my understanding, I need to do that manually, and then get the stitched usd back to LOPs, right?
Correct, it has to be a two-step process. Mark, maybe you can clarify? Value clips are a dark art that eludes my understanding.
The (two step) process is ok for me, but It would be really usefull if we could set up this kind of info in the network (with nodes) and solaris would end up building the “correct” usd file. This “two-step” process makes the workflow not so procedural when we are getting geo from SOPs, because we must bake the sequence of usds before rendering (or adding switchers in the network) to test the render befor creating the “final” usd file.
It has to be two step because creating the manifest or stitching requires opening all of the frames, whereas the usd rop operates frame-by-frame.
mtucker
If you want a separate USD file per frame, value clips is the only way to combine them back into a single animated clip at composition time. I would like at some point to have the Value Clip LOP capable of doing the “stitching” step automatically as part of the USD ROP save step, but that's probably a ways off.
If you don't specifically want a separate USD file per frame, you can create a massive single USD file which is very efficient to read in (USD only loads the data for the time samples that it needs at any given time). This is much easier than working with value clips.