Datasets:

samfred2
/

ATO_TG

+{
+  "file": "3 - Light Animation.wav",
+  "transcription": {
+    "audio_file": "3%20-%20Light%20Animation.wav",
+    "text": "In this lesson, I will show you how to create an animation of changing lighting. To do this, I copied camera number 10 because I will use this camera for the animation. We'll start by copying the world lighting settings. We'll select these settings as active. And the first thing I'll do is increase the frame count to 250 so that this animation is a bit longer than the previous one. The next step I need to take is to assign keyframes to the changing lighting parameters. In this case, at frame number 0, which is the beginning of my animation, I set the sun a little lower above the horizon. For example, to a value of 5 degrees. And I set its rotation to a value of 25 degrees. So the sun will be located roughly, very roughly, in this position. I also set the saturation to a value of 1, because I want to see how the temperature of my sun changes. With the parameters set like this, by simply hovering over them with the mouse or using the mouse cursor, I press the I key and assign a keyframe. Next, I move to the end of my animation, which is frame number 250. And at this moment, after changing to the color green, I assign the parameters that the sun will have in this frame. I'll set the sun's value above the horizon, for example, to 40. And the sun's rotation value is, for example, 135. So the sun will be roughly in this position at the end of my animation. The parameters should change to an orange color, and if that happened, I hover the mouse cursor again and select the key. And if everything is indeed correct, the parameters should turn yellow. I'm going back to the beginning of the animation. In this case, if we play the animation in this preview, we won't see anything at all. The frames will pass, but there won't be any result happening here. To see this animation effect in that preview, I need to transition over to the viewport shading view. Here, in the case of such an animation, a lot depends on your hardware. Because everything changes very dynamically here. And if I play the animation now, then I'll be able to see that change. It will indeed be quite blurry and unclear because the frame changes very quickly. But it will be visible. If you have a relatively low quality graphics card, you might have some issues with that. It might lag for you, it might take a long time and it might not be very clear. Look at how it looks on my end. I'm starting the animation playback and I can see how my lighting is changing. As I said, it's blurry, it's slightly out of focus because the frames change very quickly, which is visible at this point. But overall, it looks pretty good and I can imagine how my settings behave. If everything is okay and I decide that I want to have this animation in that form. So in this lesson, I'll render this animation. In the test version, I'll save it in the same directory as before. So moving on to the output, I have selected the directory for the animation. I'm keeping the same save format, which is FFMPG video. And then I set the appropriate resolution parameters so that the animation doesn't render super well for a long time, so that I can see how it looks and if everything is okay with it. I'll render it at a resolution of 40% of the intended output of 1920 pixels. So this animation will be at a relatively low resolution, but I think it will be more than enough for testing purposes. When it comes to samples, I'll set these samples to a value of 32.1 or 64. It gives me an effect that's quite blurry and lacking in detail. I won't know too much. They will be of low quality, but for testing purposes for the animation as I mentioned, it should be more than enough. I'll set it to maybe 64. If I've set everything up, I choose to render the animation. And we render the animation by pressing CTRL plus F12. We'll see how the individual frames are rendered. They will be rendered one after another, creating the entire complete animation. There are 250 frames, so this animation will take a bit of time. From one frame, it renders in just under two seconds, but it will still take a little while. During the rendering time, I'll pause the recording. The animation has been rendered. Let's see how it looks. It lasts eight seconds. As you can see, somehow, as I said, it's not great because a lot of elements are blurry, unclear. But as for the test animation, it looks pretty good and you can see the lighting changing well, the one we were setting. I think it's 100% satisfactory when it comes to the test animation. Final animations should of course be rendered at higher resolutions. And the absolute minimum here is full HD, which means the percentage value is set to 100. When it comes to samples, I think a good solution would be something in the range of 100 to 100. When it comes to samples, I think a good solution would be something in the range of 100 to 150. This is less than in the final visualizations, but the animations do change slightly. And here I think that by keeping the values between 100 and 150, we'll achieve a good compromise between time and quality. Let's not hide the fact that the rendering time for animations can be very long. If we take into account that for one second of animation, we have to render as many as 30 visualizations, let's say animation, it will last 30 seconds. So we need to do as many as 900 renders. That's a very large amount. So here we really need to optimize our time well and reach a compromise when it comes to quality. Nevertheless, with the parameters I mentioned, I think we can achieve quite good quality that will be satisfying. In the next lesson we'll talk about how to create an animation with changing depth of field.",
+    "language": "en",
+    "duration": 397.22,
+    "timestamp": "2025-12-10T17:37:14.274199"
+  },
+  "timestamp": "2025-12-10T17:37:14.411526",
+  "processing_time_seconds": 324.4056556224823
+}