Note that (if things haven't changed considerably) x264vfw and Vegas2Handbrake are fundamentally using the x264 same codec under the hood and the equivalent settings should have the same effect. They're just wrapping the video in different containers. If you installed the latest versions of both today I'm not sure which would use the more recent version of x264. x264vfw used to use a pretty old version of x264 and was dismissed as a serious option when some of us were intensively testing H.264 codecs a few years ago (there were other issues with it that I don't recall right now). But it may well be a more valid option these days. If it does what you want (e.g. YouTube accepts it) then I see no reason not to use it. It's certainly convenient to render to from Vegas. When I'm back on a real computer I'll take a look at the change history and test out the latest versions of both.

As for bitrate, I just use constant quality and choose a crf value between 18 and 20 for all my YouTube uploads. If you're self-hosting a file or using a service that doesn't re-encode then it's more important not to be excessive with the bit rate and the Ben Waggoner x0.75 guideline in the article John linked to is worth bearing in mind.

I've tried tweaking the settings on handbrake by setting the constant quality rate to 18 on handbrake and still get some minor artifacting in the water surface, and when I do the render to avi using the x264vfw the artifacting is not there. I uploaded two short clips here to bypass youtube added compression.

http://bit.ly/1oJ6PpQ

Oddly enough, I created a side by side clip from these two clips with vegas with one side flipped horizontally so the problem areas would be right beside each other, then rendered it with the avi-h264 option and it removed the artifacting on the water surface from the mp4 clip created with vegas2handbrake. Unless my eyes are playing trick on me..

Those two clips are encoded with very different x264 encoder settings. One looks like it was encoded with a medium preset and the other looks more like the "very fast" setting. Also, one was encoded with an average bitrate setting and the other was a crf.

The AVI was ABR mode, 24Mbps, and no bframes but high profile.

The MP4/Handbrake(?) was crf=18, probably using the very fast preset and a very limiting VBV setting. I'm not sure how/why the VBV settings are in there given the use of CRF encoding mode. It looks like you may have used the Advanced tab in Handbrake and you probably should not. Just use the "video" tab. Unless you know what every x264 setting is and how to use it then don't use it. Just stick with the x264 presets. Most people probably stick to Fast, Medium (default) and Slow.

Here is a graph of the bit rate distribution for the two files:

Note: The scale is different for the two files.

I agree with NormanPCN that the encoding options setup for the two different encoders probably swamps out any differences between the encoders.

My guess is that the Handbrake H.264 Profile=Main, Level=4 is what's clamping the peak bit rate. Matching the H.264 Profile=High, Level=5.1 used in the other encoder really unleashes the peak bit rate at CQ=18. CQ=23 or 24 would probably come closer in terms of average and peak bit rates.

Build 211. I should point out, when it comes to rendering, these are 4k (3840x2160) projects, and the only option VP 14 is giving me for an mp4 output is Sony XAVC, and that does not have the choice of 24 fps.

I have no problem here with rendering 3840x2160-24.000p MainConcept AVC/MP4 in build 211. The 24.000 (Film) option is right there in the frame rate menu, and 3840x2160 can be typed in as a custom frame size.

I agree that true 24p would be a welcome addition to the XAVC encoder.

Hi, Nick. I went back to trying MainConcept AVC/MP4. As before, the best I could find was a 1080p preset, which did not allow me to pick any higher resolution and it did not allow me to edit the numbers themselves. Then I noticed something I had not noticed before, the option for custom frame size. I picked that and this time I was able to edit the numbers. I was also able to choose 24 fps. Great:

I clicked OK, then clicked Render, and, this thing popped up:

So much for that… But don’t worry, I do prefer going directly to Handbrake.

EDIT: Here is my system info if it helps:

I clicked OK, then clicked Render, and, this thing popped up...

...So much for that… But don’t worry, I do prefer going directly to Handbrake.

Could be lots of things causing that problem. Maybe the bitrate is just too high. Or maybe it's that "allow source to adjust frame size" box.

I prefer x264 too, although I've usually used MeGUI instead of Handbrake.

OK, I lowered the bitrate to the default, unticked allow source to adjust frame size, as well as frame rate, and I still get the same error message. I am mostly saying this so if someone from Magix sees this, maybe it will help them fix it.

Just stick with the x264 presets. Most people probably stick to Fast, Medium (default) and Slow.

I will also add. In handbrake or whatever, just set the level to Auto. Don't set a specific level. Let the encoder figure that out based on your other settings. Mostly the CRF setting.

In handbrake or whatever, just set the level to Auto.

How?

Encoder level control.

http://s28.postimg.org/qn2vok1ot/screenshot_123.jpg

Oh, OK. I never touch that section.

You might try Vegas2Handbrake (Section 4c in Nick's link). It usually uses the cores at or near 100% and produces equal or better output than the render options in Vegas Pro, particularly at very low bit rates.

I tried that, went through all the instructions. But when I finally clicked Send2Handbrake, I get an error message, 0x80131600 (message missing).

When I then click on details, it says,

C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu\frameserve_scripts\Send2HandBrake.js(19) : Variable 'Timecode' has not been declared
C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu\frameserve_scripts\Send2HandBrake.js(52) : Variable 'RenderStatus' has not been declared
 

So, what now? Of course, it might be the script is trying to import Sony.Vegas, which was probably changed in this version (14). Does anybody know to what?

EDIT: Never mind, I noticed the scripting FAQ, so the script is now working, but just running in circles because for some reason it cannot find the frame server.

Could you point me to the solution or the FAQ? I have the same issue - "Variable 'Timecode' has not been declared" (and "Variable 'RenderStatus' has not been declared").

The whole process works in Vegas Pro 13 and all is set up in Vegas Pro 14 - DebugMode is under "Render As", just when I click on the toolbutton to excute Send2Handbrake.js, I get the above error message.

Of course I have changed the second line in the Send2Handbrake.js according to the suggested 14 fixes ("import ScriptPortal.Vegas;").

Any suggestions?

Edit: Solved https://www.vegascreativesoftware.info/us/forum/vegas-pro-14-and-vegas2handbrake--103569/?page=3