Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You do realize quicktime is a cyber threat
Yes. I knew that even before I installed it because I hadn't heard of quicktime before and wanted to research it. After doing some digging, and I mean a LOT of digging. Even now I'm searching quicktime 2018 exploit to see if anyone has any updated information about it, I found that it is specifically the QuickTime Player that has the exploit, not the quick time essentials aka the codecs. Source Filmmaker only requires the codecs.
All we can say is "not significantly different to it takes to render in AVI/MOV/MP4, but it will be much higher quality, is more stable than any other mode, won't mess up the lighting, and if SFM crashes three-quarters of the through you won't lose the entire render and have to restart from scratch, so why would you even want to use any other mode anyway?"
The only reason I don't want to render as image sequence is because I have a fear that it will take even more time to do that compared to rendering via sfm. Plus I don't know if software like Blender or Virtual Dub would do the converting automatically or if I have to spend time going through each and every frame manually editing, which I fear can potentially take longer.
... but it's a *massive* time saving every time it saves you having to do an entire render from scratch because SFM crashed, the video encoding corrupted, the contrast is completely shot, the image quality is completely crap or whatever.
You'll get much better and more reliable results out of image sequences, and once you're used to it, it's pretty much a couple of clicks to get the final encoding done.
In any case, yes, while a render from SFM may take hours, the encoding process is usually a matter of a few minutes. It makes very little difference to time, particularly as image sequences can actually render and export from SFM slightly faster in the first place.