[Norman Black]

Using x264 as their starting base to build the H.265 encoder seems to be a key to their possible success.

Of course due to it being GPL like x264, keeps Sony from including such an encoder directly in Vegas. It would be nice to use x264 directly from Vegas.

Of course if Sony published an encoder plug-in spec then someone(like m e) could write a wrapper for x264.

[Norman Black]

[John Rofrano] “Yea, but the problem is he wants 60p and MainConcept AVC doesn’t support this so the high bit rate doesn’t matter. :(“

Boy that’s silly. Not even 60p at 720 res. Silly since a video stream is just a series of frames. The frame rate is just a number stored in a file header for playback. So it is no work for an encoder to support any arbitrary frame rate.

I assumed the frame rate drop down would support that like other codecs. I have used 60p and 120p sources for slow mo but always rendered 30p projects for playback.

[Norman Black]

[John Rofrano] “If you want to archive the final version of your project try Sony MXF with the HD422 1920×1080-60i 50 Mbps template. That should be far superior to your original camera footage.”

I have found that my high bitrate GoPro Hero3 Black footage to lose the very fine detail with that high bitrate MPEG-2 format, compared to a similar high bitrate AVC output.

[Norman Black]

MainConcept AVC can render at very high bitrates. Sony AVC is limited to about 25-26Mbps.

[Norman Black]

Nothing in Vegas native AFAIK.

If you are using the Titles and Text generator then Vegasaur 1.9 has a new feature which lets you change text properties on multiple events.
https://vegasaur.com/Vegasaur

[Norman Black]

[Bruce Miller] “hanks. This is now the only place on the Internet where this secret information resides.”

My info came from the Vegas help file.

Bring up the help file.
In the index tab enter, A/B.
You now have a list of topics. The first one talks about A/B roll editing (track layers).
Open that help topic, and expand the track layers item.
The info is there.

I have “enabled” things in the past by accidentally hitting some keyboard shortcut I don’t know about. Fat fingering as I call it.
I searched the keyboard shortcut help page and did not find anything with a quick cursory search. I searched that help page for layer, A/B, expand, collapse.

As a new Vegas user I have found that the help file is pretty complete but not always easy to find info as the terminology I used in a search was not the exact term Vegas used.

[Norman Black]

Right click in the track header and choose, Expand track layers.
If not expanded it will expand.
If already expanded, a check mark will be on the menu item and selecting will collapse the layers.

The numeric 5 key, event edge and such are used with expanded edit mode in and out.

[Norman Black]

I agree with everyone here. The HD is the least of your worries.

Remember that video streams are 10s of mega bits per second and hard disks can easily handle 10s-100 of mega bytes per second (depending on seeks). Bits to bytes is an 8x difference already. So multiple simultaneous video streams are easily handled.

Also we typically don’t render in even real time so the effective video stream bitrate is much lower making the I/O demands lower.

[Norman Black]

>>just too many drivers and hardware combinations.
>>
>>I would bet if they went back to supporting the pro level cards >>only the same issues would not be happening….

Vegas uses OpenCL for GPU support. Driver and hardware independent.
The AVC encoders use OpenCL or CUDA depending. Driver and hardware independent. CUDA being Nvidia specific but hardware independent.

Assuming Vegas code is bug free, a very big assumption, the independent API means Vegas has no issue and all driver/hardware combinations are the problems of the driver developers and there is nothing Vegas can do about it. In other words there is nothing for Vegas to “support”. The point being that the OpenCL/CUDA compilers, and driver developers need to get their act together.

Valid OpenCL code is valid regardless of driver or hardware. This is the whole reason for encapsulation layers so you do not have to worry about “supporting” hardware.

“pro level” cards have used the same actual GPU core chips as the consumer cards, and therefore the drivers are substantially the same and as far as Vegas is concerned they are identical. OpenCL is OpenCL no matter what is running underneath. You can even run OpenCL on the CPU but Vegas does not allow that. That could be a useful differential diagnosis tool for GPU drivers issues verses a possible Vegas code bug.

The video driver guys are always trying to make their drivers faster and they tend to break things that were once working. AMD for example recently broke something in OpenGL (different than OpenCL, not a typo). This affects the NewBlue Titler. 13.4 broke this. 13.1 and earlier is fine.

[Norman Black]

A script is good for wholesale changes but also remember that you can set the resample option on any arbitrary selected events via the right click, switches, context menu.