Maybe you will find this helpful here:

https://www.vegascreativesoftware.info/us/forum/can-vegas-pro-output-mxf-op1a-mxf-opatom--128599/

Yes, from my old forum post, was wondering bout the video render, now Im clueless for the audio track,

the end result I should get 4 channels from what I've been told. All of the seniors editor are coming from Dr, Pr or FCPX. I'm the only editor that use VEGAS Pro.

The source audio im dealing is already 4channel.

So when I import to Resolve, it will create 4 audio track. Each track set to 1.0, which mean it is an Mono Track

upon rendering, simply tick render each channel per track and add 2 output stereo track.

In VEGAS, the closest thing is the channel setting via the render dialog box. Kinda clueless atm.

And in addition, maybe you find that format with the Sony MXF and Sony MXF HDCOM SR encoders. Here you receive MXF files, with OP-1a. However, if you want the 10bit, the bitrate seems to become higher then in the specifications (the bitrate of 50 Mbps was maybe for 8bit).

Not sure how that can be solved, since I have not seen that you can adjust the bitrate in those encoders.

So either you choose following encoder settings

results to

what seems to be the desired format (but with 8bit only)

OR

but results to that with 10bits, but higher data rates

So audio is not the only issue!!

So either you choose following encoder settings

results to

what seems to be the desired format (but with 8bit only)

 

OR

but results to that with 10bits, but higher data rates

So audio is not the only issue!!

how bout the audio? did u see the extra "channel" mapping in the render menu?

did the exported clip got 4 ch audio?

@alifftudm95

You might find this tutorial enlightening.

Multichannel Render Template in Vegas Pro (johnrofrano.com)

This is what one of my local broadcast station delivers.

Not what they require as input.

@alifftudm95

You might find this tutorial enlightening.

Multichannel Render Template in Vegas Pro (johnrofrano.com)

This is what one of my local broadcast station delivers.

Not what they require as input.

This is very helpful!

Now the dilemma I'm facing rn is I have to choose between High bit rate (well over 50mb/s as what stated in the spec sheet) for 10Bit color

Or

Proper 50mb/s bit rate with wrong 8 bit color

Now the dilemma I'm facing rn is I have to choose between High bit rate (well over 50mb/s as what stated in the spec sheet) for 10Bit color

Or

 

Proper 50mb/s bit rate with wrong 8 bit color

 

I think I mentioned that. While the solutions of the buses is great for the audio part, the more dramatic question is the question of 8 or 10bit. Seems to be an error in the specification - all what they have changed seems to be 8 bit to 10 bit in a chart. Vegas can both, but to keep the datarate exactly at the same level seems to be not foreseen.

I would contact the broadcast station, and ask for a clearification.

And: reading the historical documentations about xdcam - well: it was originally not 10bit format.

https://www.broadcaststore.com/pdf/model/809195/xdcam_xdcamex_prodbroch.pdf

https://pro.sony/s3/cms-static-content/uploadfile/15/1237494517315.pdf

So I wonder what they really want? The classical XDCAM, or a newer 10bit file - for HDR or whatever?

However, more modern camera systems like the FS7 were updated with XAVC-I codecs, using 10bit.

The media information you presented is what was recorded? What are the delivery specs for the TV station? I produce TV spots all the time in North America (NTSC as opposed to PAL) Where I am I deliver in an MXF 422 50 MBPS HD (1920 by 1080p) with close captioning and interlaced. The big thing is delivery specs. what are those?

After discussing with other senior editor and the production member, turns out the spec sheet provided by the station was wrong! "Typo error"

So yea, Sony MXF HD422, 25i is a correct render settings!

Thanks for the help @Wolfgang S. @john_dennis @Brian-Smith6937

Only thing left for me is to ensure my Audio Loudness is -23LUFS

Loudness is super easy with latest SoundForge pro. It's under normalize

Vegas has loudness meters. Should be easy to hit -23 with a bit of compression on peaks. I use plugins lile iZotope Nectar that are visually easy to understand.

@alifftudm95 said: "Only thing left for me is to ensure my Audio Loudness is -23LUFS".

Here's a very simplistic cheat sheet.

By simplistic, notice all the volume envelopes I added to deal with the shotgun blasts and other noises on a quiet October day in Georgia.

In a meanwhile, I was advice to use this plugin to increase "pass" QC for the audio. It can't be too consistant as they will reject it and seen it as "mono"

https://polyversemusic.com/products/wider/?fbclid=IwAR3xnMZAMyNOmZJK9BBvTYNxYUA5g1Kgy_zBcjEfMyqlFdb2tBecQhd5UEE

After installing this plug, it showed up in Resolve VST, but not in VEGAS?

Hint: -23LKFS ATSC/A85 also conforms with -23LUFS EBU/R28, but not necessarily the other way around.

My go-to Limiter/Compressor with calibrated Loudness scales is the unmatched Toneboosters Barricade. You can use it in Demo mode, and there is actually a free version, but you have to hunt for it.

Note: This particular example was normalized to -15LUFS for Streaming, not -23LUFS for Broadcast delivery.

The tiny bit of distortion in my orchestra mix at 1:25 is in the recording, not the processing. I conducted it in 2007.

In a meanwhile, I was advice to use this plugin to increase "pass" QC for the audio. It can't be too consistant as they will reject it and seen it as "mono"

https://polyversemusic.com/products/wider/?fbclid=IwAR3xnMZAMyNOmZJK9BBvTYNxYUA5g1Kgy_zBcjEfMyqlFdb2tBecQhd5UEE

After installing this plug, it showed up in Resolve VST, but not in VEGAS?

Manage to resolve dis with locating the VST2 path.

Hint: -23LKFS ATSC/A85 also conforms with -23LUFS EBU/R28, but not necessarily the other way around.

My go-to Limiter/Compressor with calibrated Loudness scales is the unmatched Toneboosters Barricade. You can use it in Demo mode, and there is actually a free version, but you have to hunt for it.

The bit of distortion in my orchestra mix at 1:25 is in the recording, not the processing. I conducted it in 2007.

Dis is nice to have

After discussing with other senior editor and the production member, turns out the spec sheet provided by the station was wrong! "Typo error"

The broadcast station has done that for the first time? And never corrected the wrong charts? Unbelievable!

Auto GOP and VBR often can result in non compliance and rejection.

For a quick loudness read-out of entire program, I use Sound Forge Pro's "Statistics" process which can analyze a one-hour program in about one minute. The factors can also be saved to the clipboard to print or otherwise document. It does not change the loudness though. The (LUFS) 'Integrated' (entire program) and (dBTP) 'True peak' are the most important for b'cast submissions. If not, your submission will likely be rejected (and you will be shamed).