While doing our
first tutorial on the
engine , we faced a number of technical difficulties. We hope that this post will help anyone pass these pitfalls.
Actually the recipe itself in the title, well, there will be more details.
After the post was ready and the code was also thought out, written and approved by the whole team (along the way the meshes generator was written), it became necessary to type it in the engine window and record what was happening in the video file. We began to look for an application for high-quality video capture. For a start, we tried Microsoft Impressions - the quality of the captured video was so-so, due to incorrectly selected or configured codecs, and we refused to capture the sound directly, due to “incompatibility”, only through a microphone. I remembered the immortal MM Zhvanetsky: “And why our records are not suitable for our player? The curves are very? ”We concluded that the video capture should be carried out without compression, and only then, when the correct video was obtained, should we choose and configure the codec for compression. It also requires the direct capture of sound, without any microphones, and then neither sneeze nor puff when recording. We tried another 3-4 programs (none took the sound directly) ... Time, it was already late, we didn’t want to drag out the publication, and when we came across
fraps and tested its demo version, 37 green ones couldn’t stop us. The utility turned out to be convenient and did everything that was needed without any dancing with a tambourine.
Time, as already mentioned, was later and we found that to “fill” the tutorial with reasonable speed and rhythm, which will not deduce an innocent reader from himself, none of us are capable of and we have already decided to postpone or cancel at all publication, as someone remembered
AutoIt . On Habré, there was already a publication about this environment, we just say that this tool is exceptionally high quality and at the same time free, thanks to it we easily solved the problem of typing a script in the console of the engine. Along the way, a couple of bugs in our console showed up, and you cannot say that we were upset because we didn’t stumble upon them in the process of manually typing commands. Actually, in our case, the AutoIt script launched the demo scene, called fraps and drove the entire script with a given input speed and delays between line breaks.
As a result, we got a 3x gigabyte file with a clip. 5 minutes of working with
virtualdub helped to complete the epic.