Final encoding for broadcast TV?

Matthias-Claflin wrote on 12/7/2018, 9:33 AM

I'm going to attach the spec sheet I was given by Comcast for delivery. I'm wondering what codec I should use in Vegas. The reason I am asking is because when I export form Vegas via my normal methods (HEVC or AVC) I can't export to an acceptable audio stream (either MPEG-1 Layer 2 or LPCM) so should I use the "Video For Windows" and deliver in 1080i (since they only allow 1080i or 720p) and use the Sony YUV encoding? I honestly am not sure what settings in Vegas are best for the spec sheet they gave me. I've never had to work with broadcast codecs before (everything has been for internet thus far). Any help would be much appreciated.

Comments

Former user wrote on 12/7/2018, 9:46 AM

None of those mention AVI or VFW. Use the MPEG2 encoding with the MPEG audio that can be rendered with the file.

 

Matthias-Claflin wrote on 12/7/2018, 9:56 AM

Would I get a higher quality file from say using Vegas to go to an intermediate codec and rendering it in Adobe Media Encoder (which I still have access to) to Avid DNxHD or is that not going to provide a noticeable quality difference?

OldSmoke wrote on 12/7/2018, 10:49 AM

What is your source like? I personally find 720 60p superior to 1080i but I guess it depends on how Comcast broadcast the video.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

john_dennis wrote on 12/7/2018, 11:01 AM

If your source is 1920x1080 or above and you have Vegas 14 or higher, you could use Magix ProRes with one customization to the template. That would allow you to keep uncompressed audio.

Under Notes:

Turd wrote on 12/7/2018, 11:11 AM

I know this doesn't exactly contribute to an answer...

I'm surprised .xmf isn't an option for you. Most TV stations use that format natively in their master control and even "flip" all other formats to .mxf with eight audio channels (LF, RF, C, LFE, SL, SR, SAPL, SAPR respectively) for playout.

Vegas Pro plays very nice with .mxf files importing and rendering. You might want to inquire Comcast about that.

Last changed by Turd on 12/7/2018, 11:11 AM, changed a total of 1 times.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis. All joking aside, listing my computer's properties is a futile endeavor. I edit multimedia in a local television station newsroom that has Vegas Pro installed on several machines with widely varied specs. We began editing non-linearly with Pinnacle Studio Version 8. That didn't last long before we upgraded to Vegas Video Version 4, then to Vegas Pro 10.

Musicvid wrote on 12/7/2018, 11:19 AM

Do you know that there are several proprietary flavors of MXF?

Unless the broadcaster specifically lists Sony mxf, it won't work. I have never seen that option listed as a broadcast format.

[I see now that this comment was unnecessarily confusing. My intention is only to point out that the because some .mxf formats such as xdcam hd are supported does not mean all .mxf container formats are, not by a mile. See below.]

ProRes is your go-to option for this project.

NickHope wrote on 12/7/2018, 11:39 AM

Note that the MAGIX ProRes encoder is called "MAGIX Intermediate" since VP15. It's not an Apple-certified encoder but that doesn't mean you shouldn't use it.

Musicvid wrote on 12/7/2018, 11:43 AM

It's also the most universal broadcast stream next to mpeg-2 TS, which has horrible layer II audio.

Turd wrote on 12/7/2018, 11:50 AM

Do you know that there are several proprietary flavors of MXF?

Unless the broadcaster specifically lists Sony mxf, it won't work. I have never seen that option listed as a broadcast format.

ProRes is your go-to option for this project.

I'm the Chief Engineer at a full power TV station. I exchange .mxf files often with other stations and I've never had one come back as long as I adhere to their specs. I only suggest .mxf as something to look into for a possible option since I find that format quite universal in the broadcast world.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis. All joking aside, listing my computer's properties is a futile endeavor. I edit multimedia in a local television station newsroom that has Vegas Pro installed on several machines with widely varied specs. We began editing non-linearly with Pinnacle Studio Version 8. That didn't last long before we upgraded to Vegas Video Version 4, then to Vegas Pro 10.

Marco. wrote on 12/7/2018, 11:55 AM

Same here around where MXF XDCAM HD is by far the most common type delivered for broadcasting.

rraud wrote on 12/7/2018, 12:00 PM

Those audio specs are antiquated. All b'cast submission specs I've encountered in the last five years or so are ATSC A/85 or EBU R128. That said, give Comcast/Xfinity what they want. Typically, -20 dBFS is the reference level via a 1k Hz calibration tone and making sure program audio peaks do not exceed -10 dBFS was common prior to DTV. I would not submit a multi-channel mix either, (L-R dual mono or stereo is the safest). The idiots I've encountered at local cable TV stations could f_ck up a free lunch.

john_dennis wrote on 12/7/2018, 12:14 PM

Oops! Completely forgot XDCAM as the spec sheet listed MPEG-1 Layer 2 Audio for MPEG-2 Transport Streams.

OldSmoke wrote on 12/7/2018, 12:31 PM

Oops! Completely forgot XDCAM as the spec sheet listed MPEG-1 Layer 2 Audio for MPEG-2 Transport Streams.

720 59.94p would have been my choice depending on the content; fast and easy to encode.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Former user wrote on 12/7/2018, 1:12 PM

A high bitrate MPEG will look great, will render fast, no intermediate and is on the list of their accepted formats. Why try anything else? I don't understand the confusion.

Turd wrote on 12/7/2018, 1:46 PM

A high bitrate MPEG will look great, will render fast, no intermediate and is on the list of their accepted formats. Why try anything else? I don't understand the confusion.

The reasons I brought up .mxf at all are three-fold:

1.) If .mxf is, in fact, Comcast's native master control file format you might be doing them a favor by not forcing them to be a middleman and "flip" the file;

2.) Your file would look better technically because it won't be transcoded;

3.) .mxf is easy to work with and it's a format that plays nicely with Vegas.

To rraud: There was a time I would have agreed with you about multichannel audio being easy to mess up. Today, however, the norm is an easy direct file transfer to the playout system and making sure the file hits all the checkmarks for quality control and timing. They don't fiddle with settings anymore. As long as you follow the broadcast standard: Channel 1: Left Front, Channel 2: Right Front, Channel 3: Center, Channel 4: LFE, Channel 5: Left Surround, Channel 6: Right Surround, Channel 7: SAP Left, Channel 8: SAP Right, Matthias-Claflin should be good to go. That's exactly how multichannel network programming is sent.

The only question in my mind is, does Comcast accept .mxf? I wouldn't be surprised if they do, and that would end up being a long-term plus for everyone.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis. All joking aside, listing my computer's properties is a futile endeavor. I edit multimedia in a local television station newsroom that has Vegas Pro installed on several machines with widely varied specs. We began editing non-linearly with Pinnacle Studio Version 8. That didn't last long before we upgraded to Vegas Video Version 4, then to Vegas Pro 10.

Musicvid wrote on 12/7/2018, 1:54 PM

Oops! Completely forgot XDCAM as the spec sheet listed MPEG-1 Layer 2 Audio for MPEG-2 Transport Streams.

+1

Also, I don't believe xdcam is an mpeg-2 transport stream, which is short GOP.

Former user wrote on 12/7/2018, 1:55 PM

Turd, I agree with your reasoning but you are suggesting that he provide a file that does not meet their specs. Maybe they do, maybe they don't but it isn't what they are asking for.

 

Musicvid wrote on 12/7/2018, 2:01 PM

MXF is a container, not a format. As such, it can contain any number of formats.

One such .mxf format is called xdcam. It is not short GOP Mpeg-2 TS. It does not support legacy layer II audio. Several of the other .mxf formats will never see a broadcast control room.

https://en.m.wikipedia.org/wiki/Material_Exchange_Format

Rather than continuing to dish us codec salad, please specify the format, not the container, and preferably one that meets the poster's requirements.

All together now, MOV is a container. ProRes is a format.

Jabberwocky.

 

Turd wrote on 12/7/2018, 2:10 PM

david-tu & Musicvid:

I don't suggest at all that Matthias-Claflin simply supply an .mxf file and be done with it. I suggest he (or she -- I don't want to assume) inquire about that format as a possibility, then act accordingly.

You're very correct in saying .mxf is a container. Admittedly, I use the word "format" as too broad a brushstroke, but If Comcast accepts .mxf files, as I suspect they do, the specs they provide would determine the flavor therein.

Last changed by Turd on 12/7/2018, 2:35 PM, changed a total of 1 times.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis. All joking aside, listing my computer's properties is a futile endeavor. I edit multimedia in a local television station newsroom that has Vegas Pro installed on several machines with widely varied specs. We began editing non-linearly with Pinnacle Studio Version 8. That didn't last long before we upgraded to Vegas Video Version 4, then to Vegas Pro 10.

Musicvid wrote on 12/7/2018, 3:10 PM

but If Comcast accepts .mxf files, as I suspect they do, the specs they provide would determine the flavor therein.

Since the specs the OP posted do not suggest that, and since you seem interested in the discussion, why not end all the background discussion and see if Comcast does in fact, support your suspicion by seeking out and posting updated format submission specs for your as-yet unspecified .mxf format?

Personally, I have no interest except for accuracy and compliance, not necessarily for Comcast.

Turd wrote on 12/7/2018, 3:59 PM

but If Comcast accepts .mxf files, as I suspect they do, the specs they provide would determine the flavor therein.

Since the specs the OP posted do not suggest that, and since you seem interested in the discussion, why not end all the background discussion and see if Comcast does in fact, support your suspicion by seeking out and posting updated format submission specs for your as-yet unspecified .mxf format?

Personally, I have no interest except for accuracy and compliance, not necessarily for Comcast.

I feel as though you believe I'm trying to hammer my suggestion -- which I'm honestly not trying to do. I just want to help someone who's asking for assistance to which I believe I can provide. I think it'd be a worthwhile endeavor for Matthias-Claflin to find out if Comcast accepts a newer industry standard, and I provided the reasons above. Perhaps the specs provided by Comcast haven't been updated to show .mxf is now allowed or, perhaps, even preferred.

.mxf is now a broadcast industry standard file, but the .mxf format contained within -- and I'm using the word correctly here -- has no broadcast industry standard that I'm aware of. I've been asked to send a variety of .mxf formats in my broadcast line of work. The .mxf format completely depends on recipient's needs -- and my experience is they're always easy to comply with in Vegas Pro. I don't have a contact at Comcast. Matthias-Claflin obviously does. It'd be quick and easy for Matthias-Claflin to ask Comcast about .mxf, and the ramifications from that simple question could result in long-term harmony between Matthias-Claflin and Comcast to the benefit of both.

It doesn't matter to me if my suspicion is correct or if Matthias-Claflin follows through with my suggestion. I just want to provide some possible assistance based on my experience.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis. All joking aside, listing my computer's properties is a futile endeavor. I edit multimedia in a local television station newsroom that has Vegas Pro installed on several machines with widely varied specs. We began editing non-linearly with Pinnacle Studio Version 8. That didn't last long before we upgraded to Vegas Video Version 4, then to Vegas Pro 10.

Musicvid wrote on 12/7/2018, 4:06 PM

The philosophical difference being whether to offer the suggestion speculatively or prevalidated by the literature or duplicable testing.

I've been caught more than once doing the former, yet I understand it is quite a popular social media style these days.

Musicvid wrote on 12/7/2018, 4:26 PM

This should lay the discussion to rest. The updated format spec is -- ProRes MOV 422 / PCM.

http://www.studiodaily.com/2018/02/new-file-delivery-specs-ad-content-set-tv-convergence-working-group/

Thanks for sharing your perspectives

Former user wrote on 12/7/2018, 9:57 PM

If I sent someone a spec sheet and they called and asked about it,I would reply "Did you get the specs?". If they asked about alternative formats I would reply "Did you get the specs?".