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
AVIs exported from Source FilmMaker tend to be broken in the way you're experiencing, and MP4s/MOVs exported from Source FilmMaker are either too dark and saturated or too bright and de-saturated, depending on the compression codec used.
Beyond that, the AVIs are also uncompressed, resulting in absurd file-sizes (which results in the broken AVI exports, as Source FilmMaker can only hold around 3-4 gigabytes of information in itself at a time, and it exports the AVI in one go), and the MP4s/MOVs have a much lower quality-to-file-size ratio than what you get from image sequence renders (as in lower quality but bigger file-size).
Image sequence renders, however, work by exporting the images of the session one-by-one (thus no broken stuff due to lack of RAM like with AVI exports), then using a program (often Blender or VirtualDub) to combine the images and sound file into a video, keeping the colours intact (unlike MP4s/MOVs exported straight from Source FilmMaker) and compressing it with a higher quality-to-file-size ratio (depending on render settings).