Datasets:

samfred2
/

ATO_TG

+{
+  "file": "2 - Viewport Render.wav",
+  "transcription": {
+    "audio_file": "2%20-%20Viewport%20Render.wav",
+    "text": "We can save such an animation, that is, the animation from our viewport to a file. To do this, the first thing we need to set is to go to the output tab and, in the output section, first choose the location where the animation will be saved, and second, the format in which it will be saved. As for the format, we will choose the MovieFFMPG video format. When it comes to encoding in the container location, we will choose MPEG file. When it comes to quality, we can raise this quality to high quality. I will save our animation in folder number 10, animations. I select the path, choose the folder, and with all the parameters set like this, I select the view option and then Viewport Render Animation. After selecting, we can see that our Viewport animation is rendering. In the middle, we see a black square, where the individual frames that are currently being rendered and saved change. Once completed, we will have a click ready for preview. The animation is about to finish, so you'll see what its final result will be. The animation has been saved in the directory we specified. Once it's turned on, we can see what it looks like. It lasts exactly 5 seconds, which is what we said. This is an interesting and very convenient way to present preliminary animations to the client, as the time required to create such a 5 second animation is practically negligible, and the client will see how the camera will move in the scene. If there are several revisions needed for the animation, for example, the client is demanding and picky and has a lot of comments, as for the animation, working with this very scheme saves a lot of time. Under normal circumstances, we should probably create such an animation, even in a test version, but it takes more time than rendering from the viewport, sending the animation to the client and making a few adjustments. It's much more labor intensive and takes a lot more time. We can create the viewport animation in one more way. I will change the name of this animation to animation. Viewport. Shade. And now I can switch to the viewport shading preview, but not the one you've been working on throughout the course. Just a simplified preview. This preview might take a moment to load, because we have quite a few materials in the scene. It also heavily depends on your hardware setup. After loading, we can see that we have an outline of the material. There is no clear lighting here, but we can see. A little better than before, in the case of the shade preview. From this position, we can also render the animation or the viewport, but it takes significantly longer and puts more strain on our hardware. We do it exactly the same way, which is view and viewport render animation. It will save in the same directory and as you can see it's running a bit slower. Here the frames aren't changing as quickly anymore. And as I said the hardware is more strained but you can get a more interesting result. If it's not a problem for you, you can do the viewport render in this form. I'm going to pause the recording for a moment. The render has finished. It was saved in the same directory as before. We can display this. The visualization. We'll see how this animation looks. And we can see that it definitely looks more interesting than just the viewport. There are some materials, things are happening more, so as I mentioned before, you can prepare such a viewport snapshot. In one form, in the second form, in the next lesson, I'll show you how to create an animation of changing.",
+    "language": "en",
+    "duration": 248.69,
+    "timestamp": "2025-12-10T17:36:05.039164"
+  },
+  "timestamp": "2025-12-10T17:36:05.045512",
+  "processing_time_seconds": 255.03998374938965
+}