Roll eggs with Unity
In this short article I want to share the results of the suffering of this night. This is not an informational article that embodies the wisdom of generations. Just a set of notes.
To begin with, the result was this video . From the viewer's point of view, here's a video on how to make a mini-game on Unity from scratch. To be exact, she doesn’t answer any of the definitions from Schreiber’s set, but she doesn’t give a damn. Seriously, if you consider yourself stupid and not capable of anything (I'm just that), then repeat as in a vidos and everything works.
But under the cut will be a little about the inner kitchen and the pain . This is only for those who write something themselves and want to discuss.
What is the goal : I need to deal with video production and development at the same time, and this is complicated without understanding the work of the video maker and the C # developer. As you know, the best way to figure out something is to try it yourself, and even better, do a video course on this.
What is not the goal : 1) Become a famous blogger, get involved in marketing, traffic surge, etc. This is the theme of a separate adventure for sometime later. 2) To produce a really high-quality video - I am not yet capable of this, at least in an acceptable time frame (two days).
What interesting conclusions were made from this recording session?
Microphone and Premiere
Have you noticed that in Lyosha Shevtsov’s earphones in the vidos are plugged into Blue Yeti? It seems now I can guess why. It turns out that the creators of Adobe Premiere 2019 in their wisdom do not allow to output sound to two different audio cards, if it is ASIO. Before, I somehow didn’t think about it, but now I’m traveling in Siberia, and of course I didn’t take a huge coffin of external USB sound with me - but in vain!
That is, naturally, switch to ASIO, and the settings block that Output disappears, you only have the ASIO channel mapping. And this means that if you record sound directly from BlueYeti using its built-in ASIO, then the surprise is that you can listen to what you recorded (just like listening to music from a browser with tutorials) only through a microphone! Listen to music through the microphone, Karl!
In general, there is such a cool ASIO router, O Deus ASIO Link Pro. The author of this program recently died, by the way, and did not transmit the source code to Open Source. Yes, that's just the license remained somewhere on the hard drive in St. Petersburg, and the outdated version from trackers is buggy on Windows 10.
Fortunately, the microphone has an audio output for minijack, where you can plug in the headphones. The mini-bad news is that this output also always monitors the microphone itself, so you won’t be able to listen quietly - with a minimum delay you will hear your clicks on the keyboard, heavy breathing, as a neighbor, Vasya, kisses Manya behind the wall, and the noise of computer fans will acquire a new deep color. Well, you can constantly press the mute button on the microphone, of course. I would also record some video about this hell, but I don’t quite understand how to do it, because you have to write with the same microphone for the same Premiere :)
By the way, you ask, why ASIO? And because BlueYeti delivers completely different sound through MME and ASIO. I conducted a test - the same loud sound was played from the phone and recorded using both methods. MME option is incredibly worse. Straight to complete instability in case the microphone clips.
Due to the convenience problems with ASIO, I write the final sound to them, and the draft sound to the MME.
Have you heard how bad the sound is in this video? This is because due to frequent reboots (which will be discussed later), I lost my final ASIO record, and I had to do it on an MME draft. There was simply no strength for the second take. Anyway, is it zashkvar writing with takes? :-)
Adobe Premiere 2019 as such
Previously, I glued the video a little in the old versions and therefore there is the opportunity to compare. The latest version has a lot of bugs. Perhaps this is partially due to Node.js, on which the new interface is written - Adobe has not figured out how to cook this beast. At the start, the Premiere creates several copies of the JS engine, which hangs in the form of separate processes next to it, and by killing these processes you can root out pieces of the interface. Redrawing is slow, with a load on the computer - it may not redraw at all (you need to resize the window with the mouse so that the redrawing starts). The interface has buggy transitions between states, which can only be exited by restarting the application - the analogue is “stuck in textures”. If you describe the sensations in one phrase, it will be "slows down and buggy."
Unfortunately, I can’t return to the old versions, because only in the fresh version a bug with Blackmagic captures was fixed.
A couple of words about the UI / UX interface itself. We are used to programming using perfectly licked things like IntelliJ IDEA and Eclipse, and trying to use something professional for other professions is usually very painful. I can’t even tell you what pain I experienced from what Premiere is trying to do to repeat Perspectives from Eclipse, it is directly physically painful to use it. Not to mention the fact that the interface directly shouts to you that it is desirable to have 2 monitors, and that monitor where the time line is, preferably in 4k UHD. And I, for example, have vision - minus 5 in both eyes, and this 4k nafig did not dig into how to be. Well, it’s probably not the Premiere is so bad, and the software development world is so good that we have tools with perfect UX. Developers make software not at the direction of analysts, but for themselves, and therefore understand
This is purely my personal problem, judging by the forums only a few sick people have similar behavior.
Under load, the computer hangs in a blue screen.
This is not my computer, but a temporary computer that exists while I am visiting Novosibirsk. Therefore, changing it is not possible / reasonable.
I read the contents of crash dumps, there is nothing intelligible, which most likely means a hardware error, which Windows can only escape from without stopping the state. Starting at some point, the crash dumps stopped writing, however, it seems like you should blame Windows Insider Preview. But there are blue screens on a stable version of Windows too.
At the previous iteration of the proceedings, I changed the thermal paste on the video card and ran it under MSI Afterburner with a downlock in all respects. Which led to a decrease in the number of freezes. I was even able to play on record in something easy like Overwatch, for a short time.
It also led to an increase in the loss of the stream, because it turned out that my Wirecast is not very friendly with Afterburner. True, he calls it differently - "Afterburner can lead to system instability, if this happens, remove it."
A lot of fakaps happened during the recording of this video.
Firstly, due to frequent reboots, I lost the final version of the recording, as a result, everything had to be done on top of a draft with disgusting sound recorded through MME instead of ASIO.
Firstly, it turned out that somewhere a minute of a normal creatively meaningful video takes an hour of editing. That is, the entire video for twenty hours can easily take a whole month. This is no good. Therefore, to speed up the process, I started by replacing the brain with more quick-acting effects from the tutorials on YouTube, blinded together and was pleasantly surprised by the effect. Especially saves time by not using the greens.
But it turned out that the video was going to render for 4 hours. I, in principle, do not mind. But the computer is a pity. At a distance of 4 hours, it freezes in a blue screen in 100% of cases. But the rendering results may also not like it!
Therefore, I had to, with a squeak of my heart, throw all this trash to the dump, and from the operation “brainless effects” go to the option “hellish trash”. The most difficult effect now is the picture transition, and this is calculated on the CPU almost faster than on the GPU. Rendering time was reduced to an hour.
And all would be well, but the devil swam there. For an hour, the computer was not able to work under load even once. I had to climb into the iron. I threw away all unnecessary extensions (such as USB wires) and rearranged the video card in PCI-E closer to the processor. By this, I intended to kill two birds with one stone: give vidyuha more air (it worked, the temperature dropped by 5 degrees!) And check if the problem is related to the buggy PCI-E.
The first phakap was immediately revealed: in the PCI-E, in which vidyuha worked normally, the HDMI capture card refuses to work outright. Well, she starts up, is identified in the system, but claims that she does not see the video stream. However, I don’t need it to record a trash video, so this is just a test: something is wrong with this PCI-E.
The second fakap is that despite such sacrifices, the computer still can not live an hour.
The last measure was to go into the BIOS and put everything there with your hands. Voltage (low), memory frequencies (manual, fixed, low), multipliers by 34, etc. Everything that was marked "smart", "intelligent" or "boost" went into either disabled or normal mode (this is for several switches that can save power and turbo besides normal - it is clear that both systems can fail ... and normal also can). He turned off all unnecessary peripherals, left only USB-3, in which Anker's hub with external power is now sticking out (what if the mother is unable to provide power to USB?). Turned off even VT-x, so 64-bit virtual machines, that is, all virtual machines, no longer work. I turned off the sound system too, I listened to the vidosiki via bluetooth headphones (disgusting, how do you use them in conjunction with a computer?).
But on the PCI-E video card I gave all the lines and agreed that all the other PCI-E on the motherboard will be turned off (two birds with one stone: and disconnect the possibly broken PCI-E, and it is possible to speed up the video card, if it suddenly knows how, I’m in this I don’t understand).
At this iteration, the computer lived an hour and rendered everything.
Now I'm suffering. Surely this is not a video card that is not integrated into the mother of a sound card, namely a combination of a sound card and a video card. Two areas in which driver writers don't give a damn. For example, on another computer, my blue screens were from a combination of an external usb sound and a network card, but that's another story.
It seems to be done, but I'm somehow morally exhausted.
1080 working recording solution
Самым рабочим решением (из имеющегося у меня железа) было захватывать видео и звук на Macbook. Сжатый захват можно делать прямо через OBS, а несжатым я бы ноут мучать не советовал, всё-таки SSD для записи это расходник, а на ноуте напаянный SSD не поменяешь. Ноут соединяется с Windows PC по Gigabit Ethernet кабелю, после чего все захваченные файлы быстренько копируются на виндовскую шару, прямо внутрь проекта Premiere. Единственная вообще цель этой сомнительной неудобной схемы — то, что ноутбук не перезагружается рандомно, как это делает мой PC.
Что-то сделано, что-то получилось. Буду делать дальше, даже если заминусуете в пол. Интересно было бы услышать отзывы других видеомейкеров ( если таковые здесь имеются) о их первых шагах и здравых вещах, которые нужно сделать в первую очередь.
It's half past five in the night. Or in the morning. It’s necessary to sleep for about three hours, then turn on the boost and have time to do yesterday’s work by the morning meeting, which I safely sent out with all this nonsense. Thank you for reading to the end. I'm not quite sure why you did this, but if so - respect and respect!