NVIDIA- OpenUSD Certification Time Codes and Time Samples @a16zspeedrun @NVIDIAOmniverse

Ajouté : 2026-05-07

[00:00:00]We are live.

[00:00:11]Check check check check.

[00:00:14]Check check check check check.

[00:00:39]done. All the checks are complete. We can start.

[00:00:44]Oh, finally.

[00:00:47]So, welcome back.

[00:00:51]How we doing? How we doing?

[00:00:53]>> We doing great. We doing great. So today I think we are going to focus on time code and time samples.

[00:00:59]>> Yeah. Yesterday uh do you just want to give a recap of what you have done till now?

[00:01:05]>> Yeah, I think till now we have completed stage prims and property and yesterday we focused on relationships specifically how relationships are used for different prims and how can you use relationship to create linkage between different kind of prims and the properties that you have. Uh I think that will cover it right or do you want me to add something else or if I have missed something?

[00:01:31]>> Yeah. So basically what uh we have completed till now is the basics of setting up a stage in open USD. Uh what are prims and how do they work in a scene description.

[00:01:44]uh what are the properties those prims have and uh uh in those properties what are attributes and what are relationships how they differ from each other. Attributes are more of uh uh you know uh about the prim like maybe the color, the shade, the lighting angles they reflect of stuff like that. And relationships are basically used to establish the linkage between uh those prim um stuff like that. Maybe to group different prims together uh in a you know uh in in a single group which uh behaves like oneself. uh for example a wheel and a uh a windshield and a wheel can be grouped under car. So we we're going to basically use a relationship to group those uh prims inside that another prim hierarchically.

[00:02:52]So and today now we're going to just focus on time codes and time samples.

[00:02:59]So I think we can get started.

[00:03:03]Yeah.

[00:03:04]>> Okay. So, time codes and time samples.

[00:03:07]In this lesson, time code and time samples uh show us how to set up animation in a stage using OpenUSD.

[00:03:15]So, in this lesson, we will basically set start and end time codes for a stage. Okay. Learn how to set start and end time code metadata for a USD stage.

[00:03:27]establishing a timeline that forms the foundation for animated scenes.

[00:03:34]Okay, it's now over here we're going to set time samples on attributes. Okay, so we're going to basically set time samples on attributes.

[00:03:45]Gain the skills to set the time samples on individual attributes allowing us to animate specific properties of prints over time. Okay. So basically I think we're going to set particular values as time samples on different attributes and we're going to let open USD animate uh the properties or let yeah it's basically going to animate the specific properties of prims over time on that stage.

[00:04:18]So over here time code uh what does it say? One sec.

[00:04:28]Time code is a unitless point in time.

[00:04:31]Um like a frame with units derived from the stage.

[00:04:37]Unitless point in time.

[00:04:42]Okay.

[00:04:45]Do you want to add something on this or >> No, I think let's like we can go ahead and see what it says now.

[00:04:54]>> Okay. And then time sample refers to individual time varying attribute values. Oh my god, fast.

[00:05:05]Refers to individual time varying attribute values in USD. Time sample refers to individual time.

[00:05:13]Individual time period.

[00:05:17]What does that mean?

[00:05:19]>> So I think I would say that okay on each and every time stamp the attribute value might change you know. So for example, we have a clip of 5 seconds and that clip is trying to render a ball and that ball is trying to change a color from red to blue.

[00:05:40]>> Mhm. So at at let's say on the first frame in the first 5 seconds or 4 seconds the the attribute val values are set to uh maybe the spear the size of the spear is four and on on the 10th second the size of the sphere is eight. So in that scenario we can see that okay the there there is some kind of change in uh dimensions or something of the sphere and that's how we we would render it. I think that's what it is trying to say.

[00:06:13]>> Okay.

[00:06:17]Attributes can have m multiple time samples. Okay. One attribute can have multiple time samples. Miping time codes to data type values for animation over time.

[00:06:29]Okay.

[00:06:32]>> So an attribute can have so have multiple time samples. So yeah, it means that okay uh an attribute can be attached onto different time points. For example, I would say if you keep the attribute same >> let's say let's say you have uh wait this is an attribute like this is an eBay card and this is an attribute of color or something right?

[00:06:58]>> Mhm. and this this attribute.

[00:07:01]So on on the first frame, >> wait, wait, wait one second. I'm going to Yeah. No.

[00:07:08]>> Okay. So on the on the first frame, the attribute is Okay, we need to show the card, >> right? And then on on a second frame, there are no attributes.

[00:07:18]>> Uh-huh.

[00:07:19]>> So what is it now? It's hidden.

[00:07:21]>> Yeah, it's hidden.

[00:07:22]>> Right. And on the fifth frame, the attribute we can you can attach the same attributes. Now you can see that the the the fra the frame is rendering the same point.

[00:07:31]>> So I think we can map the same attribute to multiple time frames over the timeline >> and in that scenario that's how we can do the animation rather than that's what it's trying to say over there I would say.

[00:07:47]>> Okay.

[00:07:50]Yeah. I think this is we we're going to get more clarity once we Okay. What's the third point? It's saying time code is oh okay never mind in open USD time code and time samples. So time code represents a point in time for quering or authoring time varying data in USD time represent a point. Okay. And time sample a time samples is a time value pair that defines an attributes value at a specific time. Okay. So it's like a dictionary where it's defining the attributes value with the key being the time like the time sample being >> yes that's what I said right that's what I said like basically you are on a time on a scale of 1 to 10 >> you're going to map this attribute let's say this is an attribute >> to that time frame and then you can move that attribute at anywhere >> so the whole so you can map the whole time uh time sample onto the same attribute >> and it's not going to change but you can change other attribute. Let's say there there is there is this card that is going to come up like this on some frame and then it's going to go down and that is what uh basically the attribute would be at that point on a different time frame.

[00:09:05]>> Okay. A time sample >> yeah a time sample is a time value pair that defines an attribute value at a specific time. Cool. Uh so in open USD time code and time sample are two important concepts that enable us to work with animation and simulations in USD. Okay.

[00:09:22]Time code is a point in time with no unit assigned to it. Time code is a point in time with no unit assigned to it.

[00:09:32]>> It's just a point in time.

[00:09:34]>> Yeah. Like you know time is relative.

[00:09:37]>> Einstein strikes again.

[00:09:41]>> [ __ ] You can think of these as frames whose units are derived from the stage.

[00:09:46]You can think of these frames whose units are derived from the stage.

[00:09:59]>> Complicated but the god is with us.

[00:10:19]think of time codes as tick marks on a ruler that doesn't have inches or centm written on it. Okay, so basically imagine you have a ruler with 60 lines, little lines, text but no labels. The text time code, these are just positions. line 30 is exactly halfway. You don't know that's 30 seconds, 30 frames or 30 minutes. Oh, okay. Okay. Okay. Okay. So, there it has no specific unit or like metric to attach to it.

[00:10:54]Got it. Um, time samples refers to individual time varying values associated with an attribute in USD. Time samples refers to their individual time varying values.

[00:11:14]Okay, I got it. I think I understood what this is.

[00:11:19]So basically time codes are those tick marks on the frames and then time samples refers to the individual time varying values.

[00:11:31]So like multiple tick marks for an associated attribute are going to be called a time sample for a individual.

[00:11:39]Yeah.

[00:11:40]>> Similar to like if you put effects in an iMovie, right? When you put the frame and then in the timeline you can put >> maybe have you used Adobe Flash?

[00:11:51]>> No, I I have used iMovie.

[00:11:54]>> I have done Adobe Flash animation classes when I was a kid.

[00:11:59]>> My god. And I think I remember what this is saying. So basically in Adobe Flags, is it you? Steve Jobs, is it you?

[00:12:09]>> [ __ ] you.

[00:12:11]>> So basically what happens is if you define like on a frame, if you define this like a circle, right?

[00:12:18]>> Mhm.

[00:12:19]>> And then let's say this is on 1 second like first second, right?

[00:12:25]>> Mhm. And then on the second you define uh like the same thing you define as a square like on the same frame.

[00:12:35]So there has to be some sort of thing. So like let this be the first frame let this be the second frame.

[00:12:44]Right?

[00:12:45]>> But for this circle to become into this square there needs to be some sort of animation that needs to happen. That that that is what we call I think we that that's where we will put attributes right because the attributes are going to change.

[00:13:01]>> Mhm.

[00:13:02]>> Yeah. Attributes are going to change. So it's going to USD is going to perform the animation on its own. We don't have to do anything. So this >> you're going to see a sphere like a circle becoming a square in real time.

[00:13:16]>> That's what I studied in um Adobe Flash.

[00:13:21]Bro, I should Yeah, I'll do that later.

[00:13:27]Okay.

[00:13:31]Time samples refers to individual time varying values associated with an attribute in USD. Okay.

[00:13:38]Each attribute can have a collection of time samples. Each attribute can have a collection of time samples. Correct.

[00:13:45]That map time code to attribute data type values. Correct. So one time code.

[00:13:51]So basically in this in an attribute um sorry.

[00:14:02]So let this be the dictionary of that time sample.

[00:14:08]And over here the this would this is going to be the time code right.

[00:14:22]>> Mhm.

[00:14:23]>> Over here.

[00:14:28]And this is going to be the attribute value like what the attribute is at that point.

[00:14:42]>> Right. And so this is going to be called a time sample as a whole.

[00:14:48]>> Mhm.

[00:14:49]>> Right. This is what it means I guess.

[00:14:59]Okay. Attribute can have a collection of time samples that map time code attributes data type values allowing for animation over time for a reminder of the purpose of attributes. Please review introductory lesson. Uh okay. How does it work in USD scene? The time code coordinates or time code ordinates of all time samples are scaled to seconds based on time codes per second.

[00:15:31]Metadata value data about prims and properties that guides USD's behavior.

[00:15:38]Metadata is about is data about prim and properties that guides USD's behavior but is not renderable in content scene.

[00:15:45]Okay.

[00:15:47]Metadata values defined in the root layer. This allows flexibility in encoding time samples within a range and scale suitable for suitable for the application while maintaining a robust mapping to real world time for playback and decoding.

[00:16:04]Okay, this allows flexibility in encoding time samples.

[00:16:10]Time codes per second.

[00:16:14]Bro, do you understand this?

[00:16:16]Time codes per second. How about what does this say? It's going to say something right now.

[00:16:21]>> This says metadata.

[00:16:26]God mode on.

[00:16:29]>> Mhm.

[00:16:30]>> Then this is a blank ruler. Ruler is the stage. Uh the tick these are position 930 is exactly halfway but you don't know that 30 seconds 30 frames. The stage acts as the label. If you tell the stage each tick represents one frame at 30 frames per second. Then time code 30 is equal to 1 second. Time code 60 is equal to 2 second. Okay.

[00:16:52]So the stage and the time code are dynamic.

[00:16:58]>> It makes your animation scalable if you animate a ball to bounce at time code 24. Later you decide to change your project from 24 fps to 60 fps. Time code says time code stays at 24. You don't have to rewrite your animation. the stage simply calculates the fast how fast playhead moves through those ticks.

[00:17:21]Yeah. See this is what I was talking about over here with Adobe Flash.

[00:17:26]>> Mhm.

[00:17:26]>> That it basically recalculates how fast player head moves through those sticks.

[00:17:31]>> So, so what does time code per second means? Because I think uh it said that time time sample or time code doesn't have a unit. Yes, it says the time code is a point in time with no unit assigned to it. Exactly.

[00:17:43]>> And then time code per second is like okay the frame is in per second that's what it meant right >> where where does it say time is in per second >> like it says time codes per second this one this variable >> oh this one wait I have not put that in right uh as of right now wait >> I was reading the earlier one second key terms in simple English time code location on the timeline >> frame Frame 10.

[00:18:13]>> Yeah, that's what I said. Frame 10.

[00:18:14]>> Yeah. The value at that location. At frame 10, the ball is 5 units high.

[00:18:20]Okay. Time sample is the value at that location.

[00:18:24]>> Yes.

[00:18:24]>> Oh, so basically this this is going to be value.

[00:18:30]>> Yes. Because it says that, right? It was a dictionary key value pair.

[00:18:34]>> Yeah. Time code and value.

[00:18:36]>> So time code is key and value. we have.

[00:18:42]>> Yeah. So basically this is going to be a time sample where if this is one and the value is something over here like uh bounce or something right for a ball and then two is something else. So basically this is going to represent like a total time sample. Got it.

[00:19:18]But yeah.

[00:19:23]Okay. Now let's see time codes per second. The speed limit.

[00:19:31]The speed limit set on stage that tells the computer how many ticks happen in one real world second. Okay.

[00:19:38]Time codes per second over here just means like in 1 second how many ticks are going to happen in 1 second. And what is a tech? How these are just positions. Line 30 is exactly half frame. But you don't know if that's 30 seconds, 30 frames or 30 minutes.

[00:19:57]The ruler the stage act as a label. If you tell the stage each stick represents one frame. Oh, okay. So you can predefine how much Oh. Oh. Okay. Okay.

[00:20:06]Okay. Okay. Makes sense. Makes sense.

[00:20:08]>> Mhm.

[00:20:09]>> Then what is time code per second then?

[00:20:13]>> Oh, the speed limit set on >> bro. The speed limit. Yes. In a in 1 second, how many time codes are happening?

[00:20:21]>> Oh, I see.

[00:20:23]>> So in USD scene, the time code ordinates of time samples are scaled to seconds based on the time codes per second.

[00:20:29]Metadata value defined in the root layer. Got it. So this is going to be defined in the root layer.

[00:20:36]How many ticks are going to take place in 1 second? Got it.

[00:20:42]>> Everything is getting slowly defined in the root layer, bro. The root layer is going to be really crazy.

[00:20:50]>> Yeah.

[00:20:51]>> Everything like relationships, attributes, time samples.

[00:20:57]>> These are like the building blocks of US Open USD, right? So we are just you know going step by step to see how we we are going to like align and put everything all together into a system >> to maybe create a render or something.

[00:21:15]>> Mhm.

[00:21:18]>> Okay.

[00:21:20]So this allows flexibility in encoding time samples within a range and scale suitable for the application. This allows flexibility in encoding time samples within a range and scale suitable for the application while maintaining a robust mapping to real world time for playback and decoding.

[00:21:38]Okay.

[00:21:41]For example, if the root layer has time codes per second equal to 24.

[00:21:46]Okay.

[00:21:48]>> It's going to >> 24 24 ticks per second. Like 24 time codes per second >> per second. Okay. Okay. Okay.

[00:21:56]>> A time code value of 48 would correspond to 2 seconds. Yes. Okay. Time code value of 48 would correspond to 2 seconds.

[00:22:05]>> Wait, how?

[00:22:06]>> Got it, >> bro. Because 48 divided by 2 24 is two, >> bro. It's simple. Time codes per second.

[00:22:16]>> Oh, okay. Okay. Okay. Okay. Okay. Okay.

[00:22:18]Okay.

[00:22:19]>> Let me explain it to you, you dumb [ __ ] Um okay so in uh the time code per second is defined as 24 right which means in 1 second uh in a one real world second there are going to be 24 ticks or time codes in 1 second. So for if a time code is 48 right this means this is showing the data for 2 seconds two real world seconds do you understand? H yeah I get it now I get it because it says 24 so we do 48ID by 24 and then we get 2 seconds what correspond to 2 seconds for real time after a time code zero what does this of the real time after the time code zero what does this mean the last line >> time code zero oh time code zero the first frame time code 0 >> 0 1 and two >> yes 0 1 2 so time code zero would be would be like uh 2 seconds right that's how we define it it says over there time code 30 is 1 second time code 60 is 2 seconds so if we say time code zero >> then wait what >> oh wait I think I understand I think over here there is no like for zero second like it's going to be zero and one so like it's going to be 24 for 0 and Wait for 24 it's going to be you you're saying zero.

[00:24:20]>> Yeah.

[00:24:24]>> Because at initially when there's no time like like when the when no time has elapsed then also time code is going to be 24 >> 30 frames. So so over here 48 means 48 frames per second right? Wait, let me >> Yeah. Yeah. It says 48 frames per second. So, so if if you look at the some look look into the Gemini one, it says at the stage act as the label, right? Each tick represents one frame at 30 frames per second, right? So, at time zero, it would be the 48 frame.

[00:24:59]It would have 48 frames, right? Or it would have what?

[00:25:04]Wait.

[00:25:11]Imagine you're looking at a long strip of movie film. The strip, the stage.

[00:25:15]This is your entire animation.

[00:25:18]Okay. The text. These are little individual frames printed on the film.

[00:25:24]The projector time code per second. This is the speed of the machine that plays in the film.

[00:25:30]Yeah. D math. If the machine is set to swallow 24 frames every second, you want to know where you are, you have reached for frame number 48. Time code value 48. The machine eats first 24 frames. 1 second has passed. Machine eats next 24 frames. Another uh one has passed. So, okay, why not just say 20 uh 2 seconds? We don't write 2 seconds because you might change the projector later if you decide the movie looks too choppy and change the speed to 48 frames per second.

[00:26:10]>> The frame 48 is now one second.

[00:26:14]>> Yeah. Yeah. Wait, I'm going to ask.

[00:26:22]Bro, >> bro, >> what?

[00:26:28]>> My system froze again. The hell? What is Why the hell is my system freezing again? Again, I think I do have some services that are breaking my system up.

[00:26:44]I would have to take a look. I'm going to restart again.

[00:26:48]>> Yeah. Okay. The hell?

[00:26:53]Do it.

[00:27:24]Yo guys, how's it going? Say hi in the chat. This is going to be right back.

[00:27:36]So over here time samples are used to store varying data for attributes such as position, rotation or material properties. When an attribute is valued at specific time code, the value is linearly interpolated from the surrounding time samples allowing for smooth animation playback.

[00:28:00]Ah I see interpolation time samples are used to store time varying data for attributes.

[00:28:11]Okay. So different uh like an attribute will have different position at different times, different rotation at different times and material properties like different sort of reflections and material shading properties at different times.

[00:28:30]So when an attribute is evaluated as a specific time code on a particular specific time code. Oh, one second is out the back.

[00:28:59]I'm excited about getting to the examples today because we have a we have our notebook working for the render as well.

[00:29:12]And we have got some pretty amazing research papers to read video generation in robotics prior workshops.

[00:29:25]What h time samples are used to store. Okay, we did this. When an attribute is evaluated at a specific time code, the value is linearly interpolated from the surrounding time samples allowing for smooth animation playback.

[00:29:48]Got it.

[00:29:53]Okay. Cube dot get display dot color attribute dot get time samples.

[00:30:23]Uh-huh.

[00:30:29]Below is example of how we can get or set time samples in Python. First, we'll be getting time samples of the display color on cube prim.

[00:30:43]This method returns a vector of the time code coordinates.

[00:30:49]time code ordinates at which time samples are authored for given attribute. Lastly, we are setting translation value of sphere at specific time code. This method says the time sample value of attribute at specific time code.

[00:31:06]Uh cube dot get display color attribute dot get time samples returns author time samples. Okay.

[00:31:19]Cool.

[00:31:21]Lastly, we are setting translation value of sphere at a specific time. Go to this method. Okay. Returns author time samples cube.

[00:31:31]Okay. Wait. I think he's here.

[00:31:43]Yeah.

[00:31:45]One second. Let me put you back in the stream.

[00:31:56]Yeah, that might be causing those issues.

[00:32:04]>> Mhm.

[00:32:08]>> Or let me You know what? I I'm paying I'm paying for cloud code, right? Let me let me pull that thing up, >> bro. to do it after the stream.

[00:32:16]>> Yeah. Yeah. I was just going to do it in background. Anyways, so where were we?

[00:32:22]>> Yeah, we were just watching this.

[00:32:25]Uh we did this and then we're talking about time samples are used to store time varying data for attributes such as position, rotation or material time properties. When attribute is evaluated at specific time code, the value is linearly interpolated from the surrounding time samples. When an attribute is evaluated at a specific time code, the values okay. So basically, if there are let's say 1 2 3 4 as time codes and we specifically stop the frame between 2 and 3, right? So the value is basically going to be linearly interpolated. This is going to be the algorithm that's going to be used for animation on the stage.

[00:33:15]>> What does description stage >> like what does it mean in simpler way simpler terms? Wait, I understood that.

[00:33:24]>> I think let's say this is the frame like this is the timeline, right?

[00:33:43]>> Mhm.

[00:33:44]>> Let's say this these are the frames, right?

[00:33:51]Okay.

[00:33:56]>> Okay.

[00:33:58]Now over here one [ __ ] bro.

[00:34:20]1 2 3 like an array.

[00:34:24]>> Yeah. So basically if they uh ask us um one second this is two this is three this is four whatever right and I specifically stop the anim like I stop the frame in this part right in the middle let's say so it's saying how is going to like a a prim going to look like if a prim was a sphere in frame two and a square in >> frame three. Right?

[00:35:00]>> How is it going to look like when if I stop it right in the middle of these two frames?

[00:35:06]>> H >> it's going to look something like this because it is going to be translating to like a sphere is going to be translating from a sphere to a cube, right?

[00:35:16]>> Mhm. Mhm.

[00:35:17]>> So the what this is basically saying is when an attribute attribute is evaluated as at a specific time code >> the value is linearly interpolated from the surrounding time samples >> the surrounding time samples over here like this. This is the attribute value over here and this is the attribute value over here.

[00:35:39]>> So that is going to be allowing for smooth animation playback.

[00:35:45]the animation playback that we are looking over there >> and I think we're going to see some really good examples in our notebook once we start running these.

[00:35:56]>> That's what I feel.

[00:35:58]>> Makes sense. Makes sense.

[00:36:01]H >> nice.

[00:36:06]Okay.

[00:36:09]Now let me below is an example of how we can get we can get or set time samples in Python.

[00:36:20]First we're getting the time samples of display color on a cube prim right.

[00:36:26]>> So that is done. This method returns a vector of time code ordinates.

[00:36:33]This method okay returns a time code ordinates at which the time samples >> displayed.

[00:36:43]>> Yeah, display color attribute. Uh and then they're using get time samples function over here.

[00:36:49]>> Okay.

[00:36:50]>> So that's basically going to return the time samples. uh it's going to return a vector of time code or coordinates at which time samples are authored for given attribute.

[00:37:05]>> Lastly, we are setting a translation value of a sphere >> at a specific at a specified time code.

[00:37:13]This method sets the time sample value of the attribute at the specific time code.

[00:37:20]This method sets the time sample value of the attribute at a spec. Set the time sample value GF ve 3D. Okay, so this is going to be RGB again. I think >> uh at a specific time code sphere xform API.transit. I think I'm going to have to ask this explanation.

[00:37:59]Guys say hi in the chat. There are six guys, six people watching this.

[00:38:04]>> Uh if Karango, if you are watching, please send a hi.

[00:38:10]>> He's your He's your buddy.

[00:38:12]>> Yeah, he's my buddy. He's going to be a millionaire soon.

[00:38:17]You like us?

[00:38:21]>> Like us. Okay.

[00:38:23]>> Same private jets. Same private jets.

[00:38:26]>> Same.

[00:38:28]>> Nice.

[00:38:29]>> Okay.

[00:38:31]Okay. Uh, this code shows the two sides of working with animation in OpenUSD. Reading existing animation data and writing new animation data. Okay. Reading animation data. What it does? It asks the computer at which specific frames did someone change the color of this cube. Okay, the result it returns a list of time codes frame numbers. Dumb analogy. Imagine a flip book where only some pages have drawings on them. This command gives you a list of the number of pages where uh that actually have link ink on them.

[00:39:06]Okay, got it. Got it. So this is basically giving us the dictionary for >> uh when the colors are actually visible, right?

[00:39:19]>> Mhm.

[00:39:21]>> Okay. Writing animation data. This is how you tell the object where to be at a specific moment. So sphere xformapi settrate the move command.

[00:39:34]GF vec 3D the destination it tells the sphere to go to these coordinates GF ve okay move this is the this is the ve this is the thing we were using to move over >> the x y or z axis for a whatever object >> mhm >> and then time equals to us dot time code 30 usd dot time code 30 the appointment time it says Don't just move there now.

[00:40:05]Make sure you are at these coordinates exactly when the timeline hits the frame 30. Okay, got it.

[00:40:16]Oh, okay. Okay. Okay.

[00:40:21]And then Okay, I think I get what this code is doing a little bit.

[00:40:28]Okay, I think we can move to our notebook.

[00:40:33]Mhm.

[00:40:35]>> Let's create a USB SH to server blah blah blah. Okay, let's see the magic over here now. Let's go. Oh, we could have just read this also.

[00:40:45]I think this is the same thing.

[00:40:47]Mhm.

[00:40:50]>> Okay, let me run this.

[00:40:52]>> Okay.

[00:40:55]Import necessary modules. Create a new USD stage. Define a transform X form primitive. Define a sphere primitive as child transform. Yes. Define a blue cube as background prim display assets.

[00:41:10]Okay. So this is our thing. Oh [ __ ] That is awesome.

[00:41:18]>> Damn.

[00:41:21]So this is on a time frame.

[00:41:23]>> No, this is not on this. We have not done the time frame stuff yet. We have just defined a new stage file called time sample code or time sample USDA.

[00:41:34]File path is assets time code sample USDA.

[00:41:41]Uh stage is USD.stage create new stage like for the file path. So this uh file is used to create the new stage.

[00:41:51]>> Mhm. And then we have defined a transform primitive at world. So remember how we were doing it in prim.

[00:42:00]>> Yeah.

[00:42:01]>> So we have just use the xform usdgm.xform API to define this uh stage.

[00:42:10]>> Mhm.

[00:42:11]>> And then we define a sphere primitive as child of the transform at world sphere.

[00:42:16]So this is how we define the child. Uh you know sphere is USDGM.phere equals to usgm.spere.

[00:42:29]It's going to be stage comma world.getpath.append path sphere.

[00:42:38]This is how this is the typical syntax for defining a like an object as a primitive as a child of a stage.

[00:42:46]And then we define a blue cube as background prim.

[00:42:51]So this is the blue cube over here that we seeing as the background prim box is usgm.cube usgm.cube.define >> stage uh comma world dot getpath append backdrop. So this they are going to use backdrop as its name. I think that this is because backdrop is something that is already defined in this USDG.

[00:43:16]Cube API.

[00:43:18]Um, yeah, I'm still a little bit confused about how that API operates exactly because they just name stuff over here like backdrop and it just magically becomes like a background thing.

[00:43:32]>> I think all of this is predefined in these APIs. We still need to look at those API docs, bro.

[00:43:40]USD GM API docs, bro. There was a list the core schema for defining interchanging.

[00:44:01]I don't know where the [ __ ] USD go and then cube X form define get Get schema static define get.

[00:44:36]Okay.

[00:44:39]Okay.

[00:44:41]So what over here what h what's happening is they set it for one. So box dot get display color attribute set this to 0, 0, 1. Cube xform API equals to usgxform common API. What does this mean, >> dude? That that's just uh a wrapper. It wraps your box into the XOMO API, I think.

[00:45:12]>> Okay.

[00:45:12]>> Yeah, it's a wrapper.

[00:45:14]>> And this is I think this is where we are defining uh >> so once we once you wrap the box in a wrapper then you can translate it over an axis. That's how it does it. So X for common API gives you gives you the power to you know translate over an axis. That is one of the feature of the X X form common API.

[00:45:36]>> Mhm.

[00:45:37]>> It it is usually used for you know uh transitions as we as we do remember in our initial uh streams when we went through >> the API it is usually used for geometric uh uh translation and all those kind of things.

[00:45:52]>> Yeah. Let me just be sure.

[00:45:54]>> Mhm. And oh my god.

[00:46:43]The code is essentially building a backdrop for your scene. You can think of it as a hanging Lu. Okay, we know this backdrop. Okay, painting it. Oh, this is just setting the color as RGB.

[00:46:54]So, RGB, this is blue. Oh, okay. Okay.

[00:46:58]Okay. And then uh cube xform API equals to us gome.xform common API box.

[00:47:06]Uh where is that?

[00:47:12]Stretching it into a wall. Cube X form API dot set scale GF ve 3F plane that take that cube and squash it. What the hell?

[00:47:21]By making it five units wide the tall units uh point one thing you have turned 3D block into a flat white panel as a piece of plywood. Okay. Pushing it back plane move this panel 2 units away from the camera.

[00:47:35]You move Z equals to Oh, we can do all this [ __ ] as well just using this cube X form API dot set translate of GFE 3D.

[00:47:46]>> Mhm.

[00:47:46]>> Create a cube, paint it blue, flatten it into white wall and side it into the background at as a strange stage floor backdrop.

[00:47:57]I see. Okay.

[00:48:02]But what does this line mean then?

[00:48:05]Which one?

[00:48:06]>> Box. It specifically skipped over the box line.

[00:48:25]You created the backdrop wall.

[00:48:29]>> Mhm.

[00:48:32]>> USD go.x like some common API. This is a specific toolkit that open USD provides the assignment. You are wrapping the box in the toolkit you use simply simp you can use simple commands on it. Why do we need this remote? Normally we are using blah blah blah blah blah without remote control to manually write out transformation by using common API unlock common easy buttons and translate. Okay.

[00:49:02]an easy to use interface so that you can move backdrop around.

[00:49:08]Oh, so this is the line basically responsible for us to be able to move this block around like this.

[00:49:15]>> Do you get it?

[00:49:16]>> Which which line are we talking about?

[00:49:18]>> This X for common API thing that it's using.

[00:49:23]>> Yeah. And then >> this is the line responsible for us to be able to move around this thing easily because look at this what it's saying.

[00:49:32]H normally moving things in open USD is incredible math heavy and annoying.

[00:49:37]Without the remote control, you would have to manually write out transformation matrix. A big grid of numbers that handle the math for you.

[00:49:44]Using the X form common API, you unlock the common easy button set, translate, move, turn, stretch. The simple analogy, the universal remote. Imagine you just bought a complicated high-end TV. You could open the back and rewire the circuit board every time you want to change the volume. Instead, you buy a universal remote X form common API and point it at the TV.

[00:50:06]>> Now you can just do volume up, volume down, and all that [ __ ] >> I see. I see.

[00:50:12]>> Makes sense. So, so it's so it's a wrapper, right? It wraps it wraps the prim into that API so that we can do we can have fun with it basically, right?

[00:50:22]>> Exactly. Yeah. Do you know uh have you seen that video from SpaceX? Oh, show open it. Go to YouTube. I will show you right now.

[00:50:33]>> Uhhuh.

[00:50:34]>> Go to YouTube and type SpaceX and Elon Musk.

[00:50:43]I think you would. Yeah.

[00:50:48]Uh no, no, no. Go down. Go down.

[00:50:54]Wait, let me send you the link. I saw that video and thing and Elon did use the same thing for SpaceX >> like the X for API.

[00:51:03]>> Yeah, I for sure SpaceX. Wait, >> is this the one? Wait. Uh, no, no, no.

[00:51:22]Yeah, this the the fu type the future of design. The future of design. Just search future of design is going to show up.

[00:51:32]The future of design.

[00:51:39]>> This one.

[00:51:39]>> This one.

[00:51:41]>> Yeah. For this I think he has used open >> USD and we're trying to create these 3D objects using variety of 2D tools and it it just it doesn't feel natural, doesn't feel normal the way you should do things. So, we started playing around with the idea and using a few of things that are available out there such as the Leap Motion and Seaman's NX which is what we used to design the rocket and we wrote some code to integrate the two and we started with what you see here. So he's not going to show how he has used it but he >> like the way he showcases it right like the moment >> and what I can do is I can go and grab it and I can rotate it multiple dimensions >> and then what I can do is I can put another hand in there and I can zoom I can zoom in and out on the on the wireframe and then I can also translate it so I can move it around the screen and then zoom and translate.

[00:52:43]And this is what we we started off with a few months ago.

[00:52:47]>> And this is how I think he was able to render the whole thing out.

[00:52:51]>> Spin it and then catch it.

[00:52:57]>> What do you think?

[00:52:57]>> A fun way to >> Yeah, this is definitely the same thing.

[00:53:01]>> Right.

[00:53:02]Yeah, but it's it's using hand gestures and motion sensors just you know he is Elon Mus. So >> definitely he won't be doing simple [ __ ] wireframes to to actually use a a full 3D CAD model of the engine.

[00:53:26]So here what you're seeing is the actual interaction with the CAD software manipulating the real 3D model of the Merlin engine just using hand gestures.

[00:53:35]If you can just go in there and do what you need to do just understanding the fundamentals of how the thing should work as opposed to figure out how to make the computer make it work then you can you can achieve a lot more in a lot shorter period of time. So then we went to a a 3D projection. We started off with the kind of 3D projection that you're familiar with in the movies where you use 3D glasses.

[00:53:59]We also did a freestanding glass projection.

[00:54:02]>> Yeah, bro. I understood.

[00:54:04]It's pretty much the same idea of doing the X for API, but yeah, they just doing it at a very sophisticated high level.

[00:54:13]>> Yeah.

[00:54:15]All right, let's move forward. um setting start and end time codes. Time code specific specifies an exact frame or moment in the animation timeline. It allows for precise control over time. Are you able to see or no?

[00:54:38]>> Yeah. Yeah, I I'm able to see.

[00:54:41]>> Okay. Read this first example.

[00:54:44]The time code specifies an exact frame or moment in the animation timeline. It allows a precise control over timing of change to properties enabling smooth and accurate animation of the 3D objects.

[00:54:57]So a USD CPP is it is it C++?

[00:55:01]>> Yep, I think it's C++.

[00:55:11]USD time code. A USD time code is therefore unitless generic time measurement that serves as the coordinate for the time sample data in USD file.

[00:55:24]USD stage defines the mapping of the time code unit like seconds and frames.

[00:55:30]What does that mean?

[00:55:32]>> Unitless. Okay. USD time code therefore generic time measurement that serves as the coordinate for time sample data in USD files. Correct. USD stage defines the mapping the mapping of time codes to units like seconds and frames. Defines the mapping of time codes.

[00:55:56]Units like second. Okay. to set the stages start time code and end time code metadata.

[00:56:05]Start time code and end time code metadata. Use set st start time code and set end time code methods. Okay, got it.

[00:56:14]So basically we're going to open a stage.

[00:56:19]Uh we're going to use the same USD stage dot open.

[00:56:25]We're going to start set the start and end time codes for the stage. Stage dot set start time code is one and the end time code is 60.

[00:56:36]>> Export a new flattened layer for this example.

[00:56:42]>> Cool.

[00:56:43]>> Wait, I'll be back. Give me Give me a minute. I'll be back.

[00:56:51]I take some issue.

[00:57:00]Boom. Boom. Boom.

[00:57:09]>> There we go. Yes, sir.

[00:57:11]>> Oh, some guy in the chat has put something, bro, for us.

[00:57:15]>> What? Open Swarm is an opensource multi- aent AI team built on agency. Swarm was made open source. So you know let's see what this open form thing is.

[00:57:32]>> I think this is something that he might have created.

[00:57:36]>> Multi- aent orchestrator. I think I've already heard about this >> open swamp. I have heard about Hermes.

[00:57:43]>> Yeah. Yeah. Yeah. I think I've already heard about this >> open AI team. Autonomous AI team. Wait, >> an AI army at your fingertips. Your free and open source mission control center for swarm of AI employees. H now in beta. Try it free. Download for Mac. I think this is some open claw [ __ ] with agents.

[00:58:14]Oh, openwarm.com. I I was looking at the GitHub.

[00:58:21]>> Just describe it. Open.

[00:58:23]>> Damn, bro. Cool UI. Cool UI. We should design something like this as well, >> bro. This is definitely cloud design.

[00:58:31]I'm 100% sure.

[00:58:33]>> I The whole thing, dude. Even even the logo is I think similar to Claude.

[00:58:40]>> The whole aesthetic is Claude design, bro. This is >> but it's not that bad, dude. It's not.

[00:58:45]>> Yeah. Yeah. Obviously, it's not bad, bro. That's what I was telling you like the other day that everything is going to look like the same thing.

[00:58:53]>> Let let me Dude, and anyways, this is an open source thing. So, >> yeah.

[00:58:58]>> How many stars do we have? Oh, 420. So, this is something new.

[00:59:02]>> Yeah, today he he he said uh Syan Dhar.

[00:59:07]>> No, dude. But he's not the contributor.

[00:59:10]>> I know, bro. He's just a guy who put it in chat.

[00:59:13]>> No, no. I thought he was contributing over here, but I think >> No, he was just he Okay, let it be.

[00:59:18]Let's focus on this.

[00:59:22]>> Got it. Uh, open stage from starting point USDA.

[00:59:29]Set the start and end time codes. Okay.

[00:59:31]Export new flattened layer for this example. Stage.export assets time code ex1.

[00:59:38]USDA. What does this mean? But let's run it first.

[00:59:43]True.

[00:59:45]Okay. Show us USD.

[00:59:49]What does that do?

[00:59:52]Nothing. This the same thing.

[00:59:56]Wait. Go up.

[00:59:58]I think this is just set. Okay. We are starting throw node the stage.

[01:00:09]Let me read over here. Bro, what what is it trying to do?

[01:00:15]Uh, open stage from starting point done.

[01:00:18]Set the stage. So, we are just setting the time code at one for the stage and stage. Okay.

[01:00:40]But okay, but what is happening over here? I'm not able to understand.

[01:00:47]>> Yeah, I'm also I'm also confused right now. That's a Gemini.

[01:01:15]Okay. Setting the in and out points.

[01:01:23]Stage dot set start time code one. Stage dot set end time code 60.

[01:01:31]uh analogy. Think of this like start and end markers of the video. What it does is you're telling OpenUSD that this specific scene begins at frame 1 and ends at frame 60. Okay? Even if you have animation data at frame 500, a player like USD view will only play the loop between 1 and 60 because of these settings. It defines the active window of your scene.

[01:02:05]Exporting the final cut.

[01:02:09]The action. This saves you your work to a new file on your computer.

[01:02:18]Okay.

[01:02:21]Uh the flattened layer means the export command creates what is called a flattened file. In open USD you often have many layers like transparent sheets stacked on top of each other. Flattening takes all those layers and bakes them into one easy one single easy to read list. Okay, what does that mean?

[01:02:51]flattening. So flattening means uh basically turning a 2D array into a 1D array. That's what flattening means.

[01:03:04]>> Okay.

[01:03:05]>> Yeah. So if you have like three-dimensional ve array or fourdimensional array then you can use flattening to convert it into a single array. So that becomes really easy for us for us to understand. That's what basically it means. But uh how does it tell the stage to run frame one and then save everything we have done into a single file called? Oh, okay. Wait, it's saying that it's going to save everything in a single file USDA.

[01:03:38]But set start time code one.

[01:03:41]>> Okay. Wait. Tell the stage to run from frame 1 to 60. Then save everything we've done into a single clean file.

[01:03:47]time code but what's the point like I'm not able to understand okay they how is it running from 1 to 60 in one block >> yeah that's what I'm also confused with so since you when when you open the new file in the pre >> anybody in the chat >> any anyone No m >> six. But it it's moving right like if you go down go down it's just it's just this like it's whatever we did.

[01:04:27]>> Okay. Leave it. Leave it. Leave it.

[01:04:28]Leave it. But it it is still moving on its own. So what if we run this code in our system? What happens?

[01:04:33]>> Yeah. Same thing. It's the same thing.

[01:04:36]>> Wait. No. Just leave it. Like this is not the code, right? Or is this?

[01:04:40]>> No. This is the code. This is the code.

[01:04:42]Oh, this is the same code that they ran.

[01:04:46]>> It's going to export.

[01:04:47]>> They've just put it in the top layer.

[01:04:50]Top of the layer. I don't know what that means.

[01:04:54]Wait, let me ask a better model.

[01:05:59]Why are we storing it in the top layer?

[01:06:03]What's when does the frames run?

[01:06:20]Oh lord, bro. I hate [ __ ] Mac.

[01:06:44]Oh, you are just adding two numbers into the scene. You're not telling it to animate.

[01:06:56]When you call stage dot set start time code one, you're not telling it to animate. You're just writing two numbers into the scene. If anyone plays this scene, the valid timeline runs from 1 to 60.

[01:07:14]Okay.

[01:07:19]USD is built in layers.

[01:07:22]Think Photoshop layers, but for 3D scenes, you might have a base layer with geometry, another layer with materials, another with animation all stacked into one stage.

[01:07:32]Start slash end time codes are stage metadata not data on any specific object. They describe the whole composition by convention. USG writes that kind of global metadata into the root layer the topmost one.

[01:07:53]Okay.

[01:08:07]Okay.

[01:08:16]Is your open USD file stamp start one and 60 onto stage metadata. Export the results to a new file.

[01:08:29]Okay. So, we're not playing anything over here. Got it.

[01:08:33]>> Yeah. Yeah. So, it's But it does say But it does say it will render from 1 to 60.

[01:08:39]>> No, no, no. It just says it that at frame from frame 1 to 60 if a like a if a software is trying to render it. So from frames 1 to 60, you need to show this.

[01:08:56]>> That's what it says. I think >> okay, some complicated [ __ ] Stage.export. So this is just exporting the flattened layer of for this example in the top layer uh into a new file basically.

[01:09:20]So uh display USD assets time code ex1 USD okay setting time samples for attributes time samples okay let's read over here example two come on read it example two time the time sample represent a collection of attribute value at various points in time allowing open USD to interpolate between the values for animation proc purp purposes.

[01:09:57]When animating an attribute, you define a time code at which the value should be applied. These values are then interpolated between time samples to get the value that should be applied at the current code. To assign a value at time code, use the set method.

[01:10:16]Okay. Oh, it's the same. We use the set meth method as usual to assign a value.

[01:10:22]And if you want to set the size of cube to one at time code one. Oh, okay. Okay.

[01:10:28]This is where we are going to render or animate something. Yes, there we go. So, we have a cube size attribute and then we are going to get the size of the attribute.

[01:10:37]>> Mhm.

[01:10:38]>> And then at time one, we are going to set the value one. And at time 60, we are going to set the value 10.

[01:10:43]>> Okay. So as as the frame moves by >> mhm >> it's going to the the size of the cube or the value that >> oh okay okay so okay let me read that one more time um I got it I understood this >> time samples represent a collection of attribute values at various points in time allowing openg to interpolate between them. So this is the animation process when animating an attribute you define a time code at which the value should be applied. Okay. So, time code at which the value should be applied.

[01:11:14]These values are then interpolated between the time samples between time samples to get the values that should be applied at the current time code. To assign a value at a particular time code, use the set method. Got it? Set uh takes two arguments. The time code and the value to assign. Got it? For example, if you want to set the size of the cube to one at the time code 1 and 10 at the time code 60, you would do get size of the attribute cube size attribute USD attribute cube dotprim dot get size attribute. Okay, set the size of the cube at time 1 equal to 1. So cube size attribute set time equal to one value equal to one. Okay, so at frame one the value is going to be one.

[01:12:01]At frame 60 the value is going to be at 10 right USD will interpolate the values from the cube size attribute between the set time samples okay um let's create the sphere that moves up and down using xform common API got it okay bro I think now is something crazy is going to Woo! Time for the magic. Time for the magic to happen.

[01:12:37]Oh, animation.

[01:12:46]Okay.

[01:12:48]Damn, bro. How? Wait, dude. This is this is some advanced [ __ ] Go back to the basics, man. Go back to the basics, please.

[01:13:01]>> No, no, I understood, bro. It's very easy.

[01:13:04]>> Yeah.

[01:13:05]>> Yeah. Yeah. Uh what's happening over here is basically so >> Oh, no. I get it. Yeah, I can see it.

[01:13:10]That's how we are doing time one time, >> bro. This is just It's like very simple interpolation, bro. It's there.

[01:13:16]>> Oh, okay. Yeah, I can see the axis set on Yaxis. We are doing on the Yaxis, right?

[01:13:21]>> Huh?

[01:13:21]>> Yeah.

[01:13:22]>> Easy peasy. at time 1 30 45 50 60.

[01:13:28]>> So, so like okay at 1 it's starting from here two.

[01:13:32]>> Yeah.

[01:13:33]>> Uh 130 45 60 and then basically that's just giving us an illusion of the ball bouncing.

[01:13:42]>> It's not actually bouncing. It's just present at that moment over here.

[01:13:52]simple.

[01:13:55]It's pretty simple if you think about it.

[01:14:00]>> The code is easy.

[01:14:03]Code is very basic over here. M >> um I think there should be like some sort of for loop or something that should >> I think I think as soon as we move ahead and go more deep into open USD we might we we would be uh I think open to more complex it's like a game they're trying to teach us through step by step >> and then they're going to give us a big villain that we have to defeat a boss level >> I see >> or something.

[01:14:34]Oh, okay. So, this was pretty easy. I'll just go through the code one more time just so we are sure that we didn't miss anything.

[01:14:44]>> Um, so open stage from example one. We just open the stage. We just again uh loaded a sphere u that we had over there.

[01:14:57]Create clear any existing translation.

[01:14:59]So, if translate atr is not equal to sphere.get Get translate op get attribute translate. So this is just clearing any translation that was previously happening on that sphere.

[01:15:11]>> Makes sense.

[01:15:12]>> And then create xform API object for the sphere. So sphere xform API equals to us gm xform common API sphere.

[01:15:27]Okay.

[01:15:30]and then set translation of sphere at time 1 and then time 30. So this is just set setting the translate and this is XYZ coordinates and but one thing I didn't understand over here so does this matter like over here they were doing time first and then value second but over here they are doing value first and then time second.

[01:15:56]Uh it depends upon the API and >> this is a different uh function as well.

[01:16:00]This is set translate. This is >> Yeah. So it depends upon so yeah so it depends upon the API like what arguments is is it going to take. So for for that if the arguments are like okay first you have to pass on the vector information and then you pass on the time information. So I think >> this whole API thing is really confusing like I don't know where that documentation is exactly from dude.

[01:16:25]document doesn't exist. It's over here.

[01:16:28]But it's like okay as as we move through we will eventually learn like you cannot like basically learn by hard anything.

[01:16:36]>> Yeah. Yeah. But for example we are doing USD GM right or what?

[01:16:44]>> Yeah. Yeah. But anyway like AI is going to code us for that. So we just have to understand what it does.

[01:16:52]Common API attributes is P. Okay. Methods.

[01:17:00]Got it.

[01:17:03]Okay. Whatever.

[01:17:07]This is some insane [ __ ] >> And this is how the USDA file looks like for this.

[01:17:14]>> Yeah.

[01:17:16]>> Okay. Let's go down.

[01:17:19]>> Yeah. we going to read from here.

[01:17:23]So I think we can move to this. So time samples can be used for baked per frame animation and it's good for interchange that is reproducible. However, time >> However, time symbols are not a replacement for >> animation curves. Curves curves >> curves >> because I think to perform like some sort of distortment in like a material, you can't just use time samples, right?

[01:17:51]Like you can use it for like very basic stuff like bouncing a ball, >> but if you want to, >> you have to use geometry like some kind of parabolic equation or something. M >> that will give you that curve because then it's all about maths.

[01:18:07]>> Yeah.

[01:18:07]>> Right. Hyperbolic or sine wave or something like let's say you have water wave something like this you can use sine wave function that's going to do that.

[01:18:17]>> Okay. And then for more complex animation it is not recommended to define the animation using scripting but rather than in digital content creation application like Houdini or stuff like that I guess.

[01:18:30]So it is possible to set three time samples for different attributes. We can demonstrate this with the scale of the sphere.

[01:18:40]Okay.

[01:18:42]Uh it is possible to set three time samples for different attributes.

[01:18:49]Okay.

[01:18:50]So that's what they did here. Or is it the same thing?

[01:18:55]H >> I think it's the same thing but let me check. open stage from 2A. So it's just loading a stage, loading a sphere. Uh if scale atr equals to scale sphere dot get scale op get atr scale clear. I think it's just clearing the scale. I guess sphere xform api equals to usgm.xform common api sphere. Okay. Uh again they're just setting the sphere to be used as from the USDX form API.

[01:19:36]Set scale of the sphere at time one. So this okay 1 3 at one it's this at 30 it's this again.

[01:19:53]Wait, at 1 and 30 it's the same, but at 45 the y-axis is reduced to 02 and Oh, wait, wait, wait, wait, wait.

[01:20:05]>> It's it's it's basic. It's I think it's it's going to like uh reduce the scale up and down accordingly.

[01:20:14]>> Oh, it's Oh, wait, wait, wait. Now, this is for the attribute of the sphere. You see it's getting compressed >> compressed and then you see there's like a >> thing happening with its geometry like it's getting like an oval thing when it's going up >> but uh now I'm confused that >> oh wait I understood bro I understood completely >> but but over here we using using set scale uh but then how is it translating I'm confused with that >> bro look at this >> scale >> it is possible to set time samples for different attributes. We can demonstrate this with the scale of the sphere. I I know I know but but uh my question is how are we uh translating like set scale is only to set the scale of that object right like you can reduce and increase it but now how are you translating on the axis >> I think that is because we are playing it from from the previous they have not like this is happening >> go up go up go up >> what >> go up yeah I want to take a look at the file. Okay. Oh, yeah. Yeah.

[01:21:25]>> Bro, they're using the same one. They're using the time code exe1 over here.

[01:21:30]>> No, no, no, no, no, no.

[01:21:31]>> Oh, execution.

[01:21:32]>> So, that is the export from this file from the >> Now I'm confused.

[01:21:38]>> Yeah, yeah, yeah. Go to this. Look at the line 27 over here.

[01:21:43]>> Oh, yeah. See, they exported it to time code exe >> and then they are using it again and then they're rendering it.

[01:21:49]>> Yes. So, so basically this USDA is already there when they're loading it over here.

[01:21:58]>> So this is the bouncing is already happening. Now in this shell they are just adding the elements to the scale as well >> like the animation to the scale as well by adding this. So that is basically what it's doing is just you know creating like a bouncy effect.

[01:22:20]>> Bouncy effect. Yeah, makes sense. This makes sense >> over here.

[01:22:24]>> Uh, you see I think we can probably I think I can uh do this.

[01:22:38]Wait, let me see if I can do this on my Mac.

[01:22:42]I think I can.

[01:22:47]Uh, if God allows.

[01:22:51]Why not?

[01:22:53]You have cloud core bro is going to allow you the chair, right? You the chair. Show me.

[01:23:12]Where is this? Stage setting read me requirement security source hidden source.

[01:23:26]Nope.

[01:24:03]What?

[01:24:05]Where is this time code? EX 2B USDA.

[01:24:54]Okay, time for the truth.

[01:24:57]Let's see what file not found. Why?

[01:25:06]I don't know, bro. It's okay. Let it be.

[01:25:13]Why? But I understood how they're doing it now.

[01:25:20]Let's move on.

[01:25:23]>> All right.

[01:25:24]>> But where are we going to move on, bro?

[01:25:25]We are done. Key takeaways.

[01:25:27]>> We are done. Time for the quiz. Time for the quiz.

[01:25:30]>> Wait, wait, wait. Let's read the key takeaways first. To sum it up, the time code provides a unitless time ordinate scaled to real world time.

[01:25:41]>> Okay. Wait, wait, wait. There's a guy in the chat. He's asking he's he's here for the first time. Can you explain quickly what you are doing?

[01:25:51]>> So, >> do you want to explain or should I explain?

[01:25:54]>> You can go ahead.

[01:25:56]>> Okay. Shantu, say hi again so that we know you're listening and we're not wasting our energy by explain it again.

[01:26:03]Again, just say hi one more time in the chat.

[01:26:10]>> I think dude, we missed missed him. It's fine. Is anyone viewing us?

[01:26:15]>> Bro, you're going to lose your mind. You know how many people like I think today's stream was like the highest grossing stream. Like three people are still watching us.

[01:26:26]Okay.

[01:26:27]>> At peak there were like 12 people watching us.

[01:26:29]>> So if if those three people can say hi it would be really you know great.

[01:26:34]>> Oh yeah they okay okay.

[01:26:38]>> Okay. So what we are Yeah. Yeah. Yeah.

[01:26:39]I'm going to tell you guys everything.

[01:26:42]So we're trying to build a startup called instructs.world world where we are basically going to be. So for robots they have these policy models that they work on, they operate on. So what we are trying to do is u improve those policy models uh by you know helping create digital twins for the environments that they're going to be training in and simulating the training required for them to perform the niche tasks that they're going to be assigned with. So once they are trained enough in this digital environment, they're going to keep improving their tasks. So like for example, they're going to improve their dexterity. They're going to improve their, you know, uh failure detection so that they know what strength to use to hold what object and how to keep it on a table or you know all sorts of stuff like that. So what we are trying to do is we're just trying to create a dashboard uh that would basically provide the robotics teams who operate these policy models for their robots uh with a dashboard that is going to have multiple agents run uh these physical AI workflows for them. So what these physical AI workflows do is uh they basically operate on five pillars over here. So first is the coverage gap analysis. So this basically tells us where the robot is failing, how is it failing, what scenario and then second is scenario generation. So what scenarios should be generated synthetically so that the robot can complete its training and not fail in the real world. And then how do we evaluate those trainings is going to be the third pillar. And then when do we need to retrain? Um so is it going to be like a cron job? uh like do we need to retrain at the end of every week or you know after some sort of iteration and then basically how do we you know amalgamate all these training learnings from the robots in a policy model and aggregate those in a compounding library um and so that those libraries can be used across all the policy models across all the robots um so that's pretty much what we are trying to uh over here and then for that we need to rely heavily on you know uh Nvidia's techstack which is Omniverse or ISAC sim or ISAC labs which are just you know some software that you use to simulate uh environments and to help robots train in those environments synthetically. Um so that uh they basically learn in those environments and you know it just saves a lot of money because right now there's like a lot of money and time involved in training these robots via maybe using imitation learning or teley operation or all sorts of stuff like that. So to avoid that we are moving towards the synthetic generation of these environments where the robots can train and to do that we would require a deep understanding of you know how sim works, how isac lab works, what is nvidia omniverse, uh what are the world foundational models, what is a world action model and all sorts of stuff like that. And um so for that we basically took a step back and realized that it's really important for us to you know get an understanding of open scene description which is this >> wait it is not that.

[01:30:50]>> Oh no wait open USD wait >> yeah.

[01:30:54]Oh, this >> this >> so this was developed by Pixar Animation Studios.

[01:31:02]>> Yeah.

[01:31:03]>> And it gives you basically power to animate different kind of uh objects. So that's what we trying to do. So if sh you can show some of the examples of the what we have rendered till now on our notebook.

[01:31:18]>> Yeah.

[01:31:19]>> Yeah. So the these are some of the cool animations that you can do with this libraries over here. So you can you can make a ball bounce, you can make the ball uh you know have some fluid motion and all those things. To to do that we have you can use this open USD library that is uh that is available in both Python and C++ since Python is a really uh friendly language in like understanding and sorry friendly syntax for that part. uh I think so you can do like basically different kind of shader movements you can put any objects so for example over here we have a plate and on that we have put we have hovered uh we have kept a ball or something kind of like that so that ball can translate like on x-axis y axis it can bounce up and down or you can even change the color of the ball as well if you want uh you can material it into different kind of wrappers or anything if you look at our earlier streams that that we did yesterday. We we did we did take a look at the material API that helped us to you know uh try to like change the color of color color of our objects or wrap them in a way. So these are the some some of the cool things that you can do with open USD and when once you put all this all together uh you can train a robot in a simulated environment for example like training a robot in a AI training pack AI factory or a warehouse where the robot doesn't know about anything about the warehouse but eventually it's going to know uh once it gets trained and that thing can be replicated uh like to you know any number of people buildings or infrastructure like that.

[01:33:07]>> I'm just going to use my cloud policy uh like the project to just you know >> like explain it to a 10year-old.

[01:33:17]>> No, no, that's fine. You can do it. That's that's the best an analogy I would say if you're if you're able to explain it to a 10-year-old. Oh, yeah.

[01:33:29]So I hope that answers a little bit of what we're doing. Shantanu Chandra 225 >> and thanks for joining our stream.

[01:33:43]>> Yes sir.

[01:33:44]>> Very motivating. This is very motivating.

[01:33:47]>> Yep. Yep.

[01:33:49]>> Okay. So I think Claude has given us like a decent >> Damn, bro.

[01:33:56]Oh, claw can do such cool animations.

[01:33:58]>> Yeah, you didn't know.

[01:34:00]>> No, bro. I only use I'm a pro user of claw code on terminal. I don't like to use the web part. So, I don't know.

[01:34:11]I still have to do the claw design, but I do >> work work and work.

[01:34:20]>> Yeah.

[01:34:22]So this is like a decent explanation over here expressed in USD.

[01:34:35]So yeah, that's pretty much what we're trying to do over here.

[01:34:40]Um, so I think we should move forward with the quiz now.

[01:34:45]>> Yeah, dude. Let's let's focus on the quiz.

[01:34:50]>> It's 116.

[01:34:52]Oh, [ __ ] >> Dude, it's >> already 11:16.

[01:34:55]>> Yeah, bro. It's already 11:16.

[01:34:57]>> Oh my god, bro. Do >> Do you have office tomorrow? Like >> Yep. Yep. Yep. I need to go to the office tomorrow.

[01:35:05]>> Oh, you have to? I thought it's hybrid, right? You were planning to go only on Tuesdays.

[01:35:11]>> Yeah, but I need to go at least like a couple of days. So >> Oh, okay. Okay. All right.

[01:35:18]>> Yeah.

[01:35:23]God damn. Okay, let me quick quick quickly.

[01:35:28]Bro, this is [ __ ] bro. Notebook LM does not capture the [ __ ] thing.

[01:35:35]>> We can use CL code as well, you know.

[01:35:38]Okay, the quiz is ready.

[01:35:39]>> No, this is the earlier one, like the old one. Uh, I see.

[01:35:45]Uh, make a coil, but I don't think Claude takes So, nice.

[01:36:29]Guys, if you're watching, spam highs in the chat. We're going to shout out your name.

[01:36:39]Okay, bro. Let's start this.

[01:36:44]>> Okay. USG has a time code for equal to 30 and attribute has time sample author.

[01:36:50]But dude, it doesn't know the pattern the way.

[01:36:53]>> No, no, no. This is really good. Like this is better, bro. Like uh because we had like options in notebook LM. You're like trying to do the elimination thing and not >> No, but that's that that's how that's how the pattern would be.

[01:37:07]>> Bro, but this is going to be like more challenging for us to remember the concepts. And we're going to do the notebook one as well. Like this is just 10 questions, right?

[01:37:17]>> Sample 30. How many real world seconds does the animation span as? 30 >> has time codes per second 30. Okay. An attribute has time samples authored at 0 60 and 150.

[01:37:37]>> Three, >> two, and then 0 2 3 4 5 6 five.

[01:37:48]>> So, so I would say only three, right?

[01:37:50]Three attribute time code is 0 60 and 150, right? So, uh, it should be 30 / 60id by 30.

[01:37:59]>> 5 seconds, bro. 5 seconds. 5 seconds.

[01:38:02]>> Yes. And 150 / 630.

[01:38:06]>> 5 seconds.

[01:38:07]>> Okay. Yeah. Five.

[01:38:08]>> I think it's going to be five.

[01:38:09]>> Yeah. Five.

[01:38:11]>> Yes, sir.

[01:38:12]>> Five.

[01:38:14]>> True or false? Uh, time code in Open USD has units of seconds. False.

[01:38:23]An attribute has time samples.

[01:38:27]An attribute has time samples at time codes 10 and 30. The stage is queried at time code 20. What value is returned and how is it computed?

[01:38:38]>> Interpolated.

[01:38:40]It is linear interpolation between the attributes of of time code 10 and time code 30.

[01:38:49]>> Revel.

[01:38:50]>> Yes. Yes sir. Linear interpolation >> surrounding samples are time code 20 midway 10 and 30. Yes sir.

[01:38:59]>> Which two methods on USD set the animation timeline boundaries >> dot set.

[01:39:07]Uh wait fetch two methods on USD dotstage set the animation timeline boundary. I think.

[01:39:15]>> Yeah. Dot set with uh >> dot dot set >> set. No, no, it's something set something. It's It is It is like >> No, no, no. More up, go up, go up, go up. It was in the post. Like, go up. Go more up. Go more up.

[01:39:31]>> This is what it is. UD attribute set.

[01:39:34]Uh, >> no, no, no. Go up, go up, go up. Is this the one? No, there is one more. Yeah, the set set start time code. Is this the one? set start time code I think.

[01:39:45]>> Oh >> for boundaries.

[01:39:49]>> Yes. This is how you define the boundaries right like start and the end of your time of your time sample.

[01:39:58]>> But that was not the question. I think animation timeline. Oh no. You're right.

[01:40:05]You're right.

[01:40:06]>> Right.

[01:40:06]>> Set start time code and set end time code. You're right.

[01:40:09]>> Yeah.

[01:40:12]Yes sir.

[01:40:13]>> Yes sir.

[01:40:15]>> Set start time code and set >> the following line return.

[01:40:20]>> Get display color attribute. Wait a list. I think it returns a list of time samples.

[01:40:28]>> Get display. Wait wait wait wait. Don't get color get display color attribute.

[01:40:35]>> Yeah it returns it return it it returns a list of time samples. I think so.

[01:40:40]Yeah, it returns a list of time samples.

[01:40:43]>> List of time samples, but also I think it returns a list of time code with the color associated at that time code.

[01:40:54]I think no attribute associated at the time code, not the color >> color attribute, bro. That it says get display color attribute color attribute.

[01:41:07]So I'm saying the attribute values.

[01:41:09]Attribute values. And so it's a key value pair. Remember it's a key value.

[01:41:12]>> Yeah. Yeah. So the value is going to be >> No, I think the value can be anything.

[01:41:17]RGB value, right? So it's going to be some numeric value.

[01:41:21]>> Oh, yes. Yes. Yes. RGB.

[01:41:25]>> Yeah.

[01:41:26]>> Let's see what this is. A vector list.

[01:41:29]Yes, you're right.

[01:41:30]>> Time samples are authored for that. uh >> it returns the time code themselves not the value of those time codes just the time code >> time code so no values only time code so if >> vector list of time code ordinates at which time samples are authored also >> so rather than returning the color it's only going to return the time code samples yeah I was correct >> in the example below how many samples are authored on x form operation translate what value is returned at time 4 37.5 go down.

[01:42:10]>> What value is written dude? This is this is like >> minus okay 0 - 5 4.75 comma 0.

[01:42:21]Yep. Minus 4.75 I think over here between 30 and Oh no no no wait wait wait wait.

[01:42:29]I don't know how are you doing the maths but >> oh yeah minus 4.75 yes in the example how many time samples are authored on x form translate and what how many time samples right 1 2 3 4 5 time samples and then this is going to be minus 4 75 >> oh yes sir >> I am right 37 37.5 and I think five time samples. Yes, >> bro. Linear interpolation.

[01:43:05]>> So what do you So you divided 37.5 divided by >> No, no, no, no, no. Not 37.5, bro. I basically did >> Oh, so >> four the the middle because it is the middle value between 30 and 45. I wanted to give the get the middle value between minus 4.5 and minus 5.

[01:43:25]>> But but this is just like a ballpark number, dude. Like I was looking for the maths.

[01:43:29]>> Yeah, this is not a ballpark number, bro. - 4.5 + 5 / 2.

[01:43:35]>> + 5 / two. Okay. Linear or divide by two. Why?

[01:43:40]>> Linear, bro. Linear.

[01:43:42]>> Oh, I see. I see.

[01:43:44]>> Interpolation is like they they they do like the equal weightage of the attributes.

[01:43:50]>> Oh. Oh. Okay. Okay. Okay. Okay. Okay.

[01:43:52]Okay. Okay. Mike, make sense. Makes sense.

[01:43:55]>> That is simple math. um divide by two.

[01:44:01]>> You're just adding 4.5 + 5 which is 9.5 divided by two it's going to be 4.75.

[01:44:09]>> H makes sense.

[01:44:14]>> Okay. What is the time?

[01:44:15]>> What is the time code per seconds defined? And which layer value is used to interpret the boards?

[01:44:23]>> Root >> or a stage? root layer. So >> okay root I don't know this I I'm not I'm not able to recall this >> the time codes per second uh is defined in the stage and which layers values used to interpret the time codes for a stage is the root root layer defined on a layer. Okay. And yes, the root layer.

[01:44:51]>> Oh, bad game.

[01:44:53]>> Okay.

[01:45:02]Okay, I'm back.

[01:45:03]>> Holy.

[01:45:05]>> Yes, sir.

[01:45:07]So, time code per second is a metadata defined on layer. Okay, it's a metadata.

[01:45:12]The article specifies that the time code ordinate of all time samples are scaled to second is based on the value defined in the root theorem.

[01:45:20]>> It's a metadata. Yes, the article notes that the samples are good for interchange and is reproducible but are not a replacement for animation curve. Why does this distinction matter?

[01:45:36]Because we are not able to animate curves.

[01:45:39]H because we need to use digital content creation tools for intricate animations.

[01:45:51]>> Okay, now it's going to for an instruct bin picking scenario. You need to record >> wait. Time samples are baked per frame speed. Yes, linear interpolation between them. They reproduce identical across applications. Great for interchange.

[01:46:08]But they cannot express curve types basier hermite in and out tangent control.

[01:46:14]This was not in the >> this was not in the article.

[01:46:18]>> This is some additional information we get. Beier hermite ease in ease out.

[01:46:24]These are like front end animation things dude. Ease in ease out is a front end tailwind CSS library.

[01:46:32]I think front end developers is anyone is over here bro in the chat. CAD.

[01:46:38]>> No, like I was talking about >> in the chat. I think there should be some developers in the chat.

[01:46:45]>> Who is >> say hi?

[01:46:48]>> Oh, okay.

[01:46:51]So, Shantan is asking, okay, so USD you said, how will you scale from that bouncing ball simulation to actual real working robots in factory?

[01:46:59]>> Is this part time or Okay, he's asking if we are doing it part time.

[01:47:04]>> Are you also taking AI help? Yeah, bro.

[01:47:06]We are depending on AI with our lives.

[01:47:09]>> Without AI, we have a lot of subscription, dude. We are completely surrounded by AI subscription.

[01:47:17]>> Yeah, that's how you should be, bro.

[01:47:19]Like, if you're going to be a psychopath and do everything on your own. Just forget it. You're not going to be able to compete with anybody in this in US.

[01:47:28]>> All the time in US.

[01:47:29]>> Yeah. At least in US. I don't know about India and [ __ ] >> Yeah.

[01:47:36]Okay.

[01:47:38]Uh, bezier curves, hermite splines, spleens or spline. I don't know what that is. Ease in, ease out.

[01:47:53]>> And dude, he dude wait, we did not answer his questions properly. So he also said that how will you scale from that bouncing ball simulation to actual real working robots in factory.

[01:48:04]>> Okay. So basically the thing that you see over here uh the code it generates a USDA file. This USDA file is an environment or a stage that gets rendered. So once we are you know good enough at generating these USDA files what our aim would be would would be to basically generate a whole environment based on some either input like photos or videos.

[01:48:37]>> Let's say let's say we you want to design a warehouse or a room >> right. So this is like basic basic building blocks like first we are trying to see how you can uh render a ball then we got we are going to learn how to render a a block and then we are going to you know put together all the things to render a big room or something eventually but yeah I think sh is going to show you the vision that Nvidia Omniverse has >> bro that uh >> wait yeah like that. Oh, wait. Is that the one? I think >> no, bro. It's I don't know. It's It's some like I don't know why they >> I can we we we can use we can show the asset packs as well. Asset packs.

[01:49:24]>> Dude, why the hell are you at the forum?

[01:49:30]>> Yeah.

[01:49:31]>> Okay. So, these are the asset packs.

[01:49:34]So the USDA file that we are showing over here is so these USDA files come as a pack from these assets and we going to be able to render these environments completely if we download these.

[01:49:50]>> Yeah. And then and as you can see the size of those packages is like 22 gigs 18 gigs and when you scale it to you know like a warehouse that is like 1,000 acres or something and you have a lot of robots running you need a lot of compute to render those things and eventually train your robots into that environment.

[01:50:08]So it's a long long shot goal that eventually robots are going to take over our jobs. And so this is these are like the building blocks like you know how how how would I say is basically the industrial revolution uh but not for industries but for robots.

[01:50:30]Yeah. Okay. Next question.

[01:50:35]For an instructs binpicking scenario.

[01:50:38]Do you want to read this or >> Yeah, sure. Sure. For an instructs bin picking scenario. uh you need to record a robot's uh joint trajectory over 4 second pick attempt at 60 Hz so it can be played deterministically in the evaluation what do you set it for time code per second start time code end time code and how many samples per joint attribute >> 4 second uh pick attempt at 60 htz. So our 60 Hz is going to be 1 by 60 which is going to be uh what >> 0.016.

[01:51:26]>> Okay. How how did you calculate that fast, bro?

[01:51:29]>> Calculator, bro. AI.

[01:51:32]>> Okay.

[01:51:33]>> Calculator and >> Yeah. Okay. So I think time codes per second would be 4 / 0.016 which is going to be 100 / 425. So time codes per second would be 25 and then start time code is going to be >> wait what did you said 4ID 0.016 016.

[01:52:04]>> Yeah, >> it's going to be 250.

[01:52:07]0. It's not 0.16. It's 0.0.

[01:52:10]>> Oh, 250. 250. Okay.

[01:52:13]>> Yeah.

[01:52:14]>> 250. Okay. Time code scores. I I I think I might be like wildly wrong, but I think that's what it should be.

[01:52:21]>> So, what do you So, what So, what do you set it for? Time code per second.

[01:52:26]>> So, you're saying what is the answer?

[01:52:27]250. So 4 seconds per attempt at 60 Hz 1 by 60 and then we divide 4. Okay. Yeah, I think 250 could be an answer. But time code per second. No, no, wait. We should multiply it, right?

[01:52:41]>> 4 to Yeah, we should multiply it rather than dividing it.

[01:52:48]>> It's going to be 0.064 >> 240.

[01:52:52]I think time codes per second is going to be 240.

[01:53:01]So over a 4 secondond f attempt at 60 Hz how it can replayed it can be replayed deterministically in in evaluation.

[01:53:21]And what does start time code and end time code over here?

[01:53:25]Start would be over a 4 secondond pick at time at 60 Hz. So start would be should be at zero.

[01:53:35]No record at zero and then end would be 60 Hz replay in evaluation.

[01:53:41]>> Let's see what >> but first wait. Okay you said 240 right?

[01:53:46]So end could be 240 and then 60 Hz.

[01:53:50]Wait 60. What is 60? So how how 7 hertz was 143 millconds, right? What was the calculation for that? Do you remember?

[01:53:58]>> 1x 7 >> 1 by 1x 7.

[01:54:03]>> So you're going to do 1x 60. So it's going to give you 16 seconds, right? 16 milliseconds >> probably. Yeah.

[01:54:13]>> Right. So we have 16 milliseconds. And if we convert it into divide by what is how how much is 1 millcond in a second >> bro just 2 4 / 1x 60 which is going to be 4 into 60.

[01:54:34]>> Okay. I think your answer is time codes per second should be 240 and I don't know about the start time and end time code because >> no that's what I'm trying to calculate since you have figured out time code per second right so uh we can do the maths 4 seconds per pick attempt at 60 Hz >> but that doesn't depend on >> no no no no at at 60 Hz you know what that means 60 Hz is the whole cycle right so if 7 Hz is 143 millconds then 60 Hz is 1 divided by 16.

[01:55:08]Uh, right. So, it's it's like 16 milliseconds, right? So, >> oh wait, wait, wait, wait, wait. Time codes per second would be 240. Start time code would be one. End time code would be 240. That's what I think. And how many time samples per joint attribute? Um, no dude, I don't think end time code should be 240.

[01:55:36]Time codes per second. Oh yeah, you're right. Wait. No. Time codes, bro. Let's reveal the answer. Let me see.

[01:55:46]>> 60. It's 60, dude. Wait. And time code was correct. 240. 4 seconds into 60.

[01:55:52]>> Yeah.

[01:55:53]>> So, but how did the 60 came? One time sample per frame per h >> one time sample per frame per joint is equal to 241 samples inclusive of both end points or 240 if treating as open-ended. The key point keep time codes per second aligned with your sensor control rate. So time codes map one is to one with frames easier reproducibility. No rounding in benchmarks.

[01:56:22]I see this is bro I think we should use claude. This is better.

[01:56:27]>> Okay, >> this is better.

[01:56:30]>> But then we then we would be able to provide him with all the information the guide that we did provided provided it to notebook LM >> bro that that [ __ ] was [ __ ] It was [ __ ] bro and notebook LM was [ __ ] It was it didn't >> but the thing is we are preparing for open USD certification.

[01:56:48]>> You just want you just want more options right? I the thing is dude if you're preparing for >> you want MCQs right you want MCQs right?

[01:56:58]>> No my goal is to because since we are preparing for an exam we have to do it in a certain manner that they have provided it but >> so that >> bro listen the questions in notebook LM were [ __ ] like >> well that's what I'm saying just upload the exam guide over here as well. Oh yeah, that I'm going to do I'm gonna create like a for tomorrow stream.

[01:57:19]>> Yeah, >> I'm going to do like a complete Yeah.

[01:57:22]>> Cloud code. Dude, I am I am advocate of cloud code. Dude, I would suggest anyone to use if they are trying to learn coding or anything any technical skill that they want to develop definitely go for cloud code. Dude, that is the best CEO, software engineer, principal engineer that exists right now. Dude, I have upgraded my plan from 100 to 200 for that only like clock is >> badass SAS SAS subscriptions two off evaluation scenario where author time code per second 20 legacy film and the time code per second 120 high rates uh regression plus runner queries both at 1.5 second do this is some [ __ ] reveal the answer >> mhm mhm Two of your evaluation scenarios were authored at time codes per second equal to 24.

[01:58:17]Okay, bro. Wait, I didn't understand this completely as well.

[01:58:24]>> Yeah. So, I was going to say like copy both of them and then >> Mhm.

[01:58:30]>> Dude, wait. Before we go in more deep, look at the time. Yeah, I think we're just going to read this one, reveal this, and just stop after.

[01:58:41]>> Yeah, >> two of scenarios were Yeah.

[01:58:47]>> authored at time codes per second 24 legacy film convention from vendor asset and time codes per second 120 high rate sensor capture a regression test runner queries.

[01:59:01]Wait, two of your evaluation scenarios were authored at time code portal 24 legacy film convention 120 high rate sensor capture a regression test runner queries both 1.5 seconds in 1.5 okay so 24 + 12 36 I think 36 and 180.

[01:59:40]Answer should be 36 and 180.

[01:59:43]>> Revel.

[01:59:49]And what's the operational risk if your test harness ignores this metadata?

[01:59:57]>> The operational risk would be I don't know.

[02:00:02]>> Reveal reveal.

[02:00:04]>> Yes, sir. 36 and 180. I was right.

[02:00:09]>> Mhm.

[02:00:09]>> Time code 36. 1.5 seconds. 24.

[02:00:14]Some quick math.

[02:00:15]>> 24.

[02:00:16]>> Quick math.

[02:00:19]And the exactly the kind of silent benchmark drift the okay whatever annoying audit traceability for pattern 19 lessens the runner queries in seconds never in raw time codes and reads >> time codes >> pattern thing >> it's because I have it in the >> Yeah Bro, >> but you're making progress, bro. Like, >> yeah, bro. I'm not.

[02:00:52]>> I'm not disagreeing, bro.

[02:00:55]>> Day one.

[02:00:56]>> One day at a time.

[02:00:58]>> One day.

[02:00:58]>> One day at a time. Day one. Amazon mentality. Jeff Bezos.

[02:01:03]>> Jeff Bezos.

[02:01:05]>> Day one, brother. It's always day one.

[02:01:09]>> Always day one. All right. I think only one guy is watching us, you know.

[02:01:15]>> Um >> I think >> it was a successful stream again.

[02:01:18]>> Yeah.

[02:01:19]>> And we are supporters. Thanks for the supporters.

[02:01:23]>> Yeah. And we've like breaken our own record. Like we're breaking our records every day, you know. I think what what are the number of views today? Let me check.

[02:01:36]97 views.

[02:01:39]>> Oh my god. Oh my All time high.

[02:01:42]>> Holy [ __ ] Let's go.

[02:01:46]>> Let's go, gang. Let's go.

[02:01:49]>> All right. All right. Time to say good night and goodbye to our >> All right.

[02:01:56]>> Followers and supporters.

[02:01:59]See you tomorrow, guys. Same time.

[02:02:05]>> Two hours done.

[02:02:08]Get the ne was there.