Norman Black
Forum Replies Created
-
[John Rofrano] “Even the latest Vegas Pro 13.0 does not support rendering AVCHD 2.0 50p which is what your camera shoots.”
-
Vegas does not really degrade source video by simply editing. Where you lose quality is when you encode again. How much you lose depends on your encode settings.
Video encoding is not lossless unless you encode to uncompressed and those files are only good as intermediates. They are HUGE. All other encoding algorithms are lossy. Period. It has nothing to do with the editor and is all about compressing the file.
-
In your preferences you can clear option for, Close media files when not the active application.
This will save time since Vegas does not have to check and re-open all the files. The only time you need this option checked, is when you want to edit a file Vegas is using, without closing Vegas, and then come back to Vegas.
-
[Brett Bodi] “Now, why is XDCAM EX so much faster to render than others?”
Some encoders are faster than than others. XDCAM EX is mpeg-2 which is a simpler codec than AVC/H.264 which can be one reason it is faster. But some implementations are just faster. Sony AVC is faster than Mainconcept AVC when on CPU alone. Mainconcept can be a little higher quality. But then the x264 AVC encoder is faster than Sony and Mainconcept and higher quality at the same time. It is just a better encoder.
As for CPU verses GPU. Only the Sony and Mainconcept AVC encoders have GPU modes. However, your video is always composited/assembled during playback AND a final render as encode. The video prefs GPU option controls this GPU usage. So if GPU in video prefs helps your playback performance, then it will also help your “render as” encoding performance.
-
With either choice Vegas is going to have to do some resampling.
Which one do you have more clips of? Choosing this would minimize the amount of resampling done by Vegas.
What is your intended output target. 30 or 60p. You might choose that. 30p is always easier for Vegas to edit than 60p by a good margin so you should look at this unless you require a 60p output.
In “preview” preview window mode. Vegas always skips a full frame rate resample. This is as if you had “disable resample” checked on all events. This will be your quickest preview mode.
Disabling resampling on everything will speed preview and most people do not like the frame blending Vegas does anyway.
-
Vegas shows the file as interlaced because that is how it is encoded in the camera output file.
Your camera exposes and captures a full frame, as opposed to exposing and capturing two fields independently, which are interlaced.
The camera output only supports interlaced output because AVCHD 1.0 did not support progressive output in 1080. Only 60i.
Since 60i contains 30 frames per second they worked around this by splitting the full recorded frames into two interlaced fields and outputting that.
The real difference here is that when you deinterlace the file you get a perfect 30p out since that is how the video was recorded. Even in high motion scenes. You should always be able to use the Blend deinterlace mode without artifacts.
A true interlaced recording cannot be perfectly deinterlaced since each field is captured at a different point in time.
-
I forgot one thing. You can reduce the slices encoding parameter to 1. That will/can increase the compression efficiency of you encode from Vegas. Of course, if the encode already looks fine at 4 slices then it probably will not help.
-
Your project settings look fine. Your question about using “use project setting” or setting Best in the render template does not really mean anything in this context given that your project already has Best set.
The Internet 1080 HD setting should be fine for upload. The other setting you had with 50Mbps average and 135 Mbps max is really out of place.
I’ll quote my previous post.
If what you upload (the video) to Youtube does not go blocky or have problems and what you get back does have problems then you are having low bitrate problems.The real problem is probably that your video does not compress well enough to work at the Youtube encoded bitrates.
I previously suggested some things you can try to improve your situation.
Youtube 1080 bitrates are about 7-8Mbps. This means they re-encode everything you send them to their standard, regardless of what you upload. If you give them(Youtube) a “perfect” video, what you get back is not likely to be perfect due to them re-encoding. You can get the major blockiness you see if the video material is problematic for compression. As stated in previous posts.
Since the encoders in Vegas are not as good as the x264 encoder Youtube uses we typically pad our encoded bitrates a little higher to compensate. The Internet 1080 template is about 50% higher than Youtube bitrates which is most cases should be fine.
-
[Cedric Divang] ”
You said that x264 is the best codec for max quality at low bitrates, but I far as I know, it’s not available in Sony Vegas because of the GPL restrictions”I render an intermediate format and use Handbrake to use x264 for final low bitrate encodes.
XAVC-S and DNxHD are two formats that work well as an intermediate to Handbrake.
-
This is known. GPU based encoders, thus far, do not have the same encoding quality as purely CPU based encoders. They make compromises in quality for performance. The difference is typically only noticed at low bitrates which is what you are encoding to.
Note that when you select CPU or OpenCL/CUDA in Mainconcept, each one is a completely different encoder with different algorithms.
When it comes to max quality at low bitrates nothing really compares to the x264 encoder.
