[Norman Black]

There is a button in the video media generator window/pane which matches the generated media length to the event length. The button is in the upper right corner.

[Norman Black]

I assume you are using Titles and Text.

You have event looping turned on.
Make the text event length match the media generenerator length.

If the generated media length is 2 seconds and you drag the event to 10 seconds and loop is on then it will repeat every two seconds. In this example if looping is off then the text generation will occur within its two second boundary and the last frame of the generated media will remain for the rest of the event time.

The animations in Titles and Text depending on the length of the generated media so to get the animation speed you are looking for you might need to play games with the generated media length and event length. You will want looping off if you do this.

[Norman Black]

Best varies in the eye of the beholder.

The easiest way would be to use the Vegas smart proxy feature.

If you want more control then using the proxy features of the Vegasaur or VASST Ultimate S utilities are pretty easy to use.

[Norman Black]

Maybe painting envelope points is a better term than writing points.

[Norman Black]

[Xavier Dolz] “Codec ID : mp42

File size : 591MB
Duration : 47min.
Overall bit rate mode : Variable
Overall bit rate : 1 737Kbps
Encoded date : UTC 2014-10-23 22:48:35
Tagged date : UTC 2014-10-24 00:09:27

Video
ID : 1

Format : tsc2

Codec ID : D0

Duration : 47min.”

The file container is MP4 and specifically version 2 of MP4. This is just the file container format.

The video format is using the codec tsc2. Looking this up is Techsmith screen capture codec 2. Vegas does not support this video codec.

[Norman Black]

There are a lot of critics out there. Almost none that actually “do”.

About multi-threading. Not all algorithms can be easily parallelized for multi-threading and some need excessive synchronization.

Speaking generally, image manipulation can be a very parallel implementation. Take a levels operation as an example. Every pixel is independent of the others and the pixels need no synchronization. Most effect like algorithms are like this.

About Vegas.
The decode operation of the source file is single threaded in Vegas. What this means is that if your CPU cannot decode a video stream in a single thread you will bottleneck. Commonly people have a 4-core hyperthread CPU so a single thread bottlenecks around 12-15% in your task manager.

With this the decode operation in Vegas will never saturate a 4-core CPU unless four video streams are being decoded. Note that a single crossfade on a track is two decode operations.

Effects. With GPU support disabled, Vegas will multi-thread for various effects. I have not checked which but I would suspect most all. I noticed this a while ago when I had to have GPU support disabled due to a conflict bug with an external plug-in. I heard my CPU fan crank up. Something I never hear with Vegas and GPU support turned on.

Which brings me to GPU. When GPU support is on, then the parallelism of the effects computations are done in the GPU and not in the CPU. In this case, if the GPU cannot keep full frame rate you will likely see the CPU utilization quite low. The CPU is really only doing video decode and you are bottlenecking in the GPU computations.

AMD GPUs seems to have the best performance with Vegas OpenCL effects.

Now you come to third party effects. Like NewBlue or Boris. Both of these use OpenGL for their GPU use. Vegas supports OpenGL mixed in with their OpenCL code but it may be causing some transition overhead.

Encoding a file: AKA “Render As”.
This is mostly a pure CPU operation, more cores always help, and every encoder will perform differently. File encoding is one of those things that is not very parallel. With compromises you can force the issue.

The AVC best encoder out there is x264 and I have seen some benchmarks showing that is scales very well from 4-core to 6-core. It starts to run out of scaling performance after 6. Still faster but not the same bang per core as 4 and 6.

The only GPU encoders are Mainconcept AVC and Sony AVC. Mainconcept AVC only supports older GPUs. Sony AVC does not use the GPU for much. Motion estimation only it seems as ME can be a parallel algorithm. Both these encoders have completely separate GPU options to turn their GPU use on/off.

Note that encoding the file and generating the video stream are separate so Vegas will still be using GPU for effects and compositing the video stream. Generation of the output video stream is always done. Both playback and encoding.

In summary:
So without GPU support enabled Vegas will use cores but best playback edit performance will come with GPU enabled and a good GPU.

You always want fast individual cores since the Vegas decode is single threaded.

For max encode performance you want more CPU cores. You still want a good GPU for the effects/composite engine but extra cores should help encoding/compressing part. Remember that each encoder is distinct and some will scale better than others with more cores.

I encode using frameserving to ffmpeg/x264. Faster than the Vegas AVC encoders and better quality.

[Norman Black]

This is what is known about the mode differences. There certainly can be other things we don’t know about that might be source specific.

Quality: Best
Scaling: bi-cubic with integration
Field Handling: on
Field Rendering: on (setting dependent)
Framerate Resample/IFR: on (switch dependent)

Quality: Good
Scaling: bi-linear
Field Handling: on
Field Rendering: on (setting dependent)
Framerate Resample/IFR: on (switch dependent)

Quality: Preview
Scaling: bi-linear
Field Handling: off
Field Rendering: off
Framerate Resample/IFR: off

Quality: Draft
Scaling: point sample
Field Handling: off
Field Rendering: off
Framerate Resample/IFR: off

[Norman Black]

[Michal Bronec] “When I used Sony Vegas 12, I need to adjust levels from computer RGB to studio RGB. It seems with Sony Vegas 13 I dont have to do it, because my videos looks same in Vegas, Youtube or WMP. Strange.”

I have noticed no difference in VP12 to VP13 with regards to levels and I do notice a difference if the videos are not encoded at Studio levels.

[Norman Black]

[Michal Bronec] “Another strange thing is – when I check or uncheck “adjust levels from studio RGB to computer RGB” in preview window of Vegas, nothing happens, there is no difference.”

This option only affects an external preview device. Not the preview window in the Vegas UI.

[Norman Black]

One thing you can try is to turn GPU support OFF in Video Prefs. Just get that question out of the way first.