Oh, so Vegas can't do the simple thing I need. Well I guess that explains why there is zero mention of a how to, literally anywhere online. I can't possibly be the only one that wants to do this simple thing. And I am aware that Voukoder can render what I want out of Vegas, but I didn't know it was my only valid option. Voukoder doe not seem to be using my GPU and takes an eternity! All I want is a finished video, not a transport format, so pro res is not an option for me. Well, this has turned out to be one of those days, but thanks for the info.

@t3t4

The Render+ tool in HappyOtterScripts supports 10bit 422 renders using the x264 avc encoder. Here's a screen grab of the encoder settings dialog.

and the resulting media info of a rendered file. For the demo, I used some 10bit 422 footage from a Canon MarkIII.

All 10bit renders from Vegas are slow since you should be using a 32bit pixel format. Additionally, 10bit renders using HOS also requires the CuminCoder FrameServer which also supports 10bit, unlike the older DebugMode FrameServer which is 8bit only.

You can find more information at https://tools4vegas.com/

@wwaag

Thanks, that looks like very capable software. It just annoys me to no end that I need a 3rd party tool to do this simple job. Vegas should have this capability already baked in, but thanks for the info.

@t3t4, you are missing the basic knowledge of motion pictures.

VEGAS Pro is an unique NLE toward producing industrial standard videos, which have the final definition with 4:2:0/8bit in Rec709 and 4:2:0/10bit in Rec2020 (including HLG/HDR10 productions).

Furthermore, VEGAS Pro can output intermediate clips from 4:2:0 to 4:4:4 in both 8bit and 10bit depth.

What a source material with which quality you do have,theoretically, has nothing to do with VEGAS Pro.

@Yelandkeil

If it can read it and otherwise edit it, then it should be able to render it, simple as that! To trans-code a 9 GB MP4 file into a 60 GB pro res file is ludicrous and makes no sense. I'm new to 422 recording and/or editing, but I gotta find a way to do it with original quality results in a reasonable amount of rendering time and with realistic file sizes.

That's another basic knowledge.

If camcorder can record with lossless codec, it will kick out the HEVC or what else you call, and your source material would be perhaps 90GB instead of 9GB.

You gotta find a way to do it with original quality results? Don't trust your eyes but monitor instruments - OK, that's another story again.

Thanks.

ProRes output is 10 bit and up to 4:4:4.

... To trans-code a 9 GB MP4 file into a 60 GB pro res file is ludicrous and makes no sense. I'm new to 422 recording and/or editing, but I gotta find a way to do it with original quality results in a reasonable amount of rendering time and with realistic file sizes.

@t3t4 That's one reason I avoid ProRes myself. Another reason is that most of my cameras have single CCD sensors which physically capture raw 420 data and debayering to 422 or 444 just bloats the clips up even more with artificial fluff. I do have a couple older triple CCD Canon cameras that can capture actual 444 and save as 422 mxf clips. But they only do hd. And the color in 10-bit hevc clips from my 4k single ccd 420 camera looks noticeably better and is easier to work with... if your camera can shoot 10-bit 420 hevc and your workstation is powerful enough to handle it, I suggest you give that a try. Otherwise, just get larger storage and work media and go with ProRes... many folks with various cameras are capturing ProRes 422 via hdmi to sata ssd using a NinjaV and keeping it in that format for edit. Personally, I prefer more compact and efficient 10-bit hevc 420.

@Howard-Vigorita

I'd be a real happy camper if I could just render out 10 bit 422 in HEVC, but 420 is my only option in Vegas with that codec. My camera (Panasonic G9) records internally 10 bit 422 @ 150 Mbs in a .MOV wrapper. I mean it's already an MP4 and Vegas can read/edit those files all day long no problem. But it can't render out the same codec or quality? I just can't seem to wrap my head around that. I'd love to have a Ninja if for no other reason than to finally be able to see a screen on my camera. All these built in screens are way too small, or I'm too blind.... But I'd still have the same problem with Vegas not being able to render an MP4 in 422.

So it looks like my only real choice is to learn a 3rd party way of doing the job in a reasonable amount of time. I have a decent computer regarding the hardware, and Voukoder seems to do what I want, but 17+ minutes of rendering time for every 1 minute of actual video is a price I'm not wiling to pay! Clearly I have to ease some settings somewhere and learn to live with it, but I know me and it's still just gonna annoy and keep me up at night.

Anyway, thanks for the info.

Cheers.

Somebody upoaded this sample clip for testing.

In VEGASpro19, my machine can play with less than 1fps even in Good/Quarter previewmodus.

I transcoded it into ProRes 422Lite and got full play speed, i.e. I can edit it in a practical way.

Till now I have very positive experience with ProRes-codec.

I transcode using the free XMedia Recode.

PS: the Sony XAVC-Intra-codec in MXF wrapper is another good intermediate.

I don't use it because it cannot handle with HDR10-info.

@Howard-Vigorita

I'd be a real happy camper if I could just render out 10 bit 422 in HEVC, but 420 is my only option in Vegas with that codec.

So it looks like my only real choice is to learn a 3rd party way of doing the job in a reasonable amount of time. I have a decent computer regarding the hardware, and Voukoder seems to do what I want, but 17+ minutes of rendering time for every 1 minute of actual video is a price I'm not wiling to pay!

What computer do you have? I tried this 2m:30 sec for 1 minute of 422 10bit 4k source encoded to HEVC 422 10bit via voukoder. This is at 30fps, so 5min for a 60fps project. The other thing that I discovered is that voukoder does this at the same speed that MagixHEVC (software encode) does for 420 10bit, so then I discovered what you're saying makes no sense.

The conclusion I come to is you are encoding via Hardware (Nvenc etc) when you use MagixHEVC, and software(CPU) encoding using voukoder. It should be obvious by the way your computer reacts and what your Task Manager displays that's there's 2 difference mechanisms of encoding going on

What you want is hardware encode of 422 HEVC 10bit, you don't get that with AMD or Nvidia GPU, you may get that with the higher end 11 and 12 series intel CPU's @Howard-Vigorita does your 11 series Intel cpu hardware encode to HEVC 422 10bit?

What you want is hardware encode of 422 HEVC 10bit, you don't get that with AMD or Nvidia GPU, you may get that with the higher end 11 and 12 series intel CPU's @Howard-Vigorita does your 11 series Intel cpu hardware encode to HEVC 422 10bit?

@Former user I think the Iris and hd750 Intel igpus only decode 422 10-bit. But Nvidia can encode 444. Just tried it with Vokouder 10.1 setting codec to "HEVC (Nvidia Nvenc)" on the encoder tab and then setting bit depth to "YUV 4:4:4 (10-bit)" on the options tab. Was able to view the output with mpc-be and load it to the Vegas timeline. Should be faster than a cpu-only x265 422 encode but probably a bigger file.

@Former user

What computer do you have? I tried this 2m:30 sec for 1 minute of 422 10bit 4k source encoded to HEVC 422 10bit via voukoder. This is at 30fps, so 5min for a 60fps project. The other thing that I discovered is that voukoder does this at the same speed that MagixHEVC (software encode) does for 420 10bit, so then I discovered what you're saying makes no sense.

The Computer does not matter, I've already stated that Voukoder does not seem to be using all of it. Just as I have already said that I must ease some settings to accomplish my task. Look folks, I appreciate the help that I asked for, and the answer has been clearly given that Vegas simply cannot do on it's own what I/we need it to do. 3rd party tools are required to get the got done. As disappointed as I am, that is the answer to my question.

Thank you all.

Cheers 🍻.

I am curious, what is the intent of this workflow? AKAIK, 422 HEVC is primarily a high compression camera format, not intended for use as an intermediate or as a delivery format. It is "lossy" so a render will lose quality - but maybe not noticeably.

Put another way, who will watch the end result, and on what devices?

Put another way, who will watch the end result, and on what devices?

If it's MP4 which is the standard delivery format for the internet and beyond, then anybody can watch it on any device. What is this?: AKAIK

Sorry, typo.... AFAIK = as far as I know. Sure, 8 bit 420 in an mp4 container is standard, but 10 bit 422 is not, is it?

Sure, 8 bit 420 in an mp4 container is standard, but 10 bit 422 is not, is it?

Not yet, but more and more cameras are internally recording 422, it's about time for the rest of the world to get up to speed so it can handle the new information. The alternative is to record 422 and render 420. This seems the most feasible choice for most. Not my choice mind you, but still realistically feasible.

Sure. Cellphones with dedicated ASIC's for decoding these formats seem to push the ball forward fastest. It is a bit "bleeding edge" for NLE's (Resolve won't render 10 bit 422 HEVC and I guess PPro won't either) and of course encoding with hardware support is limited (not NVIDIA or AMD but maybe latest intel QSV might?) so performance is likely poor.

The Computer does not matter, I've already stated that Voukoder does not seem to be using all of it.

@t3t4 It matters allot. If you had an Intel igpu you could decode 422 hevc in hardware which would speed up any subsequent renders. And if you had an Nvidia gpu you could do an accelerated 444 render with Voukoder and see for yourself if you can perceive the difference compared to rendering to 420. I predict you cannot. Because your camera sensor only captures 420 and upscaling it to 422 so early in the processing chain is probably just a waste of time, space, and subsequent processing effort. 420 and 422 get upscaled to 444 right before viewing anyway.

You'd have a better chance of seeing the difference if you had a super-expensive beam splitting triple-ccd 4k camera which would at least capture 3 chroma elements for every pixel. But having evolved on a green planet, you might still not be able to perceive the difference.

 

The Computer does not matter, I've already stated that Voukoder does not seem to be using all of it.

Ofcourse it's using less of your GPU due to the latency of software encoding, your computer takes 17minutes to encode for every 1min of video, so your GPU is being handed frames to process at an exceedingly slow rate. A hardware encoder that you used for 420 10bit HEVC is fast enough that your low spec CPU and GPU can work as hard as possible (within the coding limits of Vegas) because at 4K most hardware encoders will allow you to encode at a minimum of 60fps if not faster, the limiting factor becomes your cpu and gpu not the encoder

Just as I have already said that I must ease some settings to accomplish my task. Look folks, I appreciate the help that I asked for, and the answer has been clearly given that Vegas simply cannot do on it's own what I/we need it to do. 3rd party tools are required to get the got done.

You were complaining about that to begin with but then you moved over to complain about voukoder being too slow, and I explained why this is.

If you've realized there's no point to 422 10 HEVC encodes because you don't want to software encode due to slowness then choice is go back to 420 10 HEVC where with the help of a hardware GPU encoder(and decoder) or hardware encode to 444 10BIT HEVC via voukoder.

Files will be a bit larger, and take a little longer to enode but much faster then software encode. There may be compatibility problems as I can't load 444 10bit HEVC into Vegas , Loads into premiere but no GPU decode, loads into Resolve fine with GPU decode. Won't work with VLC or MediaPlayer, will work with MediaPlayerClassic but not GPU decode. Looks like the world isn't ready for 444 10bit HEVC just yet but you could try it via voukoder the way @Howard-Vigorita described above to see if it's for you

Like I said folks, my PC is irrelevant when the software can't use all of it regardless of your tutelage or wishful thinking. Makin noise for the sake of, is still just makin noise!