I've released a utility, s3tots to unpack mpeg2 from series 3 TY files. Please see the support thread here: http://www.dealdatabase.com/forum/sh...ad.php?t=57574 for more information including source&binary.

This thread is for development related information concerning s3tots. I think it'd make sense to start this off with a bit of a comparison between old TY format and s3 (version 3) TY format. This basically means a comparison between mpeg2 transport stream vs program stream:

Series 1/2 conversion or playback solutions all required converting TY streams to mpeg2 program streams. This was the logical approach as series 1/2 TY streams most closely resembled program streams, furthermore media players as well as mpeg2 authoring programs work best with program streams.

Series 3 TY streams are structured much differently. More simply actually. Series 3 TY streams most closely resemble mpeg2 transport streams. In fact they are little more than a container format around transport streams. That container format assists PVR operations such as trick-play. Gone is any need to re-mux the streams as was necessary for series 1/2 (at least for those conversion methods that cared about generating spec compliant mpeg2).

What is an mpeg2 transport stream? It is a standard mpeg2 format, most suitable for transport of recordings across lossy media (such as your cable or satellite or antenna). mpeg2 transport stream files most commonly are denoted with the ".ts" file extension. Some archaic equipment such as the MyHD tuner instead use ".trp" to mean the same thing but that's an exception not the norm.

One of the chronic problems with series 1/2 mpeg files has been transmission errors. Most media players and authoring programs do not expect transmission errors from program streams. Many programs fail horribly when they hit such an error. Especially DVD authoring software. Some TY conversion tools have tried to fix up such errors with limited success. For problem cases, a separate fix up pass with a program such as videoredo has always been in order.

For transport streams, transmission errors are considered routine and so utilities that can read transport streams will likely better handle such errors.