[Marco Baer]

Yes, with limited functionality because Vegas Pro does not read the meta data and you’d need to install “Adobe DNG Codec” first.

[Marco Baer]

Actually I didn’t remove that certain page but my whole VegasVideo.de website is down since end of 2016 due to some server modifications which are not compatible with the CMS version I used for creating the site.

You could still access the page via a web archive:

https://web.archive.org/web/20161013201440/www.vegasvideo.de/vegas-2-handbrake-en

But you should know that the description and the linked files doesn’t take care of the changes made to the scripting language since Magix took over, also it is not modified for the use of the current HandBrake version. What you’ll find on the web page is meant for the use of the Sony branded versions of Vegas Pro 11 to 13 and HandBrake before version 1.0.

I had to stop updating Vegas2HandBrake because meanwhile there are too many variations of Vegas Pro and other tools involved with each would need own modifications. I once made this workflow for my own use only and my limited time does not allow anymore to trace each of the tools involved, doing the modifications needed and updating files and descriptions, sorry.

[Marco Baer]

That said, you should keep in mind Vegas’ chroma keyer is an extremely(!) basic chroma keyer and there’s kind of bug in it from its first day on. It is just impossible to affect certain single rgb colors without affecting the colors between.
For example you could use an EBU color bar and try to chroma key the blue bar only. But the magenta bar will always be affected, too, even if your mask would show white only for the blue bar.

[Marco Baer]

Seems like you used the given green preset instead of picking the real background color with the keyer’s eye dropper.

[Marco Baer]

Which version and which build of Vegas Pro do you use?

Did you check your rendered ProRes video inside Vegas Pro?

What does MediaInfo say about the properties of the rendered ProRes file?

Hope you are aware Vegas Pro can’t process GV HQX as 10 bit but will process as 8 bit instead.

[Marco Baer]

Same is for the project setting templates. For any frame size up to 4k you can set the fps to any value between 0,050 to 120,000 fps and save it as custom preset.

Updates are communicated via the “News” section of the official Vegas Creative Software forum. That’s been made for build 244 and today for build 252. Also it is planned to get update information via the Vegas Pro help menu soon.

[Marco Baer]

You didn’t tell us which render codec you selected, e.g. when I select MainConcept AVC I can type 30 fps while using UHD frame size and then save this UHD 30p template.

[Marco Baer]

I think neither SCS nor Magix sells Vegas Pro 13 anymore. Magix sells Vegas Pro 14 now.

When calling Magix sales support note the service times.

[Marco Baer]

I find Acrovid FootageStudio is a good converter at a reasonable price (demo version available). And CineForm VC-5 is another recommendable intermediate format (besides XDCAM HD).

[Marco Baer]

The $50 version does not have multicam capabilities. It’s the $80 version which also has (limited) multicam features.

Vegas Pro isn’t $800, but $600 (only the Vegas Pro Suite version is $800). And if one doesn’t need disc authoring Vegas Pro Edit for $400 will do fine.

There are many differences between Movie Studio and Vegas Pro. With the Pro versions for instance you’d get more tracks, more professional input and output formats, floating point based video processing, ACES/OCIO color base, scripting, extended multicam, extended plug-in support, extended external monitoring, extended external contols, remote control, loudness control, professional internal titling, masking, compositing, scopes – and many, many more features.
For the step from $80 to $400 there is much value packed in there.