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
menu Project-->Properties Best
( in the Render Templates , the "System Tab" has a
"Follow Project settings" , to "Follow\use" that "Best" setting )
CPU only ,...GPU can reduce qualtiy .
i only use CPU
.m2ts Sony AVC\MVC at 16 Mbps 1080 ( has always been real good )
( with 5.1 dolby audio )
"View Window" settings do NOT affect render quality , i use Preview-->Auto
"View Window" with "Simulate Aspect Ratio" ON
Does your imported video look good in the Viewer , while on the Time Line ?
How do the Sample screens look in the viewer , during rendering ?
They should look good during rendering .
If the rendered file looks bad , then the
Viewer window , during rendering , should have looked bad too ( a heads up , so to speak )
When the viewer window looks bad , during rendering ,..i know i will have
a bad looking rendered file . I then stop the render and redo the
render template settings . ( if i was playing with\testing render settings ) .
most Factory blu-ray movies are made at 25 Mbps .
some of the Main Concept Templates can do over 100 Mbps ( way too much ) .
if you want more bit rate , try Sony AVC\MVC .m2ts at 21 Mbps .
your video ,
2 causes :
a. your source footage was recorded at a very low bit rate ,....2.5 Mbps
....( there is No fix for this , the mosaic blotches are there to stay )
b. you have good qualtiy source footage , recorded at 14 Mbps or higher , 1080 video res ,
.....and then it was rendered at a low bit rate 2.5 Mbps
either way ,
your video has the classic look of "Low Bit Rate" video ,
regardless of it's resolution .
There is No fix for Low BIt Rate video .
the only Video FX effect that can pixelate is the "Min Max" plug-in .
Why are you using sharp for a complex video destined to Youtube? Sharp increase bitrate needs to keep good quality and you already is using a complex video with detailed vegetation+high motion and applying sharp for edges is making it wasting too much bitrate on that. Sharpen should be used only for low motion footage when sending to Youtube.
The foliage and jaggie edges in your video already demand a lot of bitrate and you make it be far more bitrate hunger adding sharp. So the codec has bad time trying to compress that and lack bitrate for the rest of scene and artifacting is a common sympton.
When you aiming youtube 1080p30@4Mbit you should avoid complex details, instead of potencializing that you should remove details instead before uploading for the codec not waste too much bitrate with details.
What i think is than Vegas encoders(Mainconcet/SonyAVC) were designed with movie like footage in mind where uses low framerate(24fps) and has low motion passing. Gameplays has too much motion and high complex scenarios and in this case Vegas encoders struggle to keep quality because their are not tuned for this. Yet the encoders are old and bad.
If you wanting better image quality the alternative should use external x264/x265/vp9 encoder through Frameserver instead of Vegas internal templates for complex footage and sharpen.
For high motion gameplays in x264 one of most important settings for this type of footage is using good motion estimation settings. Higher values will retain better quality for fast moving content.