Skip to content
Stanford CS153 Frontier Systems | Amit Jain from Luma AI on Unified Intelligence Systems
This video isn’t embeddableWatch on YouTube →
Stanford OnlineStanford Online

Stanford CS153 Frontier Systems | Amit Jain from Luma AI on Unified Intelligence Systems

In week three of CS153, the instructor hosts Amit Jain from Luma to discuss “Unified Intelligence Systems” as a follow-up to a prior lecture on visual intelligence.

CS153 InstructorhostAmit Jainguest
May 6, 202657mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Transcript

0:10 – 0:52

Course setup and why “unified intelligence systems” matters this week

CS153 Instructor 0:10 Welcome, gang, to, uh, week three of CS153. We have today with us Amit Jain from Luma. Thank you for joining us, Amit. [laughs]

Amit Jain 0:20 Thanks for having me.

CS153 Instructor 0:22 Okay. [audience applauds and cheers] Uh, Amit is gonna be talking to us today about unified intelligence systems. You're gonna be hearing a lot more about this. I think it's a, a very relevant follow-up to the visual intelligence systems lecture we had last week from Andy Blattman at Black Forest Labs. Um, quick recap on the class and today. We're gonna talk about Amit, and today we're

0:52 – 2:56

How Luma’s origin story started with a blunt ask: “Can I have your 3D data?”

CS153 Instructor 0:52 gonna do a field trip into what I think is also one of the most exciting, uh, factories working on how to get work done, especially visual and creative work done in the world, called Luma. But before that, why don't we start by talking about Amit a little bit? I had the privilege to get to know Amit a few years ago when he was still an engineer at Apple. And, uh, I was at Discord at the time, and Amit-- I got an email from Amit saying, um, "Hey, I heard you have a bunch of 3D data."

Amit Jain 1:25 Yes.

CS153 Instructor 1:25 "Uh, can I have it?" [laughs]

Amit Jain 1:27 I remember that.

CS153 Instructor 1:27 And I said, "No, you can't."

Amit Jain 1:29 [laughs]

CS153 Instructor 1:29 Uh, because Discord had acquired the data. But I started asking Amit what-- why he needed the data. If you guys remember, um, I covered this in, in our first lecture, but Ubiquity6, the company I'd started about a decade ago, was a 3D computer vision mapping company, and we had, uh, we had millions of people around the world who were capturing the world in 3D using their smartphones. And all that data, we had terabytes of data, um, uh, that were 3D representations of the world that we'd reconstructed from 2D images. And Amit said, "Well, I wanna build, um, a 3D service that, uh, that is generative. I want to allow people to create gener-- the same kinds of meshes and point clouds and 3D representations of spaces, but through generative models because that's where the world is going." Um, and I s- got interested 'cause I kinda agreed with him, and he was ahead of the curve. And so I had a chance to invest as an angel investor at the time, and then a few years later, I had a chance to partner with Amit again at a16z when I was a general partner. And had-- Thank you for letting me lead your Series-

Amit Jain 2:27 B

CS153 Instructor 2:27 ... B.

Amit Jain 2:28 Yeah.

CS153 Instructor 2:28 Um, Amit was also one of the first customers of the a16z compute program called Oxygen, and actually helped name Oxygen as well. Um, I think the quote was, he said something like, you know, "If we don't have compute on day one-"

Amit Jain 2:41 Let's-

CS153 Instructor 2:42 "... can't really read."

Amit Jain 2:43 Suffocate. Yeah.

CS153 Instructor 2:43 So, um, tell us a little bit about what Luma is and how-- what were the dots that led from the insight at Apple that generative modeling was the future that led here?

2:56 – 5:07

From Apple LiDAR to “world simulators”: the technical and product motivation

Amit Jain 2:56 My background, b- very briefly. So at Apple, I was working on, uh, first the LiDAR systems that actually now is on our iPhones. Uh, this was called the Jasper sensor if any o- any of you are familiar. And we were trying to build, um-- We were trying to actually build like, you know, what comes after the c- after the camera. This sensor was built, now I can talk about it because, you know, the project is no more for the car, [chuckles] uh, which was called Titan. And we started to work on Vision Pro after that because, you know, the car project got, got canceled, and the Vision Pro had, had a bunch of LiDARs on it. And during that work, it started to become obvious that like, okay, you know, um, the computers of the future, uh, we still don't know what they will look like. Uh, you know, maybe they will have AI or what- whatnot. The computers of the future will need very different interfaces, will need very different kind of media, and will need very different kind of, of ways of actually capturing and creating and building those things into the system. So in 2020, uh, at Apple, we started exploring generative models. Um, and, and think about it, it's 2020, so, you know, before language model scaling was known to be working and before, um... Actually, it was before DALL-E, but NERF had already come out from Matthew Tanchik from Berkeley. So we started to explore those generative systems and, uh, that led me to thinking that, okay, if language scaling is working and here is, is a method where we-- differentiable 3D is possible, what would happen if all of these things are combined together, right? That would basically mean you have the full footprint of every observation in the universe, and you will be able to like, you know, differentiably learn about them. If you can differentiably learn about them, you can understand them, and then finally you can generate them. So that was the genesis of Luma. And at that time, because of, of the pedigree we had, 3D seemed like the most logical way of going forward because first of all, 3D tells you-- 3D has a lot more information than images do. Uh, naively, we assumed at the time 3D has a lot more information than videos do as well, and that 4D would be very easy to capture and scale. But again, I say naively because as you will learn in, in a few seconds that that was a bad assumption. But that's kind of where we started, with the idea of building what we now call a world simulator. Uh, at that time it was just like, all right, like, you know, if we can learn this and generate this, we would have something that would allow us world understanding.

5:07 – 6:10

What “differentiably learn the world” actually means (and why it’s central)

CS153 Instructor 5:07 And c- you, you talked about-- You, you said this phrase, which is important, you know, l-learn the world in a differentiable manner.

Amit Jain 5:15 Yeah.

CS153 Instructor 5:16 What does that mean?

Amit Jain 5:17 Right. So I mean, i-if you're-- I-I'm sure you guys are all familiar with like, you know, how transformers work and how AI models work. Differentiable means you can put it in a training loop and, um, you can have a loss function that can be then iteratively optimized. So differentiable allows you to do that. If the function is non-differentiable, then like, you know, you j- really can't do gradient descent on it. And, uh, if you can't do gradient descent on it, then deep learning doesn't work. So the tools that we have for this era, for this generation, is basically compute and gradient descent. Um, and yes, transformers are things that are very, very well susceptible to gradient descent, but the actual, you know, thing underneath it is gradient descent and compute. So how can we take a lot of data, a lot of compute, and gradient descent and produce something useful out of it? Differentiability is the core characteristic of that problem, those problems, basically.

CS153 Instructor 6:04 Yep.That's helpful. Could you just connect the dots on how, what that insight-

Amit Jain 6:08 Yeah

CS153 Instructor 6:08 ... led to then what-

Amit Jain 6:09 Right

CS153 Instructor 6:09 ... Luma's doing today?

6:10 – 7:25

Luma’s first flywheel: productionizing NERFs/Gaussian splats—and hitting a scaling wall

Amit Jain 6:10 So we started-- When we started the company, the idea was we will, we'll, uh, you know, capture an, uh, ungodly amount of 3D data, build a flywheel that allows people to capture that and like, you know, for us to be able to use it and then like, you know, build, build both simulation systems with it. So we released an app, uh, which is called Illuma 3D Capture. It actually was very, very popular because, one, the results were really, really great. It was for the first time that NERF and Gaussian splats were productionized. And Matthew, uh, you know, he joined our team actually to really push forward the, the frontier of, of that sort of the world. But very soon we realized that it doesn't matter how many people use the app, it will never reach the scale that was necessary to learn enough about the universe.

CS153 Instructor 6:49 Why is that?

Amit Jain 6:51 Because think about it, right? The number of people that are writing on the internet, that are taking photos on the internet, that are, are, are capturing videos on the internet, substantially outpaces anything one company can actually distribute. Also, there's like, you know, decades and decades and decades of that information that is already available. So it's all about data. It actually... You, you can make the case that like, you know, this particular modality of data is better for learning versus this or versus that. It really doesn't matter. That's a moot point because you're running against the physics of scale. So wherever there is scale in data, that's the only thing that's gonna work.

CS153 Instructor 7:25 Hmm.

7:25 – 10:27

Pivot to video: Hopper compute, Dream Machine, and the next data flywheel

Amit Jain 7:25 And you have to design the algorithms around where the, the data is, not the other way around, right? You come up with some pristine algorithm, but you don't have any data, then like, you know, what's the point? Robotics is coming u-up against this problem right now. We're like, "All right, we're gonna build like, you know, these action systems," but well, where is the action data? There's no internet of action data. You can have huge labs in, in China and India and in Vietnam and, and, and everywhere gathering this data, but the scale is really c- not comparable. So you have to just design the systems around data. So that's what, that's what we learned. Um, so in 2023, after that realization and after, uh, you know, NVIDIA Hopper architecture was announced, uh, we started to build the foundations of, um, you know, generative video because video is three-dimensional. It has two dimensions of space and one dimension of time. And human brain actually like, you know, learns about 3D representation through that time proxy. So when Hopper architecture came about, we started to think like, "All right, it might be possible actually to learn video and to learn the world representation through video." So in 2023, uh, Jiaming joined us. Jiaming, uh, was, uh, you know, at NVIDIA at that point. He's a Stanford grad. And a, a few other people from Stanford and Berkeley, uh, started to join the company with this idea of like, "All right, let's learn from video." And we started to build that infrastructure. And in February-- Sorry, in March 2024, we released the first video model, uh, that was called Dream Machine.

CS153 Instructor 8:44 Yeah.

Amit Jain 8:44 And, um, you know, in, in the first three weeks, four weeks, actually, we got up to, uh, uh, s- six million users from that because people had never seen generative video. Uh, sort of was announced but never released, so people had never experienced it, so people really wanted to actually try that out. So we started with video at that point. And then we have had the similar realization again in 2025, early 2025, uh, just like annual cycles now, that just video is not enough because video is good, but it doesn't pair human logic. It doesn't pair why an event is important. What is the sequence of events, and what does that actually lead to? Just having language models in the middle, uh, that are like, you know, u- being used for embedding is not sufficient. You need unified intelligence, so that's kind of where we are now.

CS153 Instructor 9:22 Yep.

Amit Jain 9:22 These are the dots.

CS153 Instructor 9:23 Well, um, yeah, so th-this is not the first time the class has heard that when you close the loop, you have to, you have to sort of evolve the, the mid-training, the post-training pipeline, the interface. And so can we spend a little bit of time-- So I, I don't think it's a surprise for people to hear that there was sort of an iterative loop every year as you got more and more data from customers.

Amit Jain 9:44 Yeah.

CS153 Instructor 9:44 But can we talk a little bit about that first... You know, the final projects for the class this time are the one person frontier lab, where they're going to be bootstrapping their own flywheels.

Amit Jain 9:53 That's very cool.

CS153 Instructor 9:54 Um, and the first-- You know, before-- I, I remember, you know, how nerve-wracking it was for you and for the team whe-when, when you had the realization that video was gonna be the future, but you didn't have a video model out in the world yet.

Amit Jain 10:08 Yeah.

CS153 Instructor 10:08 And you didn't have a state-of-the-art system to start collecting that, um, that context feedback loop.

Amit Jain 10:13 Yeah.

CS153 Instructor 10:14 So let's, let's, let's take a bit of a journey back in time, time travel to, uh, the launch of Dream Machine 1.

Amit Jain 10:21 Yeah.

CS153 Instructor 10:21 Can you just tell folks how you went about kickstarting or bootstrapping the, the video flywheel at Luma?

10:27 – 13:51

Bootstrapping the video flywheel: preference signals, trainers, and product telemetry

Amit Jain 10:27 So I think the core problem that you wanna think about whenever you're building these really, really large systems, they have a wild distribution, right? Like, you know, if even if you're talking about language models, well, they have all of language models, uh, language model data, and what is good, what is bad, right? So you wanna think about, okay, from this really raw distribution I get from pre-training, how do I get to a model that humans can use? And what humans find useful is a very narrow band within that distribution, and that narrow band is not like, you know, a predictable, uh, linear band. It's just like, you know, pockets of, of, of greatness that humans think are great. Some other species might find it very different, right? But we have our own aesthetics. We have our own use cases. We have our own value system. So we find those, those distributions valuable. So now the question becomes: How do you find, or how do you basically t- get that distribution out of the model? So we started to think about that problem and, and with Dream Machine, the-- because there were so many users that were using the model, the question became, "All right, can we learn something about that?" And, and preference, uh, or like, you know, preference feedback, uh, at that time, by the way, um, SFT, right, like, you know, was just started to being thought about. RLHF was a hot thing where people were thinking about like, all right, like, you know, human feedback loops. So we built a system where, um, videos that people were liking and people were downloading, we considered that to be a signal of like, all right, this is something that people prefer. Um, it was not 100% accurate because some people were downloading really bad videos as a showcase of how bad AI is at video, right? So our model also learned a lot of that. So we had to then build systems for, uh, humans to be able to, uh, go and filter out, like, uh, people we pay. So then it started to emerge what a frontier lab actually looks like. A frontier lab has these components of data, these components of compute and algorithm, but it also has huge parts of, of what we call skills and trainers and tutors and people who are doing the labeling of data and all of these systems. Um-If you don't have that, then it's actually not complete. And a part of that is also the product you built. Can the product actually give you enough information to make sure that the next model is better than the previous one? And hence the experience is better, and hence more people will use it, and hence you'll get more data from it, uh, uh, about this preference of, of human distribution, and can you make the next model actually better? So, I mean, it took us a long time to learn actually how to gather that feedback, how to... You know, and then now the system we have, uh, in, in, in the latest Luma Agent system, ungodly amount of feedback actually we get from, from, um, um, what people are doing. Every interaction that is there, we learn from, like, you know, whether they like it, dislike it, in what way they like it, what way they dislike it, whether the full chain of thought, uh, that, that the model produced and the full chain of work that the model produced is any good. Which elements of that is not good? And then that's how you actually start to get good at it. Yeah.

CS153 Instructor 13:16 Well, let's, um... Why, why don't we do a double-click on how that-

Amit Jain 13:20 Yeah

CS153 Instructor 13:20 ... that actually works. So to remind everybody about the field trip we're about to take, right? Um, this is the, the very basic standard AI factory we've talked about, right? Frontier AI, um, sort of pipeline. We've got pre-training, mid-training, and then we have post-training and deployment. And so today, we're gonna hear a little bit from Amit on how the, the Luma version of this works. Why don't you go ahead and just k-kind of talk us through-

Amit Jain 13:49 Yeah

CS153 Instructor 13:49 ... what's, what's actually going on under the hood at Luma.

13:51 – 20:45

Inside the Luma Factory: multimodal pretraining and the push to end-to-end creative work

Amit Jain 13:51 Absolutely. So, um, let me talk about what is informing the design decisions for our architecture and for our models. Um, currently, we are seeing huge amount of alpha coming from, from language models being used for, for adjacent tasks like coding, for adjacent tasks like, you know, system design and, and those kind of processes. But when we start to think about tasks that require more context than what is available in text, so creative work, right? Huge amount of things, a huge amount of information that is in, in visual domain, huge amount of information in auditory domain, actually huge amount of information in the trace of how you arrived at the final output, right? That. When we think about robotics, you can definitely start to build a, a robotic system just based on text models or VLMs or VLAs that people are starting to do now. But they will not generalize, just the same way that, like, you know, a-autonomy didn't-- uh, autonomous driving didn't generalize until people started to build full end-to-end systems that w- that had language, that had video, that had, uh, like, you know, all of the control signals, all of these things in there. So that's the problem we are coming up with, that the real world is way more complicated than coding, right? I mean, coding is a really valuable task, but not everything can be done in coding, right? Like, otherwise, programmers would be the only profession that would be left. Uh, uh, and now they are also, you know, endangered species, actually. But-

CS153 Instructor 15:14 I'm not sure that's true, but I understand your point.

Amit Jain 15:16 [laughs]

CS153 Instructor 15:16 Yeah.

Amit Jain 15:17 As a, as a programmer, uh, it's really fun.

CS153 Instructor 15:19 Well, the job has evolved, for sure-

Amit Jain 15:21 That's right

CS153 Instructor 15:21 ... to become a trainer-

Amit Jain 15:22 Yeah

CS153 Instructor 15:22 ... and a tutor. Yeah.

Amit Jain 15:23 I-It's a really fun, fun time to be that way. Uh, I-I started pr- coding like, you know, when I was thir-thirteen years old, in order to build s-simulation systems, in order to do like, you know... Uh, so my background is in physics. And in order to actually build like, you know, simulation systems for, for electromagnetism and those kind of things to l- see how these systems behave. That's why-- when I learned, uh, to start coding. And even at that point, it was really obvious that I cannot teach those systems from any observations.

CS153 Instructor 15:46 Hmm.

Amit Jain 15:47 Right? We can write the code, but that is like approximations that we have in our, in our models or in our, in our equations, but we can't actually teach those models from any data. So all of this is informing how we build our systems. So even early on, we started to think about, okay, in our pre-training, how can we learn from all of video, all of images, and all of text, right? It's a really hard problem because they're really different modalities, and they're expressed very differently. If, if you think about the encoding of these modalities, text is discrete, and text performs the best when you encode, encode it in a discrete manner. At least that is the understanding today. Video is kinda somewhere in between, and audio and images are b-be-best performed in, in a continuous space. So our factory, as you call it, is built around this idea of like, how do we learn jointly from all of these systems? In 2025, these were disparate towers that we built. Language tower, image tower, video tower, audio tower, and then like, you know, we would unify them together, um, using just like, you know, some, some fusion techniques so that like, you know, they will do better. Uh, if you look at like, you know, the work from, uh, Andy's lab, right? Like, you know, uh, stable diffusion, those kind of things. That's what it does as well, where you have a tiny little language component-

CS153 Instructor 17:04 Right

Amit Jain 17:04 ... um, and, and you learn embeddings from that to be able to understand the human instructions. It was just not sufficient. So when we talk to our customers, when they try to use our system, so where, where are systems being used, right? For instance, currently, large studios. So actually, I'm very, very, very excited about, um, a new show that is coming out on Prime Video.

CS153 Instructor 17:23 Hmm.

Amit Jain 17:23 Uh, the trailer's out. Uh, it's called, um, um, Old Stories. Uh, it's a-about Moses, right? So it has, um, Sir Ben Kingsley is the star of it.

CS153 Instructor 17:33 Oh, cool.

Amit Jain 17:33 Uh, it's, it's a proper production. It's not an AI video. Uh, it's a $4 million, uh, sorry, $4.5 million, uh, per episode production, basically. And it's all pretty much all produced using Luma Agents. So they're using it in these, like, really high intense situations where they wanna be able to model the whole world and the physics of the world and light and, and, and, and, uh, uh, fluid and interactions and all of these kind of things.

CS153 Instructor 17:54 Hmm.

Amit Jain 17:54 Now, when you do that, it's just not sufficient to build an image model or a video model. You need a model that understands time and causality and, and language, right? And it, it understands, like, proper instructions. "Okay, well, like, you know, uh, um, this looks good, but what if like, you know, the, the shirt sleeves had like, you know, this particular thing right here?"

CS153 Instructor 18:13 Hmm.

Amit Jain 18:13 How do you express that instru-instruction? "Okay, in time, when this person actually walks, uh, through the door, the whole scene explodes." All right, what does walking through the door actually means? When the person walks through the door, what does this explosion of the scene mean? Give me more instructions, right?The deeper you go into these kind of problems, and this is a very, very, very big market, right? It's about 120 million creatives in the world whose-- this is their job, right? Like, you know, these are not people who paint for a hobby or all these kind of things. These are people who actually are employed in this industry. So about, uh, you know, two times, three times by estimation of coders. Um, their work every day goes into replicating the physics of the real world-

CS153 Instructor 18:51 Mm

Amit Jain 18:51 ... into computers. So we wanna build systems for them, and if you wanna do that, you wanna build what we are now calling unified models that have the same understanding and intelligence of a language model that can follow context, that can remember, and the physical understanding and the world model understanding of video models and image models. So that is what the output, that is what the things we want to produce. This was 2025. [laughs] And now in 2026 when the models got really good, what people want to do is like they wanna do the full work end to end. You know, it's like, all right, why is it only producing five-second video for me, right? Why can't it make the whole shot? Uh, if you go to like, you know, w- w- people in advertising world, why can't it make the whole campaign? If you talk to robotics companies, why can't it actually produce the whole action and then judge its own outputs, and then tell me when this is the right action and incorrect action?

CS153 Instructor 19:40 Mm.

Amit Jain 19:40 Like, you know, why can't I get the right force in all of these kind of problems? So people want end-to-end results. So now the Luma Factory is about building systems that can do end-to-end work-

CS153 Instructor 19:51 Hmm

Amit Jain 19:51 ... in multimodal domains. So that's, that's kind of what we do. We have massive reserves of like, you know, multimodal data, uh, i-in about-- Uh, the final trainable outputs are in, in about thirty petabytes of, uh, you know, um, scale. We train them on, on, um, currently H100s and very soon GB300, uh, uh, you know, GPUs, uh, in, i-in the 0-0-010K scale, basically. So pretty much the same as, as a second-tier language model training. Like, you know-

CS153 Instructor 20:19 Hmm

Amit Jain 20:19 ... so we're not at one trillion parameter yet because that scaling hasn't been figured out, uh, but we are gonna get there. And then we do post-training on this stuff, uh, using huge amount of customer data and huge amount of, um, user preference data, as well as, uh, data that comes from our own human annotations. And finally, we put them in production, and we do reinforcement learning and, and continual learning on those systems. So that's the shape of the factory currently at Luma.

20:45 – 22:31

Enterprise deployment constraints: studio secrecy, training exclusions, and learning from traces

CS153 Instructor 20:45 And could you talk a little bit about, you know, when you started deploying these systems in, in, in the first lecture, we talked about mission-critical context, right?

Amit Jain 20:54 Mm.

CS153 Instructor 20:54 And one, one type of mission-critical context is a large studio-

Amit Jain 20:57 Yep

CS153 Instructor 20:57 ... for whom their data is super sensitive.

Amit Jain 20:59 Yep.

CS153 Instructor 20:59 They don't want... You know, they're happy to have you train their data, but, uh, with their data for them.

Amit Jain 21:04 Yeah.

CS153 Instructor 21:05 But they don't-- If, if I'm running a studio, I don't want my data being used by another studio.

Amit Jain 21:09 Yeah.

CS153 Instructor 21:09 So how, how do you, how did you navigate the deployment sort of restrictions-

Amit Jain 21:14 Yeah

CS153 Instructor 21:14 ... of these, of these professionals?

Amit Jain 21:16 So we work with two arch nemesis at the same time, Netflix and, and Amazon Prime Studio, right? Which are the two giants of streaming war at the moment. Um, so basically then, then you have to build systems that are guaranteeing that there is no way that there's any data overlap. We have internal controls and systems that like, you know, are, are some of the standard ones like SOC 2 and those, those kind of things, and then specific ones that are for AI labs on how do you not train on this, on, on this data.

CS153 Instructor 21:47 Hmm.

Amit Jain 21:47 So for instance, uh, if you're producing the next blockbuster, you don't want the next Iron Man, for instance, right, like to show up into the training data. So we have guarantees around that, like, all right, whenever certain stuff is marked or projects are marked, they will never show up in training data. They will never show up in, in any of these loops, basically. But we still learn from like, you know, what users are doing in the product-

CS153 Instructor 22:11 Hmm

Amit Jain 22:11 ... which is different from the, the visual artifacts that they're producing, but rather the traces they're producing. We, we're still able to use them and learn from them, actually.

CS153 Instructor 22:17 This is the interaction data-

Amit Jain 22:18 That's right

CS153 Instructor 22:19 ... when people are working with the interface of the agents.

Amit Jain 22:22 Yeah. That's right.

CS153 Instructor 22:23 Okay.

Amit Jain 22:23 So there's some limitations on, on these kind of high, higher sensitivity projects. Yeah.

CS153 Instructor 22:27 Um, yeah, I think you have, you know, sort of a-

Amit Jain 22:31 Yeah

22:31 – 25:15

Unified intelligence in action: generating polished slides from a mind map + style prompt

CS153 Instructor 22:31 ... well, one, uh, could you talk a little about how you created these slides? 'Cause these, these-

Amit Jain 22:34 Yeah

CS153 Instructor 22:34 ... I believe were created with, with Uni1.

Amit Jain 22:37 That's right.

CS153 Instructor 22:37 Is that right?

Amit Jain 22:37 So, uh, these are, uh, you know, I, I basically gave it... Uh, actually, let me start from that first, and then I will actually, actually ta-ta-talk about unified models as well. So here, I created this, uh, like, you know, on the top what you see, I created that, um, mind map, whatever you wanna call it, in our product. And then I basically asked, if you see on the right, um, I asked it like, you know... And I also gave it Ant slide, uh, that like, you know, the one right here. Sorry, not this one, but... Okay, I don't know. The first one you saw of the factory one.

CS153 Instructor 23:07 The factory slide. I see.

Amit Jain 23:08 That's right.

CS153 Instructor 23:08 Yeah.

Amit Jain 23:08 I gave it that, and I asked it like, "Hey, in this style, actually produce the outputs." Now, this is actually a very, very good example of what unified intelligence that I'm gonna talk about means. People, when they think about image models, video models, or, or any models, not text, they think they are just... They produce beautiful images, right?

CS153 Instructor 23:28 Mm.

Amit Jain 23:28 But that is a really big mental gap that the world has in this area. Just like language models produce words, right? The words can be beautiful. You can just say like, "Hey, it's a poem," and it could mean nothing, right?

CS153 Instructor 23:39 Hmm.

Amit Jain 23:39 And, and simultaneously, you can have a mathematical proof of Euler's problem number, pick your, uh, take your pick, right? 1152. They all are words at the end of the day, but how you string them together determines the information content and determines the informa- uh, the, the intelligence of those.

CS153 Instructor 23:54 Hmm.

Amit Jain 23:55 Just like that, how you arrange the pixels determines what they're conveying and how, how intelligent they are. So unified models that we are producing now, and I'm gonna talk about that in a second, are about how you express intelligence in whatever medium is convenient for the person that they are actually, you know, who's using it. So if a language is, uh, a language output is convenient, fantastic. If it is slides and images, fantastic. If it's a video explainer, great. But they're all basically outputs that are intelligence.

CS153 Instructor 24:26 Hmm.

Amit Jain 24:26 So that, that's what we call unified models. So yeah, basically, uh, it was one shot. Uh, it produced those slides. It produced one that I didn't like, and I deleted it, butBefore you ask me to take a screenshot of that.

CS153 Instructor 24:35 Yeah.

Amit Jain 24:35 But that w- that was pretty much about it. If I would have asked it to do a very detailed overview of that, then that's what it, it would have done. So end-to-end work, this is what we call end-to-end work, right? You know?

CS153 Instructor 24:45 So ju- just to break down what happened-

Amit Jain 24:46 Yeah

CS153 Instructor 24:47 ... you gave it, you gave it my original slide as a prompt.

Amit Jain 24:49 Yeah.

CS153 Instructor 24:50 A screenshot of that prompt.

Amit Jain 24:51 Yeah.

CS153 Instructor 24:51 You then gave it instructions on the right-

Amit Jain 24:53 Yeah

CS153 Instructor 24:53 ... in the chat, and then you gave it a little bit, like, guidance, is, is it? That scaffolding?

Amit Jain 24:57 Yeah, just my, my, my, my thoughts up there.

CS153 Instructor 24:59 Right.

Amit Jain 25:00 The top half of the screen is, like, you know, my, my thinking.

CS153 Instructor 25:02 Right.

Amit Jain 25:03 And-

CS153 Instructor 25:03 And then the output below was-

Amit Jain 25:04 Yeah

CS153 Instructor 25:04 ... essentially the slide one-shotted from that.

Amit Jain 25:06 Correct.

CS153 Instructor 25:07 Okay.

Amit Jain 25:07 So-

CS153 Instructor 25:07 And why was that not just possible trivially? Why, why can't an LLM do that, and why wasn't-- why did it take so long to get here? What's the hard part about this?

25:15 – 29:50

Why it’s hard: bridging understanding vs generation, and what “unified” architecture changes

Amit Jain 25:15 Right. So I mean, that's a good segue into unified models, basically. So, um-

CS153 Instructor 25:20 Okay

Amit Jain 25:20 ... well, LLM, first of all, doesn't generate images, right? I mean, it's a language model.

CS153 Instructor 25:25 Hmm.

Amit Jain 25:25 You can ask an LLM to use a computer and try to generate images, but again, it really falls apart because it doesn't see anything.

CS153 Instructor 25:32 Hmm.

Amit Jain 25:33 So when it tries to reason spatially, when it tries to produce, like, you know, any visual outputs, they're blind models. They see everything as a, a, a full sequence, right? Like, you know, even the grid nature of, of, of images and visual information is not apparent to LLMs. So when you start to do VLMss, which are vision language models, right? Like, you know, you start to teach them a little bit about image p- part of it, VLMs are still not generative. VLMs understand images, but VLMs can't generate images. So we have on this world where, like, you know, you have understanding in language and, and generation of text, and then you have, uh, models like Flux, which are good at generating images-

CS153 Instructor 26:07 Right

Amit Jain 26:08 ... right? Uh, which are great models, by the way, right? But then they don't have any of this understanding.

CS153 Instructor 26:13 Right.

Amit Jain 26:13 Right? And I think Andy talked about that last time as well-

CS153 Instructor 26:15 Yes

Amit Jain 26:15 ... that, like, there's this big chasm in between these two things. Understanding is separate and, and, and language is separate-- oh, sorry-

CS153 Instructor 26:20 Generation

Amit Jain 26:21 ... generation is separate. But in language, that's not true. An LLM is good because it understands text and generates text all in one go.

CS153 Instructor 26:28 Hmm.

Amit Jain 26:29 Right? There's no, there's no delta in between. There's no two models that are actually doing it. If we want to solve world understanding and, quote-unquote, "world models" that people are calling it, that's what we need to do.

CS153 Instructor 26:40 But, um, we've-- I mean, for at least about a year, I guess, we've had models that can generate language tokens and image tokens, right, with NanoBanana.

Amit Jain 26:48 Right.

CS153 Instructor 26:48 But they, they were-- like, NanoBanana was still not able to generate... I, I, I remember trying to generate schematics-

Amit Jain 26:54 Right

CS153 Instructor 26:54 ... like this.

Amit Jain 26:55 Uh-huh.

CS153 Instructor 26:55 I, I tried to generate the factory slide-

Amit Jain 26:57 Yeah

CS153 Instructor 26:58 ... with NanoBanana. I couldn't.

Amit Jain 26:59 Okay.

CS153 Instructor 27:00 Why were the capabilities still not there with basic sort of like these jointly trained models?

Amit Jain 27:04 So from what we know of Google's architecture, NanoBanana is still a fused architecture-

CS153 Instructor 27:08 Mm-hmm

Amit Jain 27:08 ... where, like, you know, there's a large diffusion tower that is generating, uh, um, images, and there's a large language tower that is generating text, and there's, like, a thin bridge in between them. So like, you know, you generate huge amount of text that's called EP, enhanced prompt, and that text you take and give it to the image model, and that image model's job is now interpreting that text using a very thin, narrow, uh, VAE, right? Like, you know, uh, um, and, and some encoder. Uh, I don't know what Google uses for their internal encoders, but these encoders are like seven hundred million parameter, eight hundred million parameters. That's the best you're able to actually get out of it. What we are building in unified architecture is different.

CS153 Instructor 27:44 Hmm.

Amit Jain 27:45 So our approach is-- well, transformers are probably the single thing, like, if, you know, I was coming back in time, this is what I would bring with me-

CS153 Instructor 27:53 Hmm

Amit Jain 27:53 ... the transformer architecture. Uh, and I would give it to people that, like, "All right," you know, "go, go, go play with this." Transformers are very good at-- they don't care actually what kind of information you're passing through them, right? Continuous, discrete, actually it's all okay. It's the pre and the post of it that, like, you know, the encoders and decoders when actually things start to fall apart. So in unified architectures, what we are building are these, uh, um... Actually, let me-- I didn't order it correctly, but anyway. Uh, this is a pretty bad diagram of that because, again, it is a-- I didn't try to go with a architecture diagram. But that's, that's kind of the idea. One single transformer or maybe one single backbone, you encode this information in the same space, whether that is audio, image, text, code, doesn't matter really.

CS153 Instructor 28:37 Hmm.

Amit Jain 28:38 And then you reason about them all in the same backbone, just like the human brain, right? So human brain, while it has, uh, you know, uh, uh, uh, different, different, different areas for processing image information and, uh, uh, um, or visual information and auditory information, those kind of things, but those are just encoders. All of that information then goes into the neocortex or maybe a little stages before that, but anyway, it ends up in neocortex, and reasoning and thinking and, and, and all the judgment happens in one single place. This is how we build the next generation of great models, right? Like, you know, that are able to do more tasks than what LLMs are able to do.

CS153 Instructor 29:16 Hmm.

Amit Jain 29:17 It took us about a year to come up with this architecture. A huge number of failed attempts, uh, uh, you probably know, right? I don't know how long I have been talking about this. Huge number of attempts at, uh, uh, trying to scale them, all of that things. But now we are at a place where we are pretty comfortable and confident at building, uh, like, you know, hundreds of billions of parameter models out of this architecture, and we know that it is going to scale. So now there's efforts within the company at all of these modalities, but one single model, one single architecture, including language.

CS153 Instructor 29:45 Right.

Amit Jain 29:45 So yeah, that's unified architecture for Luma.

CS153 Instructor 29:47 Makes sense.

Amit Jain 29:48 Yeah.

CS153 Instructor 29:48 Did you have any more before we switch to Q&A?

29:50 – 34:52

The skills/tools/model stack: how Luma agents turn expert craft into reusable leverage

Amit Jain 29:50 Uh, yeah. So actually, uh, let me talk about how we deploy these architectures, first of all. So this is what we are trying to build. If we wanted to do end-to-end work, this should be very familiar. Like, you know, if you've taken CS class, it's the REPL loop, read-eval-print loop. This is how computers work, have worked for a very, very long time. If you think about the von Neumann architecture, it is built around, like, you know, the REPL loop generally. It was not thought about at the time this way, but now we think about it this way. If you want to deploy models to not just produce, like, you know, text tokens or image tokens, but actually to do work, end-to-end work, how do you build these systems? So how do you do that REPL loop? One way is doing the left one, where, like, you know, there you have different models for each kind of things, and there's, like, two schools of thought. You produce federated models or, like, you know, you have this kind of like-... tiny models that are each doing specialized work, and then you, you make them combi- or, or you just pass outputs from each other, and you probably have a judge model on top that, like, you know, judges and orchestrates all of that work. That's approach one. And approach two is that you have these, like, you know, mega models in the middle, [chuckles] um, where they have-- where they share this, like, you know, deep connective tissue, and they can reason in one single space. And you give them, you know, inputs, and you expect outputs of them. They're iterative models, so it's not like, you know, one shot all the outputs that are gonna come out. But we are betting on this second approach.

CS153 Instructor 31:12 Hmm.

Amit Jain 31:12 And the reason is very simple, because we think intelligence is not this pipeline architecture problem. If you think about the systems of intelligence, the systems of intelligence don't look like, you know, this kind of big database problem. The systems of intelligence look more like the human brain, where you let information itself design the architectures and circuits inside it, like what we do during training, and hopefully very soon in continual learning, these circuits will change as we, as we are actually, uh, you know, using these models. And then you sort of step away from that. [chuckles]

CS153 Instructor 31:43 Hmm.

Amit Jain 31:44 You manage context outside. You, you know, manage memory, sometimes outside, sometimes inside, like how you do with caches in, in CPUs today. But the actual processing unit are these unified models. So that is sort of our approach of how we, how we think about building them. And how we think of improving them is a little bit like this. So if you wanna think about, like, what is the computer of the future looks like, actually, what is every agent product today, uh, it's some version of this, basically. Like, you know, this is not a big revelation. This is how things are being built. So you have, like, you know, a tool harness in the middle. Uh, I'm gonna go from the middle up. This tool harness means systems that can use Linux, systems that can use, uh, you know, call APIs, all of these kind of things. But then how does it all work? How does it actually full work gets done? So you have this, like, fat stack of skills on the top. These are domain-specific understanding, right? So you wanna teach a robot, like, you know, how to assemble something, right? That's not a normal thing, right? Like, you know, if you wanna think about, like, how is an iPhone assembled, this is a very domain-specific thing. You can give it all that information. It doesn't need to be in the model. It doesn't even need to be in the tools. You give this information as context, and you can do this across huge amount of verticals, huge amount of, uh, like, you know, uh, different task in those verticals. Then you have tool harnesses, where you give it as general ca-- ability to call tools and, and things like that. And finally, orchestrating all of that and thinking through all of that is this unified model-

CS153 Instructor 33:08 Hmm

Amit Jain 33:09 ... at the bottom. That is interpreting all of this multimodal information, generating tool calls, understanding which skills to use, and producing the outputs. So this is how we think the architecture of the future o- of computers will look like, and this is what we have built the current product basically on. This is, this is basically built on this-

CS153 Instructor 33:27 Right

Amit Jain 33:27 ... kind of architecture. Yeah.

CS153 Instructor 33:28 So c- actually, could you just do a one-to-one mapping? So-

Amit Jain 33:31 Yeah

CS153 Instructor 33:31 ... here, where, uh, where was the harness? Where were the skills?

Amit Jain 33:34 Yeah.

CS153 Instructor 33:35 Where was the model?

Amit Jain 33:36 So actually, when it generated these slides, right, someone on our team who's really, really good at producing greatly designed slides wrote a, I don't know about, it's a 50-page document on what it means to design good slides, right? And if you see, ac- I don't know if the prompt is there. Um, I've got a clear picture. Now kick off planning and generation. Okay, so after this, it would have, uh, said like, "Oh, let me look up the skills I have, like, access to."

CS153 Instructor 34:02 Ah, so that was the skill.

Amit Jain 34:03 That was the skill.

CS153 Instructor 34:03 That's a general purpose, um-

Amit Jain 34:06 Slide skill

CS153 Instructor 34:06 ... like, best-in-class slide creation skill-

Amit Jain 34:09 Correct

CS153 Instructor 34:09 ... that was created internally by a human and then uploaded for anybody else to use-

Amit Jain 34:12 Exactly

CS153 Instructor 34:12 ... automatically.

Amit Jain 34:13 Exactly. Uh, so that's the skill layer. Then, uh, the model layer is obviously the one that is generating and, and generating the tool calls and all of these kind of things. And the tool layer here, so not many tools were necessary, but I, I, I think, like, you know, your image that, that you gave, that was also passed as context.

CS153 Instructor 34:29 Right.

Amit Jain 34:29 And we probably ran OCR on it just to, like, you know, see, like, you know, what, what kind of things are. So this was not a very tool call heavy thing. But had you asked it to make an interactive webpage-

CS153 Instructor 34:39 Right

Amit Jain 34:39 ... that, like, you know, animates all of this stuff, then we're gone and call, uh, uh-

CS153 Instructor 34:43 A different skill

Amit Jain 34:43 ... coding tools.

CS153 Instructor 34:44 Right.

Amit Jain 34:44 Uh, tools to, like, you know, run that code, uh, uh, deploy that code, all of these kind of things. So it will have done all of these things, but it's the underlying model that is orchestrating all of that.

34:52 – 42:37

Business and market dynamics: capital intensity, enterprise adoption, and creative productivity

CS153 Instructor 34:52 Okay, I'm gonna ask you one last question before we switch, which is... Okay, so it took a couple years to put the whole system together-

Amit Jain 34:59 Mm-hmm

CS153 Instructor 34:59 ... which is a fairly high-scale system. Can you talk about the business for a sec? You announced earlier this year-

Amit Jain 35:05 Yeah

CS153 Instructor 35:05 ... I think you raised about a billion dollars.

Amit Jain 35:07 $1.5.

CS153 Instructor 35:07 $1.5 billion.

Amit Jain 35:08 Yeah, total.

CS153 Instructor 35:10 Yeah. Over your lifetime, Luma's raised about $1.5 billion. Of that, I think a billion was raised this, this-

Amit Jain 35:14 This year

CS153 Instructor 35:15 ... these last 12 months. Um, you know, it-- why does, why is this such a capital-intensive effort if it's not as high scale as language?

Amit Jain 35:23 If you really wanna do it correctly, it is larger scale than language because it is strictly a superset of, like, you know, the work that is going on in language. But currently, we don't care as much about coding, for instance, so we don't have to spend that much effort towards it. We can go towards all the areas that language models are not good at, and that means we can actually have a subscale compute infrastructure, subscale data infrastructure, things like that, so it doesn't require 100 billion yet. Uh, like, you know, we can do with one billion what, like, you know, generally takes five, 10 billion annual run rate to be able to produce. Um, but if you think about it, like, where things are going, uh, you know, in one year, two year, three years' time, we believe that these systems will far surpass language systems-

CS153 Instructor 36:07 Hmm

Amit Jain 36:07 ... just because of the access to more data. More data is better, right? Just because of their understanding of more domains. So I'll give you an example. One of our customers who's using these systems, uh, they work in energy industry. Uh, you can guess who that is. Um-

CS153 Instructor 36:21 Right

Amit Jain 36:22 ... and now suddenly, like, you know, our systems have no idea about, uh, like, you know, grid systems. Like, all right, like, you know, how the energy grid actually works and, and, and how they wanna be able to do that. So what we did isWe started to ingest their energy grid diagrams and energy grid code and all of these kind of things. And suddenly, our systems are better at producing schematics and planning than Anthropic's coding models are because they can't actually read all that information.

CS153 Instructor 36:46 Hmm.

Amit Jain 36:46 They can't actually see like, you know, how the things are laid out, that sort of problems. It's a very small example. Um, studios have another big example where like, you know, yes, LLMs they have had forever, but a story is not just text. A story is all of the physical stuff that is happening. If it has visual understanding, it can do much better. So we believe like, you know, especially as the age of robotics comes about, you will need these systems to be general-

CS153 Instructor 37:09 Right

Amit Jain 37:09 ... and these systems to be able to do everything, including writing code, and, and that's kind of where we're gonna go. But today, this gives us a very great business where language models are not really playing. Um, currently, we are... Like, you know, when we started the company, I mean, we were very small. Today, we work with some of the largest studios in the world. Now, we work with the largest advertising agency in the world, Publicis. They're just deployment channels for us. We work with the second-largest brand in the world, Coke, who is moving three billion dollar of annual production of, of content to Luma, basically. And, um, in addition to that, like, you know, in, in, in some of the areas like how do you do work just in a company, how do you communicate information visually? The- there's starting to be like, you know, these new areas in which previously only designers and, and artists could work. Now, everyone is starting to do that work.

CS153 Instructor 37:56 Yeah. So th- this was... You know, you had an event earlier this year.

Amit Jain 37:59 Mm-hmm.

CS153 Instructor 38:00 I mean, like I think it was three weeks ago-

Amit Jain 38:01 Yeah

CS153 Instructor 38:02 ... in SF, and I came by, and the thing that shocked me was that it was all artists and creatives, and y- I mean, you spoke for a little bit off the stage, but then they got you off the stage.

Amit Jain 38:11 Yeah.

CS153 Instructor 38:11 And then a bunch of folks from Hollywood came by, a bunch of designers, and it was the first time I'd seen so many artists and creators, not, not like machine learning people-

Amit Jain 38:21 Yeah

CS153 Instructor 38:21 ... but creatives excited about using tools. W- w- why has... That, that's, and that's very new.

Amit Jain 38:27 Mm-hmm.

CS153 Instructor 38:28 But, you know, there was a lot of-

Amit Jain 38:30 Negativity

CS153 Instructor 38:30 ... fear, uncertainty, doubt a couple of years ago that this was going to actually take away jobs in the creative industry.

Amit Jain 38:35 Yeah.

CS153 Instructor 38:35 Um, but for whatever reason, th- these folks, these are some of the biggest names in, in creative, in the creative world-

Amit Jain 38:41 Right

CS153 Instructor 38:42 ... um, some of whom were actually opponents of, of the technology a couple of years ago. What, what, what changed?

Amit Jain 38:47 I think the technology at that time was not good enough, and they were just looking at it from the angle of like it's... First of all, it's using all our data, and it's not good enough. So what is the point of all of that? But through all of this work that we have been doing, now the value is starting to become just, it's in their face, right? So when we go and talk to companies about, uh, uh, our work and, and, and what the products are doing, what we do is very simple. [chuckles] We actually sit right there, and someone will open a board and, and start to produce this. So actually, this happened recently at, uh, uh, a gaming company, Savvy Games, and, uh, you know, they produce Monopoly Go and some of the m- most played games in the world. And we were talking about it, and everything was hypothetical. It's like, "Oh, it will scale up production. It will reduce cost," all of these kind of things. And then like, you know, I was just-- I took a c- couple of like, you know, their assets, and we produced like, you know, a- about a 500-scale campaign while we were sitting and talking about it, right? Like, you know, it's like you can do it for all of these different, different things, and we showed like right there. When you see that, it's the same thing that coders are having that moment today. It was all slop before, right?

CS153 Instructor 39:47 Hmm.

Amit Jain 39:48 Slop just means... When someone says slop, it means they have never seen or used a good AI system before, right? When you see the results and you're like, "This is as good or better than what I can produce," or at the same, same, the similar ballpark at least, their minds change.

CS153 Instructor 40:01 Hmm.

Amit Jain 40:02 Hollywood studios were and, and still are like very apprehensive. But now when they start to see like, you know, the production that we have coming out, we actually show them, and they're like, "There's no way this is AI generated." And then we show them the back- backstage production of it, right? Like, you know, and then that changes my hearts and minds. So the best way to change hearts and minds is to just do good work-

CS153 Instructor 40:18 But-

Amit Jain 40:19 ... and actually show them

CS153 Instructor 40:19 ... but, but why does that... Does that mean the existing folks in those jobs have more productivity, or they're, they're getting ch- stuff done faster? Like what, what is the benefit to the creative? Let's put the business-

Amit Jain 40:30 Yeah

CS153 Instructor 40:30 ... people aside for a sec.

Amit Jain 40:31 Yeah.

CS153 Instructor 40:31 The actual, the creatives who are using these tools, what, what's the benefit to them?

Amit Jain 40:36 Yeah. I think it really changes the game of what they're able to do, so in, in a couple of ways. First of all, right now, execution is at a premium.

CS153 Instructor 40:45 Hmm.

Amit Jain 40:46 So you do so much work to validate the idea ahead of time, and like, you know, this is all across AI, by the way, not just like, you know, for Luma. You do so much work like, "Oh, is this the right idea once we put the execution resources on it," right? Like, you know. But think about it. It just, it just changes the equation completely. It's like, all right, let's execute on all of them and produce-

CS153 Instructor 41:02 Ah, I see

Amit Jain 41:02 ... the thing, and we'll see which one is great one. When you think about some of the best creatives in the world, and I, I don't mean creatives like just visual creators, right? Like, you know, people who made anything. They end up being prolific. If you look at their life afterwards, right? Like, you know, uh, if you look at Einstein's work, right? Yes, relativity is huge, but there's also like, you know, a huge amount of work that went into, uh, um, like, you know, Brownian motion, huge amount of work that went into light, uh, and like, you know, uh, uh, lasers and which he, for he got photoelectric effect, right? If you look at Archimedes, incredible amount of work. If you look at Mozart, uh, you know, just ungodly amount of work. Some of them was good. Some of them was not so good, right? People who are great at what they do are not just one-shotters. Like they, they actually produce a huge amount of stuff.

CS153 Instructor 41:43 Hmm.

Amit Jain 41:44 Currently, if you look at just our industry, artists and creatives are stuck in this industrial system that measures every action they do by the, by the like, you know, output that they're producing. This is no way to do great things. If you wanna do great things, you should have-

CS153 Instructor 41:57 Ah, I see

Amit Jain 41:57 ... the liberty to just like explore basically, uh, you know, unconstrained. When they start to use our stuff, they feel unconstrained, and I think that is what is bringing a lot-

CS153 Instructor 42:09 I see

Amit Jain 42:10 ... of creatives on board.

CS153 Instructor 42:11 'Cause you can paralyze-

Amit Jain 42:13 Exploration

CS153 Instructor 42:14 ... output. Exploration. I see.

Amit Jain 42:15 Right? And then you get to produce better things than you could ever do. It's more enjoyable because, you know, you're not in the slog of like every single pixel and all these kind of things. You become, come at a higher level.

CS153 Instructor 42:25 Right.

Amit Jain 42:25 This is what the moment coders are having too. It's like all these ideas I had, they're not just stuck anymore. They're now-

CS153 Instructor 42:30 You can prototype

Amit Jain 42:31 ... I can just try them out.

CS153 Instructor 42:31 Right.

Amit Jain 42:32 Yeah.

CS153 Instructor 42:32 Okay. Uh, I think we should switch to-

Amit Jain 42:34 Yeah

CS153 Instructor 42:35 ... Q&A. I'm sure there's lots and lots of questions.

42:37 – 44:59

Q&A: OpenAI Sora pause, focus as organizational physics, and what it signals for the market

Amit Jain 42:37 So the question is-What is my hypothesis why Sho- Sora shut down? Whe- whether it's a business reason, it's an architecture reason. And two, what impact does it have on us in the industry, but also, like, you know, on creatives? So, I mean, I can only give you hypothesis. I don't know really what is happening inside, uh, uh, OpenAI. But, I mean, the, the, the one word here is really focus. OpenAI, at the core of it, is a large language model lab. What they do really, really well is produce models that are very good for chat particularly, right? Chat is a vertical that has, uh, about eight billion customers, right? Um, maybe not little kids, but if you... Maybe they too, right? Like, you know, because they wanna talk to a computer. So pretty much all of humanity is a good customer of chat. Executing on that is a really hard problem. Executing on anything at that scale, you need to go into the depths of hell to be like, you know, get everything working really, really well. When you do everything, that's really hard to do. I mean, Luma also had that problem actually, right? Like, you know, in early days when we, we were not really clear about how do we execute on this, so we tried a lot of parallel paths. But doesn't matter how much money you have, doesn't matter how much, how many people you have. Uh, this was also a lesson from Apple. There's, uh, way more things at Apple that they choose not to do than they choose to do, right? That is because it doesn't matter the money, doesn't matter the people, the organizational physics still come into play.

CS153 Instructor 43:57 Less is more.

Amit Jain 43:58 Exactly. There's only so much attention you have as a company, not as a person, but as a company, that you can actually devote to making something. So OpenAI doing literally everything is not good for their business, and I think that is a realization that is setting in, and I think this will not be the last thing that they have actually canceled, right? There might be actually even more. Um, one thing I will challenge is OpenAI was not the largest player in the market. It is actually Google that is doubling down on, on video, on images, on visual generation, right? Like, you know, Gemini are... Gemini has great models that, that do pretty much all of these things actually. It doesn't indicate actually anything on the size of the market. It just indicates that they are getting their [audio cuts out] kicked because of lass of, le- lack of focus by Google, by Anthropic, and those kind of things, and they have to focus if they wanna go IPO, right? And that is the market that we are actually entering at this point. For Luma, what does this mean? Uh, I mean, this is great news. This validates like, you know, our, our, our thesis that, like, you can only do so many things at a time. And, um, this is the area that we have chosen to go in because this is a very, very big market with huge number of people that

44:59 – 57:36

Q&A: Copyright, model architectures shifting (GANs → diffusion → hybrid), and the remaining gap to “world models”

Amit Jain 44:59 call it their profession. So it actually gives us, uh, very good footing in, in the same market. So that's what I would say. So the question is, given that anyone can make a video about anything and content about anything, what happens to copyright, right? So I think copyright and the ability to produce something are orthogonal problems, right? If you're talented enough, you can make Mickey Mouse in Photoshop, really, uh, and you can actually produce great stuff about Mickey Mouse. Like, let's say you're DreamWorks. You don't have rights to Mickey Mouse, but you have all the people who can actually produce anything related to Mickey Mouse, which you don't. Why? Because the law exists that, like, you know, prevents you from doing that. So I think none of that has changed. Has it become easier to violate other people's copyright? Yes, I think so, right? You didn't ask me, like, what the responsibility of platforms is. Again, the responsibility of the platforms is the same as it was for Photoshop, right? Like, you know, it's not Photoshop's responsibility to prevent you from producing Mickey Mouse. It's your responsibility as a law-abiding citizen, um, to not violate the law of the land.

CS153 Instructor 46:07 Hmm.

Amit Jain 46:07 So I think it is pretty much orthogonal, basically. Like, you know, generative AI doesn't change copyright in any way, shape, or form, um, at least on the output side of it.

CS153 Instructor 46:15 But specifically, if there's a law that says you can't do XYZ, you'll, you will adhere to it.

Amit Jain 46:20 Absolutely.

CS153 Instructor 46:21 Yeah.

Amit Jain 46:21 If we get a DMCA notice, we'll take it down, right? Like, you know, if you're hosting it.

CS153 Instructor 46:25 Right.

Amit Jain 46:25 Um, if that person used to create it, and we get a, a call of like, all right, like, you know, this person made something, it is not our responsibility to point law enforcement to them, right? Like, you know, because that's not the law of the land.

CS153 Instructor 46:36 Ah, right. That... I see.

Amit Jain 46:37 So.

CS153 Instructor 46:37 You, you have... You, you protect the users in that case.

Amit Jain 46:39 That's right.

CS153 Instructor 46:40 Right.

Amit Jain 46:41 So the question is, um, GANs were very popular 2017, 2018, and now-

CS153 Instructor 46:46 Yeah

Amit Jain 46:46 ... you know, the world has shifted pretty much entirely towards diffusion models. What is the space of GANs in today's models? Uh, or today's architectures, basically. Um, that's a great question, actually. We still use GANs quite a lot. We use techniques from GANs quite a lot. But GANs are one of the most finicky architectures to ever work with. So GANs, if you don't know, are generative, uh, uh, like, you know, adversarial networks, and as the name says, they're adversarial networks. So, like, you know, you, you design the, the, uh, uh, objective in a very different way to diffusion models, right? Like, you know, very... You have a very predictable gradient descent. I mean, they still explode sometimes, but it's a very predictable system. GANs are still actually used quite heavily in distillation networks. Like, you know, if you wanna do distillation, like, GANs are actually pretty useful. Um, if you wanted to do a real-time system, you would still go to GANs quite a lot. But because GANs are just not very predictable, researchers don't wanna work on them. [chuckles] And that is the laws of, like, you know, physics in, in AI. What researchers wanna work on is generally what will get worked on, right? Like, so I can, I can make the case that, "Hey, Rust is more efficient." Doesn't matter. Everybody wants to code in Python, so that's what will be done. But also, GANs have not shown the kind of scaling that we are seeing with transformers, right? Uh, GANs are primarily, you know, UNet-based and, and, and convolution-based models, and they just don't really show the kind of learning that you can get from transformers. Can GANs be implemented using transformers? Yes, there are some papers about it. But at that point, you're really, really trying very hard to, like, you know, just, just do GANs, and, and that's okay. But diffusion models also now are on the way out. So, uh, I know this will be a little bit controversial if people are thinking about it, but diffusion models have physics that is not actually bearing out on scaling side of it. So Luma and, and some other companies are actually moving away to hybrid autoregressive and diffusion regimes. That's what our, our, um, unified models actually are. Because diffusion models actually have some really, really bad habits that are hard to unlearn and hard to, like, you know, get out of, of the system. So they're also on the way out, actually. So yeah.

CS153 Instructor 48:46 It's a very, uh-Um, if, if you realize basically when we first started teaching the class, Mike, there, there, there were debates about what the right l- programming language was for, for security, and it feels like architectures have come full circle, basically. Don't-

Amit Jain 48:59 Sure.

CS153 Instructor 48:59 It-- Uh, m- good note for office hours this week.

Amit Jain 49:03 The question was, as models get more and more powerful, what is the space of human creativity, especially in these unified models that can do pretty much all tasks, visual tasks, language tasks, all these kind of things? My stance on this has been actually very, very sterile from day one. I don't think anything the model is doing is creative or not creative. Whether it's creative or not creative is for humans to judge. That judgment alone is the act of creation, right? What you choose to do is an act of creation. What-- How I tend to spend my time is actually a very creative endeavor, right? Like, you know, it... because it will produce outputs that people will generate, consider creative or not creative. But more importantly, in a practical physical system that is an AI system, how-- where is human-- where is the role of human? It's in that fat skills area. This is why our slides look good, because someone who knows this really, really well went in and taught the model a million times over that, like, you know, this is what good looks like to humans, and this is what bad looks like to humans. This is just like programmers, right? Like, you know, before, artists never had this kind of huge leverage. They did something once, and it will run a billion times, right? Programmers have always had this leverage. You write the program once, and it will run again and again and again and again on everyone's computers, on everyone's phones many, many times over and produce value. Artists produce one thing, and then that's one thing. That's it, right? Now, other creatives in the world, not just programmers, have this leverage because of this architecture. You teach the model once, and they're able to produce like, you know, huge amount of really, really great things in different contexts. This is actually an explosion of creative potential that just never has been, right? So the skills and human creativity are much more important. Actually, it will weed out people who were mediocre, and it will, like, elevate people who are really great to even greater heights because now their work will be rerun a trillion times over. Okay, so Hollywood is default dead right now, right? And that has nothing to do with AI. Uh, that has really nothing to do with any of the technological changes recently. Hollywood's business model has been deteriorating for the past thirty years, and COVID really accelerated it, and then the writers' strike just was the nail in the coffin. Um, at this point, we are at a place where, like, you know, this production that I'm talking about is the first production in LA proper in the last five years. First production, because all production has moved out of Los Angeles. Think about it. Hollywood doesn't make movies anymore. Hollywood finances them, but doesn't make them.

CS153 Instructor 51:29 Where, where are they being made?

Amit Jain 51:31 In Greece, in, in Canada, in, in Ireland. Wherever you get tax incentives, you're gonna make it there. So what does so-solving this problem actually mean, right? First of all, Hollywood has to stop thinking like PE. Currently, Hollywood's business model is like a private equity. Oh, Guardians of the Galaxy was a great hit. Let's make number two, number three, number four, number five, number seven, number ten, number twenty, right? Uh, uh, l- how many Avengers are there now? I don't even know, right? And how many crossovers of Avengers and Spider-Man? And I'm-- won't be surprised if, like, you know, Tintin is in there one day, right? [laughs] Uh, like some multiverse thing. Uh, as a physicist, that's a really troubling thing for me, the multiverse universe, right? Um, that's not how it works at all. Um, but it is emblematic of a PE mindset where like, all right, we created a franchise, we created an asset. How do we rent-seek that asset the most we possibly can? But, you know, audience don't think like that. More and more people want to watch great things, want to go to theaters, want to actually like, you know, watch things on their phone. That is emblematic in Netflix's growth. I mean, the, uh, on Thursday, you're gonna see like, you know, the, the, this quarter results. I'm not saying buy or sell anything. Uh, but like you've seen the growth of Netflix, and they produce eight hundred productions a year compared to like, you know, the, the five, ten, twenty that large studios are producing right now. That is a PE mindset. So those eight hundred productions don't have five hundred million dollar budgets, right? They have, uh, uh, like, you know, they're like ten million, twenty million, thirty million, fifty million dollar budgets, and this is how they're scaled. What does this allow? This allows different kinds of, and more kinds of stories to be told, and that means it appeals to a wider audience. So your platform then becomes more appealing to more people. Are they making again a Harry Potter? Yes. I'm very happy about it, by the way, right? But this is also PE mindset that like, why are we making Harry Potter when we have so many other great books that should be made again and again and again and again, right? They shou- sorry, shouldn't be made again and again. So Hollywood has been default dead for a long time. If nothing changes, this is not about AI again. If nothing changes, all those jobs are actually already gone, right? Um, the, the people in those industries know that. AI is a chance to actually change the business model once and for all. Because you can move away from these massively expensive production methods. You can move away from these huge, huge, uh, you know, time and capital sinks and go back to an era where like, you know, many, many ideas can be tried and one has a shot of building people into the, you know, into theaters. Ryan Gosling from Hail Mary, if you have not seen it, great movie, uh, makes a great point. It's not the audience's job to come to the theaters to s- you know, keep Hollywood alive. It's Hollywood's job to make great things so the audiences want to watch it. You can't blame your customer-

CS153 Instructor 54:13 Um, what I'm gonna do is... That was well said, and I think the PE mindset is, uh, is m- is going to come up over and over again, where capital markets, where- wherever they look for predictability-

Amit Jain 54:23 Yeah

CS153 Instructor 54:23 ...um, we tend to find a stagnation of innovation, and I think that's, that's hurting a lot of people.

Amit Jain 54:28 That's a great question, and that's the one that like, you know, the whole company spends all their time thinking about, honestly. So the question is: What is the delta between where we are to getting to a place where world models, video models, whatever have you, are as generally used and useful as language models are today? Fair?

Speaker 54:44 Fair.

Amit Jain 54:44 Right. So i- there's only one word, basically: intelligence. That's the deltaSo currently, image models and video models that are not unified models are really, really stupid. And, and I mean that in a non-derogatory way of that, right? When I say stupid, I mean in, in this way. Like, when you work with a person who you don't consider to be intelligent, what are the signs? They forget what you said. You have to tell them the same thing again and again. They don't actually understand what you said. They kinda are a facsimile of understanding, right? It's like you said something, but they're like, "But that's not what I said." Like, you know, "Yes, you, you kind of interpreted my words literally, but that's not what I'm saying. You have no context of what I'm saying." They are able to do small things, but like, you know, when you ask of more of them, then they can't actually do that. This is what today's video models and image models are. All of them, basically, right? Um, that's what we tried to solve with UniOne. They need to be as intelligent as language models are. They need to have multi-turn, right? So when you, when you ask it something, afterwards, it needs to be able to go back and say, "All right. This is what I generated. This is what you had asked. I, I have memory. Let me iterate on it, and let me fix it." How annoying would ChatGPT be if you only had one turn on it, right? And then you had to repeat the thing and then another turn, and repeat the thing and then another turn. That's ridiculous, right? Nobody uses that. See, that was the difference between LLMs being a research project and them becoming generally useful. That was RLHF, right, that enabled chat multi-turn. So that was number one. Number two is, is how much intelligence did they actually have? So current image models and video models are beautiful pixel generators. They have really no understanding of what the hell they're generating, the physics of it, the, the introspection on it, all of these kind of things. Unified models are designed to solve this kind of problem. So when you use them in, in things like education, for instance, right? Like, you know, these slides could, uh... Sorry, not this one, but the ones I had, could easily be used for te- by teachers, right? With probably a lot more density, and I can show you really good examples of it producing really high-density things. Videos are some of the best explainers in the world, right? Imagine a history class that is not taught as drab text, but you can actually see, and most importantly, you can do alternatives. What if the Rubicon was not crossed, right? What if Caesar was not murdered? What if, like, you know, these things didn't happen? What if Archduke Franz Ferdinand was not shot in 1914, right? Like, you know, would there still be a World War I? I posit yes, and like, you know, we can go into that. But what if you see that flow out, you had this level of like, you know, uh, temporal understanding and coherency and these kind of things. Language models are getting there. Image and video models don't have that. That's what we need to solve. So that is the distance between them being just tools that can produce almost stock footage to things that can do end-to-end work.

CS153 Instructor 57:32 Awesome. Thank you, Amit, for being here.

Amit Jain 57:34 Thanks for having me.

CS153 Instructor 57:35 Thank you. [audience applauding]

Episode duration: 57:41

In the uListen app, the transcript lights up word by word as you listen. Get uListen

Transcript of episode 6nUl_w5W9Wk

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.