[Wayne Waag]

I can’t understand a lot of the terms.

You’re not alone in this regard. My understanding is very limited as well. A good starting point is an article written by Glenn Chan comparing HD and SD color spaces. https://www.glennchan.info/articles/technical/hd-versus-sd-color-space/hd-versus-sd-color-space.htm In fact, there are quite a few very useful articles on his website regarding color space issues in Vegas.

Will you please help me understand why Channel Blend has so many boxes and how to use numbers with them?

Here is the Channel Blend filter for the 601 to 709 conversion.

In very general terms, the Channel Blend filter enables you make systematic changes to how colors will be displayed. Vegas works in a basic RGB color space, meaning that each pixel can be described as a combination of Red, Green, and Blue. If you open an image in Photoshop, it will display the RGB values which can range from 0 to 255 for the location of your cursor. Although Vegas doesn’t display these values, it uses them internally. The channel blend filter allows you to alter these. Very simplistically, e.g. in row 1, the red channel, the 601 to 709 conversion preset tells Vegas to reduce the red a bit, add a little green and a smidgeon of blue. For the green channel, we’re reducing the red, enhancing the green, and reducing the blue component. Since each channel has these RGB components, hence the need for all these boxes. Throw in transparency (alpha), and you’ve got a pretty large matrix of numbers.

In all honesty, I can’t imagine using this filter except for those color space conversions in which the coefficients have been mathematically determined. As stated earlier, I didn’t derive these coefficients, but found them in a search. Hopefully, someone with greater expertise can add or correct any misstatements I’ve made. The bottom line–I wouldn’t worry with this filter except if you have a need for color space conversions.

wwaag

[Wayne Waag]

Doesn’t the spec also support progressive at 1080 with 24 (23.76)fps?

wwaag

[Wayne Waag]

Glad it’s working. For your info, a 1080P TV automatically de-interlaces your 1080i footage and displays it as progressive. Hence, the designation 1080P. Doesn’t mean that your footage has to be 1080P. I must admit, it’s a bit confusing.

wwaag

[Wayne Waag]

Looks OK to me, but at this point, I’d recommend you get a re-writable disc and simply “try it”.

wwaag

[Wayne Waag]

How are editors getting their videos out so much quicker?

I suspect that most editors don’t do 5 hr videos. My beloved of over 40 years would call an attorney if I asked her to watch 5 hrs of anything. LOL. If rendering time is an issue, then get a faster computer or reduce the quality of your render or reduce the length of your video. Lots of options.

wwaag

[Wayne Waag]

Yeah em virtual dub can only render avi

Yeah, but what codec do you use? When you enter Ctrl-p, the “Select video compression” window appears. You have to make a choice. Which one do you choose?

I use Virtualdub all the time and prefer using lossless codecs such as MagicYUV, UT Video or Lagarith. You can also use codecs such as Cineform or Canopus that will work well in Vegas. Black previews have always been somewhat of a problem in Vegas when using avi files. I still get them on occasion. If you do, the best procedure is to simply save your project file, close it, and then re-open. Your “black events” should now display properly. One final suggestion. Before you render, ALWAYS save your project, close the project file, shut down Vegas and then re-open Vegas and your project file, especially if you are using avi files.

wwaag

[Wayne Waag]

Agree with Steve. I gave up on nested projects a long time ago as well. For one thing, they always dramatically increased the render time for me. Aside from rendering out an intermediate for each project as Steve suggested there are a couple of other options. If you have Vegasaur, you can stitch together individual projects for a final render using their Transcoder. Another option (the one I use most often) is to simply create a final project from your individual sub-projects by copying and pasting each sub-project into the final project. This does require a common track layout for your individual projects.

wwaag

[Wayne Waag]

No need to double post. See reply in other thread.

wwaag

[Wayne Waag]

You have inadvertently entered the “expanded track layers” mode. Right-click on the track properties box. You will see “Expand Track Layers” is checked. Simply click, the check should disappear and you should be back to a single track.

wwaag

[Wayne Waag]

Glad that your system is finally up and running.

What should I do if I want to use 2 different video-files at the same time?
For example a gopro 1080P 60 frames video and a 4K 24 frames Video.
Because of the different frames and different sony vegas settings it starts lagging again.

I’m not surprised that you are still experiencing preview lags with those disparate frame sizes and frame rates within the same project. My suggestion is to create proxies based on your final render settings. E.g. if your finally delivery is 1080 24P, then create a proxy with those settings for both types of footage using one of the formats suggested by Aaron. Your preview performance will now be the same, and you can revert back to the original footage for final render.

wwaag