[Steve Ulrich]

[Craig Seeman] “Transport streams can have overhead. Episode allows this kind of setting.”

Interesting…

[Craig Seeman] “Based on what? You haven’t provided any information that would indicate and certainly the settings don’t.”

Just based on what they usually do with these videos – and based on the music licensing that they are purchasing. Of course they might want to do something else with it later. I agree that the settings don’t indicate this. All part of my confusion.

[Craig Seeman] “I believe some programs do that. Do make sure you’re making a Transport and not a Program stream. If Squeeze uses .mpg you may need to experiment by sending the encode to the client. You could send both .mpg and renamed as .ts and ask if either or both work.”

Yup, definitely a transport stream. Episode sounds like it’s a lot more flexible than Squeeze. Might be worth the investment to switch over. At least I know I’ll never run into anything I can’t do anymore. I’ll try what you suggest concerning the extensions and post back with the results.. Appreciate greatly all of your valuable input Craig.

[Steve Ulrich]

Thanks again Craig. I do get that the MPEG TS is the container and H264 the codec – just throws me a little that they are asking for an MPEG TS @ 35Mbps and H.264 Video Size of 30Mbps. If the codec sits inside the container, that means there’s 5Mbps of other stuff floating around in there which I don’t really get – seeing how the audio wouldn’t make that up.

I read the Wikipedia link and it makes sense to me that a transport stream is used for unreliable transmission of video data via packets with adequate error correction. Also makes sense to use something like that for internet streaming – for the same reasons. It’s just that this video will for sure be reduced vastly in size and quality and played in a little box in the middle of a webpage – so it seemed to me to be an odd and very specific format to ask for if it was to be reduced and reconverted again later. Then again, why not…

I also finally found how to wrap H264 up in a transport stream in Squeeze – one has to pick either “Digital Signage” or “AVCHD” as the format constraints in an MPEG preset. But this saves a file with an mpg extension. Don’t know if you can just rename it or not.

In any case, thanks for your insight. I’m going to try to read up a bit more on this and see if I can’t come out of it a little bit smarter.

[Steve Ulrich]

Thanks very much Craig, for your suggestion. I’ll have a look at the Episode trial. I’ve used it before. Pro version is 1200 bucks though – ouch.

I’m definitely going to have to look into these types of formats though. I still don’t really understand what’s going here. With MPEG-2 and H.264 in the same file with 2 different bitrates.

Can anyone tell me what these formats are usually used for? Who wants a .TS file and why would you want it? I’m only delivering a 2 minute video for a website, so this seems extremely complicated for this type of usage. But perhaps it is a good as a sort of master file for archival purposes. In any case, the file I’m delivering is going to have to be transcoded for the web, for obvious size and data rate issues – which makes me wonder why they’re asking for it in the first place.

Thanks Craig for your answer and to anyone else who may want to share some experience with this sort of thing.

Steve